Using object-oriented typing to support architectural design in the C2 style

Medvidović, Nenad; Oreizy, Peyman; Robbins, Jason E.; Taylor, Richard N.

doi:10.1145/250707.239106

Cited by 49 publications

(61 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…On the contrary, most work on reliability and validation for component-based architectures deal with Architecture Description Languages [6,7] only include static validations and do not support unanticipated reconfigurations. Recent component models, like FORMAware [8] and Plastik [9], rely on reflexive architectures to allow unanticipated reconfigurations while supporting some kinds of guarantees checked at runtime.…”

Section: Discussionmentioning

confidence: 99%

A Multi-stage Approach for Reliable Dynamic Reconfigurations of Component-Based Systems

David¹,

Léger²,

Grall³

et al. 2008

Distributed Applications and Interoperable Systems

View full text Add to dashboard Cite

Abstract. In this paper we present an end-to-end solution to define and execute reliable dynamic reconfigurations of open component-based systems while guaranteeing their continuity of service. It uses a multistage approach in order to deal with the different kinds of possible errors in the most appropriate way; in particular, the goal is to detect errors as early as possible to minimize their impact on the target system. Reconfigurations are expressed in a restricted, domain-specific language in order to allow different levels of static and dynamic validation, thus detecting errors before executing the reconfiguration where possible. For errors that can not be detected early (including software and hardware faults), a runtime environment provides transactional semantics to the reconfigurations.

show abstract

Section: Discussionmentioning

confidence: 99%

A Multi-stage Approach for Reliable Dynamic Reconfigurations of Component-Based Systems

David¹,

Léger²,

Grall³

et al. 2008

Distributed Applications and Interoperable Systems

View full text Add to dashboard Cite

show abstract

“…A number of architecture description languages (ADLs) have been defined to describe, model, check and im-plement software architectures [51]. The C2 system provides a framework for implementing software architectures but does not automatically ensure that the code instantiating the framework respects architectural constraints [50]. The SADL system [53] formalizes architectures in terms of theories, providing a framework for proving that communication integrity is maintained when refining an abstract architecture into a concrete one, however it does not provide automated support for enforcing communication integrity.…”

Section: Enforcing Architectural Structure In Codementioning

confidence: 99%

A case study in re-engineering to enforce architectural control flow and data sharing

Abi-Antoun

Aldrich

Coelho

2007

Journal of Systems and Software

View full text Add to dashboard Cite

Without rigorous software development and maintenance, software tends to lose its original architectural structure and become difficult to understand and modify. ArchJava, a recently proposed programming language which embeds a componentand-connector architectural specification within Java implementation code, offers the promise of preventing the loss of architectural structure. AliasJava, which can be used in conjunction with ArchJava, is an annotation system that extends Java to express how data is confined within, passed among, or shared between components and objects in a software system.We describe a case study in which we incrementally re-engineer an existing Java implementation to obtain an implementation which enforces the architectural control flow and data sharing. Building on results from similar case studies, we chose an application consisting of over 16,000 source lines of Java code and over 90 classes. We describe our process, the detailed steps involved (some of which can be automated), as well as some lessons learned and perceived limitations with the languages, techniques and tools we used.

show abstract

“…The issues and ramifications of applying object-oriented (00) type theory to the C2 architectural style were examined in [MORT96]. Relating the two clarifies the composition properties of components and enables more aggressive architecture analysis.…”

Section: Architectures and User Interfacesmentioning

confidence: 99%

Research in Advanced Environments

Taylor¹,

Richardson²,

Selby³

et al. 2001

Self Cite

View full text Add to dashboard Cite

Public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of informetion, including suggestions for reducing this burden, ObjectiveThe fundamental objective of Arcadia was to develop technically rich solutions across the breadth of the problem (developer support, product architectures, tool technologies) that are technically compatible, functionally comprehensive, and mutually reinforcing.Active process support was developed to help human developers, including non-technical managers, coordinate their activities while integrating commercial project planning tools. Analysis and testing tools were developed to provide high assurance in software, through provision of pre-run-time analyses, test case development, test result checking, and test process management tools. Powerful program analysis tools were developed which enable early detection of subtle coordination errors in concurrent systems composed of heterogeneous parts. Evolvable software architectures, first in the domain of user interface software, were developed to enable a more component-based software economy. World-Wide-Web and hypermedia technology were developed to foster easy information access, connections between software artifacts, and human understanding of complex systems. ApproachProcedurally, the Arcadia project's approach was one of iteration, prototyping, and integration. Emphasis was placed on identification of principles that transcend idiosyncratic implementations. The integrating environment conceptual architecture was based on a set of coherent principles iteratively refined through experience with the prototype component implementations. Specific technology transition efforts with various consumers were used to validate the technology in actual practice situations. Separate technologies were first prototyped, then pair-wise integrations performed, then multi-way integrations.The work in distributed, team-oriented software development was focused on determining effective ways of explicitly describing team-based activities, determining which parts of those activities could best be supported by automated tools, and technologies were developed to perform that automation. A critical aspect of this work was developing an effective basis for management of projects over the net; consequently, a distributed architecture implemented in Java was adopted. In a nutshell, this was research targeted at the intersection of software process research and computer-supported cooperative work (CSCW)/Groupware research. Specific technical innovation came from support for non-technical users, techniques supporting two-way integration with commercial project planning and communication tools, and support for reuse and adaptation of process fragments.

show abstract

Using object-oriented typing to support architectural design in the C2 style

Cited by 49 publications

References 25 publications

A Multi-stage Approach for Reliable Dynamic Reconfigurations of Component-Based Systems

A Multi-stage Approach for Reliable Dynamic Reconfigurations of Component-Based Systems

A case study in re-engineering to enforce architectural control flow and data sharing

Research in Advanced Environments

Contact Info

Product

Resources

About