Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
Dynamic structure in software architectures
SIGSOFT '96 Proceedings of the 4th ACM SIGSOFT symposium on Foundations of software engineering
A formal basis for architectural connection
ACM Transactions on Software Engineering and Methodology (TOSEM)
A language and environment for architecture-based software development and evolution
Proceedings of the 21st international conference on Software engineering
Behavior Protocols for Software Components
IEEE Transactions on Software Engineering
Using Architectural Style as a Basis for System Self-repair
WICSA 3 Proceedings of the IFIP 17th World Computer Congress - TC2 Stream / 3rd IEEE/IFIP Conference on Software Architecture: System Design, Development and Maintenance
Speechnet: A Network of Hyperlinked Speech-Accessible Objects
WECWIS '99 Proceedings of the International Workshop on Advance Issues of E-Commerce and Web-Based Information Systems
Unified Modeling Language User Guide, The (2nd Edition) (Addison-Wesley Object Technology Series)
Unified Modeling Language User Guide, The (2nd Edition) (Addison-Wesley Object Technology Series)
Software—Practice & Experience
Component-Based Development Process and Component Lifecycle
ICSEA '06 Proceedings of the International Conference on Software Engineering Advances
Search-based many-to-one component substitution
Journal of Software Maintenance and Evolution: Research and Practice - Search Based Software Engineering [SBSE]
Software Architecture: Foundations, Theory, and Practice
Software Architecture: Foundations, Theory, and Practice
A three-level component model in component based software development
Proceedings of the 11th International Conference on Generative Programming and Component Engineering
| Hi-index | 0.00 |
Architecture-centric, component-based development intensively reuses components from repositories. Such development processes produce architecture definitions, using architecture description languages (Adls). This paper proposes a three step process. Architecture specifications first capture abstract and ideal architectures imagined by architects to meet requirements. Specifications do not describe complete component types but only component roles (usages). Architecture configurations then capture implementation decisions, as the architects select specific component classes from the repository to implement component roles. Finally, architecture assemblies define how components instances are created and initialized to customize the deployment of architectures in their own execution contexts. This development process is supported by a three-level Adl which enables the separate definition of these three representations. The refinement relationships between these architecture representations are also discussed.