Results 1 - 10
of
109
Basic concepts and taxonomy of dependable and secure computing
- IEEE TDSC
, 2004
"... This paper gives the main definitions relating to dependability, a generic concept including as special case such attributes as reliability, availability, safety, integrity, maintainability, etc. Security brings in concerns for confidentiality, in addition to availability and integrity. Basic defin ..."
Abstract
-
Cited by 779 (6 self)
- Add to MetaCart
(Show Context)
This paper gives the main definitions relating to dependability, a generic concept including as special case such attributes as reliability, availability, safety, integrity, maintainability, etc. Security brings in concerns for confidentiality, in addition to availability and integrity. Basic definitions are given first. They are then commented upon, and supplemented by additional definitions, which address the threats to dependability and security (faults, errors, failures), their attributes, and the means for their achievement (fault prevention, fault tolerance, fault removal, fault forecasting). The aim is to explicate a set of general concepts, of relevance across a wide range of situations and, therefore, helping communication and cooperation among a number of scientific and technical communities, including ones that are concentrating on particular types of system, of system failures, or of causes of system failures.
An Experiment to Assess the Cost-Benefits of Code Inspections in Large Scale Software Development
- IEEE Transactions on Software Engineering
, 1995
"... We are conducting a long-term experiment (in progress) to compare the costs and benefits of several different software inspection methods. These methods are being applied by professional developers to a commercial software product they are currently writing. Because the laboratory for this experime ..."
Abstract
-
Cited by 65 (6 self)
- Add to MetaCart
(Show Context)
We are conducting a long-term experiment (in progress) to compare the costs and benefits of several different software inspection methods. These methods are being applied by professional developers to a commercial software product they are currently writing. Because the laboratory for this experiment is a live development effort, we took special care to minimize cost and risk to the project, while maximizing our ability to gather useful data. This article has several goals: (1) to describe the experiment's design and show how we used simulation techniques to optimize it, (2) to present our preliminary results and discuss their implications for both software practitioners and researchers, and (3) to discuss how we expect to modify the experiment in order to reduce potential risks to the project. For each inspection we randomly assign 3 independent variables: (1) the number of reviewers on each inspection team (1, 2 or 4), (2) the number of teams inspecting the code unit (1 or 2), and (...
The Three Dimensions of Requirements Engineering
, 1993
"... . Requirements engineering (RE) is perceived as an area of growing importance. Due to the increasing effort spent for research in this area many contributions to solve different problems within RE exist. The purpose of this paper is to identify the main goals to be reached during the requirements en ..."
Abstract
-
Cited by 58 (4 self)
- Add to MetaCart
(Show Context)
. Requirements engineering (RE) is perceived as an area of growing importance. Due to the increasing effort spent for research in this area many contributions to solve different problems within RE exist. The purpose of this paper is to identify the main goals to be reached during the requirements engineering process in order to develop a framework for RE. This framework consists of the three dimensions: . the specification dimension . the representation dimension . the agreement dimension Looking at the RE research using this framework, the different approaches can be classified and therefore their interrelationships become much clearer. Additionally the framework offers a first step towards a common understanding of RE. + This work was supported by ESPRIT Basic Research Action 6353 (NATURE) which is concerned with Novel Approaches to Theories Underlying Requirements Engineering and by the state Nordrhein-Westfalen, Germany. 1 Introduction There is general agreement among softwa...
Dependable computing: From concepts to design diversity
- Proceedings of the IEEE
, 1986
"... This paper is composed of two sections. The first provides a conceptual framework for expressing the attributes of what constitutes dependable and reliable computing: a) the impairments to dependability (faults, errors, and failures), 6) the means for dependability (fault avoidance, tolerance, remov ..."
Abstract
-
Cited by 50 (4 self)
- Add to MetaCart
This paper is composed of two sections. The first provides a conceptual framework for expressing the attributes of what constitutes dependable and reliable computing: a) the impairments to dependability (faults, errors, and failures), 6) the means for dependability (fault avoidance, tolerance, removal, and forecasting), and c) the measures of dependability (reliability, availability, safety). The second section focuses on one of the most challenging pro& /ems for dependable computing: coping with design faults.
System and Software Requirements Engineering
- IEEE Computer Society Press Tutorial
, 1990
"... Editor’s Note: The following article is reprinted from the book Software Requirements Engineering, Second Edition, and is provided for readers who want to read a brief tutorial on requirements engineering. The views expressed in this article are the author’s only and do not ..."
Abstract
-
Cited by 45 (0 self)
- Add to MetaCart
Editor’s Note: The following article is reprinted from the book Software Requirements Engineering, Second Edition, and is provided for readers who want to read a brief tutorial on requirements engineering. The views expressed in this article are the author’s only and do not
A review of software inspections
- Software Process, volume 42 of Advances in Computers
, 1996
"... For two decades, software inspections have proven e ective for detecting defects in software. We have reviewed the di erent ways software inspections are done, created a taxonomy of inspection methods, and examined claims about the cost-e ectiveness of di erent methods. We detect a disturbing patter ..."
Abstract
-
Cited by 27 (1 self)
- Add to MetaCart
For two decades, software inspections have proven e ective for detecting defects in software. We have reviewed the di erent ways software inspections are done, created a taxonomy of inspection methods, and examined claims about the cost-e ectiveness of di erent methods. We detect a disturbing pattern in the evaluation of inspection methods. Although there is universal agreement on the e ectiveness of software inspection, their economics are uncertain. Our examination of several empirical studies leads us to conclude that the bene ts of inspections are often overstated and the costs (especially for large software developments) are understated. Furthermore, some of the most in uential studies establishing these costs and bene ts are 20 years old now, which leads us to question their relevance to today's software development processes. Extensive work is needed to determine exactly how, why, and when software inspections work, and whether some defect detection techniques might be more cost-e ective than others. In this article we ask some questions about measuring e ectiveness of software inspections and determining how much they really cost when their e ect on the rest of the development process is considered. Finding answers to these questions will enable us to improve the e ciency of software development. 1
Coupling Use Cases and Class Models as a Means for Validation and Verification of Requirements Specifications
, 2001
"... this paper, we propose a method for a proper coupling of UML use cases and class models. Since the class model provides a finer granularity and more rigorous semantics compared to the use case model, we start with a refinement of use cases to achieve more precise specifications. To this end, we tail ..."
Abstract
-
Cited by 22 (4 self)
- Add to MetaCart
this paper, we propose a method for a proper coupling of UML use cases and class models. Since the class model provides a finer granularity and more rigorous semantics compared to the use case model, we start with a refinement of use cases to achieve more precise specifications. To this end, we tailor activity graphs for a suitable modeling of use case behavior. Granularity and semantics of the refinement allow to establish a seamless, traceable transition of use cases via activity graphs to the class model. The approach supports not only consistency and completeness checks but also the verification of the class model against the use case model. The verification ensures that the class model is able to cope with the use cases, or more precise, that the instances of classes in the class model are able to execute the use cases. Furthermore, the activity graph based Correspondence and offprint requests to: Mario Winter, FernUniversitt Hagen, Prakt. Inf. III / IZ, Feithstr. 142, D-58084 Hagen, Germany. Email: mario.winter@fernuni-hagen.de
Heterogeneous View Integration and its Automation
- PhD thesis, USC
, 2000
"... xiv 1 ..."
(Show Context)
Identifying Nocuous Ambiguity in Natural Language Requirements
, 2006
"... This dissertation is an investigation into how ambiguity should be classified for authors and readers of text, and how this process can be automated. Usually, authors and readers disambiguate ambiguity, either consciously or unconsciously. However, disambiguation is not always appropriate. For insta ..."
Abstract
-
Cited by 20 (3 self)
- Add to MetaCart
This dissertation is an investigation into how ambiguity should be classified for authors and readers of text, and how this process can be automated. Usually, authors and readers disambiguate ambiguity, either consciously or unconsciously. However, disambiguation is not always appropriate. For instance, a linguistic construction may be read differently by different people, with no consensus about which reading is the intended one. This is particularly dangerous if they do not realise that other readings are possible. Misunderstandings may then occur. This is particularly serious in the field of requirements engineering. If requirements are misunderstood, systems may be built incorrectly, and this can prove very costly. Our research uses natural language processing techniques to address ambiguity in requirements. We develop a model of ambiguity, and a method of applying it, which represent a novel approach to the problem described here. Our model is based on the notion that human perception is the only valid criterion for judging ambiguity. If people perceive very differently how an ambiguity should be read, it will cause misunderstandings. Assigning a preferred reading to it is therefore unwise. In
On the Interplay between Consistency, Completeness, and Correctness in Requirements Evolution
- the Journal of Information and Software Technology, Volume 45, Issue
, 2003
"... The initial expression of requirements for a computer-based system is often informal and possibly vague. Requirements engineers need to examine this often incomplete and inconsistent brief expression of needs. Based on the available knowledge and expertise, assumptions are made and conclusions are d ..."
Abstract
-
Cited by 17 (1 self)
- Add to MetaCart
(Show Context)
The initial expression of requirements for a computer-based system is often informal and possibly vague. Requirements engineers need to examine this often incomplete and inconsistent brief expression of needs. Based on the available knowledge and expertise, assumptions are made and conclusions are deduced to transform this "rough sketch" into more complete, consistent, and hence correct requirements. This paper addresses the question of how to characterize these properties in an evolutionary framework, and what relationships link these properties to a customer's view of correctness. Moreover, we describe in rigorous terms the di#erent kinds of validation checks that must be performed on di#erent parts of a requirements specification in order to ensure that errors (i.e., cases of inconsistency and incompleteness) are detected and marked as such, leading to better quality requirements.
