A study to observe relations between software engineers' responses to incomplete requirements and requirements volatility
International Conference on Software Engineering Theory and Practice 2009, SETP 2009
1 - 7
Item Usage Stats
MetadataShow full item record
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.
KeywordsDesign and implementations
Software development process
Software requirements specifications
Permalink (Please cite this version)http://hdl.handle.net/11693/28622
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, Ö. (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 ...
Albayrak Ö.; Kurtoǧlu H.; Biçakçi, M. (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 ...
Albayrak, Ö.; Albayrak, D.; Kiliç, T. (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 ...