In embedded systems development safety and reliability are important quality characteristics. It is thus required to determine the reliability and safety of a complete system including hardware and software. It is rea...
详细信息
In embedded systems development safety and reliability are important quality characteristics. It is thus required to determine the reliability and safety of a complete system including hardware and software. It is reasonable to analyze particular failures that may cause, for example, safety critical situations. The basic idea of our approach is the automated generation of so-called fault trees based on the source code of the software. These may be combined with fault trees based on the electronic circuit design of the hardware. It is important to do the generation in such a way that the software and the hardware fault trees can be composed into a valid fault tree of the system. Fault tree generation is a largely automated approach. We have implemented a prototype of a fault tree generation tool that is capable to generate fault trees based on C++ code. The fault tree generation tool for electronic circuits has already been used to analyze failure situations in industrial automation applications. If a structural approach is not applicable, stochastic techniques may be used. We developed the reliability assessment tool RAT that supports reliability analysis of softwaresystems.
A company builds a software system capable of running a diesel engine in a week, and in one case over a weekend, as opposed to the full year that it used to take. Another company builds one of its typical systems with...
ISBN:
(纸本)9780769510507
A company builds a software system capable of running a diesel engine in a week, and in one case over a weekend, as opposed to the full year that it used to take. Another company builds one of its typical systems with 13 software engineers instead of the more than 100 it once required, and at the same time decreases the systems defect rate ten-fold. Still another increases its software-intensive product offerings from four per year to 50 per year. Imagine being able to use one person to integrate and test 1.5 million source lines of Ada for a real-time command-and-control system onboard a ship, with safety-critical requirements? Or increasing software productivity four-fold over three years, as another company has done? These organizations all achieved their results through strategic software reuse. We software people have been promising the benefits of reuse for decades. Are we finally achieving a reuse strategy that lives up to its hype?
After a software inspection the project manager has to decide whether a product has sufficient quality to pass on to the next software development stage or whether a second inspection cycle, a reinspection, is likely ...
详细信息
After a software inspection the project manager has to decide whether a product has sufficient quality to pass on to the next software development stage or whether a second inspection cycle, a reinspection, is likely to sufficiently improve its quality. The reinspection decision of recent research focused on the estimation of product quality after inspection, which does not take in to account the effect of a reinspection. Thus we propose to use estimation models for the quality improvement during reinspection and the cost and benefit of a reinspection as basis for the reinspection decision. We evaluate the reinspection decision correctness of these models with time-stamped defect data from a large-scale controlled experiment on the inspection and reinspection of a software requirements document. The main finding of the investigation is that the product quality criterion is likely to force products to be reinspected, if a large number of defects were detected in the first inspection. Further the product-quality, criterion is especially sensitive to an underestimation of the number of defects in the product and will let bad products pass as good. The cost-benefit criterion is less sensitive to estimation error than the product-quality criterion and should in practice be used as second opinion, if a product-quality criterion is applied.
Many small and medium-sized companies that develop software experience the same problems repeatedly, and have few systems in place to learn from their own mistakes as well as their own successes. Here, we propose a li...
详细信息
This paper presents a skills management system in a medium-sized software consulting company, and how it is used. We found four different types of usage: Searching for competence to solve problems, allocating resource...
详细信息
software inspections have established an impressive track record for early defect detection and correction. To increase their benefits, recent research efforts have focused on two different areas: systematic reading t...
详细信息
ISBN:
(纸本)0769510434
software inspections have established an impressive track record for early defect detection and correction. To increase their benefits, recent research efforts have focused on two different areas: systematic reading techniques and defect content estimation techniques. While reading techniques are to provide guidance for inspection participants on how to scrutinize a software artifact in a systematic manner, defect content estimation techniques aim at controlling and evaluating the inspection process by providing an estimate of the total number of defects in an inspected document. Although several empirical studies have been conducted to evaluate the accuracy of defect content estimation techniques, only few consider the reading approach as an influential factor. The authors examine the impact of two specific reading techniques: a scenario based reading technique and checklist based reading, on the accuracy of different defect content estimation techniques. The examination is based on data that were collected in a large experiment with students of the Vienna University of Technology. The results suggest that the choice of the reading technique has little impact on the accuracy of defect content estimation techniques. Although more empirical work is necessary to corroborate this finding, it implies that practitioners can use defect content estimation techniques without any consideration of their current reading technique.
The inspection of early life-cycle artifacts such as requirement documents promises great benefits. However, research demonstrates that the inspection process is complex and expensive and that tool support would be hi...
详细信息
ISBN:
(纸本)076951426X
The inspection of early life-cycle artifacts such as requirement documents promises great benefits. However, research demonstrates that the inspection process is complex and expensive and that tool support would be highly desirable. Existing inspection tools focus largely on the inspection of source code. We have therefore devised groupware support for inspecting requirements. Based on our experience with adopting a group support system (GSS) for requirements negotiation, we decided to tailor this commercial GSS to support inspection of requirements. The paper discusses our concept of a Groupware-supported Requirements Inspection Process (GRIP) and shows that tailoring a COTS GSS works well to automate this process.
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 af...
详细信息
ISBN:
(纸本)0769510507
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.
暂无评论