릴리즈 플랜의 적응적 요구사항 우선순위 프로세스
An Adjustable Process of Requirements Prioritizing for Release Plan
0
조회
0
다운로드
1
인용
0
참고문헌
키워드
초록
요구사항에 대한 우선순위는 릴리즈 플랜을 위한 핵심적 활동이기 때문에 요구공학에서 특히, 오픈 시장(Open Market)을 고객으로 하는 시장 주도형 제품개발에 있어서 중요하다. 또한, 요구사항 우선순위는 주어진 요구사항 간의 상호의존 관계를 바탕으로 프로세스 모델, 제품 종류 및 우선순위 프로세스에 대한 경험 등을 사전에 고려하여 우선순위화를 위한 방법과 관점 등을 선택하는 활동이 중요하다. 그러나, 기존 연구들은 요구사항간의 상호의존 관계를 정적 관계만 고려하였고, 고려된 관점들이 비용/가치 등으로 한정적이고 체계적인 우선순위 프로세스를 제공치 못하고 있다. 따라서 본 논문에서는 우선순위화를 위한 모델을 설계하고 개발 제품의 목표와 조직에 적합하도록 우선순위 방법과 관점 등을 선택할 수 있는 적응적 요구사항 우선순위 기법 및 프로세스를 제안한다. 특히, 요구사항간의 정적/동적 상호의존 관계 유형을 정의하고, 다양한 관점에 의한 우선순위화를 통해 릴리즈 플랜의 완성도를 높였다. 이로써 상호의존 관계 및 다양한 관점을 고려한 우선순위 모델기반의 체계적인 우선순위 프로세스를 정립하여 유연하고 충족스러운 우선순위화와 릴리즈 플랜을 통하여 합리적으로 의사결정을 도모할 수 있다.
Abstract
The priority of requirement is important because the priority is a critical activity of release plan especially in software development which has an open market customer. Also, it is important for stakeholders to select a method and aspects to prioritize requirements. The selection is based on the organizational experience of a priority process, the process model of the product, goals and a type of products, and dependencies between requirements. But, the current researches considered only static dependency between requirements and did not suggest a systematic priority process. In addition, the current researches only suggest limited aspects to prioritize requirements, such as cost and value. Therefore, this paper proposes an adjustable priority process based on a priority model to select a method and aspects for the suitable priority for product and organization. Especially, this paper enhances the completeness of a release plan by a definition of static and dynamic dependency types between requirements. This paper suggests a priority model, which considers the dependencies between requirement and various viewpoint of software development. Based on the priority model, the paper suggests a systematic priority process to promote reasonable decisions to the priority and release plan of requirement.
참고문헌 (45)
- M Khurum, "A Method for Early Requirements Triage and Selection Utilizing Product Strategies", Software Engineering Conference 2007, APSEC 2007. 14th Asia-Pacific, pp.97~104 (2007)
- Firesmith, D. G., "Prioritizing Requirements", Journal of Object Technology (JOT), 3(8), pp.35~47 (2004)
- Joachkim Karlsson, "An Evaluation of methods for prioritizing software requirements", Information and Software Technology, 39(14), pp.939~947 (1998)
- Berander, P., "Requirements Prioritization in Engineering and Managing Software Requirements", pp.69~94 (2005), Springer Verlag
- Carlshamre P., "An industrial survey of requirements interdependencies in software Release Planning", Proceedings of the 5th IEEE international symposium on requirements engineering, pp.84~91 (2001)
- Karlsson, J., "A Cost-Value Approach for Prioritizing Requirements", IEEE Software, 14(5), pp.67~74 (1997)
- Karl E. Wiegers, "Software Requirements, second edition", pp.247~258 (2003), Microsoft Press
- Berander P., "Using students as subjects in requirements prioritization", Proceedings of the 2004 International Symposium on Empirical Software Engineering(ISESE’04),, pp.167~176 (2004)
- K. Beck, "Extreme Programming Explained: Embrace Change" (2000), Addison-Wesley
- Penny D. A., "An Estimation-Based Management Framework for Enhancive Maintenance in Commercial Software Products", In Proceedings of International Conference on Software Maintenance (ICSM), pp.122~130 (2002)
- Denne, M., "The Incremental Funding Method: Data Driven Software Development", 21(3)pp.39-47, 213, pp.39~47 (2004)
- Ruhe, G., "The Science and Practice of Software Release Planning", IEEE Software (2005)
- Greer, D., "Software Release Planning: an Evolutionary and Iterative Approach", Information and Software Technology, 46(4), pp.243~253 (2004)
- Saliu O., "Supporting software Release Planning decisions for evolving systems", Proceedings of 29thIEEE, 2005, ~
- B. Regnell, "Market-Driven Requirements Engineering for Software Products", pp.287~308 (2005), Springer Verlag
- Jacobson, I., "The Unified Software Development Process", pp.94~98 (1999), Addison Wesley
- G. Ruhe, "The Art and Science of Software Release Planning", IEEE Softare, 22(6), pp.47~53 (2005)
- "IEEE Std 830-1998, IEEE recommended practice for software requirements specifications.,IEEE Computer Society, Los Alamitos", ~ (1998)
- WeiZhang, "A Feature-Oriented Approach to Modeling Requirements Dependencies", Proceedings of the 2005 13th IEEE International Conference on Requirements Engineering(RE’05), (2005)
- W. N. Robinson, "Requirements Interaction Management", ACM Computing Surveys, 35(2), pp.132~190 (2003)
- Y. Lee, "An Approach to Managing Feature Dependencies for Product Releasing in Software Product Line", in Proceeding of the 9th International Conference on Software Reuse: Reuse of Offthe- Shelf Components (ICSR 2006),, pp.27~141 (2006)
- A.G. Dahlstedt, "Requirements Interdependencies-Moulding the State of Research Into a Research Agenda", In Proceedings of Ninth International Workshop on Requirements Engineering: Foundation for Software Quality, pp.55~64 (2003)
- W. Zhang, "Feature-driven requirement dependency analysis and high-level software design", Requir. Eng, 11(3), pp.205~220 (2006)
- A.G. Dahlstedt, "“Requirements Interdependencies: State of the Art and Future Challenges,” Engineering and Managing Software Requirements", pp.95~116 (2005), Springer Berlin Heidelberg
- Karl E. Wiegers, "Karl Wiegers Describes 10 Requirements Traps to Avoid" (2000), Software Testing & Quality Engineering
- Market-Driven Requirements Engineering Processes for Software Products-a Report on Current Practices, "Dahlstedt, Å. G.", ~, pp.DoPS-03, (2003)
- 성 재석, "요구사항 우선순위 프로세스 설계", 한국정보과학회 학술발표논문집, 한국정보과학회 2008 종합학술대회 논문집, 통권 : 35, pp.13~18 (2008)
- Robertson, S., "Mastering the Requirements Process. 2nd Ed.", pp.333~ (1999), Addison-Wesley
- C. Turner, "A Conceptual basis for Feature engineering", J. Syst. Software, 49, pp.3~15 (1999)
- Dean Leffingwell, "Managing Software Requirements ; A Use Case Approach, Second Edition", pp.10~11 (2003), Addison Wesley
- Feature-Oriented Domain Analysis(FODA) Feasibility Study, "K. Kang et al.", ~, pp.tech. report CMU (1990), SEI-90-TR-21
- K.C.Kang, "FORM: A Feature-Oriented Reuse Method with Domain-Specific Reference", Architectures; Annals of Software Engineering, 5 (1998)
- J. Momoh, "Release Planning process improvement - an industrial case study", Software Process: Improvement and Practice, 11(3), pp.295~307 (2006)
- Frank Moisiadis, "The fundamental of Prioritizing Requirements, System Engineering", Test & Evaluation Conference (2002)
- 성재석, "적응적 요구사항 우선순위 기법", 한국정보처리학회 학술발표논문집, 제30회 한국정보처리학회 추계학술발표대회, 통권 : 15, pp.462~465 (2008)
- P. Berander, "Towards a Research Framework on Requirements Prioritization", SERPS 06 (2006)
- Karlsson, L., "Evaluating the practical use of different measurement scales in requirements prioritization", In: ISESE 2006. Proceedings of the 2006 ACM, 2006, 326~335[DOI]
- Karlsson, J., "Improved Practical Support for Large-scale Requirements Prioritization", Requirements Engineering Journal, 2(1), pp.51~60 (1997)
- Lehtola, L., "Empirical Evaluation of Two Requirements Prioritization Methods in Product Development Projects", Proceedings of the European Software Process Improvement Conference (EuroSPI 2004),, pp.161~170 (2004)
- Karlsson, J., "Software Requirements Prioritizing", Proceedings of the 2nd International Conference on Requirements Engineering (ICRE’96),, pp.110~116 (1996)
- Karlsson, L., "Pair-Wise Comparisons versus Planning Game Partitioning - Experiments on Requirements Prioritisation Techniques", Journal of Empirical Software Engineering, 1 (2006)
- Ahl, Viggo, "An Experimental Comparison of Five Prioritization Techniques - Investigating Ease of Use, Accuracy, and Scalability", 석사, pp.2005
- A. I. Antón, "Goal-Based Requirements Analysis", Proceedings of ICRE’96, pp.136~144 (1996)
- A. Lamsweerde, "Goal-Oriented Requirements Engineering: A Guided Tour", 5th International Symposium on Requirements Engineering, pp.249~261 (2001), IEEE Computer Society Press
- WATTS S. HUMPHREY, "Why Does Software Work Take So Long?" (1998), SEI Interactive
