요구사항 획득 프로세스에 대한 연구 = A Study of Requirement Gathering Process

다국어 초록 (Multilingual Abstract)

Requirements acquisition process is very important in the IT project development process. Over 50% of the project failure results from incorrect acquisition of requirements. Requirements acquisition is the most important step in the requirements engineering process. Many researches for the requirement engineering process were performed, but the tasks/artifacts/techniques of the requirement acquisition phase are not concrete and the consistency is not maintained among the researches. This intensifies the confusion of the requirements engineer, and it is difficult to be materially used because the concrete technique doesn't exist. This paper proposes new requirements acquisition process which consists of 5 activities and 17 tasks based on the existing requirements engineering processes in order to get requirements efficiently. The efficiency and feasibility of the proposed activities and procedures is verified by comparing with the existing researches using the statistical method. The proposed requirements acquisition process is utilized as core information in the system analysis or specification phase.

참고문헌 (Reference)

1 W.G. Vincenti, "What Engineers Know and How They Know It – Analytical Studies from Aeronautical History" John Hopkins University Press 1990

2 R.S. Pressman, "Web Engineering A Practitioner’s Approach" McGraw-Hill 2007

3 Ian Sommerville, "Viewpoint: princi ples, problems and a practical approach to require ments engineering" 3 : 101-130, 1997

4 Per Kroll, "The Rational Unified Process Made Easy : A Practitioner's Guide to the RUP" Addison-Wesley 2003

5 Lonnie D. Bentley, "System An alysis and Design for the Global Enterprise seventh edition" McGraw-Hill 2007

6 K. Wiegers, "Software Requirement" Microsoft Press 2003

7 Daniel Galin, "Software Quality Assurance" Addison Wesley 2004

8 R.S. Pressman, "Software Engineering A Practitioner’s Approach" McGraw-Hill 2005

9 G. Kotonya, "Requirements Engin eering: Processes and Techniques" John Willey and Sons 2000

10 M. Sue White, "Requirements : A quick and inexpens ive way to improve testing"

11 Elizabeth H., "Requirement Engineering" Springer 2005

12 S. Robertson, "Mastering the Requirements Process" Addition Wesley 2006

13 Alan Davis, "Just Enough Requirements Management: where software development meets marketing" Dorset House Publishing 2005

14 K.C. Kang, "Issues in Requirements Elicitation" CMU/SEI 1992

15 IEEE, "IEEE Recommended Practice for Software Requirements Specifications"

16 Ivy F. Hooks, "Customer-Centered Products" AMACOM 2001

17 Standish Group, "CHAOS Report" Standish Group 1995

18 Kevin Brennan, "A Guide to the Business Analysis Body of Knowledge Version 2. 0" IIBA 2009