Journal of KIISE:Software and Applications (한국정보과학회논문지:소프트웨어및응용)

Korean Institute of Information Scientists and Engineers (한국정보과학회)
권호 표지

An Integrated Requirements Analysis Method based on Goal and Scenario

목표와 시나리오 기반의 통합적 요구 사항 분석 방안

  • Published : 2004.05.01
Download PDF
⟨ Previous Next ⟩

Abstract

In Requirements engineering, requirements elicitation and analysis are very important tasks to develop software systems successfully. Even though various methods have been proposed including scenario-based analysis, goal based analysis, and coupling goal with scenario, each method has its own strengths and weaknesses. If you use only one method, it is very difficult to elicit and to analyze system requirements completely. Since these methods don't support a comprehensive elicitation process, this paper proposes an integrated approach. This integrated approach is focused on two viewpoints. One is what factors are comprised and the other is how they are integrated. This paper also shows how the proposed approach can be applied to Meeting Reservation System (MRS) development. An experiment has been conducted using this approach to demonstrate how complete requirements are elicited and analyzed and to show relative time savings during elicitation in comparison to each method.

요구 공학에서 초기에 요구 사항을 추출하고 분석하는 것은 성공적인 소프트웨어 시스템을 개발하기 위한 중요한 작업이다. 그러나 시나리오 기반의 분석, 목표기반의 분석, 시나리오를 이용한 목표기반의 분석 등과 같은 다양한 분석 기법이 있음에도 불구하고, 각 기법들은 장, 단점을 가지고 있기 때문에, 하나의 기법만을 가지고 요구 사항을 분석한다면, 개발할 시스템 전체의 요구 사항을 정확하게 이해하기가 쉽지 않다. 또한 각각의 기법들은 요구 사항 추출 단계를 지원하지 않으므로 분석을 위한 가공되지 않은 데이타(raw data)를 다루기 어렵다. 본 논문에서는 요구 사항 분석을 위한 데이타 획득과 여러 기법들을 효율적으로 통합하는 통합적 요구 사항 분석 방안을 제안한다. 통합적 요구 사항 분석 방안은 2가지 관점에서 기술된다. 첫째는 어떤 요소들이 통합될 수 있는지를 기술하고, 두 번째는 그 요소들이 어떻게 통합되어야 하는지를 기술한다. 본 논문에서 제안된 방안이 어떻게 적용되는지를 미팅예약시스템(Meeting Reservation System)을 예로 설명한다. 또한 다른 기법들과의 비교를 위해 30여명의 요구 사항 분석 실무 경험자를 대상으로 한 실험의 결과를 통해 제안된 기법의 효과를 검증한다.

Keywords

References

  1. Richard H.Thayer, Merlin Dorfman, Software Requirements Engineering, 2nd Edition IEEE Computer Society Press, 1997
  2. Daniel Gross, Eric Yu, From Non-Functional Requirements to Design through Patterns, Requirements Engineering, Springer-Verlag, 2001, pp. 18-36
  3. Steve McConnell, Code Complete: A Practical Handbook of Software Construction, Microsoft Press, 1993
  4. Ivar Jacobson, 'Four Macro Trend in Software Development,' Korea Conference of Software Engineering, 2002, pp. 1-14
  5. Sutcliffe, A, 'Scenario based requirement analysis,' Requirements Engineering Journal, 1998, pp. 48-65
  6. V.Plihon, J.Ralyte, A.Benjamen, N.A.M. Maiden, A.Sutcliffe, E.Dubois, and P.Heymans, 'A Reuse-Oriented Approach for the Construction of Scenario Based methods,' Proc. Int'l Software process Assoc. Fifth Int'l Conf. Software Process(ICSP'98), Chicago, June 1998, pp. 14-17
  7. Annie I. Anton, 'Goal-Based Requirements Analysis,' Proceedings of ICRE 96, pp. 136-144 https://doi.org/10.1109/ICRE.1996.491438
  8. Anne Dardenne, Axel van Lamsweerde, Stephen Fickas, 'Goal-Directed Requirements Acquisition,' Science of Computer Programming, 20(1-2), 1993, pp. 3-50 https://doi.org/10.1016/0167-6423(93)90021-G
  9. C. Rolland, C. Souveyet, C. Ben Achour, 'Guiding Goal Modelling using Scenarios,' IEEE Transactions on Software Engineering, Special Issue on Scenario Management, Vol. 24, No. 12, Dec. 1998. pp 1055-1071 https://doi.org/10.1109/32.738339
  10. E. Yu and J. Mylopoulos, 'Why Goal-Oriented Requirements Engineering,' Proceedings of the 4th International Workshop on Requirements Engineering: Foundations of Software Quality(8-9 June 1998, Pisa, Italy). E. Dubois, A.L. Opdahl, K. Pohl, eds. Presses Universitaires de Namur, 1998. pp.15-22
  11. Ian Sommerville, Software Engineering 6th Edition, Addison-Wesley, 2001, pp 137-139, pp194-211
  12. Colette Rolland, Georges Grosz, Regis Kla, 'Experience With Goal-Scenario Coupling In Requirements Engineering,' Requirements Engineering. 1999 Proceedings. IEEE International Symposium on, 1999 Page(s): 74-81 https://doi.org/10.1109/ISRE.1999.777987
  13. Gerald Kotonya, Ian Sommerville, Requirements Engineering processes and techniques, Wiley, 1997, pp. 139-14
  14. Alan M. Davis, Software Requirements-Analysis and specification, Prentice Hall, 1990, pp. 46-51
  15. Annie I. Antn, Goal Identification and Refinement in the Specification of Software-Based Information Systems, Ph.D. Thesis, Georgia Institute of Technology, Atlanta, GA, USA, June 1997
  16. International Organization for Standards, ISO/IEC 9126-1 Information Technology; Software Product Quality, International Organization for Standards, 2002
  17. Paul Clements, Rick Kazman, Mrak Klein, Evaluating Software Archtectures : Methods and Case Studies, Addison-Wesley, 2002, pp 211-239
  18. Maiden, N.A.M., Sutcliffe, A.G., Requirements critiquing using domain abstractions. In: Proceedings First International Conference on Requirements Engineering, J. Siddiqi (ed.) IEEE Computer Society Press, 1994, 184-193 https://doi.org/10.1109/ICRE.1994.292386
  19. OMG, A UML Profile for Enterprise Distributed Object Computing Specification, 2002-08, pp B-1-B-3
  20. B.WBoehm, 'Software Engineering Economics,' Prentice Hall, 1981