Nothing Special   »   [go: up one dir, main page]

Skip to main content

Situational Factors in Safety Critical Software Development

  • Conference paper
  • First Online:
Systems, Software and Services Process Improvement (EuroSPI 2016)

Abstract

The generic software development situational factors model has been developed in order that environments within which software is developed can be profiled and better understood. Situational context is a complex concern for software developers, with a broad set of situational factors holding the potential to affect any one software development project. Safety critical software development is broadly similar to other kinds of software development/ engineering. But there are some additional or more dominant situational factors. In this article we conduct a conceptual experiment to define safety critical software development context using situational factors. Eleven such factors are identified, with some of the factors requiring elaboration beyond the detail presently available in the generic situational factors model. We firstly discuss the appropriateness of the selected factors in generic safety critical software development context. Thereafter we apply the selected factors to the medical device and nuclear power domains. Selected situational factors can be used as a high level profile and starting point for more detailed process and safety assessment. Discussion about potential use cases and further development needs is also presented.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Similar content being viewed by others

Notes

  1. 1.

    Such “generic safety critical software” may not exist, because most industry sectors use their own standards. Note also that terminology may vary in standards, for example “safety-related software” or “software important for safety”.

References

  1. Clarke, P., O’Connor, R.V., Leavy, B.: A Complexity theory viewpoint on the software development process and situational context. In: Proceedings of the 2016 International Conference on Software and System Process (ICSSP 2016). IEEE, San Francisco (2016)

    Google Scholar 

  2. Clarke, P., O’Connor, R.V.: The situational factors that affect the software development process: towards a comprehensive reference framework. J. Inf. Softw. Technol. 54(5), 433–447 (2012)

    Article  Google Scholar 

  3. Knight, J.C.: Safety critical systems: challenges and directions. In: Proceedings of the 24th International Conference on Software Engineering, pp. 547–550. IEEE (2002)

    Google Scholar 

  4. Manson, S.M.: Simplifying complexity: a review of complexity theory. Geoforum 32(3), 405–414 (2001)

    Article  Google Scholar 

  5. Clarke, P., O’Connor, R., Leavy, B., Yilmaz, M.: Exploring the relationship between software process adaptive capability and organisational performance. IEEE Trans. Softw. Eng. 41(12), 1169–1183 (2015)

    Article  Google Scholar 

  6. Clarke, P., Lepmets, M., McCaffery, F., Finnegan, A., Dorling, A., Eagles, S.: Characteristics of a medical device software development framework. In: Industrial Proceedings of EuroSPI 2014 conference, pp. 1–9 (2014)

    Google Scholar 

  7. IEC: IEC 62304 medical device software - software life-cycle processes. IEC, Geneva, Switzerland (2006)

    Google Scholar 

  8. Clarke, P., Lepmets, M., Dorling, A., McCaffery, F.: Safety critical software process assessment: how MDevSPICE® addresses the challenge of integrating compliance and capability. In: Rout, T., O’Connor, R.V., Dorling, A. (eds.) SPICE 2015. CCIS, vol. 526, pp. 13–18. Springer, Heidelberg (2015)

    Chapter  Google Scholar 

  9. Varkoi, T., Nevalainen, R.: FiSMA report 2014-2. Advanced nuclear SPICE assessment process. Version 1.0, 2015-01-08. SAFIR2014. FiSMA, Espoo Finland (2015)

    Google Scholar 

  10. IEC: IEC 61508, functional safety of electrical/electronic/programmable electronic safety related systems. Parts 1 – 7. IEC, Geneva, Switzerland (2010)

    Google Scholar 

  11. ISO: ISO 14971 - medical devices - application of risk management to medical devices. ISO, Geneva, Switzerland (2009)

    Google Scholar 

  12. IEC: IEC 60601-1 - medical electrical equipment – part 1: general requirements for basic safety and essential performance. IEC, Geneva, Switzerland (2005)

    Google Scholar 

  13. BEL-V, BfS, CNSC: Common positio006E. Licensing of safety critical software for nuclear reactors. Common position of seven European nuclear regulators and authorised technical support organisations. Regulator Task Force on Safety Critical Software (TF SCS) (2013)

    Google Scholar 

  14. IEC: IEC 60880, nuclear power plants – instrumentation and control systems important to safety – software aspects for computer-based systems performing category A functions. IEC, Geneva, Switzerland (2006)

    Google Scholar 

  15. IEC: IEC 62138, nuclear power plants – I&C systems important to safety – software aspects for computer based systems performing category B and C functions. IEC, Geneva, Switzerland (2004)

    Google Scholar 

  16. IEC: IEC 61513, nuclear power plants – instrumentation and control for systems important to safety – general requirements for systems. IEC, Geneva, Switzerland (2001)

    Google Scholar 

  17. IEC: IEC 61226, nuclear power plants – instrumentation and control systems important for safety – classification of instrumentation and control functions. IEC, Geneva, Switzerland (2009)

    Google Scholar 

  18. Clarke, P., Elger, P., O’Connor, R.V.: Technology enabled continuous software development. In: Proceedings of the International Conference on Software Engineering (ICSE) Workshop on Continuous Software Evolution and Delivery (CSED). ACM / IEEE, New York (2016)

    Google Scholar 

Download references

Acknowledgments

This research is supported in part by the Science Foundation Ireland Research Centres Programme, through Lero - the Irish Software Research Centre (http://www.lero.ie) grant 10/CE/I1855 & 13/RC/20194; and in part by the Finnish national nuclear safety program SAFIR2018 (http://safir2018.vtt.fi/).

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Risto Nevalainen .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2016 Springer International Publishing Switzerland

About this paper

Cite this paper

Nevalainen, R., Clarke, P., McCaffery, F., O’Connor, R.V., Varkoi, T. (2016). Situational Factors in Safety Critical Software Development. In: Kreiner, C., O'Connor, R., Poth, A., Messnarz, R. (eds) Systems, Software and Services Process Improvement. EuroSPI 2016. Communications in Computer and Information Science, vol 633. Springer, Cham. https://doi.org/10.1007/978-3-319-44817-6_11

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-44817-6_11

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-44816-9

  • Online ISBN: 978-3-319-44817-6

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics