Incomplete software requirements and assumptions made by software engineers
Proceedings - Asia-Pacific Software Engineering Conference, APSEC
333 - 339
MetadataShow full item record
Please cite this item using this persistent URLhttp://hdl.handle.net/11693/28635
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.
Showing items related by title, author, creator and subject.
Tekinerdogan B.; Erdoğan O.O.; 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 ...
Çoban S.; Uçar E.; Chouseinoglou O.; Sevgi C.; Testik M.C. (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 ...
Gürbüz H.G.; Tekinerdogan, B.; Pala Er, N. (Springer Verlag, 2014)Various software architecture viewpoint approaches have been introduced to model the architecture views for stakeholder concerns. To address quality concerns in software architecture views, an important approach is to ...