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

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

Requirements Redundancy and Inconsistency Analysis for Use Case Modeling

유스케이스 모델링을 위한 요구사항 중복 및 불일치 분석

  • 최진재 (지엠대우오토엔테크놀로지) ;
  • 황선영 (서강대학교 전자공학과)
  • Published : 2004.07.01
Download PDF
⟨ Previous Next ⟩

Abstract

This paper proposes an effective method to create logically consistent and structured requirement model by applying consistency control approach of the formal method to the use-case modeling. This method integrates the multi-perspective scattered requirement segments that may overlap and conflict each other into a structured requirement model. The model structure can be analyzed based on context goal and concerned area overlap analysis. The model consistency can be achieved by using specification overlap-based consistency checking method as an integration vehicle. An experimental application to case study shows that the Proposed method can successfully identify requirement overlaps and inconsistency. It can also transfer multi-viewpoint requirement segments into a consistently integrated use-case model to clarify software behaviors and functionality This method helps users to enhance capability to identify specification inconsistency in the use-case modeling at the early stage of software engineering development. The proposed approach can also facilitate communication between users and developers to ensure customer satisfaction.

본 논문에서는 정형방법론의 일관성 검사방법을 유스케이스 모델링에 적용함으로써 논리적으로 일관되고 구조화된 요구사항 모델을 생성할 수 있는 방안을 제안하였다. 제안된 방안을 통해 서로 중복되거나 충돌할 수 있는 다중 사용자관점의 부분적인 요구사항들을 구조화된 요구사항 모델로 통합할 수 있다. 요구사항 모델의 구조는 문맥목표와 관심영역의 중복구조를 통하여 분석되며, 요구사항의 모델의 일관성은 요구사항 통합의 수단으로 요구사항 명세의 중복관계에 기반한 일관성 검사방법을 사용함으로써 획득된다. 제시된 방법을 사례분석에 적용한 결과 제안된 방안이 요구사항의 중복관계 및 불일치를 도출할 수 있을 뿐만 아니라 다중 사용자관점의 부분적인 요구사항들을 일관성을 갖는 통합된 요구사항 모델로 전환함으로써 소프트웨어의 행위와 기능을 명확하게 규명할 수 있음을 보여 주었다. 제안된 방안을 통하여 개발 초기단계의 유스케이스 모델링에 있어서 요구사항 불일치 도출능력을 강화할 수 있으며, 고객만족을 위해 사용자와 개발자간의 의사소통을 촉진할 수 있다.

Keywords

