Component software: beyond object-oriented programming
Component software: beyond object-oriented programming
Applied software architecture
Investigating and improving a COTS-based software development
Proceedings of the 22nd international conference on Software engineering
Component-based software engineering: putting the pieces together
Component-based software engineering: putting the pieces together
Building systems from commerical components
Building systems from commerical components
Software product lines: practices and patterns
Software product lines: practices and patterns
Component-based product line engineering with UML
Component-based product line engineering with UML
A ROOM Framework for the Spectrometer Controller Product-Line
Proceedings of the Workshop on Object-Oriented Technology
Using UML for Modeling Complex Real-Time Systems
LCTES '98 Proceedings of the ACM SIGPLAN Workshop on Languages, Compilers, and Tools for Embedded Systems
| Hi-index | 0.00 |
Large networked systems can include the whole technological spectrum of embedded systems from deeply embedded applicationspecific systems to software intensive applications including COTS component intensive subsystems. Significant up-front and early-stage architectural design is required for COTS component acquisition and evaluation. COTS related architectural decisions, constraints and knowledge must be communicated from design processes to component acquisition and business processes and vice versa. This paper describes a model for identifying and recording constraints, possibilities and needs for COTS components in architecture. The decision model associates COTS component needs with elements in the first part of the software architecture to be designed. Decisions related to a specific architectural model are listed in a table form. A decision includes a reference to the related architectural model element or to a separate variation point model that describes relationships between architectural elements and the results of the decision.