Abstract
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.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
