Safety Standards demand that industrial applications demonstrate they have the required safety integrity and this starts with the initial requirements phase. This paper shows how the Problem Oriented Software Engineering (POSE) framework, in conjunction with the Alloy formal method, supports this task through its ability to elaborate, transform and analyse the project requirements and thus develop a solution for an avionics case study. In particular, this work reports on how the POSE/Alloy combination was used in conjunction with the POSE safety pattern to improve the requirements analysis capabilities of an existing, successful safety critical development process.
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
Preview
Unable to display preview. Download preview PDF.
References
Barnes, J. (1996). High Integrity Ada; The SPARK Approach, Addison-Wesley.
Bate, I. and P. Conmy (2005). Safe composition of real time software. HASE'05, Heidelberg, Germany.
Courtois, P.-J. and D. L. Parnas (1997). Documentation for Safety Critical Software. 15th International Conference on Software Engineering, Baltimore, USA.
da Cruz, M. F. and P. Raistrick (2007). AMBERS: Improving Requirements Specification Through Assertive Models and SCADE/DOORS Integration. Safety Critical Systems Symposium, Bristol, UK.
de Lemos, R., A. Saeed and T. Anderson (1998). On the Integration of Requirements Analysis and Safety Analysis for Safety-Critical Systems, University of Newcastle upon Tyne, UK.
Ellis, A. (1995). Achieving Safety in Complex Control Systems. Safety Critical Systems Symposium, Brighton, United Kingdom, Springer-Verlag.
Gerstinger, A., G. Schedl and W. Winkelbauer (2002). Safety versus Reliability: Different or Equal. 20th International System Safety Conference, Denver, Colorado, USA, System Safety Society.
Hall, J. G., D. Mannering and L. Rapanotti (2007a). Arguing safety with Problem Oriented Software Engineering. 10th IEEE Int. Sym. on High Assurance Systems Engineering (HASE 2007), Dallas, Texas.
Hall, J. G., L. Rapanotti and M. Jackson (2007b). Problem Oriented Software Engineering: A design-theoretic framework for software engineering. 5th IEEE Int. Conference on Software Engineering and Formal Methods (SEFM 2007), London, UK.
Heitmeyer, C. and R. Jeffords (2007). Applying a formal requirements method to three NASA systems: Lessons learned. IEEE Aerospace Conference, Big Sky, MT.
Jackson, D. (2006). Software Abstractions Logic, Language, and Analysis, The MIT Press.
Jackson, M. A. (2001). Problem frames : analysing and structuring software development problems. Harlow, Addison-Wesley.
Kleene, S. (1964). Introduction to Metamathematics, Van Nostrand, Princeton.
Leveson, N. (1995). Safeware : system safety and computers. Reading, Mass. ; Wokingham, Addison-Wesley.
Leveson, N. G. (2000a). "Completeness in formal specification language design for process-control systems." Proceedings of the third workshop on Formal methods in software practice 2000, Portland, Oregon. ACM Press: 2000.
Leveson, N. G. (2000b). "Intent Specifications: An Approach to Building HumanCentered Specifications." IEEE Transactions on Software Engineering Vol. 26 ( No. 1): pp. 15-35.
Lutz, R. R. (1993). Analysing Software Requirements Errors in Safety-Critical Embedded Systems. IEEE International Symposium Requirements Engineering, San Diego, California.
Mannering, D., J. G. Hall and L. Rapanotti (2007a). Relating Safety Requirements and System Design through Problem Oriented Software Engineering. SAFECOMP 07, Nuremburg, Germany.
Mannering, D., J. G. Hall and L. Rapanotti (2007b). Safety Process Improvement: Early Analysis and Justification. IET Safety 07, London, England.
Mannering, D., J. G. Hall and L. Rapanotti (2007c). Towards Normal Design for Safety Critical Systems. FASE 07, Braga, Portugal.
Martino, P. A. and C. Muniak (2002). The Role of System Safety Engineering in Product Safety. 20th International System Safety Conference, Denver, Colorado, USA, System Safety Society.
Redmill, F. (1999). "An introduction to the safety standard IEC61508." System Safety Society 35(1).
RTCA/DO-178B Software Considerations in Airborne Systems and Equipment Certification.
SAE (1996). ARP4761: Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment.
Schneider, S. (2001). The B-method: An Introduction, Palgrave.
Spivey, J. M. (1992). The Z-Notation - A Reference Manual, Prentice Hall.
UK-MoD (2004). Safety Management Requirements for Defence Systems Part 1 Requirements, MoD: 44.
van Lamsweerde, A. (2000). Requirements Engineering in the Year 00: A Research Perspective. ICSE'00, 22nd International Conference on Software Engineering, Limerick.
Vesely, W., F. Goldberg, N. Roberts and D. Haasl (1981). Fault Tree Handbook, U.S. Nuclear Regulatory Commission.
Vincenti, W. G. (1990). What Engineers Know and How They Know It: Analytical Studies from Aeronautical History, The Johns Hopkins University Press.
Zave, P. and M. Jackson (1997). "Four Dark Corners of Requirements Engineering." ACM Transactions on Software Engineering and Methodology VI((1)): 1-30.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2008 Springer-Verlag London Limited
About this paper
Cite this paper
Mannering, D., Hall, J.G., Rapanotti, L. (2008). Safety Process Improvement with POSE and Alloy. In: Redmill, F., Anderson, T. (eds) Improvements in System Safety. Springer, London. https://doi.org/10.1007/978-1-84800-100-8_3
Download citation
DOI: https://doi.org/10.1007/978-1-84800-100-8_3
Publisher Name: Springer, London
Print ISBN: 978-1-84800-099-5
Online ISBN: 978-1-84800-100-8
eBook Packages: Computer ScienceComputer Science (R0)