Lessons learned from applying the spiral model in the software requirements analysis phase

Abstract

Summary form only given, as follows. Boehm's spiral model is currently gaining popularity over the traditional waterfall software development model. The spiral model is a risk-driven approach. The process steps are determined by the need to resolve the high-risk situations-ones that have greatest chance to ruin the project. This approach contrasts with traditional document-driven approach where the process step is determined by the type of document that has to be submitted. Over a period of two years, the author applied the spiral model approach in the requirements analysis phase for four projects. These projects were with different sectors of the Thai government. The author was the head of the requirement analysis team for three projects and was responsible for quality assurance in one project. The author's experience reveals factors that foster the spiral approach's success in requirement analysis as well as factors that inhibit its effectiveness. Some of these factors include the Thai culture, governmental regulations, the educational background of the requirement engineers, the governmental employees' understanding of requirements analysis, terms in the contract, etc. The experience also reveals the risks in conducting software requirements analysis in a country that endures shortages of software engineers.