2009 ICSE Workshop on Software Quality 2009
DOI: 10.1109/wosq.2009.5071552
|View full text |Cite
|
Sign up to set email alerts
|

Inspection effectiveness for different quality attributes of software requirement specifications: An industrial case study

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
10
0

Year Published

2009
2009
2021
2021

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 14 publications
(10 citation statements)
references
References 7 publications
0
10
0
Order By: Relevance
“…Inspections are important because some defects cannot be found through conventional test units (e.g., a badly design iteration over an array, which does unnecessary loops causing performance degradation). Furthermore, there are well documented reports showing that the usage of software inspection in the early stages of the development cycle reduces the costs of bug fixes and leverages productivity [7] [18].…”
Section: Software Inspectionmentioning
confidence: 99%
See 1 more Smart Citation
“…Inspections are important because some defects cannot be found through conventional test units (e.g., a badly design iteration over an array, which does unnecessary loops causing performance degradation). Furthermore, there are well documented reports showing that the usage of software inspection in the early stages of the development cycle reduces the costs of bug fixes and leverages productivity [7] [18].…”
Section: Software Inspectionmentioning
confidence: 99%
“…Its benefits, such as cost reduction and defect prevention in earlier stages of software development, are well discussed and established among the literature [6] [19] [18]. However, since inspection is a human-driven process, the effectiveness of its process is heavily influenced by people's skills and knowledge.…”
Section: Introductionmentioning
confidence: 99%
“…It is one of static testing (verification) techniques, and its main objective is to find and avoid an error which appears during the software development process. Software review process can be applied to any artefact created during the software development lifecycle, for example, business requirements, system designs, code, test plans, test cases and documentation [10], [12]. A systematic evaluation of these documents and artefacts occurs during this process.…”
Section: Related Researchmentioning
confidence: 99%
“…In order to decrease the number of defects detected at the end of testing or after the release of the software, it is necessary to take preventive measures starting with the project earliest phases. One of these preventive measures is static testing [6], [10].…”
Section: Introductionmentioning
confidence: 99%
“…Different sources however indicate that this might not be the case [11,12]. In fact it seems that some of the most critical quality attributes (like "completeness") escape reviews to a large extend [12].…”
Section: Introductionmentioning
confidence: 99%