2003
DOI: 10.1109/ms.2003.1241366
|View full text |Cite
|
Sign up to set email alerts
|

Software reviews: The state of the practice

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
63
0
10

Year Published

2005
2005
2021
2021

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 88 publications
(78 citation statements)
references
References 8 publications
0
63
0
10
Order By: Relevance
“…We do not know whether our sample is representative of the Italian software engineering industry in general (it is a hard task), and are aware that Southern Italy is more represented by Northern Italy. On the other hand, we are aware that the size of our sample is similar to the one previously performed in German industry [2]. Of course, further data points are highly desired to generalize our findings.…”
Section: Threats To Validitymentioning
confidence: 66%
See 3 more Smart Citations
“…We do not know whether our sample is representative of the Italian software engineering industry in general (it is a hard task), and are aware that Southern Italy is more represented by Northern Italy. On the other hand, we are aware that the size of our sample is similar to the one previously performed in German industry [2]. Of course, further data points are highly desired to generalize our findings.…”
Section: Threats To Validitymentioning
confidence: 66%
“…The questionnaire has been developed following a standard schema [2]. The questionnaire consists of four sections and, depending on the three different paths (see Figure 1) followed by organizations that had already faced in the past at least one migration project (Group 1), that are planning to perform it in the near future (Group 2) and that did not perform any migration or are planning to do it (Group 3).…”
Section: Questionnaire Designmentioning
confidence: 99%
See 2 more Smart Citations
“…Software inspection is a specific type of software review (Ciolkowski et al, 2003) applied to artifacts by means of a systematic and well-planned defect identification process (Fagan, 1986;Kalinowski and Travassos, 2004;Sauer et al, 2000). According to CeBASE (http://www.cebase.org/defectreduction.html), over 60% of defects can be identified at early stages of the software life-cycle (Boehm and Basili, 2001;Gilb and Graham, 1993).…”
Section: Background Of the Studymentioning
confidence: 99%