A case study: validation of guidance control software requirements for completeness, consistency and fault tolerance

Sheldon, Frederick T.; Kim, Hye Yeon; Zhou, Zhiyuan

doi:10.1109/prdc.2001.992714

Cited by 8 publications

(5 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Most recent studies of completeness of specification in the literature are related to the application of some formal method for analysis and validation or often related to algebraic specifications [28]. For example Sheldon et al [29] have combined Z, Statecharts, and Stochastic Activity Network to validate a Natural Language software requirements specifications for completeness, consistency, and fault-tolerance.…”

Section: Completenessmentioning

confidence: 99%

On the interplay between consistency, completeness, and correctness in requirements evolution

Zowghi

Gervasi

2003

Information and Software Technology

114

103

View full text Add to dashboard Cite

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 different kinds of validation checks that must be performed on different 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. (C) 2003 Elsevier B.V. All rights reserved

show abstract

Section: Completenessmentioning

confidence: 99%

On the interplay between consistency, completeness, and correctness in requirements evolution

Zowghi

Gervasi

2003

Information and Software Technology

114

103

View full text Add to dashboard Cite

show abstract

“…The investigation should ask whether procedures were followed and whether there was appropriate control to prevent distribution of the defective product. The validation of the system subjected to various system parameters such as consistency and fault tolerance are tested for the detected defect [12]. The magnitude of the investigation should correlate with the significance and risk of the problem.…”

Section: A Failure Investigationmentioning

confidence: 99%

A cutting edge quality management system to optimize quality and to ensure compliance in life sciences automation

Kumar

Amma

2015

2015 Online International Conference on Green Engineering and Technologies (IC-GET)

View full text Add to dashboard Cite

The 21 st century is moving with advanced and aggressive technologies in the world. Even mankind found great technologies to help in life sciences industries. There are some great challenges that arise in the life sciences and medicines industries. The great way to deal with this challenge is to interface the engineering technologies with the life science and medicines. The adaptation of engineering in these fields is mandatory in data handling and regulatory compliance in order to maintain high quality of life sciences products. To reduce the risks in poor quality control and regulatory issues, life science industry's needed to go for the engineering solutions. Software solutions should help to maintain the quality management at high level and handle the regulatory compliance. The proposed system is focusing the problems faced by the life science, health care and medical industry in quality arena and the solutions with the engineering technologies to those problems. The life science industries such as pharmacy, biotech and medical devices manufacturers need to dealt with the regulatory compliance and quality management. In the proposed approach the requirements validation factors such as consistency, completeness, and scalability, stability, and validity factors are checked before workflow design. It helps to solve the systems consistency problems and system design issues in the developed stages of the system. Solving these issues at initial stages helps users to save time and cost and it improves the productivity. The centralized quality management system helps to maintain the quality and regulatory compliance at a single system.

show abstract

“…Many works (e.g., [11], [12], [13] and [14]) aim at studying the quality attributes of software requirements, such as correctness, completeness, consistency, clarity, and feasibility.…”

Section: Background and Related Workmentioning

confidence: 99%

Errors on Space Software Requirements: A Field Study and Application Scenarios

Véras

Villani

Ambrosio

et al. 2010

2010 IEEE 21st International Symposium on Software Reliability Engineering

View full text Add to dashboard Cite

This paper presents a field study on real errors found in space software requirements documents. The goal is to understand and characterize the most frequent types of requirement problems in this critical application domain. To classify the software requirement errors analyzed we initially used a well-known existing taxonomy that was later extended in order to allow a more thorough analysis. The results of the study show a high rate of requirement errors (9.5 errors per each 100 requirements), which is surprising if we consider that the focus of the work is critical embedded software. Besides the characterization of the most frequent types of errors, the paper also proposes a set of operators that define how to inject realistic errors in requirement documents. This may be used in several scenarios, including: evaluating and training reviewers, estimating the number of requirement errors in real specifications, defining checklists for quick requirement verification, and defining benchmarks for requirements specifications.

show abstract

A case study: validation of guidance control software requirements for completeness, consistency and fault tolerance

Abstract: In this paper, we discuss a case study performed for validating a Natural Language (NL) based software requirements specification (SRS)

Cited by 8 publications

References 15 publications

On the interplay between consistency, completeness, and correctness in requirements evolution

On the interplay between consistency, completeness, and correctness in requirements evolution

A cutting edge quality management system to optimize quality and to ensure compliance in life sciences automation

Errors on Space Software Requirements: A Field Study and Application Scenarios

Contact Info

Product

Resources

About