The Journal of the Institute of Internet, Broadcasting and Communication (한국인터넷방송통신학회논문지)

The Institute of Internet, Broadcasting and Communication (한국인터넷방송통신학회)
권호 표지
DOI QR코드

DOI QR Code

Life Cycle Model of Over lapped-Concur rent Software

중첩-동시개발 소프트웨어의 생명주기 모델

  • 최명복 (강릉원주대학교 멀티미디어공학과) ;
  • 한태용 (강릉원주대학교 여성인력개발학과) ;
  • 이상운 (강릉원주대학교 멀티미디어공학과)
  • Received : 2014.02.06
  • Accepted : 2014.04.11
  • Published : 2014.04.28
Download PDF
⟨ Previous Next ⟩

Abstract

Though a dozen of different software life cycle models are suggested, there is no universal model which can satisfy all the characteristics of software. Organizations mix and match different life cycle models to develop a model more tailored for their systems and capabilities. We suggest overlapped-concurrent development life cycle model that is more suitable in various software development environment. Firstly, we divided the development process into abstract and implementation stage. Abstract stage is from software concept phase to detailed design starting time, and implementation stage is from detailed design phase to system testing phase. Next, the abstract stage introduced the overlapped phase concept that begins the next phase when the step is completed 20% by applying pareto's law. In the implementation stage, we introduced the concurrent development which the several phases are performed some time as when one use-case (UC) is completed the next development phase is started immediately. The proposed model has an advantage that it can reduce the inefficiency of development resource greatly. This model can increase the customer satisfaction with a great product at a low cost and on a short schedule. Also, this model can contribute to increase the software development success rate.

소프트웨어 프로젝트에 대해 12개의 다른 소프트웨어 생명주기 모델들이 제안되었지만 모든 소프트웨어의 특성을 만족시킬 수 있는 일반화된 모델이 없는 실정이다. 개발조직은 여러 모델들을 적절히 혼합하여 개발될 시스템과 능력에 맞도록 새로운 모델을 개발하여야만 한다. 본 논문에서는 다양한 소프트웨어 개발 상황에 보다 적합할 것으로 판단되는 중첩-동시개발 생명주기 모델을 제안하였다. 먼저, 개발 과정을 추상화와 구현으로 구분하여 추상화는 개념정립단계부터 상세설계단계 시작시점까지로, 구현은 상세설계단계부터 시스템 시험단계로 분류하였다. 다음으로, 추상화는 파레토 법칙을 적용하여 하나의 단계에서 개발될 기능이 20% 진행된 시점에서 다음 단계를 시작하는 중첩된 단계 개념을 도입하였다. 구현은 하나의 UC가 완료되면 바로 다음 단계 수행 팀에게 전달하여 여러 단계가 동시 수행되어 개발하는 형태를 도입하였다. 제안된 모델은 개발자원 활용의 비효율성을 크게 줄일 수 있는 장점이 있다. 제안된 모델을 적용시 보다 빠른 시간에 보다 저렴한 비용으로 보다 좋은 품질의 소프트웨어를 개발하여 고객에게 납품할 수 있어 고객을 만족도를 향상시킬 수 있으며, 더불어 소프트웨어 개발 성공률을 높이는데도 기여할 것으로 판단된다.

Keywords

