An Experimental Analysis of the Use Case and Activity Diagrams' Efficiency in Software Requirement Inspection
Hamayoon Ghafory · Journal of Critical Reviews · 2021
Software inspection is a technique for identifying errors in software artifacts such as documentation and source code. The purpose of an inspection is to visually locate and identify defects in a software product. Finding flaws early in the development life cycle is critical, as the expense of rectification grows as the development cycle progresses. Inspections can detect flaws early, as they may be done as soon as an artifact is generated. Diagrams created using the Unified Modeling Language (UML) have been widely utilized to model many elements of software systems throughout their life cycle. The purpose of this study is to determine the effect of integrating Use Case and Activity diagrams in software requirements specifications on the efficacy of inspections and the number of reported faults in an educational institution. The results indicated that students who inspected documents solely with text reported more faults than students who inspected documents with text + diagram, and those who inspected documents with text + diagram reported the same number of correct faults as those who inspected documents with text only. However, students who inspected documents solely with text reported more incorrect faults than students who inspected documents with text + diagram