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

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

DOI QR Code

An Establishment of the Process System for Software Requirements Engineering

소프트웨어 요구공학에 대한 처리 시스템 정립

  • Lee, Sang-Un (Dept. of Multimedia Eng., Gangneung-Wonju National University) ;
  • Choi, Myeong-Bok (Dept. of Multimedia Eng., Gangneung-Wonju National University)
  • 이상운 (강릉원주대학교 멀티미디어공학과) ;
  • 최명복 (강릉원주대학교 멀티미디어공학과)
  • Received : 2013.08.20
  • Accepted : 2014.02.07
  • Published : 2014.02.28
Download PDF
⟨ Previous Next ⟩

Abstract

This paper proposes a optimal process after analyzing the existing papers of software requirements engineering process. In analyzing it examines requirement pursuit management and origin, and considers a variety of starting points that draw requirement documents. Also, this paper considers carefully the multiple methods of stakeholder needs, problem analysis, processing priority of business modeling. From the analyzed result this paper proposes the best method that draws systematically the requirement documents. The proposed method can minimize the requirement changes, draw the higher project success ratio, and satisfy the customer.

본 논문은 지금까지 제안된 요구사항 공학과정을 체계적으로 분석하고 최적의 과정을 제안하였다. 세부적으로는 요구사항 추적관리와 기원을 살펴보고, 요구사항 명세서를 도출하는 다양한 출발점 (고객이 제시한 요구사항 명세서로부터, 요구사항 도출로부터, 문제분석으로부터, 비즈니스 모델링부터)을 고찰하였다. 또한, 이해 당사자 욕구 도출, 문제 분석, 비즈니스 모델링의 수행 우선순위에 대한 다양한 방법을 고찰하였다. 이들 결과로부터 "전산화 목표 파악, 비즈니스 프로세스 파악, 비즈니스 모델링, 문제분석, 이해당사자 욕구 도출, 시스템 특징 도출, 요구사항 도출, 요구사항 명세와 검증" 과정을 수행하는 것이 가장 체계적으로 요구사항 명세서를 도출하는 과정임을 제안하였다. 이 방법을 적용하면 개발단계에서 관리하면 개발단계에서의 요구사항 변경을 최소화 시키고 프로젝트 성공률을 향상시킬 수 있으며, 고객의 만족도도 향상시킬 수 있을 것이다.

Keywords

