O. Laitenberger and J-M. DeBaud, Perspective-Based Reading of Code Documents at Robert Bosch GmbH, Special Issue on Information and Software Technology, vol. 39, pp. 781-791, 1997.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....than teams which did not use PBR. These results were confirmed in a replicated experiment conducted by other researchers with undergraduate students and real team meetings (Ciolkowski et al. 1997) PBR has been also tailored and applied for reviewing source code documents in an industrial setting (Laitenberger and DeBaud, 1997). Results from an empirical comparison with checklist based inspection shows that PBR is more effective and less costly than using checklists (Laitenberger et al. 1999) From the empirical studies of PBR, an unexpected effect was that individuals applying PBR, rather than just teams, were more ....

O. Laitenberger and J.M. DeBaud, "Perspective-based Reading of Code Documents at Robert Bosch GmbH", Information and Software Technology, 39:781--791, 1997.

....al. 11] identify the number of inspections sessions as another factor influencing inspection effectiveness. Additionally, the defect detection technique chosen for an inspection may have an impact on effectiveness as well. For example, more systematic techniques may help inexperienced inspectors [12]. 1 Using the proportion of defects found would be equivalent as this is the number of detected defects divided by a constant: the total number of defects. 2 Effort spent examining the document in the inspection meeting per unit of document size (e.g. LOC) 3 Effort spent reading the document ....

Oliver Laitenberger and Jean-Marc DeBaud, Perspective-based Reading of Code Documents at Robert Bosch GmbH, Information and Software Technology, vol. 39, pp. 781-791, Mar. 1997

....to compare the amount of comprehension afforded by ad hoc detection, checklists or scenarios. More recently, a variation on scenarios has appeared, Perspective Based Reading [4] They are similar to scenarios and were also originally designed for Software Requirement Specifications. More recently [31] a version of perspectivebased reading techniques for code has been proposed, but no conclusive evidence to their effectiveness for code inspections as compared with other current methods has so far been produced. 2.4 Summary The inspection process has been around since the early 70 s, originally ....

O. Laitenberger and J.-M. DeBaud, Perspective-based Reading of Code Documents at Robert Bosch GmbH, Special Issue on Information and Software Technology, Nov. 1997.

.... Defect Based Reading (DBR) focused on defect detection in requirements, where the requirements were expressed using a state machine notation called SCR [13, 22] Perspective Based Reading (PBR) also focused on defect detection in requirements, but for requirements expressed in natural language [4, 16]. Use Based Reading (UBR) focused on anomaly detection in user interfaces [27] Second Version of PBR (PBR2) consisted of new techniques that were more procedurally oriented versions of the earlier set of PBR techniques. In particular, we made the techniques more specific in all of their ....

O. Laitenberger, and J. M. DeBaud, "Perspective-based reading of code documents at Robert Bosch GmbH", Journal of Information and Software Technology, 39, pp.781-791, 1997.

....different specific experimental hypotheses. The study was originally run twice at NASA and has been replicated several times, including the replication conducted by the Fraunhofer Institute for Experimental Software Engineering using professional developers during a pre project training course. [4, 24] 7 . Use Based Reading (UBR) This experiment focused on anomaly detection in user interfaces. It is a family of analysis techniques based on three system user perspectives (expert, novice, error handling) In the experiment run at the Bureau of Census, UBR was compared against the usability ....

O. Laitenberger, and J. M. DeBaud, "Perspective-based reading of code documents at Robert Bosch GmbH", Journal of Information and Software Technology, 39, pp.781-791, 1997.

.... scenario based reading techniques: Defect based Reading [109] for inspecting requirements documents, a scenario based reading technique based on function points for inspecting requirements documents [23] and Perspective based Reading for inspecting requirements documents [5] or code documents [76]. The main idea behind Defect based Reading is for different inspectors to focus on different defect classes while scrutinizing a requirements document [93] 105] 109] 117] For each defect class, there is a scenario consisting of a set of questions an inspector has to answer while reading. ....

....the function point scenarios. However, experience seemed to be a confounding factor that biased the results of the experiment. The main idea behind the perspective based reading technique is that a software product should be inspected from the perspective of different stakeholders [5] 18] [76] [77] The rationale is that there is no single monolithic definition of software quality, and little general agreement about how to define any of the key quality properties, such as correctness, maintainability, or testability. Therefore, inspectors of an inspection team have to check software ....

[Article contains additional citation context not shown here]

Laitenberger, O. and DeBaud, J.-M., 1997. Perspective-based Reading of Code Documents at Robert Bosch GmbH. Information and Software Technology, 39:781-791.

.... [Porter et al. 1995b] for inspecting requirements documents, a scenario based reading technique based on function points for inspecting requirements documents [Cheng and Jeffrey, 1996] and Perspective based Reading for inspecting requirements documents [Basili et al. 1996] or code documents [Laitenberger and DeBaud, 1997]. The main idea behind Defect based Reading is for different inspectors to focus on different defect classes while scrutinizing a requirements documents [Porter et al. 1995b] For each defect class, there is a scenario consisting of a set of questions an inspector has to answer while reading. ....

....scenarios. However, it seems that experience is a confounding factor that biased the results of the experiment. The main idea behind the perspective based reading technique is that a software product should to be inspected from the perspective of different stakeholders [Basili et al. 1996] [Laitenberger and DeBaud, 1997]. The rationale is that there is no single monolithic definition of software quality, and little general agreement about how to define any of the key quality properties, such as correctness, maintainability, or testability. Therefore, inspectors of an inspection team have to check software quality ....

[Article contains additional citation context not shown here]

Laitenberger, O. and DeBaud, J.-M. (1997). Perspective-based Reading of Code Documents at Robert Bosch GmbH. Information and Software Technology, 39:781--791.

....inspected documents were performed. We support the view of Sauer et al. 28] that defect detection is rather an individual than a group activity and that the synergy effect of inspection meetings is rather low in terms of defects that are detected in the meetings. Recent experimental studies [22][20] support this view. 3.2 Evaluation Criteria To evaluate the different models and estimators, we use three criteria as follows: Relative Error To evaluate the accuracy of the estimate, we use the relative error (RE) defined as: eq. 2) RE allows us to distinguish between overestimation (too ....

O. Laitenberger and J. DeBaud: "Perspective-based Reading of Code documents at Robert Bosch GmbH". In Proceedings of the First Conference on Empirical Assessment and Validation, March 1997.

....to evaluate these reading techniques for inspecting code documents as well. In contrast to the other two scenario based reading techniques, the PBR technique has been tailored for defect detection in code artefacts and applied in the context of a software development project at a German company [54]. However, a systematic comparison with CBR is still missing. 2.4 Experimental Hypotheses Before we explain the expected effects when comparing PBR with CBR in the form of hypotheses, we define the following notation (we use d(a b) for defining d(a) or d(b) respectively) Term Definition e ....

O. Laitenberger and J.-M. DeBaud. Perspective-based Reading of Code Documents at Robert Bosch GmbH. Information and Software Technology, 39:781--791, March 1997.

No context found.

O. Laitenberger and J-M. DeBaud, Perspective-Based Reading of Code Documents at Robert Bosch GmbH, Special Issue on Information and Software Technology, vol. 39, pp. 781-791, 1997.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC