In the current software project, it is still very difficult to extract and define clear requirements in the requirement engineering. Informal requirements documents based on natural language can be interpreted in different meanings depending on the degree of understanding or maturity level of the requirements analyst. Also, Furthermore, as the project progresses, requirements continue to change from the customer. This change in requirements is a catastrophic failure from a management perspective in software projects. In the situation of frequent requirements changes, a current issue of requirements engineering area is how to make clear requirements with unclear and ambigous requirements. To solve this problem, we propose to extract and redefine clear requirements by incorporating Design Thinking methodologies into requirements engineering. We expect to have higher possibilities to improve software quality by redefining requirements that are ambiously and unclearly defined.
목차
Abstract 1. Introduction 2. Related Studies 2.1 Design Thinking 2.2 Software development life cycle and requirements engineering 3. Enhancing the quality of unclear requirement specifications 4. Case study 5. Conclusion Acknowledgement References
키워드
Software EngineeringSoftware Development Life CycleDesign ThinkingRequirement EngineeringNLR
저자
Janghwan Kim [ M.S, Software Engineering Laboratory, Department of Software and Communication Engineering, Hongik University, Korea ]
Young Chul Kim [ Professor, Software Engineering Laboratory, Department of Software and Communication Engineering, Hongik University, Korea ]
Corresponding author