References

  1. E. Dijkstra, "The Humble Programmer," Communications of the ACM, 1972.
  2. B. Lewis, "The 70-Percent Failure," Infoworld. http://archive.infoworld.com/articles/op/xml/01/10/ 29/011029/opservival.html, 2003.
  3. Standish group, "The CHAOS Report,"http://ww w.standishgroup. com/sample/PDFpages/chaos1994. pdf, 1994.
  4. G. L. Ray, "IS 2510 Information Systems: The Requirements Problem," Department of Information Science, School of Information Sciences, University of Pittsburgh, http://www.sis.pitt.edu/-gray/ INFSCI2510/PowerPoints/ 01Lecture.ppt, 2005.
  5. IEEE, "IEEE STD 610.12-1990 IEEE Standard Glossary of Software Engineering Terminology," http://standards.ieee.org/reading/ieee/std_public/ description/se/610.12-1990_desc.html,IEEE-SA, 2004.
  6. I. Sommerville and P. Sawyer, "Requirements Engineering: A Good Practice Guide," John Wiley and Sons Ltd., 2000.
  7. J. Suen, "ELEC3605: Engineering Software Requirements," http://www.users.on.net/-jsuen/ elec3605_chp_summ_ts. doc, Sydney University, 2005.
  8. R. Hossenlopp, "Diagnostic Modeling in Business Analysis: Solving the Right Problem is Key to Project Success," ESI International Inc., 2004.
  9. K. Wiegers, "Software Requirements 2nd Edition," Microsoft Press, 2003.
  10. J. Brackett, "Software Requirements Engineering Overview," Requirements Engineering course material, Software Engineering Institute, Carnage Melon University, Pittsburgh, PA. 1992.
  11. M. G. Matthews, "Software Requirements and Specification," http://mason.gmu.edu/-mmatthe1/ Fall01/CourseOverview.pdf, The George Mason University, 2001.
  12. D. Leffingwell and D. Widrig, "Managing Software Requirements," Addison-Wesley, 2000.
  13. S. McEwen, "Requirements: An Introduction," http://www-128.ibm.com/developerworks/rational /library/4166.html, The Rational e-zine, 2004.
  14. O. Ormandjieva, "SOEN 342 Software Requirements and Specifications," Department of Computer Science and Software Engineering, Concordia University, 2006.
  15. O. Gotel and A. Finkelstein, "An Analysis of the Requirements Traceability Problem," Proceedings of the IEEE International Conference on Requirements Engineering, pp: 94-102, Colorado Springs, Colorado, 1994.
  16. K. Bittner and I. Spence, "Establishing the Vision for Use Case Modeling," http://www.awprofessional /articles/article.asp, Addison Wesley Professional, 2002.
  17. A. Holub, "The OO Design Process: Beginning to Design Software," The Rational E-zine, 2000.
  18. B. Nuseibeh and S. Easterbrook, "Requirements Engineering: A Roadmap," http://www.doc.ic.ac.uk/ -ban/pubs/sotar.re.pdf, ICSE, 2000.
  19. A. Cahill, "CS5702 Software Engineering Requirements: Requirements Elicitation Sources of Requirements," Department of Computer Science and Information Systems, University of Limerick, 2004.
  20. R. R. Young, "Implementing Effective Requirements Practices," Systems and Process Engineering, Northrop Grumman Information Technology, http://www.ralphyoung.net/publications/ ImplementingEffReqPractices.ppt,
  21. E. Whitney, "An Introduction to Gathering Requirements, Creating Use Cases and the UML," http://www.eps-software.com/download/whitepaper_the_devel opment_process. pdf , Component Developer (CoDe) Magazine, 2001.
  22. J. Huang, 'Software Requirements," School of Computer Science, Telecommunications, and Information Systems, Depaul Universit, http://facweb.cs depaul.edu/jhuang/se681/ CSDP_RE.pdf, 2004.
  23. R. Offen, "ITEC 821: Requirements Engineering," Division of Information and Communication Sciences, Macquire, http://www.comp.mq.edu.au/ units/itec821/ITEC821_s104_week1.pdf, 2004.
  24. A. Finkelstein, "Requirements Engineering Research: Coordination and Infrastructure," Requirements Engineering, Vol. 1, pp: 63-69, 1996. https://doi.org/10.1007/BF01235766
  25. S. Feldman, "SE031 - Software Engineering: Application Requirements Determination," http://www.cs.bgu.ac.il/-se031/Slides/Lecture /select2_02.pdf, 2002.
  26. Wikipedia, "The Free Encyclopedia," http://en.wikipedia.org/wiki/main_page.Wikimedia Foundation, 2007.
  27. N. Iyengar, K, Kapoor, J, S, Greenstein, and K. Gramopadhye, "Data Gathering Methodologies to Identify Impact Variables in Aviation Maintenance," Human Computer Systems Lab., Department of Industrial Eng., Clemson University, http://www.hf.faa.gov/docs/508/docs/maintlERC2004WebSAT2.pdf, 2004.
  28. S. Giacoppo, "Development Methods: User Needs Assessment & Task Analyses," Department of Psychology, Catholic University, 2001.
  29. R. Baghai, "Requirements Management: Building Quality from the Beginning," Rational Software Corporation, http://www. seasim.org/archive/sim92001e.pdf, 2002.
  30. S. W. Ambler, "Agile Requirements Modeling," http://www.agilemodeling.com/essays/agileRequirements.htm, Ambysoft Inc., 2006.
  31. RIT, "Why is Developing Software Hard?," Rochester Institute of Technology, http://www.se. rit.edu/-se361/Slides/ TJR-Requiremetns.pdf
  32. A. U. Rehman, "Requirement Engineering," http://www. feditec.com/downloads/RequirementEngg. ppt, Feditec Enterpise, 2005.
  33. K. Pohl, "Process Centered Requirements Engineering," John Wiley & Sons, Ltd., 1996.
  34. P. Darke, "ISM9110 - Systems Analysis and Design: Information Gathering for Information Systems Development," School of Information Management and Systems, Monash University, 2005.
  35. Z. Zhu, "Requirements Determination and Requirements Structuring," http://www.umsl.edu/ -sauter/analysis/6840 _f03_papers/zhu/, Information Systems, College of Business Administration, University of Missouri, 2003.
  36. U. Magsarjav, "Requirements Documents Evolution and Synchronization with Activities in the Refined Requirements Generation Model," Master of Science in Computer Science and Applications, Blacksburg, Virginia University, 2004.
  37. S. P. Maliyakkal, "Requirements Elicitation," Methoden und Werkzeuge zur Softwareproduktion, 1998.
  38. B. Bruegge and A. H. Dutoit, " Object-oriented Software Engineering: Conquering Complex & Changing Systems," Prentice Hall, 2000.
  39. D. C. Gause and G. M. Weinberg, "Are Your Lights On? How to Know What the Problem Really Is," Dorset House Publishing, New York, 1989.
  40. L. Probasco, "The Ten Essentials of RUP: The Essence of an Effective Development Process," http://www.devarticles.com/ c/a/Development-Cycles /The-Ten-REssentials-of-RUP/, IBM Corporation, 2001.
  41. A. Davis, "Software Requirements: Objects, Functions, and States," Prentice-Hall, 1993.
  42. D. Leffingwell. "Features, Use Cases, Requirements, Oh My!," http://www.download. boulder.ibm.com/ibmdl/pub/software/dw/rationaledge/ dec00/FeaturesUseCasesRequirementsOhMyDoc00. pdf, The Rational Software, 2000.
  43. A. Cofod, "System Analysis," Computer Science Instructor, Business Division, San Juaguin Delta Community College, 2005.
  44. H. Krasner, "Requirements Dynamics in Large Software Projects: A Perspective on New Directions in the Software Engineering Process," 11th World Computer Congress (IFIP89), Elsevier, New York, 1989.
  45. G. Kotonya and I. Sommerville, "Requirements Engineering: Processes and Techniques," John Wiley and Sons, 2000.
  46. G. Kotonya and I. Sommerville, "Requirements Elicitation and Analysis," http://www.compapp.dcu.ie/-nbrophy/ca222/week4_6/som3.pdf, 1998.
  47. A. S. Sidky, R. R. Sud, S. Bhatia, and J. D. Arthur, "Problem Identifiaction and Determination Within the Requirements Generation Process," Department of Computer Science, Virginia Tech, 2002.
  48. H. E. Eriksson and M. Penker, "Business Modeling with UML," http://www.therationaledge.com/ rosearchitect/mag/archives/fall99/f15.html, The Rational E-zine, 1999.
  49. B. Baker, "Business Modeling with UML: The Light at the End of the Tunnel," http://www.therationaledge.com/content/dec_01/m_businessModeling_bb.html, The Rational E-zine, 2001.
  50. Rational Software, "Business Modeling with the UML and Rational Suite AnalystStudio," A Rational Software White Paper, 2002.
  51. P. W. Ng, "Business Process Modeling and Simulation with UML," http://www.therationaledge.com/content/apr_02/t_businessProcessModeling_pn.jsp, The Rational E-zine, 2002.
  52. B. Roggio, "CSCI 630 Software Engineering: Business Modeling - Domain Analysis," http://www.ecst.csuchico.edu/-broggio/8.Domain Modeling(B027).ppt, 2005.
  53. E. Ritter, "Fundamentals of Computer Science: Software Requirements," http://www.cs.bham.ac.uk /-exr/teaching/lectures/se/04/Requirements.pdf, School of Computer Science, University of Birmingham, 2004.
  54. A. V. Lamsweerde, R. Darimont, and E. Letier, "Managing Conflicts in Goal-driven Requirements Engineerin," IEEE Trans. on Software Eng., Vol. 24, No. 11, pp. 908-926, 1998. https://doi.org/10.1109/32.730542
  55. 강문석, "시스템 분석 및 설계," 정익사, 2004.
  56. J. Amsden, "Business Services Modeling," http://www128.ibm.com/developerworks/rational /library/05/1227_amsden/index.html, Rational E-zine, 2005.
  57. V. Muchandi, "Establishing Traceability - From Requirements to Design," First Software Services, http://www.fcg.com/ EK_Images/FCG/Technology/ FCGSS_WP_Trace-ability_022306.pdf, 2006.
  58. K. Eustace, "SME Business Modeling Advice for Client- Server Application Developers," School of Information Studies, Charles Sturt University, http://www.csu.edu.au/faculty/sis/subjects/itc382 /sme.doc, 2006.
  59. J. Heumann, "Introduction to Business Modeling Using the Unified Modeling Language (UML)," http://www-128.ibm.com/developerworks/rational /library/360.html, The Rational E-zine, 2003.
  60. G. Booker, "INFO 627 Requirements Engineering and Management: Analyzing the Problem," http://users.snip.net/-gbooker/INFO627/lect2.ppt, Drexel University, 2003.
  61. J. Zdravkovic, "Identifying Problems," http://www.hig.se/ -jzc/isa/isal_2.pdf, Computer Science Department, Ga"vle University, 2006.
  62. S. U. Lee, M. B. Choi, "A Definition and Evaluation Criteria for Software Development Success," Journal of The Institute of Internet, Broadcasting and Communication (IIBC), pp.233-241, vol. 12, no.2, April 2012. https://doi.org/10.7236/JIWIT.2012.12.2.233
  63. 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, 2011. https://doi.org/10.5762/KAIS.2011.12.10.4543

Cited by

  1. A study on Deployment of the Optimized WBS and Effective Small and Medium Enterprise Informatization System using Standardized PSDM vol.14, pp.6, 2014, https://doi.org/10.7236/JIIBC.2014.14.6.199
  2. An Automatic code generation through UML Meta modelling and transformation of Model for electronic government framework vol.16, pp.5, 2015, https://doi.org/10.5762/KAIS.2015.16.5.3407
  3. Study of Problem Design for PBL in Creative Engineering Design Subject vol.15, pp.8, 2014, https://doi.org/10.5762/KAIS.2014.15.8.5242
  4. A Case Study of Software Development Quality Improvement by Agile Methodology and MDA/MDD Technology vol.16, pp.4, 2015, https://doi.org/10.5762/KAIS.2015.16.4.2744