You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at http://www.ieee.org/web/publications/rights/copyrightpolicy.html)
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at http://www.acm.org/pubs/copyright_policy/)
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact webmaster@ide.mdh.se

Specifying Software Requirements for Safety-Critical Railway Systems: an Experience Report

Fulltext:


Publication Type:

Conference/Workshop Paper

Venue:

International Working Conference on Requirements Engineering: Foundation for Software Quality

DOI:

10.1007/978-3-319-54045-0_25


Abstract

Software safety requirements are fundamental in the definition of risk reduction measures for safety critical systems, since they are developed to satisfy the system safety constraints as identified by mandated safety analyses. It is therefore imperative that the requirements are defined clearly and precisely. We describe our experiences in introducing a safety compliant method of writing safety software requirements for railway projects in a distributed organization. Our goal was twofold, to develop requirements specifications that comply with the EN 50128 standard and that are understandable by the persons involved in the software development. We introduced methods to transform natural language requirements to functional requirements described as scenarios, sequence, use-case and state-machine diagrams. Our experience shows that new ways of expressing requirements, even if proper to solve technical issues such as compliance with standards, bring other challenges to the organization like people’s reluctance to changes in working routines and process updates.

Bibtex

@inproceedings{Provenzano4625,
author = {Luciana Provenzano and Kaj H{\"a}nninen},
title = {Specifying Software Requirements for Safety-Critical Railway Systems: an Experience Report},
editor = {Springer},
pages = {363--369},
month = {February},
year = {2017},
booktitle = {International Working Conference on Requirements Engineering: Foundation for Software Quality},
url = {http://www.es.mdh.se/publications/4625-}
}