Skip to main content

Achieving Dependable Systems by Synergistic Development of Architectures and Assurance Cases

  • Chapter
Architecting Dependable Systems IV

Part of the book series: Lecture Notes in Computer Science ((LNPSE,volume 4615))

Abstract

Assurance Based Development (ABD) is an approach to the construction of critical computing systems in which the system and an argument that it meets its assurance goals are developed simultaneously. ABD touches all aspects of the system lifecycle, but in this paper we focus on how the evolving assurance argument can guide architectural choices to increase system dependability. The goals with this approach to architectural choice are twofold. The first is to develop the architecture so that it provides the required evidence. The second is to refine the assurance case as architectural choices are made so that the evidence that will be provided supports the assurance claims. Combining development and assurance in this way facilitates detection—and thereby avoidance—of potential assurance difficulties as they arise, rather than after development is complete.

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

Access this chapter

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 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

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. ANSI/IEEE standard, 1471-2000, Recommended Practice for Architectural Description of Software-Intensive Systems -Description

    Google Scholar 

  2. Bishop, P., Bloomfield, R.: A Methodology for Safety Case Development. In: Proc. of the Sixth Safety-critical Systems Symposium, Birmingham (February 1998), http://www.adelard.co.uk/resources/papers/index.htm

  3. de Lemos, R., Gacek, C., Romanovsky, A. (eds.): Architecting Dependable Systems. LNCS, vol. 2677. Springer, Heidelberg (2003)

    MATH  Google Scholar 

  4. de Lemos, R., Gacek, C., Romanovsky, A. (eds.): Architecting Dependable Systems II. LNCS, vol. 3069. Springer, Heidelberg (2004)

    Google Scholar 

  5. de Lemos, R., Gacek, C., Romanovsky, A. (eds.): Architecting Dependable Systems III. LNCS, vol. 3549. Springer, Heidelberg (2005)

    Google Scholar 

  6. EUROCONTROL. The EUR RVSM Pre-Implementation Safety Case, ver. 2.0. Document RVSM 691 (August 14, 2001)

    Google Scholar 

  7. Green, D.F.: Runway Safety Monitor Algorithm for Runway Incursion Detection and Alerting. Technical report NASA CR-2002-211416 (January 2002)

    Google Scholar 

  8. Green, D.F.: Runway Safety Monitor Algorithm for Single and Crossing Runway Incursion Detection and Alerting. Technical report NASA CR-2006-214275 (February 2006)

    Google Scholar 

  9. Kelly, T.P.: A Systematic Approach to Safety Case Management. In: Proc. of SAE 2004 World Congress, Detroit, MI (March 2004)

    Google Scholar 

  10. Kelly, T., McDermid, J.: Safety Case Patterns – Reusing Successful Arguments. In: Proc. of IEE Colloquium on Understanding Patterns and Their Application to System Engineering, London (1998)

    Google Scholar 

  11. Kinnersly, S.: Whole Airspace ATM Safety Case - Preliminary Study (November 2001)

    Google Scholar 

  12. MoD, 00-56 Safety Management Requirements for Defence Systems, U.K. Ministry of Defence, Defence Standard, Issue 3 (December 2004)

    Google Scholar 

  13. Nagra. Project Opalinus Clay: Safety Report. Technical report NTB 02-05. (December 2002)

    Google Scholar 

  14. RTCA. Software Considerations in Airborne Systems and Equipment Certification, document RTCA/DO-178B. Washington, DC: RTCA (December 1992)

    Google Scholar 

  15. Shaw, M., Garlan, D.: Software Architecture: Perspectives On An Emerging Discipline. Prentice-Hall, Englewood Cliffs (1996)

    MATH  Google Scholar 

  16. Strunk, E.A., Knight, J.C.: Dependability Through Assured Reconfiguration in Embedded System Software. IEEE Transactions on Dependable and Secure Computing 3(3), 172–187 (2006)

    Article  Google Scholar 

  17. Weaver, R.A., Kelly, T.P.: The Goal Structuring Notation - A Safety Argument Notation. In: Proc. of Dependable Systems and Networks, Workshop on Assurance Cases (July 2004) http://www-users.cs.york.ac.uk/~tpk/dsn2004.pdf

  18. Wojcik, R., Bachmann, F., Bass, L., Clements, P., Merson, P., Nord, R., Wood, B.: Attribute-Driven Design (ADD), Version 2.0. Technical report CMU/SEI-2006-TR-023 (November 2006)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Rogério de Lemos Cristina Gacek Alexander Romanovsky

Rights and permissions

Reprints and permissions

Copyright information

© 2007 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Graydon, P.J., Knight, J.C., Strunk, E.A. (2007). Achieving Dependable Systems by Synergistic Development of Architectures and Assurance Cases. In: de Lemos, R., Gacek, C., Romanovsky, A. (eds) Architecting Dependable Systems IV. Lecture Notes in Computer Science, vol 4615. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-74035-3_16

Download citation

  • DOI: https://doi.org/10.1007/978-3-540-74035-3_16

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-74033-9

  • Online ISBN: 978-3-540-74035-3

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics