Managing architectural design decisions for safety-critical software systems

Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)

Volumn 4214 LNCS, Issue , 2006, Pages 59-77

  Wu, Weihang ^a   Kelly, Tim ^a  

^a UNIVERSITY OF YORK   (United Kingdom)

Author keywords

[No Author keywords available]

Indexed keywords

ACTION MODELS; SAFETY CONCERNS; SAFETY CRITICAL SYSTEMS; SAFETY QUALITIES; SAFETY-CRITICAL SOFTWARE SYSTEMS;

ARCHITECTURAL DESIGN; COMPUTER SOFTWARE SELECTION AND EVALUATION;

SOFTWARE ARCHITECTURE;

EID: 77049087325     PISSN: 03029743     EISSN: 16113349     Source Type: Book Series    
DOI: 10.1007/11921998_9     Document Type: Conference Paper

References (19)

1. ARP 4761: Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment. Society of Automotive Engineers, Inc (1996)
2. IEC 61508 - Functional Safety of Electrical/Electronic/Programmable Electronic Safety-Related Systems. International Electrotechnical Commission (1998).
3. The United Modelling Language Specification 1.5. Object Management Group, http://www.uml.org
4. Alexander, I.: Misuse Cases: Use Cases with Hostile Intent. IEEE Software, 20 (1) (2003) 58-66
5. Bachmann, F., Bass, L. and Klein, M.: Deriving Architectural Tactics: A Step toward Methodical Architectural Design. Tech. Report. CMU/SEI-2003-TR-004. SEI (2003)
6. Bass, L., Clements, P. and Kazman, R.: Software Architecture in Practice. 2nd Edition. Addison Wesley, Reading, USA (2003)
7. Buhr, R.J.A. and Casselman, R.S.: Use Case Maps for Object-Oriented Systems. Prentice Hall (1996)
8. Burns, A. and Lister, A.: A Framework for Building Dependable Systems. The Computer Journal, 34 (2). (1991) 173-181
9. Douglass, B.P.: Doing Hard Time: Developing Real-Time Systems with UML, Objects, Frameworks, and Patterns. Addison-Wesley (1999)
10. Feather, M.S., and Cornford, S.L.: Quantitative Risk-Based Requirements Reasoning. Requirements Engineering, 8 (4) (2003) 248-265
11. Kruchten, P.: The 4+1 View Model of Architecture. IEEE Software, 12 (6) (1995) 42-50
12. Leveson, N.G.: Safeware: System Safety and Computers. Addison-Wesley (1995)
13. Lions, J.L.: ARIANE 5: Flight 501 Failure. Inquiry Board report. Paris (1996)
14. Nuseibeh, B.: Weaving Together Requirements and Architectures. IEEE Computer, 34 (3) (2001) 115-114
15. Ramesh, B. and Dhar, V.: Supporting systems development by capturing deliberations during requirements engineering. IEEE Trans. on Software Engineering, 18 (6) (1992) 498-510
16. Rozanski, N. and Woods, Eoin: Software Systems Architecture. Addison-Wesley (2005)
17. Sosa, E. and Tooley, M. (eds.): Causation. Oxford University Press, New York (1993)
18. Wu, W. and Kelly, T.: Safety Tactics for Software Architecture Design. Proceedings of the 28th Annual International Computer Software and Applications Conference (COMPSAC'04). IEEE Computer Society (2004) 368-375
19. Wu, W. and Kelly, T.: Failure Modelling in Software Architecture Design for Safety. ACM SIGSOFT Software Engineering Notes, 30 (4) (2005) 1-7