Requirements Engineering for Critical Systems:
A Good Practice Guide
RE-GPG
|
|
Introduction
The requirements engineering (RE) process is the process which is concerned with
developing the set of requirements a system must satisfy. Organisations concerned
with developing large systems have usually evolved their own requirements
engineering process that is part of a more general systems engineering process.
The RE-GPG suggests a set of good practices for the requirements engineering
process. The good practice guidelines are presented in a clear and readable way.
They range from very simple guidelines to improve traceability through to more
complex suggestions for process improvement.
The RE-GPG is to be published as a
book.
Summary Description
The RE-GPG presents a list of over 50 recommended good practices which may
included in a requirements engineering process. Guidelines cover the following
areas:
- The requirements engineering process
- The system development process
- Requirements evolution
- Requirements management
- Critical systems requirements
All of the guidelines include a simple guideline statement, an explanation of
what this means, an explanation of why it is useful, an explanation of how you
can implement the guideline, indications of possible problems of implementing the
guideline and what it might cost and a list of related guidelines.
The document also includes a number of appendices describing some of the
practices suggested in the guidelines in more detail.
Benefits and Application Areas
This list of guidelines may be considered as a support for RE process improvement
and for the PI-GPG module. Rather than rigid maturity categories as suggested in
the SEI Capability Maturity Model, we recognise that different organisations have
different priorities in their process improvement. The problems of requirements
engineering process improvement can be tackled by comparing your current process
with these guidelines then selecting a set of guidelines for implementation. This
process can continue iteratively as resources and time become available thus
ensuring continuous process improvement.
The guidelines may be applied in any organisation which is concerned with
requirements engineering. However, some of the guidelines are specifically
concerned with problems of critical, safety-related systems.
How to Apply
The good practices recommended for the requirements engineering process can be
applied in any software development organisation. There are no pre-requisites
for applying some of the suggestions here but others may require more detailed
information found in other REAIMS modules such as MERE, PERE and PREview.
More information available from:
|
| Prof Ian Sommerville
Computing Department
Lancaster University
Lancaster LA1 4YR
United Kingdom
|
Phone: +44-1524-593795
FAX: +44-1524-593608
email: is@comp.lancs.ac.uk
|
|
| Stephen Shirlaw
Project Coordinator
GEC Alsthom
|
Phone: +44-181-236-9254
FAX: +44-181-207-6694
email:
s.shirlaw@gasl.co.uk
|
|
| Herbert Schippers
TÜV Informationstechnik GmbH
Im Teelbruch 122
D - 45219 Essen
Germany
|
Phone: +49 201 825 5120
FAX: +49 201 825 5131
email: H.Schippers@tuvit.cubis.de
|
|
| Robin Bloomfield
Adelard
3, Coborn Road
London E3 2DA
United Kingdom
|
Phone: +44-181 983 0217
FAX: +44-181 983 1845
email: reb@adelard.co.uk
|
|
| Jean-Pierre Heckmann
Aerospatiale Avions
A/BTE/SY/SQIP
316, Route de Bayonne
F-31060CX Toulouse
France
|
Phone: +33-6193 6012
FAX: +33-6193 8090
email:
jean-pierre.heckmann@avions.aerospatiale.fr
|
Page last updated Thu, 18 December 1997. Please report problems to
reaims-request@comp.lancs.ac.uk