Optimization of software requirement process: An integrated conceptual model of lean six sigma and requirement planning

Abstract

Providing quality requirements in Software Engineering is vital to ensure the product developed is able to deploy and function to meet the operational objectives. Software Requirement Engineering is the most complex process because it involves the integration of human, logics and process. Extracting or capturing what customers need and want is called Requirement Elicitation (RE) and it is the most crucial process in requirement engineering. If handled poorly, the cost of the failures would be very expensive. Most of the software projects that failed were due to poor requirements which occurred at RE phase. Thus, enhancing and optimizing the RE methods have been subject to a long research debate to ensure quality requirements are captured. Recently, Lean Six Sigma (LSS) had emerged as part of a continuous improvement in Software Development Life Cycles (SDLC). LSS is known for a systematic and structure business improvement successfully deployed in many fields of industry that contributes a significant gain not only in quality of products and services but also in operational costs and delivery. The objective of the research is to develop an integrated conceptual framework of LSS principles with Software Requirement Engineering methodology to optimize RE process. The article will produce conceptual framework as the comprehensive guidelines to capture quality software requirements.

How can lean tools support the innovation process of SMEs?

“…The traditional PD process can be improved by a series of components, including practices and functional roles for a new lean PD process (Hoppmann et al ., 2011; Nepal et al ., 2011), and to counteract specific PD problems, such as ambiguity regarding tasks' responsibilities and project cost overruns (Tortorella et al ., 2016). On the one side, current frameworks on components of lean PD defined them according to the typology of innovation projects (Lermen et al ., 2018) or in integration with Six Sigma (Salleh and Nohuddin, 2019) and the green approach (Oliveira et al ., 2018). On the other side, more structured classifications of lean tools are based on wastes and impacts that mainly characterise the production process (Alaskari et al ., 2016; Belhadi et al ., 2018).…”

Identifying the Requirements of Visually Impaired Users for Accessible Mobile E-book Applications

“…Therefore, the results of this study may be affected and the number of collected requirements may not be enough. In addition, a single requirement gathering technique is insufficient, leading to the essential implementation of a combination of techniques to solve different types of requirements [39], [38], the study suggests implementing other requirement gathering techniques in future research, such as a case study, literature review, and experimentation, as well as increasing the number of participants.…”

“…Requirement gathering is a method used to discover features or behaviors of a system by one or more stakeholders [38]. Many research methods serve as requirement gathering methods by adopting or modifying interviews, questionnaires, observations, prototyping, task analysis, brainstorming, and laddering [39]. Interviews and questionnaires are the most used methods of system and software engineering to gather qualitative and quantitative data.…”