Software engineering for safety: a roadmap (0)

by R R Lutz
Venue:In ICSE - Future of SE Track
Add To MetaCart
Results 1 - 10 of 38

Testing: A Roadmap

by Mary Jean Harrold - In The Future of Software Engineering , 2000
"... Testing is an important process that is performed to support quality assurance. Testing activities support quality assurance by gathering information about the nature of the software being studied. These activities consist of designing test cases, executing the software with those test cases, and ex ..."
Abstract - Cited by 100 (0 self) - Add to MetaCart
Testing is an important process that is performed to support quality assurance. Testing activities support quality assurance by gathering information about the nature of the software being studied. These activities consist of designing test cases, executing the software with those test cases, and examining the results produced by those executions. Studies indicate that more than fifty percent of the cost of software development is devoted to testing, with the percentage for testing critical software being even higher. As software becomes more pervasive and is used more often to perform critical tasks, it will be required to be of higher quality. Unless we can find efficient ways to perform effective testing, the percentage of development costs devoted to testing will increase significantly. This report briefly assesses the state of the art in software testing, outlines some future directions in software testing, and gives some pointers to software testing resources.
(Show Context)

Templates for Misuse Case Description

by Guttorm Sindre , Andreas L. Opdahl - PROCEEDINGS OF THE 7 TH INTERNATIONAL WORKSHOP ON REQUIREMENTS ENGINEERING, FOUNDATION FOR SOFTWARE QUALITY (REFSQ'2001 , 2001
"... Use cases have proven helpful for eliciting, communicating and documenting requirements. But whereas functional requirements are well supported, use cases provide less support for working with extra-functional requirements, such as security requirements. With the advent of e-commerce applications ..."
Abstract - Cited by 63 (1 self) - Add to MetaCart
Use cases have proven helpful for eliciting, communicating and documenting requirements. But whereas functional requirements are well supported, use cases provide less support for working with extra-functional requirements, such as security requirements. With the advent of e-commerce applications, security and other extra-functional requirements are growing in importance. In an earlier paper, the authors have introduced the concept of misuse cases -- inverted use cases to denote functions that should not be possible to perform in a system. In this paper, security related misuse cases are elaborated in further detail through a discussion of templates for their textual description.

PLFaultCat: A Product-Line Software Fault Tree Analysis Tool

by Josh Dehlinger - Tool”, Automated Software Engineering, Jan , 2006
"... Abstract. Industry currently employs a product line approach to software development and deployment as a means to enhance quality while reducing development cost and time. This effort has created a climate where safety-critical software product lines are being developed without the full range of acc ..."
Abstract - Cited by 23 (12 self) - Add to MetaCart
Abstract. Industry currently employs a product line approach to software development and deployment as a means to enhance quality while reducing development cost and time. This effort has created a climate where safety-critical software product lines are being developed without the full range of accompanying safety analysis tools available to software engineers. Software Fault Tree Analysis (SFTA) is a technique that has been used successfully to investigate contributing causes to potential hazards in safety-critical applications. This paper further extends the adaptation of SFTA to product lines of systems by describing a software safety analysis tool called PLFaultCAT. PLFaultCAT is an interactive, partially-automated support tool to aid software engineers in the application of product-line software SFTA. The paper describes the integration of product-line SFTA and PLFaultCAT with the software development life cycle. The description includes the initial construction of the product-line SFTA as well as the automated derivation of software fault trees for product line members. The technique and tool are illustrated with a small case study throughout the paper.

Software fault tree analysis for product lines

by Josh Dehlinger - In IEEE International Symposium on High Assurance Systems Engineering , 2004
"... The current development of high-integrity product lines threatens to outstrip existing tools for product-line verification. Software Fault Tree Analysis (SFTA) is a technique that has been used successfully to investigate contributing causes to potential hazards in safety-critical applications. This ..."
Abstract - Cited by 23 (6 self) - Add to MetaCart
The current development of high-integrity product lines threatens to outstrip existing tools for product-line verification. Software Fault Tree Analysis (SFTA) is a technique that has been used successfully to investigate contributing causes to potential hazards in safety-critical applications. This paper adapts SFTA to product lines of systems. The contribution is to define: (1) the technique to construct a product-line SFTA and (2) the pruning technique required to reuse the SFTA for the analysis of a new system in the product line. The paper describes how product-line SFTA integrates with forward-analysis techniques such as Software Failure Modes, Effects, and Criticality Analysis (SFMECA), supports requirements evolution, and helps identify previously unforeseen constraints on the systems to be built. Applications to two small examples are used to illustrate the technique. 1.
(Show Context)

Software Engineering for Real-Time: A Roadmap

by Hermann Kopetz , 2000
"... The next ten years will see distributed real-time computer systems replacing many mechanical and hydraulic control systems in high-dependability applications. In these applications a failure in the temporal domain can be as critical as a failure in the value domain. This paper discusses some of the ..."
Abstract - Cited by 14 (3 self) - Add to MetaCart
The next ten years will see distributed real-time computer systems replacing many mechanical and hydraulic control systems in high-dependability applications. In these applications a failure in the temporal domain can be as critical as a failure in the value domain. This paper discusses some of the technology trends that explain why distributed embedded real-time systems for highdependability applications will move into the mainstream. It then investigates the new requirements that must be addressed by the software engineering process. Two of the most important requirements are the design for composability and the systematic validation of highdependability distributed real-time systems. In the last two sections, these issues of composability and validation are treated in some detail. KEYWORDS Real-time systems, composability, distributed systems, validation, system architecture 1.

Safety and Software Intensive Systems: Challenges Old and New

by Mats P. E. Heimdahl , 2007
"... There is an increased use of software in safety-critical systems; a trend that is likely to continue in the future. Although traditional system safety techniques are applicable to software intensive systems, there are new challenges emerging. In this report we will address four issues we believe wil ..."
Abstract - Cited by 13 (0 self) - Add to MetaCart
There is an increased use of software in safety-critical systems; a trend that is likely to continue in the future. Although traditional system safety techniques are applicable to software intensive systems, there are new challenges emerging. In this report we will address four issues we believe will pose challenges in the future. First, the nature of safety is continuing to be widely misunderstood and known system safety techniques are not applied. Second, our ability to demonstrate (certify) that safety requirements have been met is inadequate. Third, modeling and automated tools, for example, code generation and automated testing, are introduced in a hope to increase productivity; this reliance on tools rather than people, however, introduces new and poorly understood problems. Finally, safety-critical systems are increasingly relying on data (configuration data or databases), incorrect data could have catastrophic and widespread consequences.

A Comparative Study into Architecture-Based Safety Evaluation Methodologies using AADL’s Error Annex and Failure Propagation Models

by Lars Grunske, Jun Han
"... Early quality evaluation and support for decisions that affect quality characteristics are among the key incentives to formally specify the architecture of a software-intensive system. The Architecture Analysis and Description Language (AADL) with its Error Annex is a new and promising architecture ..."
Abstract - Cited by 7 (1 self) - Add to MetaCart
Early quality evaluation and support for decisions that affect quality characteristics are among the key incentives to formally specify the architecture of a software-intensive system. The Architecture Analysis and Description Language (AADL) with its Error Annex is a new and promising architecture modeling language that supports analysis of safety and other dependability properties. This paper reviews the key concepts that are introduced by the Error Annex, and compares it to the existing safety evaluation techniques regarding its ability in providing modeling, process and tool support. Based on this review and the comparison, its strengths and weaknesses are identified and possible improvements for the model-driven safety evaluation methodology based on AADL’s Error Annex are highlighted. 1
(Show Context)

Towards an Integration of Standard Component-Based Safety Evaluation Techniques with SaveCCM

by Lars Grunske
"... Abstract. To deliver complex functionalities in a cost effective manner, embedded software should ideally be developed with standardized interoperable components. At the same time, most of these embedded systems must be demonstrably safe and reliable. This paper aims to extend SaveCCM, a modelling l ..."
Abstract - Cited by 7 (2 self) - Add to MetaCart
Abstract. To deliver complex functionalities in a cost effective manner, embedded software should ideally be developed with standardized interoperable components. At the same time, most of these embedded systems must be demonstrably safe and reliable. This paper aims to extend SaveCCM, a modelling language for component-based embedded systems, with standard safety evaluation models. Based on this extension, failure and hazard probabilities can be estimated early in the development process and can be used to check if a system can fulfil its safety requirements. The procedure of the safety evaluation is demonstrated with the case study of a computer assisted braking system. 1
(Show Context)

A consortium-based model for the development of a concentration track in embedded systems

by Gerald C. Gannod, Forouzan Golshani, Ben Huey, Yann-hang Lee, Sethuraman Panchanathan, David Pheanis - in Proc. of the 2002 American Society for Engineering Education Annual Conference and Exposition , 2002
"... 1 ..."
Abstract - Cited by 6 (1 self) - Add to MetaCart
Abstract not found
(Show Context)

Trust-By-Contract: Modelling, Analysing And Predicting Behaviour Of Software Architectures

by Heinz Schmidt, Iman Poernomo, Ralf Reussner , 2001
"... this paper, we focus on several aspects of TrustME that facilitate specification and analysis of middlewarebased architectures for trusted enterprise computing systems ..."
Abstract - Cited by 6 (1 self) - Add to MetaCart
this paper, we focus on several aspects of TrustME that facilitate specification and analysis of middlewarebased architectures for trusted enterprise computing systems