The Assurance Recipe: Facilitating Assurance Patterns

  • Justin FirestoneEmail author
  • Myra B. Cohen
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 11094)


As assurance cases have grown in popularity for safety-critical systems, so too has their complexity and thus the need for methods to systematically build them. Assurance cases can grow too large and too abstract for anyone but the original builders to understand, making reuse difficult. Reuse is important because different systems might have identical or similar components, and a good solution for one system should be applicable to similar systems. Prior research has shown engineers can alleviate some of the complexity issues through modularity and identifying common patterns which are more easily understood for reuse across different systems. However, we believe these patterns are too complicated for users who lack expertise in software engineering or assurance cases. This paper suggests the concept of lower-level patterns which we call recipes. We use the safety-critical field of synthetic biology, as an example discipline to demonstrate how a recipe can be built and applied.


Assurance case Assurance pattern Synthetic biology iGEM 



This work was supported in part by the National Institute of Justice grant 2016-R2-CX-0023 and the National Science Foundation Grant CCF-1745775.


  1. 1.
    Cohen, M.B., Firestone, J., Pierobon, M.: The assurance timeline: building assurance cases for synthetic biology. In: Skavhaug, A., Guiochet, J., Schoitsch, E., Bitsch, F. (eds.) SAFECOMP 2016. LNCS, vol. 9923, pp. 75–86. Springer, Cham (2016). Scholar
  2. 2.
    Conmy, P., Bate, I.: Assuring safety for component based software engineering. In: 2014 IEEE 15th International Symposium on High-Assurance Systems Engineering (HASE), pp. 121–128. IEEE (2014)Google Scholar
  3. 3.
    Denney, E.W., Pai, G.J.: Safety case patterns: theory and applications (2015)Google Scholar
  4. 4.
    Hawkins, R., Kelly, T.: A Software Safety Argument Pattern Catalogue. The University of York, York (2013)Google Scholar
  5. 5.
    Jee, E., Lee, I., Sokolsky, O.: Assurance cases in model-driven development of the pacemaker software. In: Margaria, T., Steffen, B. (eds.) ISoLA 2010. LNCS, vol. 6416, pp. 343–356. Springer, Heidelberg (2010). Scholar
  6. 6.
    Kelly, T., Weaver, R.: The goal structuring notation-a safety argument notation. In: Proceedings of the Dependable Systems and Networks 2004 Workshop on Assurance Cases, p. 6. Citeseer (2004)Google Scholar
  7. 7.
    Levskaya, A., Chevalier, A.A., Tabor, J.J., Simpson, Z.B., Lavery, L.A., Levy, M., Davidson, E.A., Scouras, A., Ellington, A.D., Marcotte, E.M., et al.: Synthetic biology: engineering Escherichia coli to see light. Nature 438(7067), 441 (2005)CrossRefGoogle Scholar
  8. 8.
    Mandell, D.J., Lajoie, M.J., Mee, M.T., Takeuchi, R., Kuznetsov, G., Norville, J.E., Gregg, C.J., Stoddard, B.L., Church, G.M.: Biocontainment of genetically modified organisms by synthetic protein design. Nature 518(7537), 55–60 (2015)CrossRefGoogle Scholar
  9. 9.
    Ruiz, A., Habli, I., Espinoza, H.: Towards a case-based reasoning approach for safety assurance reuse. In: Ortmeier, F., Daniel, P. (eds.) SAFECOMP 2012. LNCS, vol. 7613, pp. 22–35. Springer, Heidelberg (2012). Scholar
  10. 10.
    Szczygielska, M., Jarzębowicz, A.: Assurance case patterns on-line catalogue. In: Zamojski, W., Mazurkiewicz, J., Sugier, J., Walkowiak, T., Kacprzyk, J. (eds.) DepCoS-RELCOMEX 2017. AISC, vol. 582, pp. 407–417. Springer, Cham (2018). Scholar
  11. 11.
  12. 12.
  13. 13.
  14. 14.
  15. 15.
  16. 16.
  17. 17.

Copyright information

© Springer Nature Switzerland AG 2018

Authors and Affiliations

  1. 1.Department of Computer Science and EngineeringUniversity of Nebraska - LincolnLincolnUSA

Personalised recommendations