An Empirical Study of Requirements Acquisition Process
0
조회
0
다운로드
0
인용
0
참고문헌
키워드
초록
Requirements acquisition is a very important process when IT development project development process. The incorrect requirements acquisition occupies over 50-percent of project failure. In requirements engineering process, the requirements acquisition is the most important phase. The existing researches for requirements engineering do not present the detailed tasks, artifacts and techniques. Moreover the researches are inconsistent. Accordingly, requirements engineers are confused and have trouble in using the techniques. To solve the problem, new process for requirements acquisition based on the existing processes is proposed in this paper. The proposed requirements acquisition process consists of 5 activities and 17 tasks. This paper verifies the validity and efficiency of the proposed process through the empirical comparision with the existing researches using a statistical technique. The proposed process is used in the system analysis or system specification phase as the key information. It is also used to develop the CASE tool for requirements engineering as the base information.
Abstract
Requirements acquisition is a very important process when IT development project development process. The incorrect requirements acquisition occupies over 50-percent of project failure. In requirements engineering process, the requirements acquisition is the most important phase. The existing researches for requirements engineering do not present the detailed tasks, artifacts and techniques. Moreover the researches are inconsistent. Accordingly, requirements engineers are confused and have trouble in using the techniques. To solve the problem, new process for requirements acquisition based on the existing processes is proposed in this paper. The proposed requirements acquisition process consists of 5 activities and 17 tasks. This paper verifies the validity and efficiency of the proposed process through the empirical comparision with the existing researches using a statistical technique. The proposed process is used in the system analysis or system specification phase as the key information. It is also used to develop the CASE tool for requirements engineering as the base information.
참고문헌 (18)
- M. Sue White, "Requirements : A quick and inexpens ive way to improve testing", pp.5~6 (1994), Test Techniques Newsletter, Software Research
- Ivy F. Hooks, "Customer-Centered Products" (2001), AMACOM
- Daniel Galin, "Software Quality Assurance" (2004), Addison Wesley
- IEEE, "IEEE Recommended Practice for Software Req uirements Specifications" (1998), IEEE
- G. Kotonya, "Requirements Engin eering: Processes and Techniques" (2000), John Willey and Sons
- W.G. Vincenti, "What Engineers Know and How They Know It – Analytical Studies from Aeronautical History" (1990), John Hopkins University Press
- R.S. Pressman, "Software Engineering A Practitioner’s Approach" (2005), McGraw-Hill
- R.S. Pressman, "Web Engineering A Practitioner’s Approach" (2007), McGraw-Hill
- S. Robertson, "Mastering the Requirements Process" (2006), Addition Wesley
- K. Wiegers, "Software Requirement" (2003), Microsoft Press
- Elizabeth H., "Requirement Engineering" (2005), Springer
- K.C. Kang, "Issues in Requirements Elicitation", pp.1992, CMU
- Ian Sommerville, "Viewpoint: princi ples, problems and a practical approach to require ments engineering", Annals of Software Engineering, 3, pp.101~130 (1997)
- Alan Davis, "Just Enough Requirements Managem ent: where software development meets marketing" (2005), Dorset House Publishing
- Kevin Brennan, "A Guide to the Business Analysis Body of Knowledge Version 2. 0" (2009), IIBA
- CMMI Product Team, "CMMI for development, vers ion 1.2" (2006), Software Engineering Institute
- A Study of Requirement Gathering Proces, "Iw Choi", KIPM, 149~157 (2016)
- Kano Noriaki, "Attractive Quality and Must-Be Quality", Journal of the Japanese Society for Quality Control, 14(2), pp.39~28 (1984)