| Basili V, Green S, Laitenberger O, Lanubile F, Shull F, Sorumgard S, Zelkowitz M (1996) The empirical investigation of perspective-based reading. J Empirical Softw Eng 2(1):133--164 |
....a well defined metrics. They normally produce a high success rate, i.e. by spending 10 of the development effort, we diagnose 2 3 of the defects before testing, and save 20 of the total effort a win win: so quality is free . Inspections can be applied on most documents, even requirements [Basili96]. They also promote team learning, and provide a general assessment of reviewed documents. Of current research topics are: The role of the final inspection meeting (emphasized by Tom Gilb [Gilb93] see also [Votta93] When to stop inspections When to stop testing, cf. Adams84] The ....
Victor R. Basili, Scott Green, Oliver Laitenberger, Filippo Lanubile, Forrest Shull, Sivert Srumgrd, and Marvin V. Zelkovitz: "The Empirical Investigation of Perspective-Based Reading", J. of Empirical Software Engineering, Vol. 1, No. 2, 1996, p. 133---164.
....for the specifications written in the software cost reduction notation, a formal notation developed by Heninger [6] for event driven process control systems. This notation is not widely used in the commercial sector. In this regard, perspective based reading (PBR) developed by Basili et al. [1, 12] has been considered a more widely applicable technique, as it can be used for inspecting specifications written in natural language. An important feature of PBR is that it allows reviewers in the inspection team to select their own perspectives (say, as a tester, developer, or user) when ....
....applicable technique, as it can be used for inspecting specifications written in natural language. An important feature of PBR is that it allows reviewers in the inspection team to select their own perspectives (say, as a tester, developer, or user) when inspecting the specifications. Studies [1, 8, 12] report that inspection teams using PBR find more defects than teams using other approaches. In this paper, we propose a problem driven approach for supporting PBR. We recommend that, based on the reviewer s perspective as well as the characteristics of the problem domain of the specification, ....
[Article contains additional citation context not shown here]
V. R. Basili, S. Green, O. Laitenberger, F. Lanubile, F. Shull, S. Srumgard, and M. V. Zelkowitz, "The Empirical Investigation of Perspective-Based Reading", Empirical Software Engineering: An International Journal, vol. 1, no. 2, 1996, pp. 133--164.
....the work by themselves, it is important to provide coaching and encouragement. It is also important that all participants have the possibility to allocate enough time for the study. 3. 5 Validity of evaluation The study has been designed with the objective to obtain high validity (see for example [Robson93, Basili96]) Threats to internal validity are threats that can bias the measured variables and therefore lead to false conclusions. Examples of threats to internal validity of a study are that the history affects the study, i.e. different compared methods etc. are used in different occasions, and that ....
V. Basili, S. Green, O. Laitenberger, F. Lanubile, F. Shull, S. Srumgrd, M. Zelkowitz, `The Empirical Investigation of Perspective-Based Reading', Empirical Software Engineering, Vol. 1, No. 2, 1996, pp. 133-164.
....denotes this type of strategy, where scenarios are a means of controlling the reading of e.g. requirements, design, and code. It is important here to distinguish between meta scenarios that describe the reading process itself and usage scenarios that describe the system requirements. In [18], a technique called Perspective Based Reading (PBR) is presented and evaluated. PBR uses meta scenarios for instructing a reviewer how to carry out the reading. Each reviewer is assigned a specific perspective and the meta scenario is tailored for this perspective. Typical perspectives are user, ....
....meta scenarios for instructing a reviewer how to carry out the reading. Each reviewer is assigned a specific perspective and the meta scenario is tailored for this perspective. Typical perspectives are user, designer, and tester perspectives. A main argument for PBR, confirmed in empirical studies [18], is that different perspectives are likely to find different defects and by including many perspectives the reading will be more efficient compared to other reading techniques. PBR suggests that the reviewer should be more active and create some kind of model during the reading to better ....
[Article contains additional citation context not shown here]
Basili, V. R., Green, S., Laitenberger, O., Lanubile, F., Shull, F., Srumgrd, S., Zelkowitz, M. V., "The Empirical Investigation of Perspective-based Reading", Empirical Software Engineering: An International Journal, vol. 1, no. 2, pp. 133--164, 1996.
No context found.
Basili, V.R., Green, S., Laitenberger, O., Lanubile, F., Shull, F., Sorumgard, S., and Zelkowitz, M.V. "The Empirical Investigation of Perspective Based Reading." Empirical Software Engineering --- An International Journal, 1(2): 133-164, 1996.
No context found.
Basili, V.R., Green, S., Laitenberger, O., Lanubile, F., Shull, F., Sorumgard, S., Zelkowitz, M.V., "The Empirical Investigation of Perspective-Based Reading," Empirical Software Engineering -- An International Journal, vol. 1, no. 2, 1996.
No context found.
V. R. Basili, S. Green, O. Laitenberger, F. Lanubile. F. Shull, S. Sorumgaard, and M.V. Zelkowitz, "The Empirical Investigation of Perspective-Based Reading," Empirical Software Engineering: An International Journal, Kluwer Acade mic Publishers, Boston, Massachusetts, 1996, pp. 133164.
No context found.
V.R. Basili, S. Green , O. Laitenberger, F. Lanubile, F. Shull, S. Soerumgaard, and M.V. Zelkowitz, "The Empirical Investigation of Perspective-Based Reading", Empirical Software Engineering, 1(2): 1996, pp. 133-164.
....a software artifact, we focus on the individual inspector and his or her activities. 2. 2 Reading Techniques (PBR) In order to help inspectors find requirements defects during their individual preparation or inspection time, a technique called Perspective Based Reading (PBR) was developed [Basili96]. PBR has three important aspects. First, because a requirements document will potentially be used by a number of different stakeholders, PBR asks each inspector to assume the perspective of one of those stakeholders. By taking a perspective, the inspector is focused on ensuring that the ....
Basili, V.R., Green, S., Laitenberger, O., Lanubile, F., Shull, F., Sorumgard, S., Zelkowitz, M.V., "The Empirical Investigation of Perspective-Based Reading," Empirical Software Engineering -- An International Journal, vol. 1, no. 2, 1996.
....nine months with Professor Victor Basili s Experimental Software Engineering Group at the University of Maryland (UMD) in Maryland, USA. During these nine months I was working on a replication of an experiment in order to test the validity of a new technique for reading requirement specifications (Basili, 1996). The problems we encountered during the investigation of process quality, together with some of the problems we saw in the empirical investigation at the UMD, took me to the conclusion that a fundamental difficulty in today s research is how to understand, measure and control process conformance. ....
....a textual description. The process model is used in a prescriptive sense. Simple process model in terms of structure and communication. The process is often carried out independently by the subjects. Thus, the processes are straightforward, simple and low level. Perspective based reading (Basili, 1996) is a typical example of such a process. This does not mean that the approach to process conformance is necessarily inapplicable to other processes, it means that these are the processes that will primarily be considered. It makes little sense to concentrate on more advanced and complicated ....
[Article contains additional citation context not shown here]
Victor R. Basili, Scott Green, Oliver Laitenberger, Filippo Lanubile, Forrest Shull, Sivert Srumgrd and Marvin Zelkowitz. The Empirical Investigation of Perspective-Based Reading. To appear in the Journal of Empirical Software Engineering.
....findings across individual studies. A common approach to summarize a number of empirical studies is to conduct a post mortem analysis (e.g. meta analysis) of historic experiments. A number of successes with conducting individual and replicated studies has been reported in the last decade [4][11] 12] 24] 25] 26] 27] 28] Still, it seems hard to define the context of a set of studies to support the widespread generalization of common study results. Miller [22] applied classical meta analysis to generalize results and found it lacking to compare studies with different variables and ....
....responsibilities. This approach has been shown to increase the effectiveness of a variety of different kinds of inspections over less procedural approaches. Some areas for which this approach has been tailored include inspections of formal language requirements [26] natural language requirements [4], Object Oriented designs [17] 31] code [19] and user interfaces [39] 2.2 Related Work on Empirical Methodology 2.2.1 Empirical Studies in Software Engineering Research in software engineering is often concerned with the development of new techniques, methods, or tools for software ....
[Article contains additional citation context not shown here]
Basili, V., Green, S., Laitenberger, O., Lanubile, F., Shull, F., Sorumgard, S., and Zelkowitz, M., 1996. The Empirical Investigation of Perspective-based Reading. Journal of Empirical Software Engineering, 2(1):133-164.
.... the object of study was an innovative reading technique, called Perspective based Reading (PBR) This technique was selected because several controlled experiments demonstrated its benefits in comparison with other, state of the practice techniques, such as ad hoc or checklist based reading [2], 6] However, few results have been reported in using the PBR approach in real projects. Hence, 346 the objective of the PIE was the investigation and the quantitative evaluation of this kind of inspections in case studies at Allianz Life. The remainder of this paper is structured as follows: ....
....in the software development process and the quality of the resulting products at Allianz Life. Such improvement was achieved by introducing a very promising quality assurance methodology: inspections using PBR on artefacts of the early phases of the life cycle (requirements analysis and design) [2]. Experiments in practice have shown that PBR has cost effectiveness benefits in comparison with state of the practice techniques, such as ad hoc or checklist based reading [2] 6] 347 The PIE was performed in the context of a project with strategic importance for the company: the ....
[Article contains additional citation context not shown here]
Basili, V., Green, S., Laitenberger, O., Lanubile, F., Shull, F., Sorumgard, S. , and Zelkowitz M., 1996. The Empirical Investigation of Perspective-based Reading. Empirical Software Engineering, 2(1): pp. 133--164.
....(i.e. underlying human misconceptions) in a document rather than the individual faults that they cause. In the context of a controlled experiment, we assess both benefits and costs of the process of abstracting errors from faults in requirements documents. 1. Introduction Previous experiments [3, 5, 11] have evaluated Perspective Based Reading (PBR) a method for detecting defects in natural language requirements documents. In each case, defect detection effectiveness was measured by the percentage of faults2 found in the requirements documents reviewed. The documents used contained seeded ....
V.R. Basili, S. Green, O. Laitenberger, F. Lanubile, F. Shull, S. Sommgftrd, and M. Zelkowitz. The empirical investigation of Perspective-Based Reading. Empirical Software Engineering: An International Journal, 1 (2): 133-164, 1996.
....(for requirements expressed in English or SCR, a formal notation) and to usability inspections of user interfaces. There is empirical evidence that software reading increases the effectiveness of inspections on different types of software artifacts, not just limited to source code [13][1][2] 8] 14] 25] In this work, we describe a family of software reading techniques for the purpose of defect detection of high level Object Oriented (OO) designs diagrams represented using Unified Modeling Language (UML) 7] A high level design is a set of artifacts concerned with the ....
....Section 4 introduces the reading techniques and discusses In this text we distinguish a technique from a method as follows: A technique is a series of steps, at some level of detail, which can be followed in sequence to complete a particular task. We use the term method as defined in [1], a management level description of when and how to apply techniques, which explains not only how to apply a technique, but also under what conditions the technique s application is appropriate. the process inspectors can use to apply them. Finally, some suggestions for future work are ....
Basili, V. R.; Green, S.; Laitenberger, O.; Lanubile, F.; Shull, F.; Sorumgard, S. and Zelkowitz, M. V. (1996) The Empirical Investigation of Perspective-Based Reading, Empirical Software Engineering Journal, I, 133-164.
....forms and report templates to collect product and process data. In the attempt to shorten the overall cost and total time of the inspection process, the need for a meeting has been empirically investigated by many independent studies together with other factors affecting inspection effectiveness [1, 8]. In a recent article [10] Sauer et al. consider a reorganization of the inspection process on the basis of a set of propositions, borrowed from the behavioral theory of group performance. The propositions are the following: 1) Task expertise is the dominant determinant of group performance; 2) ....
V. Basili, S. Green, O. Laitenberger, F. Lanubile, F. Shull, S. Sorumgard, and M. Zelkowitz, "The Empirical Investigation of Perspective-based Reading", Empirical Software Engineering, 1, 133-- 164, 1996.
....represents what we have learned about balancing the needs of research and industry throughout the process. This methodology has been abstracted from lessons learned on multiple research programs, for example understanding Cleanroom techniques [3] and PBR techniques for requirements inspections [2]. Although we claim this methodology will be useful for any software development process (e.g. new improvements in compilers and automated test methods) for the purpose of a concrete discussion in this paper we restrict our discussion to software processes 1 . In later sections of this paper, ....
Basili, V.R., Green, S., Laitenberger, O., Shull, F., Sorumgaard, S.L., and Zelkowitz, M.V. "The Empirical Investigation of Perspective-based Reading." Empirical Software Engineering, An International Journal, Volume 1, Number 2, pp. 133164, Kluwer Academic Publishers, October 1996.
....but are more costly than conventional inspections. This may be one explanation why we did not find extensive use of the phased inspection approach in practice. There has been noticeable growth in research on how individual defect detection takes place and can be supported with adequate techniques [5] [6] 109] We tackle this issue later in more detail when we discuss reading techniques to support defect detection. Defect Collection In most published inspection processes, more than one person participates in an inspection and scrutinizes a software artifact for defects. Hence, the defects ....
.... three different 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 ....
[Article contains additional citation context not shown here]
Basili, V., Green, S., Laitenberger, O., Lanubile, F., Shull, F., Sorumgard, S., and Zelkowitz, M., 1996. The Empirical Investigation of Perspective-based Reading. Journal of Empirical Software Engineering, 2(1):133-164.
No context found.
Basili V, Green S, Laitenberger O, Lanubile F, Shull F, Sorumgard S, Zelkowitz M (1996) The empirical investigation of perspective-based reading. J Empirical Softw Eng 2(1):133--164
No context found.
V. R. Basili, S. Green, O. Laitenberger, F. Lanubile, F. Shull, S. Srumgrd, and M. Zelkowitz, The Empirical Investigation of Perspective-Based Reading, Empirical Software Engineering, 2(1), pp. 133-164, 1996.
No context found.
Basili, V. R., Green, S., Laitenberger, O., Lanubile, F., Shull, F., Srumgrd, S. & Zelkowitz, M." The Empirical Investigation of Perspective-Based Reading". Empirical Software Engineering Journal, vol 1, nr. 2, 133-146, 1996.
No context found.
V.R. Basili, S. Green, O. Laitenberger, F. Lanubile, F. Shull, S. Sorumgard, M.V. Zelkowitz, The Empirical Investigation of Perspective-Based Reading, Empirical Software Engineering: An International Journal 1 (2) (1996) 133-164.
No context found.
Basili, V. R., Green, S., Laitenberger, O., Lanubile, F., Shull, F., Srumgrd, S., and Zelkowitz, M. V. 1996. "The Empirical Investigation of Perspective-Based Reading" Empirical Software Engineering , 1(2): 133-164.
No context found.
Basili, Green, Laitenberger, Lanubile, Shull, Sorumgard, Zelkowitz : "The Empirical Investigation of Perspective-Based Reading" , Empirical Software Engineering 1:2 (1996) 133-164
No context found.
Victor R. Basili, Scott Green, Oliver Laitenberger, Filippo Lanubile, Forrest Shull, Sivert Srumgard, and Marvin V. Zelkovitz. The Empirical Investigation of Perspective-Based Reading, 39 p. Empirical Software Engineering, (forthcoming), 1996.
No context found.
V. Basili et al., "The Empirical Investigation of Perspective -Based Reading," Empirical Software Eng.: An Int'l J., Vol. 1, No. 2, 1996, pp. 133-164.
First 50 documents Next 50
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