Incomplete software requirements and assumptions made by software engineers
2009 16th Asia-Pacific Software Engineering Conference
333 - 339
Item Usage Stats
MetadataShow full item record
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 implementation phase deliverables, we conducted an experiment with 251 software engineers from eight companies. The results of this empirical study showed that how software engineers responded (using source code, pseudo code, or prototype) to an incomplete requirement significantly impacted the number of explicit assumptions they made. We studied relationships between the number of explicit assumptions and the engineers' experience and educational backgrounds. On average, non-computer-background engineers made more explicit assumptions than computerbackground graduates. We found a significant relationship between the engineers' experience and the number of explicit assumptions made. We discuss the results and their implications. © 2009 IEEE.
Incomplete software requirements
Published Version (Please cite this version)http://dx.doi.org/10.1109/APSEC.2009.39
Showing items related by title, author, creator and subject.
Çoban, S.; Uçar, Erkan; Chouseinoglou, Oumout; Sevgi, C.; Testik, Murat Caner (CEUR-WS, 2016)Today, Cloud Computing offers attractive and effective solutions for organizations which enable them to decrease IT costs, provide flexibility to ser-vices and make it easier to access IT services -Therefore enable faster ...
Tekinerdogan, B.; Erdoğan, Ö. Ö.; Aktuğ, O. (Elsevier Inc., 2014)The increased size and complexity of software systems has led to the notion of multiple software product lines (MPLs) in which products are composed from subproducts in separate software product lines. Thus, it is important ...
Aydın, Seçil; Mishra, D. (Springer, Berlin, Heidelberg, 2009)Software developers have been successfully tailoring software development methods according to the project situation and more so in small scale software development organizations. There is a need to share this knowledge ...