The KIPS Transactions:PartD (정보처리학회논문지D)

Korea Information Processing Society (한국정보처리학회)
권호 표지

An Object-Oriented Modeling of Object-Oriented Software Development Methods : OMOS(Object-oriented software development Method for Object-oriented software System)

객체지향 소프트웨어 개발 방법론의 객체지향 모델링 : OMOS(Object-oriented software development Method for Object-oriented software System)

  • 최성운 (명지대학교 컴퓨터공학과)
  • Published : 2001.08.01
Download PDF
⟨ Previous Next ⟩

Abstract

Object-oriented software development methods are used to develop object-oriented software systems. Object-oriented systems are believed to habe better modularity, reusability, maintainability, and extensibility than systems modeled in conventional methods. Current object-oriented software development methods, however, are modeled in terms of procedural, functional, and structural models. There models cause problems such as tight coupling among activities, and uncontrolled access to global artifacts. In this paper, were introduce OMOS(Object-oriented software development Method for Object-oriented software System), an object-oriented modeling of object-oriented software development methods. Artifacts and their related activities are modeled as classes and objects. Development lifecycles are modeled as interactions among the objects. By modeling the software development method in an object-oriented way, OMOS achieves better reusability, flexibility, extensibility, and maintainability.

객체지향 모델은 구조적 모델에 비해 모듈성, 재사용성, 유지보수성, 확장성 등의 장점을 제공한다. 이러한 이유로 객체지향 소프트웨어 개발 방법들을 정보 시스템 개발에 광범위하게 적용되고 있다. 그러나 현재의 객체지향 소프트웨어 개발 방법들은 목적 소프트웨어 시스템의 객체지향 모델링을 지원할 뿐, 방법론 그 자체는 구조적 및 절차적 체계를 기반으로 하고 있다. 본 논문에서는 객체지향 소프트웨어 개발 방법론을 객체지향적으로 모델링한 OMOS(Object-oriented software development Method for Object-oriented software System)를 제시한다. OMOS에서는 개발 산출물과 관련된 활동이 객체로써 모델링 되며, 개발 생명주기 프로세스가 객체간의 상호작용으로 모델링 된다. 소프트웨어 개발 방법론의 객체지향적 모델링은 방법론 자체의 재사용성, 유연성, 확장성, 유지보수성의 용이성 등의 장점을 제공한다.

Keywords

References

  1. Watts S. Humphrey, Introduction to the Personal Sogwrae Process, SEI series in Software Engineering, Addison Wesley, 1997
  2. ISO, 'ISO/IES 12207 International Standards Information Technology Software Life Cycle Processes,' Aug., 1995
  3. C. Mazza, J. Faircolough, et al., Software Engineering Standards, Prentice Hall, 1994
  4. Ross D. T., Applications and Extensions of SADT, IEEE Computer, April, 1985 https://doi.org/10.1109/MC.1985.1662862
  5. Yourdon, E., Modern Structured Analysis, Yourdon Press/Prentice Hall, 1989
  6. Yourdon, E. Structured Walkthroughs, 4th edition, Engle-wood Cliffs, Prentice-Hall/Yourdon Press, 1989
  7. Timothy Budd, An Introduction to Object-Oriented Pro-gramming, Addison-Wesley, 1991
  8. Brad J. Cox, Object Oriented Programming : An Evolu-tionary Approach, Addison-Weseley, Redaing, MA. 1986
  9. Arthur Anderson & Co series, 'METHOD/1 Overview School,' 1988
  10. Martin, J., Information Engineering(3 Volumes), Prentice-Hall, 1989
  11. James Rumbaugh, Michael Blaha, William Premerlani, Frederick Eddy, and William Lorensen, Object-Oriented Modeling and Design, Prentice-Hall, 1991
  12. Grady Booch, Object-Oriented Design with Applications, Redwood City : Benjamin/Cummings, 1991
  13. Ivar Jacobson, Object-Oriented Software Engineering, Addison-Wesley, 1995
  14. Ernst & Young Navigator Systems Series, 'Accelerated System Development-Infrastructure Development,' 1995
  15. Ivar Jacobson, Grady Booch, and Jim Rumbaugh, The Unified Software Development Process, Addison-Wesley, 1999
  16. Rational Unified Process Process Manual 5.0, 'Project Management,' 1999
  17. Grady Booch, Jim Rumbaugh, and Ivar Jacobson, Unified Modeling Language Users Guide, Addison-Wesley, 1997
  18. Martin Fowler, UML Distilled : Applying the Standard Object Modeling Language, Addison-Wesley, 1997
  19. Jim Rumbaugh, Ivar Jacobson, and Grady Booch, Unified Modeling Language Manual, Addison-Wesley, 1997
  20. Mark P. Ginsberg, and Lauren H. Quinn, Process Tailoring and The Software Capability Maturity Model, CMU/SEI-94-TR-024, Technical Report, Carnegie Mellon University, 1995