ISSN 2394-5125
 

Research Article 


An Experimental Analysis of the Use Case and Activity Diagrams' Efficiency in Software Requirement Inspection

Hamayoon Ghafory.

Abstract
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

Key words: Software Requirements, Software engineering


 
ARTICLE TOOLS
Abstract
PDF Fulltext
How to cite this articleHow to cite this article
Citation Tools
Related Records
 Articles by Hamayoon Ghafory
on Google
on Google Scholar


How to Cite this Article
Pubmed Style

Hamayoon Ghafory. An Experimental Analysis of the Use Case and Activity Diagrams' Efficiency in Software Requirement Inspection. JCR. 2021; 8(2): 1521-1526. doi:10.31838/jcr.08.02.151


Web Style

Hamayoon Ghafory. An Experimental Analysis of the Use Case and Activity Diagrams' Efficiency in Software Requirement Inspection. http://www.jcreview.com/?mno=88254 [Access: June 15, 2021]. doi:10.31838/jcr.08.02.151


AMA (American Medical Association) Style

Hamayoon Ghafory. An Experimental Analysis of the Use Case and Activity Diagrams' Efficiency in Software Requirement Inspection. JCR. 2021; 8(2): 1521-1526. doi:10.31838/jcr.08.02.151



Vancouver/ICMJE Style

Hamayoon Ghafory. An Experimental Analysis of the Use Case and Activity Diagrams' Efficiency in Software Requirement Inspection. JCR. (2021), [cited June 15, 2021]; 8(2): 1521-1526. doi:10.31838/jcr.08.02.151



Harvard Style

Hamayoon Ghafory (2021) An Experimental Analysis of the Use Case and Activity Diagrams' Efficiency in Software Requirement Inspection. JCR, 8 (2), 1521-1526. doi:10.31838/jcr.08.02.151



Turabian Style

Hamayoon Ghafory. 2021. An Experimental Analysis of the Use Case and Activity Diagrams' Efficiency in Software Requirement Inspection. Journal of Critical Reviews, 8 (2), 1521-1526. doi:10.31838/jcr.08.02.151



Chicago Style

Hamayoon Ghafory. "An Experimental Analysis of the Use Case and Activity Diagrams' Efficiency in Software Requirement Inspection." Journal of Critical Reviews 8 (2021), 1521-1526. doi:10.31838/jcr.08.02.151



MLA (The Modern Language Association) Style

Hamayoon Ghafory. "An Experimental Analysis of the Use Case and Activity Diagrams' Efficiency in Software Requirement Inspection." Journal of Critical Reviews 8.2 (2021), 1521-1526. Print. doi:10.31838/jcr.08.02.151



APA (American Psychological Association) Style

Hamayoon Ghafory (2021) An Experimental Analysis of the Use Case and Activity Diagrams' Efficiency in Software Requirement Inspection. Journal of Critical Reviews, 8 (2), 1521-1526. doi:10.31838/jcr.08.02.151