A Domain Analysis Method for Saftware Product Lines Based an Goals, Scenarios, and Features

소프트웨어 프로덕트 라인을 위한 목표, 시나리오, 휘처 기반의 도메인 분석 방안

  • Published : 2006.07.01

Abstract

Software product lines (SPL) are recently an emerging software reuse paradigm, which helps organizations develop their products from reusable core assets rather than from scratch. For developing these assets, understanding commonality and variability (C&V) is essential. A feature-oriented approach has been used extensively for C&V analysis in the SPL. However, this contains no proposal to systematically identify features and provide the rationale for the features. Further, the approach does not directly show how the results of C&V analysis will satisfy an organization's high-level business goals and provide the rationale for the C&V. Therefore, this paper presents a domain analysis method for the SPL based on goals, scenarios, and features in order to overcome some of the deficiencies and limitations of the feature-oriented approach. In particular, the paper proposes a domain requirements model (DRM) and a domain requirements modeling method based on the DRM. This method has been applied to the home integration system (HIS) domain to demonstrate its feasibility with a supporting tool, namely IDEAS. Our approach makes it possible to systematically identify the features and provide the rationale for both the features and the C&V.

소프트웨어 재사용을 위한 새로운 패러다임으로서 대두되고 있는 소프트웨어 프로덕트 라인에서 가장 중요하며, 기본이 되는 것은 바로 재사용 가능한 소프트웨어 자산을 개발하기 위한 프로덕트 라인의 공통성과 가변성 식별이라고 하겠다. 현재 이를 위해 휘처 중심의 도메인 분석 방법이 많이 사용되고 있으나, 이 방법은 휘처를 식별하고, 식별된 휘처의 근거를 제시하기 위한 체계적인 방법을 제공하지 못하고 있다. 또한 프로덕트의 공통성과 가변성 분석 결과가 프로덕트 라인 개발 조직의 최상위 수준 목표(goals)를 만족시키고, 그 근거를 보여줄 수 있어야 하지만 현재 이러한 부분에 대한 연구가 부족한 실정이다. 따라서 본 논문에서는 기존의 휘처 중심의 도메인 분석 방법에서의 문제점들을 해결하고, 보안하기 위해 프로덕트 라인을 위한 목표, 시나리오, 휘처 기반의 도메인 분석 방안을 제안하였다. 이것은 목표와 시나리오 그리고 휘처의 관계를 통하여 프로덕트 라인을 위한 도메인 요구사항 모델(DRM: domain requirements model)을 제시하고, 그러한 모델을 바탕으로 도메인 요구사항 모델링 방법(domain requirements modeling method)을 제안한다. 마지막으로는 제안된 방안을 지원하는 도구 (IDEAS)를 설명하고, 이를 통해 주택 통합 시스템(HIS)에 적용함으로써 제안된 방법을 검증하였다. 제안된 방법은 체계적으로 휘처를 식별하고, 그에 대한 근거 및 공통성과 가변성에 대한 근거를 제공할 수 있을 것이다.

Keywords

