Proceedings of the 4th ACM SIGSOFT Symposium on Foundations of Software Engineering 1996
DOI: 10.1145/239098.239106
|View full text |Cite
|
Sign up to set email alerts
|

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

Abstract: --Software architectures enable large-scale software development. Component reuse and substitutability, two key aspects of large-scale development, must be planned for during software design. Object-oriented (OO) type theory supports reuse by structuring inter-component relationships and verifying those relationships through type checking in an architecture definition language (ADL). In this paper, we identify the issues and discuss the ramifications of applying OO type theory to the C2 architectural style. Th… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
15
0

Year Published

2000
2000
2019
2019

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 115 publications
(15 citation statements)
references
References 23 publications
0
15
0
Order By: Relevance
“…MetaH [23] and UniCon [24] for example do not support component evolution thereby they can't be used to reason about dynamic problems such as microservice granularity. Other ADLs such as ACME [25], Rapide [26] and C2 [27] support component evolution by sub-typing, which is a less suitable counterpart to decomposition/merging which we support using transactions in the granularity adaptation aspect.…”
Section: B Qualitative Evaluation 1) Effectiveness and Expressivenesmentioning
confidence: 99%
See 1 more Smart Citation
“…MetaH [23] and UniCon [24] for example do not support component evolution thereby they can't be used to reason about dynamic problems such as microservice granularity. Other ADLs such as ACME [25], Rapide [26] and C2 [27] support component evolution by sub-typing, which is a less suitable counterpart to decomposition/merging which we support using transactions in the granularity adaptation aspect.…”
Section: B Qualitative Evaluation 1) Effectiveness and Expressivenesmentioning
confidence: 99%
“…Although most ADLs examined (e.g. [25], [27], [28]) support logical location by allowing hierarchical compositions of components and connectors, they do not capture explicitly the space in the hierarchy where these components are allowed to move, which is significant to the microservice granularity problem.…”
Section: B Qualitative Evaluation 1) Effectiveness and Expressivenesmentioning
confidence: 99%
“…For example, [32] emphasized notions from object-oriented (OO) type systems to describe interesting concepts of component type refinement in the C2 ADL. While C2 supports a particular class of architectures (layered message passing systems) and confines type descriptions to a modeling tier analogous to CALM's module tier, CALM emphasizes use of typing including OO concepts such as inheritance in meta-modeling facilities (at the CALM style tier) that allow one to describe any number of component model styles, style refinement, combinations of styles, nesting relationships between styles.…”
Section: Other Frameworkmentioning
confidence: 99%
“…Wright [4] use a process algebra to ensure that there will be no deadlocks in components interactions. C2 [24] can check the conformance of an architecture description relative to style constraints. However, as identified by [29], ADLs are not enough.…”
Section: Component Configuration and Reconfigurationmentioning
confidence: 99%