Abstract

An essential basis for the development of safety-critical systems is to establish high-quality requirements specifications. However, there is little guidance on the formulation of requirements for the architectures of these systems. Existing approaches to eliciting safety requirements such as those advocated by ARP 4761 and 4754 focus on the hazard analysis of either purely functional requirements (i.e. Functional Hazard Analysis) or Zonal and Particular Risks Assessments that can only be performed once the physical details of systems have been defined (typically, late lifecycle). Furthermore, there needs to be systematic consideration of the behaviours of architectural components to help refine safety requirements. In this paper, we present an approach to deriving safety requirements using Use Case Maps. Use Case Maps help capture the early interaction between requirements and architectural components and help formulate safety requirements in the early stages of architecture definition. The aim of this approach is to provide assurance on the integrity of requirements elicitation and formulation. Practical techniques for prioritising safety requirements are also integrated in this approach. We illustrate the approach by means of an example.

-- DanielAmyot - 01 Apr 2008

Discussion

FormForVirtualLibrary edit

Title Deriving Safety Requirements as Part of System Architecture Definition
Authors W. Wu and T.P. Kelly
Type Conference
Conference/Journal Title Proc. 24th Int. System Safety Conference, Albuquerque, USA
Volume/Number
Editors
Publisher System Safety Society
Month August
Year 2006
Pages
Keywords Safety requirements, Use Case Maps, Architectural design decisions
Topic revision: r1 - 01 Apr 2008, DanielAmyot
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback