정보과학회 논문지 (Journal of KIISE)

  • 제44권5호
  • /
  • Pages.510-521
  • /
  • 2017
  • /
  • 2383-630X(pISSN)
  • /
  • 2383-6296(eISSN)
한국정보과학회 (Korean Institute of Information Scientists and Engineers)
권호 표지
DOI QR코드

DOI QR Code

OOPT: 소프트웨어공학 교육을 위한 객체지향 소프트웨어 개발 방법론

OOPT: An Object-Oriented Development Methodology for Software Engineering Education

  • 정세진 (건국대학교 컴퓨터 정보통신공학과) ;
  • 이동아 (건국대학교 컴퓨터 정보통신공학과) ;
  • 김의섭 (건국대학교 컴퓨터 정보통신공학과) ;
  • 장천현 (건국대학교 컴퓨터공학부) ;
  • 유준범 (건국대학교 컴퓨터공학부)
  • 투고 : 2017.01.12
  • 심사 : 2017.02.19
  • 발행 : 2017.05.15
⟨ 이전 논문 다음 논문 ⟩

초록

소프트웨어 개발 프로세스(Software Development Process: SDP)는 소프트웨어공학 교육에서 가장 기초적이며 중심적인 역할을 한다. 모든 소프트웨어는 개발의 시작부터 마지막까지를 모두 포함하는 특정 SDP에 기반해서 개발된다. 따라서, SDP 교육은 소프트웨어공학의 제반 기술에 대한 이해를 도울 수 있다. 본 논문은 대학의 소프트웨어공학 수업에서 활용할 수 있는 소프트웨어 개발 방법론(프로세스)인 OOPT(Object Oriented Process with Traceability)를 소개한다. OOPT는 객체지향 소프트웨어를 개발하기 위한 방법론으로서, 각 단계마다 구체적인 요구사항과 산출물을 정의하고 있으며, 단위/시스템 시험 및 추적성 분석 등의 추가적인 내용들도 포함하고 있다. 본 논문은 OOPT에 대한 적용 사례로서 다년간의 건국대학교 컴퓨터공학과 소프트웨어공학 관련 수업들을 소개하고 있으며, 향후 개선 및 발전 방향을 포함한다.

The software development process (SDP) plays an important basic role in software engineering education. Every software is developed in accordance with a specific SDP which contains all phases of software development. SDP education helps students to understand the overall techniques and the process of software engineering. This paper introduces a software development methodology (i.e., process) - 'OOPT (Object Oriented Process with Traceability),' which was proposed for use in university software engineering classes. The OOPT is based on object-oriented software development, and it defines concrete requirements as well as outputs of each process/phases. It also contains the unit/system testing and a traceability analysis. We have used the OOPT in software engineering classes at Konkuk university for eight years. This paper conveys our experience as well as future extension and improvement plans.

키워드

참고문헌

  1. P. Naur, B. Randell, "Software Engineering: A Report on a Conference Sponsored by NATO science Committee," NATO, 1969.
  2. Winston W Royce, "Managing the development of large software systems," Proceedings of IEEE WESCON, Vol. 26, No. 8, pp. 328-338, 1970.
  3. Ian Sommerville, "Software Engineering," Addison-Wesely, Boston, 2007.
  4. FA Masoud, MU Shaikh, SH Mustafa, "SASD methodology from a practical point of view problems and suggestions for improvement," WIT Transactions on Information and Communication Technologies, Vol. 17, pp. 93-102, 1997.
  5. Grady Booch, "Object-oriented Analysis and Design with Applications 3rd edition," Addison-Wesley, Boston, 2007.
  6. James Rumbaugh, Michael Blaha, William Premerlani, Frederick Eddy, William Lorensen, "Object-Oriented Modeling and Design," Prentice Hall, New Jersey, 1990.
  7. L. Jacobson, "Object-Oriented Software Engineering: A Use Case Driven Approach," Pearson Education, India, 1993.
  8. Derek Coleman, Patrick Arnold, Stephanie Bodoff, Chris Dollin, Helena Gilchrist, Fiona Hayes, Paul Jeremaes, "Object-oriented development: the fusion method," Prentice-Hall, Inc, 1994.
  9. Boehm B, "A Spiral Model of Software Development and Enhancement," IEEE Computer, Vol. 21, No. 5, pp. 61-72, 1988.
  10. Per Kroll, Philippe Kruchten, Grady Booch, "The Rational Unified Process Made Easy a Practitioner's Guide to the RUP," Addison-Wesley, Boston, 2003.
  11. Philippe Kruchten, "The rational unified process: an introduction," Addison-Wesley Professional, Boston, 2004.
  12. Michael Halling, Wolfgang Zuser, Monika Kohle, Stefan Biffl, "Teaching the Unified Process to Undergraduate Students," IEEE 15th Conference on Software Engineering Education and Training, pp. 148-159, 2002.
  13. Jiang Li, "Teaching unified process in software design and development courses - A case study," Journal of Computing Sciences in Colleges, Vol. 24, No. 5, pp. 5-11, 2009.
  14. Wilson P. Paula Filho, "An Educational Software Development Process," Proc. of the International Conference on Computer Science, Software Engineering, Information Technology, E-Business and Applications, 2002.
  15. Wilson P. Paula Filho, "Requirements for an Educational Software Development Process," ACM SIGCSE Bulletin, Vol. 33, No. 3, pp. 65-68, 2001. https://doi.org/10.1145/507758.377476
  16. P. Runeson, "Experience from teaching PSP for freshman," Proc. of the 14th conference on Software Engineering Educational and Training, pp. 98-107, 2001.
  17. N. Davis, J. Mullaney, "The Team Software Process( TSP) in Practice: A Summary of Recent Results," Technical Report CMU/SEI-2003-TR-014, Software Engineering Institute, 2003.
  18. G. Kelecic, Z. Car, "Teaching Software Process: An Experience in Implementing RUP in a Student Project," Proc. of the 8th International Conference on Telecommunications, pp. 479-484, 2005.