References

  1. J. Bosch, Design and Use of Software Architectures: Adopting and Evolving a Product-Line Approach, Addison-Wesley, Boston, 2000
  2. P. Clements and L. Northrop, Software Product Lines: Practices and Patterns, Boston, MA: Addision Wesley Longman, Inc., 2001
  3. Donohoe, P., ed., Software Product Lines: Experience and Research Directions. Denver, Colorado, August 28-31 2000. Boston, MA: Kluwer Academic Publishers, 2000
  4. K.C. Kang, K. Lee, J. Lee, S. Kim, 'Feature Oriented Product Line Software Engineering: Principles and Guidelines,' Domain Oriented Systems Development: Practices and Perspectives, Taylor & Francis, pp. 19-36, 2003
  5. K.C. Kang, J. Lee, P. Donohoe, 'Feature-Oriented Product Line Engineering,' IEEE Software, Vol. 9, No. 4, Jul./Aug., pp. 58-65, 2002 https://doi.org/10.1109/MS.2002.1020288
  6. D. Fey, R. Fajta, A. Boros, 'Feature Modeling: A Meta-model to Enhance Usability and Usefulness,' G. Chastek, ed., Proc. 2nd Software Product Line Conf., Springer Lecture Notes in Computer Science, vol. 2379, Heidelberg, Germany, 2002
  7. W. B. Frakes and K. C. Kang 'Software Reuse Research: Status and Future,' IEEE Transactions on Software Engineering(TSE), Vol. 31, No.7, July, pp.529-536, 2005 https://doi.org/10.1109/TSE.2005.85
  8. K.C. Kang, S. Cohen, J. Hess, W. Novak, A. Peterson, Feature-Oriented Domain Analysis (FODA) Feasability Study, tech. report CMU/SEI-90-TR-21, Software Eng. Inst., Carnegie Mellon Univ., Pittsburgh, PA, 1990
  9. K.C. Kang, S. Kim, J. Lee, K. Kim, E. Shin, M. Huh, 'FORM: A Feature-Oriented Reuse Method with Domain-Specific Reference Architectures,' Annals of Software Engineering, Vol. 5, pp. 143-168, 1998 https://doi.org/10.1023/A:1018980625587
  10. S. Thiel, F. Peruzzi, 'Starting a Product Line Approach for an Envisioned Market: Research and Experience in an Industrial Environment,' Patrick, ed. Proc. 1st Software Product Line Conf.(SPLCl), Kluwer Academic Publishers, Boston, pp.495-512, 2000
  11. G. Chastek, P. Donohoe, K.C. Kang, S. Thiel, Product Line Analysis: A Practical Introduction, tech. report CMU/SEI-2001-TR-001, Software Eng. Inst., Carnegie Mellon Univ., Pittsburgh, 2001
  12. C. Potts, K. Takahashi, and A. I. Antn, 'Inquirybased requirements analysis,' IEEE Softw., vol. 11, no. 2, pp. 21-32, 1994 https://doi.org/10.1109/52.268952
  13. A. Sutcliffe, 'Scenario-based requirement analysis,' Requirements Engineering Journal, pp. 48-65, 1998 https://doi.org/10.1007/BF02802920
  14. A.I. Antn, 'Goal-based requirements analysis,' in Proc. 2nd Int. Conf. Requirements Engineering (ICRE'96), Colorado Springs, CO, April, pp. 136-144, 1996
  15. C. Rolland, C. Souveyet, and C. Ben Achour, 'Guiding goal modeling using scenarios,' IEEE Trans. Software Eng., vol. 24, pp. 1055-1071, 1998 https://doi.org/10.1109/32.738339
  16. J. Lee and K. C. Kang, 'Feature Binding Analysis for Product Line Component Development,' Proceedings of the Fifth International Workshop on Product Family Engineering (PFE-5), Siena, Italy, November 4-6, pp.266-276, 2003
  17. K. Lee, K. C. Kang, M. Kim and S. Park, 'Combining Feature-Oriented Analysis and Aspect-Oriented Programming for Product Line Asset Development', Proc. of 10th International Software Product Line Conference (SPLC 2006), Baltimore, Maryland, 2006 (accepted for publication)
  18. I. Jacobson, M. Griss, P. Jonsson, Software Reuse: Architecture, Process and Organization for Business Success, Addison-Wesley Publishing Company, May 1997
  19. A. D. Vici and N. Argentieri, 'FODAcom: An Experience with Domain Analysis in the Italian Telecom Industry,' Proceedings of the 5th International Conference on Software Reuse (ICSR), Victoria, BC, Canada, pp. 166-175, June 1998 https://doi.org/10.1109/ICSR.1998.685741
  20. M. Griss, J. Favaro, M. d' Alessandro, 'Integrating Feature Modeling with the RSEB,' Proc. 5th International Conference on Software Reuse (ICSR'98). IEEE Computer Society Press. Victoria BC, Canada, June2-5, 1998 https://doi.org/10.1109/ICSR.1998.685732
  21. M. Eriksson, J. Borstler, and K. Borg, 'The PLUSS Approach - Domain Modeling with Features, Use Cases and Use Case Realizations,' 9th International Software Product Line Conference (SPLC Europe), Rennes, France, September 26-29, pp.33-44, 2005
  22. E. Yu, 'Why Goal-Oriented Requirements Engineering,' Proc. Fourth Int'l Workshop Requirements Eng.: Foundation for Software Quality (RESFQ '98), Pisa, Italy, June 1998
  23. J. Mylopoulos, L. Chung, and E. Yu, 'From Object-Oriented to Goal-Oriented Requirements Analysis,' Communications of the ACM, 42(1), pp. 31-37, 1999 https://doi.org/10.1145/291469.293165
  24. A. van Lamsweerde, 'Goal-Oriented Requirements Engineering: A Guided Tour,' Proc. RE'01 5th Intl. IEEE Symp. on Requirements Engineering, August, pp. 249-263, 2001 https://doi.org/10.1109/ISRE.2001.948567
  25. E. Letier, A. van Lamsweerde, 'Reasoning about partial goal satisfaction for requirements and design engineering,' SIGSOFT FSE pp.53-62, 2004 https://doi.org/10.1145/1041685.1029905
  26. H. Van, A. van Lamsweerde, Philippe Massonet, Christophe Ponsard: Goal-Oriented Requirements Animation. Proc. of 12th IEEE Int. Req. Engineering Conf. (RE'04), pp. 218-228, 2004 https://doi.org/10.1109/RE.2004.24
  27. B. Nuseibeh, S. Easterbrook, 'Requirements Engineering: A Roadmap,' In: The Future of Software Engineering, Special Issue 22nd International Conference on Software Engineering, ACM, pp. 37-46. 2000 https://doi.org/10.1145/336512.336523
  28. P. Hsia, J. Samuel, J. Gao, D.Kung,Y. Toyoshima, and C. Chen, 'Formal approach to scenario analysis,' IEEE Softw., vol. 11, no. 2, pp. 33-41, 1994 https://doi.org/10.1109/52.268953
  29. C. Rolland, G. Grosz, R. Kia, 'Experience With Goal-Scenario Coupling In Requirements Engineering,' Fourth IEEE International Symposium on Requirements Engineering, 1999 https://doi.org/10.1109/ISRE.1999.777987
  30. K. C. Kang, S. Kim, J. Lee, and K. Lee, 'Feature-Oriented Engineering of PBX Software for Adaptability and Reusability,' Software- Practice and Experience, Vol. 29, Issue 10, pp. 875-896, 1999 https://doi.org/10.1002/(SICI)1097-024X(199908)29:10<875::AID-SPE262>3.0.CO;2-W
  31. B. Chandrasekaran and H. Kaindl, 'Representing functional requirements and user-system interactions,' in Proc. AAAI-96 Workshop on Modeling and Reasoning about Function, Portland, OR: AAAI, Aug.l996
  32. H. Kaindl, 'An integration of scenarios with their purposes in task modeling,' in Proc. Symp. Designing Interactive Systems: Processes, Practices, Methods, and Techniques (DIS '95). Ann Arbor, MI: ACM, August, pp. 227-235, 1995 https://doi.org/10.1145/225434.225460
  33. H. Kaindl, 'A Design Process Based on a Model Combining Scenarios with Goals and Functions,' IEEE Transactions on Systems, Man, and Cybernetics, Part A, Vol. 30, No. 5, September 2000 https://doi.org/10.1109/3468.867861
  34. A. Dardenne, A. van Lamsweerde and S. Fickas, 'Goal-Directed Requirements Acquisition,' Science of Computer Programming, Vo1.20, pp. 3-50, 1993 https://doi.org/10.1016/0167-6423(93)90021-G
  35. Karl E. Wiegers, Software Requirements, Microsoft Press, 1999
  36. S. Jacobs and R. Holten, 'Goal-Driven Business Modelling Supporting Decision Making within Information Systems Development,' Proc. Conf. On Organizational Computing Systems, Milpitas, Calif. pp. 96-105, 1995 https://doi.org/10.1145/224019.224029
  37. G. Chastek, P. Donohoe, J. McGregor, Product Line Production Planning for the Home Integration System Example, tech. note CMU/SEI-2002-TN-029, Software Eng. Inst., Carnegie Mellon Univ., Pittsburgh, 2002