A Component- and Message-Based Architectural Style for GUI Software
IEEE Transactions on Software Engineering - Special issue: best papers of the 17th International Conference on Software Engineering (ICSE-17)
Acme: architectural description of component-based systems
Foundations of component-based systems
Heavyweight extensions to the UML metamodel to describe the C3 architectural style
ACM SIGSOFT Software Engineering Notes
Trustworthy components-compositionality and prediction
Journal of Systems and Software - Special issue on: Component-based software engineering
A formal approach to software architecture
A formal approach to software architecture
Architecture-based specification-time software evolution
Architecture-based specification-time software evolution
Software Reuse Research: Status and Future
IEEE Transactions on Software Engineering
A Dynamic Component and Aspect-Oriented Platform
The Computer Journal
MADL: Meta Architecture Description Language
SERA '05 Proceedings of the Third ACIS Int'l Conference on Software Engineering Research, Management and Applications
Moving architectural description from under the technology lamppost
Information and Software Technology
Enhancing dependability of component-based systems
Ada-Europe'07 Proceedings of the 12th international conference on Reliable software technologies
A software architecture modeling tool
TELE-INFO'09 Proceedings of the 8th Wseas international conference on Telecommunications and informatics
An environment for describing software systems
WSEAS Transactions on Computers
| Hi-index | 0.00 |
The more important level of abstraction in the description of large and complex software is its architecture description. So, at this abstraction level we can describe the principal system components and their pathways of interaction. Software architecture is considered to be the driving aspect of the development process; it allows specifying which aspects and models in each level needed according to the software architecture design. Early Architecture Description Languages (ADLs), nearly exclusive, focus on structural abstraction hierarchy ignoring behavioural description hierarchy, conceptual hierarchy, and metamodeling hierarchy. In this paper we show that all those hierarchies constitute views to appropriately "reason about" software architectures described using our C3 metamodel which is a minimal and complete ADL. We provide a set of mechanisms to deal with different levels of each hierarchy; also we introduce a new enhanced definition for connector concept deployed in C3 architectures.