UML 분석 모델의 구조적 제약사항에 대한 OCL 기반의 명세 및 검증

OCL Based Specification and Verification of Structural Constraints for UML Analysis Models

  • 발행 : 2006.02.01

초록

분석 모델은 오직 시스템의 기능적 요구사항에 초점을 두며, 비 기능적인 요구사항과 구현과 관련된 이슈들은 이후의 설계 작업이 착수될 때까지 미루어진다. 설계 활동은 분석 모델을 상세화하고 명확하게 하는 방식으로 수행된다. 따라서, 분석 모델의 품질은 설계 모델에 지대한 영향을 미친다. 그러므로, 정확한 분석 모델을 구축하기 위하여 많은 노력을 기울여야 한다. 본 논문에서는 전형적인 객체지향 개발 방법론의 분석 모델이 항상 충족해야 하는 구조적 제약 사항을 제안한다. 제약 사항은 개별 클래스에 관한 제약사항, 클래스간의 관계에 대한 제약 사항과 클래스의 사용에 대한 제약사항으로 분류된다. 각 제약사항 변로 정형적인 정의와 OCL을 이용한 기술이 제공된다. 또한, 2개의 산업체 프로젝트를 대상으로 수행된 사례 연구를 통하여 제안된 기법이 객체지향 분석 모델에 존재하는 심각한 오류를 발견하고 이를 수정하는 데 도움을 줄 수 있음을 보여 준다.

Analysis model focuses only on functional requirements and postpones nonfunctional requirements and implementation specific issues until subsequent design activities are undertaken. Based on the analysis models, the design activities are performed by refining and clarifying the analysis models. Thus, the quality of analysis models has a vast impact on the design models. Therefore, much effort should be taken to build correct analysis model. In this paper, we propose a set of structural constraints that analysis models of typical object-oriented development methods should satisfy. Three kinds of constraints are proposed: class related constraints, relation related constraints, and usage related constraints. For each constraint, formal definition and description with OCL are provided. In addition, through a case study with two medium-sired industrial systems, we demonstrated that the proposed approach can help to identify and correct serious deficiencies in object-oriented analysis models.

키워드

참고문헌

  1. I. Jacobson, et al, The Unified Software Development Process, Addison-Wesley, 1999
  2. OMG. MDA Guide Version 1.0.1. OMG Document formal/03-06-01, 2003
  3. OMG. UML 1.4 Specification. OMG Document formal/04-07-02, 2002
  4. J. Warmer and A. Kleppe, The Object Constraint Language: Precise Modeling with UML. Addison-Wesley, 1998
  5. M. Gogolla, 'Using OCL for Defining Precise, Domain-Specific UML Stereotypes,' Proc. 6th Australian Workshop on Requirement Engineering, 2001
  6. M. Gogolla and B. Henderson-Sellers, 'Analysis of UML Stereotypes within the UML Metamodel,' Proc. 5th Conf. Unified Modeling Language, pp. 84-99, 2002
  7. M. Gogolla, John and M. Richters, 'Validation of UML and OCL Models by Automatic Snapshot Generation,' Proc. 6th Conf. Unified Modeling Language, pp. 265-279, 2002
  8. L. Ol'khovich and D. V. Koznov, 'OCL-Based Automated Validation Method for UML Specifications,' Programming and Computer Science, pp. 323-327, 2003 https://doi.org/10.1023/B:PACS.0000004132.42846.11
  9. M. Richters and M. Gogolla, 'Validating UML Models and OCL Constraints,' Proc. 3rd Int. Conf. Unified Modeling Language, pp. 265-277, 2000
  10. P. Selonen and J. Xu, 'Validating UML Models Against Architecture Profiles,' ESEC/FSE '03, pp. 58-67, 2003 https://doi.org/10.1145/940071.940081
  11. P. Ziemann and M. Gogolla, 'Validating OCL Specifications with the USE Tool - An Example Based on the BART Case Study,' Proc. 8th Int. Workshop on Formal Methods for Industrial Critical Systems, 2003 https://doi.org/10.1016/S1571-0661(04)80816-8
  12. B. Hnatkowska, Z. Huzar, J. Kuzniarz, and L. Tuzinkiewics, 'A Systematic Approach to Consis-tency Within UML based Software Development Process,' Workshop on Consistency Problems in UML-based Software Development, Oct. 2002
  13. B. Hnatkowska and A. Walkowiak, 'Consistency Checking of USDP Models,' Workshop on Con-sistency Problems in UML-based Software Development, Oct. 2004
  14. L. Kuzniarz, G. Reggio, J. Sourrouille, and Z. Huzar, Workshop on Consistency Problems in UML-based Software Development, UML 2002, 2002
  15. I. Kuzniarz, G. Reggio, J. Sourrouille, Z. Huzar, and M. Staron, Workshop on Consistency Problems in UML-based Software Development II, UML 2003, 2003
  16. Z. Huzar, I. Kuzniarz, G. Reggio, and J. Sourrouille, Workshop on Consistency Problems in UML-based Software Development III, UML 2004, 2004
  17. M. Elaasar and L. Briand, 'An Overview of UML Consistency Management,' Technical Report SCE-04-18, Dept. of Systems and Computer Engineering, Carleton University, Canada
  18. M. Benattou, J-M. Brnel, and N. Hameurlain, 'Generating Test Data from OCL Specification,' Workshop on Integration and Transformation of UML Models, 2002
  19. I. Jacobson, Object-Oriented Software Engineering: A Use Case Driven Approach, Addison-Wesley, 1992
  20. Jim Arlow and Ila Neustadt, UML and the Unified Process: Practical Object-Oriented Analysis & Design, Addison-Wesley, 2002
  21. D. Rosenberg and K. Scott, Applying Use Case Driven Object Modeling with UML: An Annotated E-Commerce Example, Addison-Wesley, 2001
  22. OCL Evaluator http://lci.cs.ubbcluj.ro/ocle
  23. A. Schleicher and B. Westfechtel, 'Beyond Stereotyping: Metamodeling Approaches for the UML,' Proc. of 34th Hawaii Int. Conf. on System Sciences, 2001
  24. T. Ziadi, B. Traverson and J-M. Jezequel, 'From a UML Platform Independent Component Model to Platform Specific Component Models,' Workshop in Software Model Engineering, 2002