An Approach to Developing Domain Architectures Based on Variability Analysis

  • Mikyeong Moon
  • Keunhyuk Yeom
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3981)


Software product line engineering is a method that prepares for future reuse and supports seamless reuse in the application development process. A domain architecture, sharing a common software architecture across a product line, brings a core set of knowledge and assets to the development process. Domain architectures reduce the complexity and cost of developing and maintaining code. However, technically excellent domain architectures do fail, often because they are not effectively developed. The key concept in the development of domain architecture is variability, the ability to derive various products from the product family. Variability occurs at different levels. It is important to consider variability at the higher architectural levels, and not only at the code level. In this paper, we suggest a method of producing architectures that will be core assets in the product line. We describe a domain architecture where commonality and variability are explicitly considered.


Product Family Variation Point Software Product Line Domain Architecture Object Management Group 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Muthig, D., Atkinson, C.: Model-Driven Product Line Architecture. In: Chastek, G.J. (ed.) SPLC 2002. LNCS, vol. 2379, p. 110. Springer, Heidelberg (2002)CrossRefGoogle Scholar
  2. 2.
    The Object Management Group (OMG), Reusable Asset Specification (RAS) Version 2.2 (November 2005),
  3. 3.
    Moon, M., Yeom, K., Chae, H.S.: An Approach to Developing Domain Requirements as a Core Asset Based on Commonality and Variability in a Product Line. IEEE Transactions on Software Engineering 31(7), 551–569 (2005)CrossRefGoogle Scholar
  4. 4.
    Kang, K.C., Kim, S., Lee, J., Kim, K.: FORM: A Feature-Oriented Reuse Method with Domain Specific Reference Architectures. Annals of Software Engineering 5, 143–168 (1998)CrossRefGoogle Scholar
  5. 5.
    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
  6. 6.
    Keepence, B., Mannion, M.: Using patterns to model variability in product families. IEEE Software 16(4), 102–108 (1999)CrossRefGoogle Scholar
  7. 7.
    Gomma, H.: Designing Software Product Lines with UML. In: From Use Cases to Pattern-Based Software Architectures. Addison-Wesley, Reading (2004)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Mikyeong Moon
    • 1
  • Keunhyuk Yeom
    • 1
  1. 1.Department of Computer EngineeringPusan National UniversityBusanKorea

Personalised recommendations