Product-line requirements specification (PRS): an approach and case study

Faulk, Stuart

doi:10.1109/isre.2001.948543

Cited by 24 publications

(21 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The approach exploits genericity both within as well as between target system variants. Although productline engineering has been applied in engine and flight control systems [25,19], we are not aware of any such work in the FDM domain. Using UML-B we define generic classes of failure-detection test for sensors and variables in the system environment, such as rate-of-change, limit, and multiple-redundant-sensor, which are simply instantiated by parameter.…”

Section: Contributionmentioning

confidence: 99%

“…[36,19,26,25]. In this type of approach, application engineering deploys an instance derivation process against generic models/architectures and specific components/interfaces and variation points, to generate an instance system: an elaborate process of syntactic modification.…”

Section: Related Work In Contextmentioning

confidence: 99%

“…This kind of generic systems engineering is well known in the avionics industry; e.g. [25,19] describe the reuse of generic sets of requirements in engine control and flight control systems. Domain analysis and object oriented frameworks are among numerous solutions proposed to product line technology.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Rigorous engineering of product-line requirements: A case study in failure management

Snook

Poppleton

Johnson³

2008

Information and Software Technology

View full text Add to dashboard Cite

We consider the failure detection and management function for engine control systems as an application domain where product line engineering is indicated. The need to develop a generic requirement set -for subsequent system instantiation -is complicated by the addition of the high levels of verification demanded by this safety-critical domain, subject to avionics industry standards. We present our case study experience in this area as a candidate method for the engineering, validation and verification of generic requirements using domain engineering and Formal Methods techniques and tools. For a defined class of systems, the case study produces a generic requirement set in UML and an example system instance. Domain analysis and engineering produce a validated model which is integrated with the formal specification/ verification method B by the use of our UML-B profile. The formal verification both of the generic requirement set, and of a simple system instance, is demonstrated using our U2B, ProB and prototype Requirements Manager tools. This work is a demonstrator for a tool-supported method which will be an output of EU project RODIN 1 . The use of existing and prototype formal verification and support tools is discussed. The method, developed in application to this novel combination of product line, failure management and safety-critical engineering, is evaluated and considered to be applicable to a wide range of domains.

show abstract

Section: Contributionmentioning

confidence: 99%

Section: Related Work In Contextmentioning

confidence: 99%

See 1 more Smart Citation

Rigorous engineering of product-line requirements: A case study in failure management

Snook

Poppleton

Johnson³

2008

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…The approach exploits genericity both within as well as between target system variants. Although product-line engineering has been applied in engine and flight control systems [16,11], we are not aware of any such work in the FDM domain. We define generic classes of failure-detection test for sensors and variables in the system environment, such as rate-of-change, limit, and multiple-redundantsensor, which are simply instantiated by parameter.…”

Section: Failure Detection and Management For Engine Controlmentioning

confidence: 99%

“…The need for generic approaches to support reuse in systems engineering is well known; in the avionics industry, for example, [16,11] describe the reuse of generic sets of requirements in engine control and flight control systems. The need for reuse arises in many contexts, such as in system evolution, adaptation, or component-based construction.…”

Section: Introductionmentioning

confidence: 99%

Towards a Method for Rigorous Development of Generic Requirements Patterns

Snook

Poppleton

Johnson³

2006

Rigorous Development of Complex Fault-Tolerant Systems

View full text Add to dashboard Cite

Abstract. We present work in progress 3 on a method for the engineering, validation and verification of generic requirements using domain engineering and formal methods. The need to develop a generic requirement set for subsequent system instantiation is complicated by the addition of the high levels of verification demanded by safety-critical domains such as avionics. Our chosen application domain is the failure detection and management function for engine control systems: here generic requirements drive a software product line of target systems. A pilot formal specification and design exercise is undertaken on a small (twosensor) system element. This exercise has a number of aims: to support the domain analysis, to gain a view of appropriate design abstractions, for a B novice to gain experience in the B method and tools, and to evaluate the usability and utility of that method. We also present a prototype method for the production and verification of a generic requirement set in our UML-based formal notation, UML-B, and tooling developed in support. The formal verification both of the structural generic requirement set, and of a particular application, is achieved via translation to the formal specification language, B, using our U2B and ProB tools.

show abstract

Structuring product family requirements for n-dimensional and hierarchical product lines

Heimdahl

2003

Requirements Engineering

View full text Add to dashboard Cite

The software product-line approach (for software product families) is one of the success stories of software reuse. When applied, it can result in cost savings and increases in productivity. In addition, in safety-critical systems the approach has the potential for reuse of analysis and testing results, which can lead to a safer systems. Nevertheless, there are times when it seems like a product family approach should work when, in fact, there are difficulties in properly defining the boundaries of the product family.In this paper, we draw on our experiences in applying the software product-line approach to a family of mobile robots, a family of flight guidance systems, and a family of cardiac pacemakers, as well as case studies done by others to (1) illustrate how domain structure can currently limit applicability of product-line approaches to certain domains and (2) demonstrate our progress towards a solution using a set-theoretic approach to reason about domains of what we call n-dimensional and hierarchical product families.

show abstract

Product-line requirements specification (PRS): an approach and case study

Cited by 24 publications

References 9 publications

Rigorous engineering of product-line requirements: A case study in failure management

Rigorous engineering of product-line requirements: A case study in failure management

Towards a Method for Rigorous Development of Generic Requirements Patterns

Structuring product family requirements for n-dimensional and hierarchical product lines

Contact Info

Product

Resources

About