Canada Spends Logo

Explorez notre analyse du budget 2026

Grant: Discovery Grants Program - Individual

University of Waterloo

$36,000.00

Effects of Scope Determining and Scope Determined Requirements on the Software Development Lifecycle

EF 2024-25

Résumé
Before writing the software (SW) for any computer-based system (CBS), it is necessary to determine its requirements, in what is called requirements engineering (RE). Since no SW can be written without knowing what it is required to do, RE is inevitable even if it is done as the SW is being written. The scope of a CBS is the set of requirements that drive its implementation. Some believe that RE for a CBS should be done up front, producing a complete requirements specification before any of the CBS's SW is written. A common complaint is that (1) new requirements never stop coming; so upfront RE goes on forever with an ever growing scope. However, data show that (2) the cost to modify written SW to include a new requirement is at least 10 times the cost of writing the SW with the requirement included from the start; so upfront RE saves development costs, particularly if the new requirement is one that was needed to prevent a failure of the implementation of a requirement already included in the scope. I, colleagues, and past HQPs, who are now colleagues, have developed a hypothesis that both (1) and (2) are correct, but each is about a different kind of requirements, (1) scope determininG (G) or (2) scope determineD (D), respectively. The aim of the research is to empirically validate the hypothesis and to show that focusing RE for a chosen scope on finding all and only the D requirements for the scope, while deferring any G requirements to later releases, allows upfront RE (1) that does not go on forever, and (2) that discovers all requirements whose addition after implementation would be wastefully expensive, wasteful because these requirements are discoverable during RE if enough time is devoted to looking for them. This approach will allow more defect-free CBSs to be developed at lower costs than currently, thus saving Canada significant money in CBS development. List of Abbreviations AIartificial intelligence CBScomputer-based system MLmachine learning RErequirements engineering RSrequirements specification SLRsystematic literature review SWsoftware
Programme
Discovery Grants Program - Individual
Emplacement
Ontario, Canada
Type de bénéficiaire
Academia
Type
Grant
Source
NSERC's Awards Data

Tel que publié

Application id
RGPIN-2023-03584
Name nom
Berry, Daniel
Department département
Cheriton School of Computer Science
Organization id
33
Institution établissement
University of Waterloo
Province en
Ontario
Province fr
Ontario
Country en
CANADA
Country fr
CANADA
Fiscal year exercice financier
2024
Competition year année de concours
2023
Award amount
36000
Program id
RGPIN
Program name en
Discovery Grants Program - Individual
Program name fr
Programme de subventions à la découverte - individuelles
Group en
DISCOVERY RESEARCH
Group fr
RECHERCHE AXÉE SUR LA DÉCOUVERTE
Committee code
1507
Committee name en
Computer Science
Committee name fr
Sciences informatiques
Area of application code
801
Area of application group en
Information and communication services
Area of application group fr
Services d'information et de télécommunications
Area of application en
Computer software
Area of application fr
Logiciel
Research subject code
2706
Research subject group en
Information technology
Research subject group fr
Technologie de l'information
Research subject en
Software engineering
Research subject fr
Génie logiciel
Field of research list names en
Not available
Field of research list names fr
Non disponible
Socioeconomic objective list names en
Not available
Socioeconomic objective list names fr
Non disponible
Application title
Effects of Scope Determining and Scope Determined Requirements on the Software Development Lifecycle
Keywords
requirements engineering; software engineering; software development lifecycle; waterfall methods; agile methods; requirements specification; missing requirement; scope of a development or sprint; scope-determining requirement; scope-determined requirement
Application summary
Before writing the software (SW) for any computer-based system (CBS), it is necessary to determine its requirements, in what is called requirements engineering (RE). Since no SW can be written without knowing what it is required to do, RE is inevitable even if it is done as the SW is being written. The scope of a CBS is the set of requirements that drive its implementation. Some believe that RE for a CBS should be done up front, producing a complete requirements specification before any of the CBS's SW is written. A common complaint is that (1) new requirements never stop coming; so upfront RE goes on forever with an ever growing scope. However, data show that (2) the cost to modify written SW to include a new requirement is at least 10 times the cost of writing the SW with the requirement included from the start; so upfront RE saves development costs, particularly if the new requirement is one that was needed to prevent a failure of the implementation of a requirement already included in the scope. I, colleagues, and past HQPs, who are now colleagues, have developed a hypothesis that both (1) and (2) are correct, but each is about a different kind of requirements, (1) scope determininG (G) or (2) scope determineD (D), respectively. The aim of the research is to empirically validate the hypothesis and to show that focusing RE for a chosen scope on finding all and only the D requirements for the scope, while deferring any G requirements to later releases, allows upfront RE (1) that does not go on forever, and (2) that discovers all requirements whose addition after implementation would be wastefully expensive, wasteful because these requirements are discoverable during RE if enough time is devoted to looking for them. This approach will allow more defect-free CBSs to be developed at lower costs than currently, thus saving Canada significant money in CBS development. List of Abbreviations AIartificial intelligence CBScomputer-based system MLmachine learning RErequirements engineering RSrequirements specification SLRsystematic literature review SWsoftware