2009
DOI: 10.1016/j.infsof.2009.01.004
|View full text |Cite
|
Sign up to set email alerts
|

A systematic literature review to identify and classify software requirement errors

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
75
0
2

Year Published

2010
2010
2024
2024

Publication Types

Select...
5
4

Relationship

0
9

Authors

Journals

citations
Cited by 149 publications
(77 citation statements)
references
References 53 publications
0
75
0
2
Order By: Relevance
“…The proposed framework most importantly affects the software development process, switching the focus from interpreting requirements, coding, and testing to analyzing requirements, modeling, and validating the behavior of the system. This increases the quality of the software dramatically, as nearly three quarters of failures found in operational software originate from errors or oversights in the requirements [33]. Admittedly, our approach may prolong the obtention of the initial control design, but by catching design faults early, the testing costs are mitigated and the overall production time is shortened.…”
Section: Discussionmentioning
confidence: 99%
“…The proposed framework most importantly affects the software development process, switching the focus from interpreting requirements, coding, and testing to analyzing requirements, modeling, and validating the behavior of the system. This increases the quality of the software dramatically, as nearly three quarters of failures found in operational software originate from errors or oversights in the requirements [33]. Admittedly, our approach may prolong the obtention of the initial control design, but by catching design faults early, the testing costs are mitigated and the overall production time is shortened.…”
Section: Discussionmentioning
confidence: 99%
“…The taxonomy of defect types is taken into account by several more studies, such as in Alshazly et al (2014;Teixeira et al, 2015;Travassos et al ., 1999;Walia and Carver, 2009). For example, the IEEE Standard 1012-2012 recommends verifying and validating an inspected system throughout defect types, such as: Complete, Correct, Omissions, Ambiguities, Traceable, Testable and Consistent (IEEE, 2012).…”
Section: Background Of the Studymentioning
confidence: 99%
“…However, a large percent of IS projects are considered a failure in terms of budget overruns, time overruns, and abandonment (Bulatovic, 2011;Li, Huang, Luftman, & Sha, 2010;Luftman & Ben-Zvi, 2010;Nauman, Aziz, & Ishaq, 2005;Standish Group, 2009;Thong, Yap, & Raman, 1996). But the main contributor of project failure as suggested by IS scholars is poor quality software products being developed and delivered (Brooks, 1987;Walia & Carver, 2009). …”
Section: Introductionmentioning
confidence: 99%