Abstract
Context and motivation: 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. Question/Problem: 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. Principal ideas/results: We introduced methods to transform natural language requirements to functional requirements described as scenarios, sequence, use-case and state-machine diagrams. Contribution: 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.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Similar content being viewed by others
References
CENELEC EN 50128 Railway applications – Communication, signaling and processing systems – Software for railway control and protection systems (2011)
Shahrokni, A., Feldt, R.: Towards a framework for specifying software robustness requirements based on patterns. In: Wieringa, R., Persson, A. (eds.) REFSQ 2010. LNCS, vol. 6182, pp. 79–84. Springer, Heidelberg (2010). doi:10.1007/978-3-642-14192-8_9
Gustavsson, J., Österlund, M.: Requirements on maintainability of software systems – an investigation of the state of the practice. In: SERPS 2005 5th Conference on Software Engineering and Practice in Sweden (2005)
Bondi, A.B.: Best practices for writing and managing performance requirements: A tutorial. In: ICPE 2012 Proceedings of the 3rd ACM/SPEC International Conference on Performance Engineering, pp. 1–8 (2012)
Cockburn, A.: Writing Effective Use Cases. Addison-Wesley, Boston (2011)
Larrucea, X., Combelles, A., Favaro, J.: Safety-critical software [Guest editors’ introduction]. IEEE Softw. 30(3), 25–27 (2013)
IBM Rational DOORS. http://www-03.ibm.com/software/products/en/ratidoor
FMEA. https://en.wikipedia.org/wiki/Failure_mode_and_effects_analysis
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2017 Springer International Publishing AG
About this paper
Cite this paper
Provenzano, L., Hänninen, K. (2017). Specifying Software Requirements for Safety-Critical Railway Systems: An Experience Report. In: Grünbacher, P., Perini, A. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2017. Lecture Notes in Computer Science(), vol 10153. Springer, Cham. https://doi.org/10.1007/978-3-319-54045-0_25
Download citation
DOI: https://doi.org/10.1007/978-3-319-54045-0_25
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-54044-3
Online ISBN: 978-3-319-54045-0
eBook Packages: Computer ScienceComputer Science (R0)