References

  1. The Standish Group, 'The CHAOS Report (1994),' http://www.standishgroup.com/sample_research/chaos_1994_1.php, 1994
  2. F. Brooks. 'No Silver Bullet ; Essence and Accidents of Software Engineering,' Computer, Vol. 20, No.4, pp. 10-19, 1987 https://doi.org/10.1109/MC.1987.1663532
  3. R.M. Tong, L.A. Appelbaum, V. N. Askman, and J. F. Cunningham, 'Conceptual Information Retrieval Using RUBIC' in Proc. of 10th Annual Int. ACM SIGIR Conference on Research and Development in Information Retrieval, New Orleans, Louisiana, pp.247-253, 1987 https://doi.org/10.1145/42005.42033
  4. B. Mynatt, Software Engineering with Student Project Guidance, Prentice Hall : Englewood Cliffs, NJ, 1990
  5. S. Park, H. Kim, Y, Ko, and J. Seo, 'Implementation of an Efficient Requirements - Analysis Supporting System Using Similarity Measure Techniques,' Information and Software Technology, Vol. 42, No. 6, pp. 429-438, 2000 https://doi.org/10.1016/S0950-5849(99)00102-0
  6. S. Jones, D. Till, and A. Wrightson, 'Formal Methods and Requirements Engineering ; Challenges and Synergies,' Journal of Systems and Software, Vol. 40, No. 3, pp. 263-273, 1998 https://doi.org/10.1016/S0164-1212(97)00171-4
  7. A. Davis and D. Leffingwell, 'Using Requirements Management to Speed Delivery of Higher Quality Applications,' Rational Software Corp., Technical Report, http://www.rational.com/media/whitepapers/ 696wp.pdf, 1995
  8. K. Yue, 'What Dose It Mean to Say that a Specification is Complete?' in Proc. IWSSD-4, 4th Int. Workshop on Software Specification and Design, Monterey, CA, IEEE Computer Society Press, pp.42-49, 1987
  9. 이재호, 김재선, 박수용, '유즈케이스 모델링을 위한 시나리오 근간의 목표지향 분석 방안', 정보과학회논문지: 소프트웨어 및 응용, 29권, 4호, pp. 211-224, 2002
  10. I. Jacobson, Object-Oriented Software Engineering : A Use case Driven Approach, Addison-Wesley : Reading, MA, 1992
  11. G. Booch, Object-Oriented Analysis And Design with Applications, Benjamin/Cummings : Redwood City, CA, 1994
  12. J. Rumbaugh, M. Blaha, W. Premerlani, F. Eddy, and W. Lorensen, Object-Oriented Modeling and Design, Prentice-Hall : Englewood Cliffs, NJ, 1991
  13. A. Hunter and B. Nuseibeh, 'Analyzing Inconsistent Specifications,' in Proc. of Third IEEE International Symposium on Requirements Engineering (RE'97), Annapolis, MD, IEEE Computer Society, pp.78-86, 1997 https://doi.org/10.1109/ISRE.1997.566844
  14. A. Dardenne, A. van Lamsweerde and S. Fickas, 'Goal-directed Requirements Acquisition,' Science of Computer Programming, Vol. 20, No. 1-2, pp. 3-50, 1993 https://doi.org/10.1016/0167-6423(93)90021-G
  15. G. Spanoudakis and A. Finkelstein, 'Reconciling Requirements : A Method for Managing Interference, Inconsistency and Conflict,' Annals of Software Engineering, Vol. 3. No. 1, pp. 433-457, 1997 https://doi.org/10.1023/A:1018998207415
  16. G. Spanoudakis, A. Finkelstein. and D. Till. 'Overlaps in Requirements Engineering.' Automated Software Engineering, Vol. 6, No. 2, pp. 171-198, 1999 https://doi.org/10.1023/A:1008718614166
  17. M. Heimdahl and N. Leveson, 'Completeness and Consistency Analysis of State-Based Requirements.' IEEE Trans. on Software Engineering, Vol. 22, No. 6, pp. 363-377, 1996 https://doi.org/10.1109/32.508311
  18. M. Fowler, UML Distilled; Applying the Standard Object Modeling Language, Addison-Wesley : Reading, MA. 1998
  19. 서정훈, 강교철, '소프트웨어 요구공학에서 휘처 기반의 운영 모델 타당성 검사', 석사논문, 포항공과대학교 정보통신대학원, 1998
  20. A. Finkelstein. G. Spanoudakis, and D. Till. 'Managing Interference.' in joint Proc. of Viewpoints 96 : An International Workshop on Multiple Perspectives in Software Development. ACM Press: San Francisco, pp. 172-174, 1996 https://doi.org/10.1145/243327.243646
  21. A. Finkelstein. D. Gabbay, A. Hunter. J. Kramer. and B. Nuseibeh 'Inconsistency Handling in Multi-perspective Specifications.' IEEE Trans. on Software Engineering, Vol. 20, No. 8, pp. 569-578, 1994 https://doi.org/10.1109/32.310667
  22. B. Neseibeh, J. Kramer. and A. Finkelstein. 'A Framework for Expressing the Relationships between Multiple Views in Requirements Specification.' IEEE Trans. on Software Eng., Vol. 20. No. 10, pp. 760-773, 1994 https://doi.org/10.1109/32.328995
  23. G. Spanoudakis and H. Kim 'Diagnosis of the Significance of Inconsistencies in Object-Oriented Designs : A Framework and its Experimental Evaluation.' Journal of Systems and Software, Vol. 64. No. 1. pp.3-22, 2002 https://doi.org/10.1016/S0164-1212(02)00018-3
  24. B. Neuseibeh, A. Finkelstein. and J. Kramer. 'Method Engineering for Multi -perspective Software Development.' Information and Software Technology, Vol. 38, No. 4, pp. 267-274, 1996 https://doi.org/10.1016/0950-5849(95)01054-8
  25. 황만수, 이원우, 류성렬, 'CSCW환경에 기반한 요구공학 프로세스모델 설계', 한국정보처리학회 논문지, 7권, 10호, pp. 3075-3085, 2000
  26. B. Nuseibeh, S. Easterbrook, and A. Russo, 'Making Inconsistency Respectable in Software Development.' Journal of Systems and Software, Vol. 58, No. 2, pp. 171-180, 2001 https://doi.org/10.1016/S0164-1212(01)00036-X
  27. United Nations Center for Trade Facilitation and Electronic Business (UN/CEFACT), Business Process Analysis Working Group. 'International Supplier Chain Reference Model (BP044),' http://www.unece.org/cefact/docum/sessdocs/bawg 0398.htm. 2001
  28. OMG, 'OMG Unified Modeling Language Specification Version 1.5,' OMG formal document, http://www.omg.org/technology/documents/modeling_spec_catalog.htm, 2003
  29. 유철중, 정소영, '요구사항 기술서로부터 유스케이스 다이어그램 추출기법', 한국정보처리학회 논문지 D, 9-D권, 4호, pp.639-650, 2002 https://doi.org/10.3745/KIPSTD.2002.9D.4.639
  30. A. Anton, R. Carter, A. Dagnino, J. Dempster and D. Siege, 'Deriving Goals from a Use Case Based Requirements Specification,' Requirements Engineering Journal, Springer-Verlag, Vol. 6, pp. 63-73, 2001 https://doi.org/10.1007/PL00010356
  31. K. Bittner, 'Managing Use-Case Details,' in the Rational Edge of IBM, white paper, http://www.therationaledge.com/content/apr_01/t_usecase_kb.html, 2001