Advertisement

Integration of the 4+1 Software Safety Assurance Principles with Scrum

  • Osama DossEmail author
  • Tim Kelly
  • Tor Stålhane
  • Børge Haugset
  • Mark Dixon
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 748)

Abstract

Some researchers have attempted to tailor agile methods to comply with specific standards (e.g. SafeScrum and IEC61508). However, this risks over-configuring the agile method in such a way as to make it difficult to apply it to another safety standard. Our approach sought to look at the problems of addressing the more fundamental principles of safety assurance by adopting the 4+1 safety principles and investigating how a Scrum process challenges, and can be adapted to give strong indication that the practitioners felt that there is a significant potential for successful integration of the 4+1 principles within Scrum. There were some issues where practitioners were concerned to focus only on one safety standard, and neither the agile practitioners nor the safety practitioners had a clear understanding of the outlook and work of the other group. However, we used these issues to inform a further set of questions. We conducted semi-structured interviews with participants to explore the general feasibility of the approach, and to provide an assessment as to whether the 4+1 principles can be addressed without compromising agility.

Keywords

Safety-critical systems Agile methods Assurance case Scrum 

References

  1. 1.
    Bowers, J., May, J., Melander, E., Baarman, M., Ayoob, A.: Tailoring XP for large system mission critical software development. In: Wells, D., Williams, L. (eds.) XP/Agile Universe 2002. LNCS, vol. 2418, pp. 100–111. Springer, Heidelberg (2002). doi: 10.1007/3-540-45672-4_10 CrossRefGoogle Scholar
  2. 2.
    Bedoll, R.: A tail of two projects: how ‘Agile’ methods succeeded after ‘Traditional’ methods had failed in a critical system-development project. In: Maurer, F., Wells, D. (eds.) XP/Agile Universe 2003. LNCS, vol. 2753, pp. 25–34. Springer, Heidelberg (2003). doi: 10.1007/978-3-540-45122-8_4 CrossRefGoogle Scholar
  3. 3.
    Bruce, D.: Agile analysis practices for safety-critical, 19 February 2013 http://www.ibm.com/developerworks/rational/library/agile-analysis-practicessafety-critical-development/
  4. 4.
    Kelly, T.: Software certification: where is confidence won and lost? In: Anderson, T., Dale, C. (eds.) Addressing Systems Safety Challenges, Safety Critical Systems Club (2014)Google Scholar
  5. 5.
    Doss, O., Kelly, T.P.: Challenges and opportunities in agile development in safety critical systems: a survey. SIGSOFT Software Eng. Notes 41(2), 30–31 (2016)CrossRefGoogle Scholar
  6. 6.
    Fitzgerald, B., Stol, K.J., Sullivan, R.O., Brien, D.O.: Scaling agile methods to regulated environments: an industry case study. In: 2013 35th International Conference on Software Engineering (ICSE), San Francisco, CA, pp. 863–872 (2013)Google Scholar
  7. 7.
    Jonsson, H., Larsson, S., Punnekkat, S.: Agile practices in regulated railway software development. In: 2012 IEEE 23rd International Symposium on Software Reliability Engineering Workshops (ISSREW), Dallas, TX, pp. 355–360 (2012)Google Scholar
  8. 8.
    Ge, X., Paige, R.F., McDermid, J.A.: An iterative approach for development of safety-critical software and safety arguments. In: Agile Conference, Florida, pp. 35–43 (2010)Google Scholar
  9. 9.
    Stålhane, T., Myklebust, T., Hanssen, G.: The application of Scrum IEC-61508 certifiable software (2011, Unpublished)Google Scholar
  10. 10.
    Beznosov, K., Kruchten, P.: Towards agile security assurance. In: Proceedings of the 2004 Workshop on New Security Paradigms (NSPW 2004), pp. 47–54. ACM, New York (2004)Google Scholar
  11. 11.
    Othmane, L.B., Angin, P., Bhargava, B.: Using assurance cases to develop iteratively security features using Scrum. In: 2014 Ninth International Conference on Availability, Reliability and Security (ARES), Fribourg, pp. 490–497 (2014)Google Scholar
  12. 12.
    Flink, A.: The Survey Handbook, 2nd edn. Sage Publications, Thousand Oaks (2003)CrossRefGoogle Scholar
  13. 13.
    Shull, F., Singer, J., Sjøberg, D.I.K.: Guide to Advanced Empirical Software Engineering, 1st edn. Springer, London (2010)Google Scholar
  14. 14.
    Doss, O., Kelly, T.: The 4+1 principles of software safety assurance and their implications for Scrum. In: Sharp, H., Hall, T. (eds.) XP 2016. LNBIP, vol. 251, pp. 286–290. Springer, Cham (2016). doi: 10.1007/978-3-319-33515-5_27 Google Scholar
  15. 15.
    Azham, Z., Ghani, I., Ithnin, N.: Security backlog in Scrum security practices’. In: 5th Malaysian Conference in Software Engineering (MySEC), Johor Bahru, pp. 414–417 (2011)Google Scholar
  16. 16.
    Doss, O., Kelly, T.: Addressing the 4+1 software safety assurance principles within Scrum. In: Proceedings of the Scientific Workshop Proceedings of XP2016 (XP 2016 Workshops). ACM, New York (2016)Google Scholar

Copyright information

© Springer International Publishing AG 2017

Authors and Affiliations

  • Osama Doss
    • 1
    Email author
  • Tim Kelly
    • 2
  • Tor Stålhane
    • 3
  • Børge Haugset
    • 4
  • Mark Dixon
    • 1
  1. 1.School of Computing, Creative TechnologiesLeeds Beckett UniversityLeedsUK
  2. 2.Department of Computer ScienceUniversity of YorkYorkUK
  3. 3.Norwegian University of Science and TechnologyTrondheimNorway
  4. 4.SINTEF ICTTrondheimNorway

Personalised recommendations