| 1. |
- Thelin, Thomas
(författare)
-
Empirical evaluations of usage-based reading and fault content estimation for software inspections
- 2003
-
Ingår i: Empirical Software Engineering. - : Springer Science and Business Media LLC. - 1573-7616 .- 1382-3256. ; 8:3, s. 309-313
-
Tidskriftsartikel (refereegranskat)abstract
- This thesis describes six empirical investigations of two techniques applied to software inspections, namely reading techniques and fault content estimation techniques. The first part of the thesis presents a series of experiments of a novel reading technique called usage-based reading. The second part investigates fault content estimation applied to the software inspection process. The estimation methods used are capture-recapture and curve fitting.
|
|
| 2. |
- Thelin, Thomas, et al.
(författare)
-
Evaluation of usage-based reading - Conclusions after three experiments
- 2004
-
Ingår i: Empirical Software Engineering. - 1573-7616 .- 1382-3256. ; 9:1-2, s. 77-110
-
Tidskriftsartikel (refereegranskat)abstract
- Software inspections have been introduced in software engineering in order to detect faults before testing is performed. Reading techniques provide reviewers in software inspections with guidelines on how they should check the documents under inspection. Several reading techniques with different 16 purposes have been introduced and empirically evaluated. In this paper, we describe a reading technique with the special aim to detect faults that are severe from a user's point of view. The reading technique is named usage-based reading (UBR) and it can be used to inspect all software artefacts. In the series of experiments, a high-level design document is used. The main focus of the paper is on the third experiment, which investigates the information needed for UBR in the individual preparation and the meeting of software inspections. Hence, the paper discusses (1) the series of three experiments of UBR, (2) the individual preparation of the third experiment, and (3) the meeting part of the third experiment. For each of these three parts, results are produced. The main results are (1) UBR is an efficient and effective reading technique that can be used for user-focused software inspections, (2) UBR is more efficient and effective if the information used for UBR is developed prior to, instead of during the individual preparation, and (3) the meeting affects the UBR inspection in terms of increased effectiveness and decreased efficiency. In summary, the empirical evidence shows that UBR is an efficient and effective reading technique to be used by software organizations that produce software for which the user perceived quality is important.
|
|
| 3. |
|
|
| 4. |
|
|
| 5. |
- Höst, Martin, et al.
(författare)
-
Using Students as Subjects – A Comparative Study of Students and Professionals in Lead-Time Impact Assessment
- 2000
-
Ingår i: Empirical Software Engineering. - 1573-7616. ; 5:3, s. 201-214
-
Tidskriftsartikel (refereegranskat)abstract
- In many studiesin software engineering students are used instead of professionalsoftware developers, although the objective is to draw conclusionsvalid for professional software developers. This paper presentsa study where the difference between the two groups is evaluated.People from the two groups have individually carried out a non-trivialsoftware engineering judgement task involving the assessmentof how ten different factors affect the lead-time of softwaredevelopment projects. It is found that the differences are onlyminor, and it is concluded that software engineering studentsmay be used instead of professional software developers undercertain conditions. These conditions are identified and describedbased on generally accepted criteria for validity evaluationof empirical studies.
|
|
| 6. |
- Regnell, Björn, et al.
(författare)
-
Are the perspectives really different? Further experimentation on scenario-based reading of requirements
- 2000
-
Ingår i: Empirical Software Engineering. - 1573-7616. ; 5:4, s. 331-356
-
Tidskriftsartikel (refereegranskat)abstract
- Perspective-Based Reading (PBR) is a scenario based inspection technique where several reviewers read a document from different perspectives (e.g. user, designer, tester). The reading is made according to a special scenario, specific for each perspective. The basic assumption behind PBR is that the perspectives find different defects and a combination of several perspectives detects more defects compared to the same amount of reading with a single perspective. The paper presents a study which analyses the differences in perspectives. The study is a partial replication of previous studies. It is conducted in an academic environment using graduate students as subjects. Each perspective applies a specific modelling technique: use case modelling for the user perspective, equivalence partitioning for the tester perspective and structured analysis for the design perspective. A total of 30 subjects were divided into 3 groups, giving 10 subjects per perspective. The analysis results show that: (1) there is no significant difference among the three perspectives in terms of defect detection rate and number of defects found per hour, (2) there is no significant difference in the defect coverage of the three perspectives, and (3) a simulation study shows that 30 subjects is enough to detect relatively small perspective differences with the chosen statistical test. The results suggest that a combination of multiple perspectives may not give higher coverage of the defects compared to single-perspective reading, but further studies are needed to increase the understanding of perspective difference
|
|