References

  1. A. Kushniruk, "Rapid Development: Lifecycle Planning," Department of Mathematics & Statistics, http://www.math.yorku.ca/-andrek/ITEC-4010/ITEC4010-8.ppt, 1996.
  2. S. McConnell, "Rapid Development," Microsoft Press, 1996.
  3. J. Mohr, "The Software Life Cycle," http://www.augustana.ab.ca/mohrj/courses/2005.fall/csc220/, Augustana Faculty, University of Alberta, Canada, 2005.
  4. C. Wallin and R. Land, "Software Development Lifecycle Models: The Basic Types," Research Methodology for Computer Science and Engineering, 2001.
  5. J. J. Kuhl, "Project Lifecycle Models: How They Differ and When to Use Them," Business eSolution, http://www.business-esolutions.com/islm.htm, 2002.
  6. S. Huitsing, "Lifecycle Models," http://faculty.washington.edu/sharonh0/UW-HIA421/, UW Computing & Communications, 2001.
  7. K. Curran, "Project Management: Project Lifecycle Planning," http://www.infm.ulst.ac.uk/kevin/com820/week3.ppt, University of Ulster, Magee Collage, N. Ireland, 2005.
  8. R. Sorensen, "A Comparison of Software Development Methodologies," http://www.stsc.hill.af.mil/crosstalk/1995/01/Comparis.asp, 1995.
  9. M. Kropp, "The Software Process: Life-Cycle Models," Fachhochschule Solothurn/NWS, http://swe.fhso.ch/modules/ch02-softwareProcess/ch02_lcm.pdf, 2003.
  10. S. Cohen, "Software Life Cycles," Electrical & Computer Engineering, University of Pittsburgh, http://j7.ee.pitt.edu, 2005.
  11. K. Owens, "Software Management Planning Guide: Software Milestone Reviews," Ver. 1.0, Jet Propulsion Lab., 1995.
  12. R. L. Kumar, "Alternative Systems Development Methodologies, Enterprise Systems, Implementation Issues," http://www.bwlkcollege.uncc.edu/rlkumar/course/8200/altmethods.ppt
  13. Hanu Software, "Development Life Cycle Models," http://www.hanusoftware.com/p_2_1.html, 2003.
  14. T. Sloan, "Development Models," http://www.nesc.ac.uk/talks/Wodsmes/day3/dev-models.pdf, National e-Science Centre , 2002.
  15. M. Kochanski, "Software Process," Computing & Software Systems, University of Washington, 2005.
  16. J. Kontio, "Software Engineering Process," Helsinki University of Technology, http://www.cs.hut.fi/Opinnot/Tik-76.601/, 2000.
  17. R. Lewallen, "Software Development Life Cycles Model," http://codebetter.com/blogs/raymond.lewallen/archive/2005/07/13/129114.aspx, 2005.
  18. N. B. Priyanto, "Software Project Management: Planning," Computer Science at University of Indonesia, 2005.
  19. S. R. Schach, "Object-Oriented and Classical Software Engineering," McGrew-Hill, 2002.
  20. M. Ardis, "Software Lifecycle Models," http://www.rose-hulman.edu/class/cs/csse372/Lectures/CSSE372-041214-Lifecycle.ppt,Rose-Hulman Institute, 2004.
  21. A. Sivaran, "Agile Methods and Its Principles," http://www.developeriq.com/articles/view-article.php, DeveliperlQ Magazine, 2004.
  22. J. F. Dooley, "Life Cycle Models," http://deptorg.knox.edu/CS322/322PDFLectures/L2LifeCycle.pdf, KNOX College, 2005.
  23. S. Thomas, "Problems, Solutions, More Process Models," http://users.ev1.net/-Ryoga/6351/I5.pdf, 2000.
  24. R. Johnson, "Alternate Approaches to System Building, "http://www.bus.ucf.edu/rjohnson/ISM6121/Lectures/alternatives.pdf, ISM 6121, 2005.
  25. J. M. Demasco, "Software Life Cycle Models," http://www.apl.3hu.edu/lasses/Notes/Demasco/605704/SoftwareLifeCycles.pdf, Johnson Hopkins University, 2001.
  26. G. Booker, "Software Project Management: Life Cycle Models," http://users.snip.net/-gbooker/INFO638/lect3.ppt, 2005.
  27. J. Borg, "Development Methodologies - An Overview," http://www.kep3.de/en/30Series/60SwDevelopment/Articles/P_DevMethod.html, KEP3, 2002.
  28. M. Kathrin, "The Key Elements of an Iterative Software Development Process," Department of Computer Science, University of Salzburg, 2002.
  29. Standish Group, "Extreme CHAOS," The Standish Group International, Inc., 2001.
  30. D. F. Rico, "Using Cost Benefit Analysis to Development Software Process Improvement(SPI) Strategies," http://www.dacs.dtic.mil/techs/RICO/2-6cycles.shtml
  31. I. Spench and K. Bittner, "What is Iterative Development," http://www-128ibm.com/developerworks/rational/library/mar05/bittner/, The Rational Edge, 2005.
  32. P. McBreen, "Incremental Requirements Capture," XProgramming.com, 1999.
  33. A. Crain, "Overlapping Iterations in a RUP-based Projects, http://www-106.ibm.com/developerworks/rational /library/may05/crain/, The Rational Edge, 2005.
  34. R. Koch, "The 80/20 Principle: The Secret to Success by Achieving More with Less," Amazon.com, 1999.
  35. B. A. Will, "Software Risk Management," http://www.paroxys.com/SoftwareRiskManagement/SoftwareRiskManagement.html, 2004.
  36. Surge Works, "Succeed Fast and Reap Business Benefits four Times Faster with SurgeWorks Software Development," 2004.
  37. J. B. Park, H. S. Yang, "Quality Evaluation Method of Open Source Software," Journal of the Korea Academia-Industrial, cooperation Society, Vol. 13, No. 5 pp. 2353-2359, 2012. https://doi.org/10.5762/KAIS.2012.13.5.2353
  38. D. S. Kim, H. C. Kim, "The Study of Software Reliability Model from the Perspective of Learning Effects for Burr Distribution," Journal of the Korea Academia-Industrial Cooperation Society, Vol. 12, No. 10 pp. 4543-4549, 2001. https://doi.org/10.5762/KAIS.2011.12.10.4543