A study to observe relations between software engineers' responses to incomplete requirements and requirements volatility
Date
2009Source Title
International Conference on Software Engineering Theory and Practice 2009, SETP 2009
Pages
1 - 7
Language
English
Type
Conference PaperItem Usage Stats
115
views
views
18
downloads
downloads
Abstract
For high quality software, software requirements must be complete. In practice, not all software requirements are complete. In case of incomplete software requirements, software engineers fill in the requirements' gaps by getting feedback from the stakeholders or by making explicit or implicit assumptions. Explicit assumptions can be validated during analysis, while implicit assumptions validation is carried to design and implementation. Thus, compared to implicit assumption, explicit assumptions are better. Software requirements specifications change during different phases of project life-cycle. In an attempt to improve software development processes, we conducted an empirical study to search possible relationships between the number of implicit assumptions made by software engineers and requirements' volatility. This practice paper presents data from three completed projects at one CMMI level 3 company. Within the limit of our data set, our experience shows that possible relationships between projects' requirements volatility and the number of implicit assumptions are worth studying.
Keywords
Design and implementationsEmpirical studies
High-quality software
Requirements volatility
Software development process
Software engineers
Software requirements
Software requirements specifications
Engineers
Requirements engineering
Software engineering
Permalink
http://hdl.handle.net/11693/28622Collections
- Work in Progress 354
Related items
Showing items related by title, author, creator and subject.
-
An experiment to observe the impact of UML diagrams on the effectiveness of software requirements inspections
Albayrak, Özlem (IEEE, 2009)Software inspections aim to find defects early in the development process and studies have found them to be effective. However, there is almost no data available regarding the impact of UML diagram utilization in software ... -
Incomplete software requirements and assumptions made by software engineers
Albayrak, Özlem; Kurtoǧlu, Hülya; Biçakçi, M. (IEEE, 2009)Many software engineers make implicit assumptions when working with incomplete software requirements. To study assumptions made by software engineers while converting incomplete requirements to software design or to ... -
Are software engineers' responses to incomplete requirements related to project characteristics?
Albayrak, Özlem; Albayrak, Duygu; Kiliç, T. (IEEE, 2009)Software requirements quality affects software product quality. For high-quality software products, software requirements must be complete. When faced with incomplete requirements, software engineers attempt to fill the ...