A model management approach for assurance case reuse due to system evolution

ABSTRACT

Evolution in software systems is a necessary activity that occurs due to fixing bugs, adding functionality or improving system quality. Systems often need to be shown to comply with regulatory standards. Along with demonstrating compliance, an artifact, called an assurance case, is often produced to show that the system indeed satisfies the property imposed by the standard (e.g., safety, privacy, security, etc.). Since each of the system, the standard, and the assurance case can be presented as a model, we propose the extension and use of traditional model management operators to aid in the reuse of parts of the assurance case when the system undergoes an evolution. Specifically, we present a model management approach that eventually produces a partial evolved assurance case and guidelines to help the assurance engineer in completing it. We demonstrate how our approach works on an automotive subsystem regulated by the ISO 26262 standard.

References

1. P. A. Bernstein. Applying Model Management to Classical Meta Data Problems. In Proc. of CIDR '03, volume 2003, pages 209-220, 2003.
2. R. Bloomfield and P. Bishop. Safety and Assurance Cases: Past, Present and Possible Future -- an Adelard Perspective. In Proc. of SSS'10, pages 51--67. Springer, 2010.
3. J. Brunel and J. Cazin. Formal Verification of a Safety Argumentation and Application to a Complex UAV System. In Prof. of SAFECOMP Workshops, pages 307--318. Springer, 2012.
4. G. Brunet, M. Chechik, S. Easterbrook, S. Nejati, N. Niu, and M. Sabetzadeh. A Manifesto for Model Merging. In Proc. of GAMMA@ICSE'06, pages 5--12. ACM, 2006.
5. M. Calder, M. Kolberg, E. H. Magill, and S. Reiff-Marganiec. Feature Interaction: a Critical Review and Considered Forecast. Computer Networks, 41(1):115--141, 2003.
6. A. Dardenne, A. Van Lamsweerde, and S. Fickas. Goal-directed requirements acquisition. Science of computer programming, 20(1):3--50, 1993.
7. J. L. de la Vara. Current and Necessary Insights into SACM: An Analysis Based on Past Publications. In Proc. of RELAW14, pages 10--13. IEEE, 2014.
8. A. Di Sandro, R. Salay, M. Famelis, S. Kokaly, and M. Chechik. MMINT: A Graphical Tool for Interactive Model Management. In Proc. of MODELS'15 (demo track), 2015.
9. Z. Diskin, S. Kokaly, and T. Maibaum. Mapping-Aware Megamodeling: Design Patterns and Laws. In Proc. of SLE'13, pages 322--343. Springer, 2013.
10. Z. Diskin, A. Wider, H. Gholizadeh, and K. Czarnecki. Towards a Rational Taxonomy for Increasingly Symmetric Model Synchronization. In Proc. of ICMT'14, pages 57--73. Springer, 2014.
11. Z. Diskin, Y. Xiong, and K. Czarnecki. From state-to delta-based bidirectional model transformations. In Theory and Practice of Model Transformations, pages 61--76. Springer, 2010.
12. U. Fahrenberg, M. Acher, A. Legay, and A. Wąsowski. Sound Merging and Differencing for Class Diagrams. In Proc. of FASE'14, pages 63--78. Springer, 2014.
13. J. L. Fenn, R. D. Hawkins, P. Williams, T. P. Kelly, M. G. Banner, and Y. Oakshott. The Who, Where, How, Why and When of Modular and Incremental Certification. In Proc. of ICSS'07, pages 135--140. IET, 2007.
14. J. L. Fiadeiro. On the Emergence of Properties in Component-Based Systems. In Proc. of AMAST'99, pages 421--443. Springer, 1996.
15. S. Ghanavati, D. Amyot, and L. Peyton. A Systematic Review of Goal-Oriented Requirements Management Frameworks for Business Process Compliance. In Proc. of RELAW'11, pages 25--34. IEEE, 2011.
16. International Organization for Standardization. ISO 2626: Road Vehicles -- Functional Safety, 2011. 1^st version.
17. C. W. Johnson. What Are Emergent Properties and How Do They Affect the Engineering of Complex Systems? J. Reliability Engineering & System Safety, 91(12):1475--1481, 2006.
18. T. Kelly and R. Weaver. The Goal Structuring Notation -- A Safety Argument Notation. In Proc. of DSN'04, 2004.
19. T. P. Kelly and J. A. McDermid. Safety Case Construction and Reuse Using Patterns. In Proc. of SafeComp'97, pages 55--69. Springer, 1997.
20. A. Khalil and J. Dingel. Supporting the Evolution of UML Models in Model Driven Software Development: a Survey. Technical Report 602, School of Computing, Queen's University, Ontario, Canada, 2013.
21. S. Kokaly, R. Salay, M. Sabetzadeh, M. Chechik, and T. Maibaum. Model Management for Regulatory Compliance: a Position Paper. In Proc. of MiSE'16, 2016. (to appear).
22. K. Lano and S. K. Rahimi. Slicing of UML Models. In Proc. of ICSOFT'10 Vol. 2, pages 259--262, 2010.
23. N. G. Leveson. Safety as a system property. Communications of the ACM, 38(11):146, 1995.
24. S. Nejati, M. Sabetzadeh, D. Falessi, L. Briand, and T. Coq. A SysML-based Approach to Traceability Management and Design Slicing in Support of Safety Certification: Framework, Tool Support, and Case Studies. Information and Software Technology, 54(6):569--590, 2012.
25. K. Noda, T. Kobayashi, K. Agusa, and S. Yamamoto. Sequence Diagram Slicing. In Proc. of APSEC'09, pages 291--298. IEEE, 2009.
26. OMG. OMG's MetaObject Facility, 2015. http://www.omg.org/mof/.
27. R. Salay, M. Famelis, J. Rubin, A. Di Sandro, and M. Chechik. Lifting Model Transformations to Product Lines. In Proc. of ICSE'14, pages 117--128. ACM, 2014.
28. R. Salay, S. Kokaly, A. Di Sandro, and M. Chechik. Enriching Megamodel Management with Collection-Based Operators. In Proc. of MODELS'15, pages 236--245. IEEE, 2015.
29. M. Widl, A. Biere, P. Brosch, U. Egly, M. Heule, G. Kappel, M. Seidl, and H. Tompits. Guided Merging of Sequence Diagrams. In Proc. of SLE'12, pages 164--183. Springer, 2012.