|
Held in conjunction with the 12th IEEE International Requirements
Engineering Conference,
sponsored by the IEEE Computer Society Technical Council on Software
Engineering (TCSE), and the Information Processing Society of Japan, held
September 6, 2004, Kyoto, Japan
Welcome - Conference Description
|
Papers
|
Workshop Description
|
Goal
Workshop Chairs
|
Program Committee
|
Disclaimers and Copyright Information
Note:
the RHAS 2004 Workshop Proceedings
and the RHAS 2003 Workshop Proceedings
are also available in portable document format (PDF).
Welcome - Workshop Chairs
A high assurance system is a software-intensive system that must
dependably deliver its services by exhibiting sufficient safety, security,
survivability, reliability, robustness, and performance. Safety critical
systems are those high assurance systems that can cause accidents resulting in
significant harm to people, property, or the environment. For such systems,
safety risks must be reduced to an acceptably low level. Thus,
developers of such systems must eliminate or minimize hazards to avoid
accidents and minimize the negative consequences of any accidents that do
occur.
The goal of the RHAS 04 Workshop was to bring together in a set of small
focused working groups researchers and practitioners from the fields of safety
engineering and requirements engineering to exchange ideas and their
experiences concerning the engineering of safety-related requirements.
Much research and development remains to be done on this important problem,
and together researchers and practitioners need to identify and explore
important subproblems and propose, formulate, and evaluate promising
solutions. This third workshop on Requirements for High Assurance Systems was
one of many forums that will allow new ideas to be proposed and discussed.
A set of topics has been identified for discussion at the workshop.
Discussing these topics should clarify common assumptions and important
issues. The accepted papers are each associated with at least one of the
topics. The topics include the following:
- What types of safety-related requirements exist, and how do their
differences affect the way they are elicited, analyzed, and specified?
- What are useful processes and techniques for engineering safety-related
requirements?
- What kinds of tools are needed to support the engineering of
safety-related requirements?
Additionally another topic to be selected by attendees will be
discussed.
We thank the authors for their submissions, the members of the RHAS '04
program committee for their constructive reviews, and the organizers of the
International Requirements Engineering Conference (RE '04) for providing a
forum for the RHAS '04 Workshop. We also appreciate the support received from
the Software Engineering Institute for the publication process. The support of
Pamela D. Curtis, the SEI editor who prepared these proceedings, is especially
appreciated.
Donald Firesmith, Co-Chair, and Nancy R. Mead, Co-Chair
Software Engineering Institute, Carnegie Mellon University
Pittsburgh, Pennsylvania, U.S.A.
return to top
Papers
Note: the following are all in portable document format (PDF).
Applying ISO/IEC 9126-1 Quality Model to Quality
Requirements Engineering on Critical Software,
Motoei Azuma, Waseda University
Managing a System Safety Case in an Integrated
Environment, Saeed Fararooy, rcm2.limited
A Taxonomy of Safety-Related
Requirements, Donald G. Firesmith, SEI
Using Abuse Frames to Bound the Scope of Security
Problems, Luncheng Lin, Bashar Nuseibeh, and Darrel Ince,
The Open University
Requirements Elicitation and Analysis Processes for
Safety and Security Requirements, Nancy R. Mead, SEI
From System Safety Analysis to Software
Specification, Elena Troubitsyna, Abo Akademi University
return to top
Description
A high assurance system is a software-intensive system that must
dependably deliver its services by exhibiting sufficient safety, security,
survivability, reliability, robustness, and performance. Safety critical
systems are those high assurance systems that can cause accidents resulting in
significant harm to people, property, or the environment. For such systems,
safety risks must be reduced to an acceptably low level. Thus,
developers of such systems must eliminate or minimize hazards to avoid
accidents and minimize the negative consequences of any accidents that do
occur.
Goal
To bring together in a set of small focused working groups researchers and
practitioners from the fields of safety engineering and requirements
engineering to exchange ideas and their experiences concerning the engineering
of safety requirements, safety constraints, and safety-critical functional,
data, and interface requirements.
return to top
Workshop Chairs
Donald G. Firesmith
Software Engineering Institute
Carnegie Mellon University
E-mail: dgf@sei.cmu.edu
Nancy R. Mead
Software Engineering Institute
Carnegie Mellon University
E-mail: nrm@sei.cmu.edu
Program Committee Members
Motoei Azuma, Japan
Dan Berry, Canada
Ramesh Bharadwaj, U.S.A.
Anthony Hall, U.K.
Scott Hissam, U.S.A.
Tohru Kikuno, Japan
Robyn Lutz, U.S.A.
Bashar Nuseibeh, U.K.
Paul Tiplady, U.K.
Naoki Yonezaki, Japan
return to top
|
RHAS main page
|
SEI Home Page
The Software
Engineering Institute (SEI) is a federally funded research and
development center sponsored by the U.S. Department of Defense
and operated by Carnegie Mellon University.
Copyright
2007
by Carnegie Mellon University
Terms of Use
URL: http://www.sei.cmu.edu/rhas-workshop/2004/rhas04-proceedings.html
Last Modified: 3 August 2007
|