Component J: A component-based programming language with dynamic reconfiguration

Seco, João Costa; Silva, Ricardo; Piriquito, Margarida

doi:10.2298/csis0802063s

Cited by 14 publications

(10 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Reification and reflection are not explicitly advocated in ComponentJ [14]. However, it appears that a running system certainly has a partial representation of itself to allow for dynamic reconfiguration of components internal architectures as described in [14] but it seems to be a localized and ad.hoc capability, the reification process being neither explicited nor generalized as in our proposal.…”

Section: Prototype Implementationmentioning

confidence: 87%

“…However, it appears that a running system certainly has a partial representation of itself to allow for dynamic reconfiguration of components internal architectures as described in [14] but it seems to be a localized and ad.hoc capability, the reification process being neither explicited nor generalized as in our proposal. This makes architecture reasoning, constraints and transformations difficult to implement.…”

Section: Prototype Implementationmentioning

confidence: 88%

See 1 more Smart Citation

Wringing out objects for programming and modeling component-based systems

Špaček

Dony

Tibermacine

et al. 2013

Proceedings of the Second International Workshop on Combined Object-Oriented Modelling and Programming Languages

View full text Add to dashboard Cite

Languages and technologies used to implement componentbased software are not component-based, i.e. while the design phase happens in the component world, the programming phase occurs in the object-oriented world. When an object-oriented language is used for the programming stage, then the original component-based design vanish, because component concepts like requirements and architectures are not treated explicitly. This makes it difficult to keep model and its implementation causally connected. We present a new pure reflective component-based programming and modeling language where all core component concepts are treated explicitly and therefore keeping original componentdesign alive. The language makes it possible to model and program component-based software using the same language plus its uniform component-based meta-model and integrated reflection capabilities make the language and its applications open and flexible.

show abstract

Section: Prototype Implementationmentioning

confidence: 87%

Section: Prototype Implementationmentioning

confidence: 88%

Wringing out objects for programming and modeling component-based systems

Špaček

Dony

Tibermacine

et al. 2013

Proceedings of the Second International Workshop on Combined Object-Oriented Modelling and Programming Languages

View full text Add to dashboard Cite

show abstract

“…ComponentJ [27] is a Java-like programming language with basic idea to be used as a glue language for existing components that are afterwards used in standard Java code. ArchJava [2] is used for expressing software architectural structure thus it provides the confirmation for implementation of the specified architecture at every stage of the software lifecycle.…”

Section: Related Workmentioning

confidence: 99%

An Analysis of Some Aspects of Component-Based Programming for Selecting Appropriate Categorical Structures as their Models

Steingartner¹,

Radaković²,

Novitzká³

et al. 2017

AEI

View full text Add to dashboard Cite

Formal methods and formal models are important tools in software engineering. Formal methods provide unambiguous meaning of programs written in some language or constructed from modules. Moreover, they provide the basic mathematical techniques necessary for those who are working with theoretical background in computer science. Categories are interesting mathematical structures which have become important for constructing the models of programs and program systems. In this paper we formulate an introductory analysis of some aspects of component-based programming for selecting appropriate categorical structures as their models.

show abstract

“…Another interesting approach covered by the literature refers to the use of DomainSpecific Languages (DSL), which provide a domain-oriented notation for building application. In this context, a category of DSL, such as ArchJava [1] or ComponentJ [20], deals with component-oriented programming and propose to merge architectural description with component implementations by specializing the Java programming language with CBSE keywords. However, the definition of these keywords remains hardcoded within the grammar and cannot be further extended.…”

Section: Related Workmentioning

confidence: 99%

Rapid prototyping of domain-specific architecture languages

Rouvoy

Merle

2012

Proceedings of the 15th ACM SIGSOFT Symposium on Component Based Software Engineering

View full text Add to dashboard Cite

Software architecture has become a sensitive discipline, which consists in concretizing the user requirements into a set of artifacts that can be used to model and reason about the software to be developed. However, the architect often relies on its own knowledge to map domain-specific requirements onto generic software abstractions. Most of the time, this leads to the definition of repetitive tasks and architecture fragments, which can be particularly error prone. We therefore believe that architects need a more flexible approach to cope with the definition of domain-specific architectures by leveraging general purpose architecture description languages. This paper introduces the FraSCAla framework as an adaptive architectural framework that can be used to rapidly prototype and experiment domain-specific ADLs in order to catalyze the definition and to improve the reliability of software architectures. We demonstrate the merits of this approach on two representative architectural patterns of component-based software architectures.

show abstract

Component J: A component-based programming language with dynamic reconfiguration

Cited by 14 publications

References 9 publications

Wringing out objects for programming and modeling component-based systems

Wringing out objects for programming and modeling component-based systems

An Analysis of Some Aspects of Component-Based Programming for Selecting Appropriate Categorical Structures as their Models

Rapid prototyping of domain-specific architecture languages

Contact Info

Product

Resources

About