A Metamodel Approach to Architecture Variability in a Product Line
Architecture describes the organizational structure of a system including components, interactions, and constraints. Reusable components, units of software systems, have been considered to support a considerable improvement in reducing development costs and time to market because their interfaces and functionality are explicitly defined. Instead of reusing an individual component, however, it is much more advantageous to reuse a whole design or architecture. A domain architecture, sharing a common software architecture across a product line, includes common components shared by all products and optional components exploited by a subset of the products. Variability, one of the key concepts in the development of domain architectures indicates the ability to derive various products from the product line. Clearly, we need to support variability during domain architecture development. In this paper, we suggest a metamodeling concept that enables a common under-standing of architecture variability. The domain architecture metamodel reflects the Object Management Group’s (OMGTM) Reusable Asset Specification (RAS) which addresses the engineering elements of reuse. We describe a domain architecture in which commonality and variability are explicitly considered.
KeywordsVariation Point Software Product Line Domain Architecture Object Management Group Domain Component
Unable to display preview. Download preview PDF.
- 1.Muthig, D., Atkinson, C.: Model-Driven Product Line Architecture. In: Proc. Second Software Product Line Conference (August 2002)Google Scholar
- 2.The Object Management Group (OMG), Reusable Asset Specification (RAS) Version 2.2 (November 2005), http://www.omg.org/technology/documents/formal/ras.htm
- 3.The Object Management Group (OMG), Meta-Object Facility (MOF) Version 1.4 (2003), http://www.omg.org/docs/formal/02-04-03.pdf
- 4.Duffy, D.J.: Domain Architectures: Models and Architectures for UML Applications. Wiley, Chichester (2004)Google Scholar
- 7.Kang, K., Cohen, S., Hess, J., Novak, W., Peterson, S.: Feature-Oriented Domain Analysis (FODA) Feasibility Study. Technical Report CMU/SEI-90-TR-21, Software Engineering Institute, Carnegie Mellon University (November 1990)Google Scholar
- 9.Gomma, H.: Designing Software Product Lines with UML, From Use Cases to Pattern-Based Software Architectures. Addison-Wesley, Reading (2004)Google Scholar