An experiment to observe the impact of UML diagrams on the effectiveness of software requirements inspections
2009 3rd International Symposium on Empirical Software Engineering and Measurement, ESEM 2009
506 - 510
MetadataShow full item record
Please cite this item using this persistent URLhttp://hdl.handle.net/11693/28609
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 requirements specification documents on inspection effectiveness. This paper addresses this issue by investigating whether inclusion of UML diagrams impacts the effectiveness of requirements inspection. We conducted an experiment in an academic environment with 35 subjects to empirically investigate the impact of UML diagram inclusion on requirements inspections' effectiveness and the number of reported defects. The results show that including UML diagrams in requirements specification document significantly impacts the number of reported defects, and there is no significant impact on the effectiveness of individual i nspections. © 2009 IEEE.
Showing items related by title, author, creator and subject.
A study to observe relations between software engineers' responses to incomplete requirements and requirements volatility Albayrak O.; Bicakci, M.; Bozkurt H. (2009)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 ...
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 ...