Design of Product-Line Architecture based-on Common Architecture

공통 아키텍처 기반 제품계열 아키텍처 설계

  • 오영배 (수원여자대학교 컴퓨터응용학부) ;
  • 신성욱 (고려대학교 컴퓨터학과 대학원) ;
  • 김영갑 (고려대학교 컴퓨터학과 대학원) ;
  • 백두권 (고려대학교 컴퓨터학과)
  • Published : 2006.08.31

Abstract

Software product line is a software product or a set of software system, which has common functions. We can develop a specific software product, which satisfies requirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed software architecture through the software product line. Software development methodology based on the software product line can develop a software more easily and fast by reusing the developed software core asset. Developed countries of software technology select software product line as a core field of software production technology, and support technology development. In case of USA, CMU/SEI(Carnegie Mellon University/Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Department of Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. However, industries in our country understand the necessity of software production technology based on product line concept for the purpose of increasing productivity, it is not sufficient to invest for this technology development. In this paper, we aim to construct the common architecture of software product line for production of the software product line.

Keywords

References

  1. Allen, P. and S. Frost, Component-Based Development for Enterprise Systems, Applying the SELECT Perspective, Cambridge University Press/SIGS, Cambridge, 1998
  2. Atkinson, C., J. Bayer, et al., Componentbased Product Line Engineering with UML, 2002
  3. Bayer, J., O. Flege, P. Knauber, R. Laqua, D. Muthig, K. Schmid, T. Widen, and J. Debaud, 'PuLSE. A Methodology to Develop Software Product Lines', in Proceedings of the Symposium on Software Reuse (SSR '99), May 1999
  4. Cheesman, J. and J. Daniels, UML Components: A Simple Process for Specifying Component-Based Software, Addison- Wesley, 2000
  5. Clements, P. and, L. Northrop, Software Product Lines:Practices and Patterns, 2002
  6. Coleman, D., P. Arnold, S. Bodoff, C. Dollin, H. Gilchrist, F. Hayes, and P. Jeremaes, Object-oriented Development, The Fusion Method, Prentice Hall, 1994
  7. D'Souza, D. F. and A. C. Wills, Objects, Components and Frameworks with UML: The Catalysis Approach, Addison-Wesley, 1998
  8. Kang, K. C., S. G. Cohen, W. E. Novak, and A. S. Peterson, 'Feature-oriented Domain Anlaysis(FODA) Feasibility Study', Technical Report CMU/SEI-90-TR-21, SEI, November 1990
  9. Reenskaug, T., P. Wold, and O. Lehne, Working with Objects:The OOram Software Development Method, Manning/Prentice Hall, 1996
  10. Robinson, P. J., Hierarchical Object- Oriented Design, Prentice Hall, 1992
  11. Rumbaugh, J., M. Blaha, W. Premerlani, F. Eddy, and W. Lorensen, Object-Oriented Modelling and Design, Prentice Hall, 1991
  12. Selic, B., G. Gullekson, and P. T. Ward, Real-Time Object-Oriented Modeling, John Wiley and Sons, 1994
  13. Weiss, D. and C. Lai, Software Product-line Engineering:A Family-Based Software Development Process, 1999