The Experts below are selected from a list of 22683 Experts worldwide ranked by ideXlab platform
Thomas Thelin - One of the best experts on this subject based on the ideXlab platform.
-
a case study of reading techniques in a Software company
International Symposium on Empirical Software Engineering, 2004Co-Authors: T Berling, Thomas ThelinAbstract:Software Inspection is an efficient method to detect faults early in the Software lifecycle. This has been shown in several empirical studies together with experiments on reading techniques. However, experiments in industrial settings are often considered expensive for a Software organization. Hence, many evaluations are performed in the academic environment with artificial documents. In this paper, we describe an empirical study in a Software organization where a requirements document under development is used to compare two reading techniques. There are several benefits as well as drawbacks of using this kind of approach, which are extensively discussed in the paper. The reading techniques compared is the standard technique used in the organization (checklist-based) with the test perspective of perspective-based reading. The main result is that the test perspective of perspective-based reading seems more effective and efficient than the company standard method. The impact of this study is that the Software organization will apply the new reading technique in future requirements Inspections.
-
team based fault content estimation in the Software Inspection process
International Conference on Software Engineering, 2004Co-Authors: Thomas ThelinAbstract:The main objective of Software Inspection is to detect faults within a Software artifact. This helps to reduce the number of faults and to increase the quality of a Software product. However, although Inspections have been performed with great success, and although the quality of the product is increased, it is difficult to estimate the quality. During the Inspection process, attempts with objective estimations as well as with subjective estimations have been made. These methods estimate the fault content after an Inspection and give a hint of the quality of the product. This paper describes an experiment conducted throughout the Inspection process, where the purpose is to compare the estimation methods at different points. The experiment evaluates team estimates from subjective and objective fault content estimation methods integrated with the Software Inspection process. The experiment was conducted at two different universities with 82 reviewers. The result shows that objective estimates outperform subjective when point and confidence intervals are used. This contradicts the previous studies in the area.
Oliver Laitenberger - One of the best experts on this subject based on the ideXlab platform.
-
investigating the cost effectiveness of reInspections in Software development
International Conference on Software Engineering, 2001Co-Authors: Stefan Biffl, Bernd Freimut, Oliver LaitenbergerAbstract:Software Inspection is one of the most effective methods to detect defects. ReInspection repeats the Inspection process for Software products that are suspected to contain a significant number of undetected defects after an initial Inspection. As a reInspection is often believed to be less efficient than an Inspection an important question is whether a reInspection justifies its cost. In this paper we propose a cost-benefit model for Inspection and reInspection. We discuss the impact of cost and benefit parameters on the net gain of a reInspection with empirical data from an experiment in which 31 student teams inspected and reinspected a requirements document. Main findings of the experiment are: a) For reInspection benefits and net gain were significantly lower than for the initial Inspection. Yet, the reInspection yielded a positive net gain for most teams with conservative cost-benefit assumptions. b) Both the estimated benefits and number of major defects are key factors for reInspection net gain, which emphasizes the need for appropriate estimation techniques.
-
measurable Software quality improvement through innovative Software Inspection technologies at allianz life assurance
2001Co-Authors: Bernd Freimut, Oliver Laitenberger, Brigitte Klein, Gunther RuheAbstract:The development of high quality Software satisfying cost, schedule, and resource requirements is an essential prerequisite for improved competitiveness of life insurance companies. One major difficulty to master this challenge is the inevitability of defects in Software products. Since defects are known to be significantly more expensive if detected in later development phases or testing, companies in this marketplace must use cost-effective technologies to detect defects early on in the development process. A particular promising one is Software Inspection. This paper describes the ESPRIT/ESSI Process Improvement Experiment "High Quality of Software Products by Early Use of Innovative Reading Techniques (HYPER)". The core of this project has been the transfer of innovative Software Inspection technologies to the Allianz EURO conversion projects. The innovation in the area of Software Inspection is based on a systematic reading technique, that is, Perspective-based reading (PBR), that tells Inspection participants what to look for and more important how to scrutinise a Software artefact for defects. Although numerous controlled experiments have shown the PBR technique to be particularly cost-effective, few results have been reported on its use in the context of development projects. The paper presents in a quantitative manner the final results regarding the application of PBR Inspections on requirements and design documents in the ESSI PIE. The results are based on 9 requirements and 44 design Inspections and demonstrate the benefits to be expected from PBR Inspections in an industrial environment.
-
an encompassing life cycle centric survey of Software Inspection
Journal of Systems and Software, 2000Co-Authors: Oliver Laitenberger, Jeanmarc DebaudAbstract:Abstract This paper contributes an integrated survey of the work in the area of Software Inspection. It consists of two main sections. The first one introduces a detailed description of the core concepts and relationships that together define the field of Software Inspection. The second one elaborates a taxonomy that uses a generic development life-cycle to contextualize Software Inspection in detail. After Fagan's seminal work presented in 1976, the body of work in Software Inspection has greatly increased and reached measured maturity. Yet, there is still no encompassing and systematic view of this research body driven from a life-cycle perspective. This perspective is important since Inspection methods and refinements are most often aligned to particular life-cycle artifacts. It also provides practitioners with a roadmap available in their terms. To provide a systematic and encompassing view of the research and practice body in Software Inspection, the contribution of this survey is, in a first step, to introduce in detail the core concepts and relationships that together embody the field of Software Inspection. This lays out the field key ideas and benefits and elicits a common vocabulary. There, we make a strong effort to unify the relevant vocabulary used in available literature sources. In a second step, we use this vocabulary to build a contextual map of the field in the form of a taxonomy indexed by the different development stages of a generic process. This contextual map can guide practitioners and focus their attention on the Inspection work most relevant to the introduction or development of Inspections at the level of their particular development stage; or to help motivate the use of Software Inspection earlier in their development cycle. Our work provides three distinct, practical benefits: First, the index taxonomy can help practitioners identify Inspection experience directly related to a particular life-cycle stage. Second, our work allows structuring of the large amount of published Inspection work. Third, such taxonomy can help researchers compare and assess existing Inspection methods and refinements to identify fruitful areas of future work.
Poong Hyun Seong - One of the best experts on this subject based on the ideXlab platform.
-
An effective technique for the Software requirements analysis of NPP safety-critical systems, based on Software Inspection, requirements traceability, and formal specification
Reliability Engineering & System Safety, 2005Co-Authors: Poong Hyun SeongAbstract:A thorough requirements analysis is indispensable for developing and implementing safety-critical Software systems such as nuclear power plant (NPP) Software systems because a single error in the requirements can generate serious Software faults. However, it is very difficult to completely analyze system requirements. In this paper, an effective technique for the Software requirements analysis is suggested. For requirements verification and validation (V&V) tasks, our technique uses Software Inspection, requirement traceability, and formal specification with structural decomposition. Software Inspection and requirements traceability analysis are widely considered the most effective Software V&V methods. Although formal methods are also considered an effective V&V activity, they are difficult to use properly in the nuclear fields as well as in other fields because of their mathematical nature. In this work, we propose an integrated environment (IE) approach for requirements, which is an integrated approach that enables easy Inspection by combining requirement traceability and effective use of a formal method. The paper also introduces computer-aided tools for supporting IE approach for requirements. Called the nuclear Software Inspection support and requirements traceability (NuSISRT), the tool incorporates Software Inspection, requirement traceability, and formal specification capabilities. We designed the NuSISRT to partially automate Software Inspection and analysis of requirement traceability. In addition, for the formal specification and analysis, we used the formal requirements specification and analysis tool for nuclear engineering (NuSRS).
-
development of a traceability analysis method based on case grammar for npp requirement documents written in korean language
Nuclear Engineering and Technology, 2004Co-Authors: Yeong Jae Yoo, Poong Hyun Seong, Man Cheol KimAbstract:Software Inspection is widely believed to be an effective method for Software verification and validation (V&V). However, Software Inspection is labor-intensive and, since it uses little technology, Software Inspection is viewed upon as unsuitable for a more technology-oriented development environment. Nevertheless, Software Inspection is gaining in popularity. KAIST Nuclear I&C and Information Engineering Laboratory (NICIEL) has developed Software management and Inspection support tools, collectively named “SIS-RT.” SIS-RT is designed to partially automate the Software Inspection processes. SIS-RT supports the analyses of traceability between a given set of specification documents. To make SIS-RT compatible for documents written in Korean, certain techniques in natural language processing have been studied [9]. Among the techniques considered, case grammar is most suitable for analyses of the Korean language [3]. In this paper, we propose a methodology that uses a case grammar approach to analyze the traceability between documents written in Korean. A discussion regarding some examples of such an analysis will follow.
Stefan Biffl - One of the best experts on this subject based on the ideXlab platform.
-
A family of experiments to investigate the effects of groupware for Software Inspection
Automated Software Engineering, 2006Co-Authors: Stefan Biffl, Paul Grunbacher, Michael HallingAbstract:It is widely accepted that the Inspection of Software artifacts can find defects early in the development process and gather information on the quality of the evolving product. However, the Inspection process is resource-intensive and involves tedious tasks, such as searching, sorting, and checking. Tool support for Inspections can help accelerating these tasks and allows inspectors to concentrate on tasks particularly needing human attention. Only few tools are available for Inspections. We have thus developed a set of groupware tools for both individual defect detection and Inspection meetings to lower the effort of Inspections and to increase their efficiency. This paper presents the Groupware-supported Inspection Process ( GrIP ) and describes tools for inspecting Software requirements. As only little empirical work exists that directly compares paper-based and tool-based Software Inspection, we conducted a family of experiments in an academic environment to empirically investigate the effect of tool support regarding defect detection and Inspection meetings. The main results of our family of experiments regarding individual defect detection are promising: The effectiveness of inspectors and teams is comparable to paper-based Inspection without tool support; the Inspection effort and defect overlap decreases significantly with tool support, while the efficiency of Inspection teams increases considerably. Regarding tool support for Inspection meetings the main findings of the experiments are that tool support considerably lowers the meeting effort, supports inspectors in identifying false positives, and reduces the number of true defects lost during a meeting. The number of unidentified false positives is still quite high.
-
an empirical study on groupware support for Software Inspection meetings
Automated Software Engineering, 2003Co-Authors: Paul Grunbacher, Michael Halling, Stefan BifflAbstract:Software Inspection is an effective way to assess product quality and to reduce the number of defects. In a Software Inspection, the Inspection meeting is a key activity to agree on collated defects, to eliminate false positives, and to disseminate knowledge among the team members. However, Inspection meetings often require high effort and may lose defects found in earlier Inspection steps due to ineffective meeting techniques. Only few tools are available for this task. We have thus been developing a set of groupware tools to lower the effort of Inspection meetings and to increase their efficiency. We conducted an experiment in an academic environment with 37 subjects to empirically investigate the effect of groupware tool support for Inspection meetings. The main findings of the experiment are that tool support considerably lowered the meeting effort, supported inspectors in identifying false positives, and reduced the number of true defects lost.
-
investigating the influence of Software Inspection process parameters on Inspection meeting performance
IEE Proceedings - Software, 2002Co-Authors: Michael Halling, Stefan BifflAbstract:The question of whether Inspection meetings justify their cost has been discussed in several studies. However, it is still open as to how modern defect detection techniques and team size influence meeting performance, particularly with respect to different classes of defect severity. The influence of Software Inspection process parameters (defect detection technique, team size, meeting effort) on defect detection effectiveness is investigated, i.e. the number of defects found for 31 teams which inspected a requirements document, to shed light on the performance of Inspection meetings. The sets of defects reported by each team after the individual preparation phase (nominal-team performance) and after the team meeting (real-team performance) are compared. The main findings are that nominal teams perform significantly more effectively than real teams for all defect classes. This implies that meeting losses are on average higher than meeting gains. Meeting effort was positively correlated with meeting gains, indicating that synergy effects can only be realised if enough time is available. With regard to meeting losses, existing reports are confirmed that for a given defect, the probability of being lost in a meeting decreases with an increase in the number of inspectors who detected this defect during individual preparation.
-
investigating the cost effectiveness of reInspections in Software development
International Conference on Software Engineering, 2001Co-Authors: Stefan Biffl, Bernd Freimut, Oliver LaitenbergerAbstract:Software Inspection is one of the most effective methods to detect defects. ReInspection repeats the Inspection process for Software products that are suspected to contain a significant number of undetected defects after an initial Inspection. As a reInspection is often believed to be less efficient than an Inspection an important question is whether a reInspection justifies its cost. In this paper we propose a cost-benefit model for Inspection and reInspection. We discuss the impact of cost and benefit parameters on the net gain of a reInspection with empirical data from an experiment in which 31 student teams inspected and reinspected a requirements document. Main findings of the experiment are: a) For reInspection benefits and net gain were significantly lower than for the initial Inspection. Yet, the reInspection yielded a positive net gain for most teams with conservative cost-benefit assumptions. b) Both the estimated benefits and number of major defects are key factors for reInspection net gain, which emphasizes the need for appropriate estimation techniques.
Katsuro Inoue - One of the best experts on this subject based on the ideXlab platform.
-
an experimental comparison of checklist based reading and perspective based reading for uml design document Inspection
International Symposium on Empirical Software Engineering, 2002Co-Authors: Giedre Sabaliauskaite, Fumikazu Matsukawa, Shinji Kusumoto, Katsuro InoueAbstract:This paper describes an experimental comparison of two reading techniques, namely Checklist-based reading (CBR) and Perspective-based reading (PBR) for Object-Oriented (OO) design Inspection. Software Inspection is an effective approach to detect defects in the early stages of the Software development process. However Inspections are usually applied for defect detection in Software requirement documents or Software code modules, and there is a significant lack of information how Inspections should be applied to OO design documents. The comparison was performed in a controlled experiment with 59 subject students. The results of individual data analysis indicate that (a) defect detection effectiveness using both Inspection techniques is similar (PBR: 69%, CBR: 70%); (b) reviewers who use PBR spend less time on Inspection than reviewers who use CBR; (c) cost per defect of reviewers who use CBR is smaller. The results of 3-person virtual team analysis show that CBR technique is more effective than PBR technique.