Critical Systems Specification

Slides:



Advertisements
Similar presentations
Critical Systems Specification
Advertisements

Critical Systems Specification
Chapter 12 – Dependability and Security Specification
Chapter 12 – Dependability and Security Specification
SWE Introduction to Software Engineering
Critical Systems Specification
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 9 Slide 1 Critical Systems Specification.
“ Hard work and concern for the society is the key to success ” - O P Jindal On-site and Off-site Emergency Plans Based on Integral Risk Management – Key.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 30 Slide 1 Security Engineering.
Soft. Eng. II, Spr. 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 9 Title : Reliability Reading: I. Sommerville, Chap. 16, 17 and 18.
SWE Introduction to Software Engineering
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 9 Slide 1 Critical Systems Specification.
©Ian Sommerville 2004Software Engineering, 7th edition. Insulin Pump Slide 1 An automated insulin pump.
©Ian Sommerville 2004Software Engineering, 7th edition. Insulin Pump Slide 1 The portable insulin pump Developing a dependability specification for the.
©Ian Sommerville 2006Critical Systems Slide 1 Critical Systems Engineering l Processes and techniques for developing critical systems.
CIS 376 Bruce R. Maxim UM-Dearborn
Software Dependability CIS 376 Bruce R. Maxim UM-Dearborn.
Software Project Management
Software Reliability Categorising and specifying the reliability of software systems.
1 Copyright © 2003 M. E. Kabay. All rights reserved. Critical Systems Specification IS301 – Software Engineering Lecture #18 – M. E. Kabay,
Slide 6.1 CHAPTER 6 TESTING. Slide 6.2 Overview l Quality issues l Nonexecution-based testing l Execution-based testing l What should be tested? l Testing.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Slide 1 Critical Systems Specification 2.
Chapter 12 – Dependability and Security Specification
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 3 Slide 1 Critical Systems 1.
 CS 5380 Software Engineering Chapter 11 Dependability and Security.
Building Dependable Distributed Systems Chapter 1 Wenbing Zhao Department of Electrical and Computer Engineering Cleveland State University
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 9 Slide 1 Critical Systems Specification 1.
Slide 1 Security Engineering. Slide 2 Objectives l To introduce issues that must be considered in the specification and design of secure software l To.
©Ian Sommerville 2000Dependability Slide 1 Chapter 16 Dependability.
Safety Assessment: Safety Integrity Levels
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
Advanced Query Analysis
Chapter 11 – Reliability Engineering
Software Quality I.
Rapid Software Development
IS301 – Software Engineering V:
Distributed Systems Architectures
Software Metrics and Reliability
Software Quality Assurance
IS301 – Software Engineering V:
Design for Security Pepper.
Hardware & Software Reliability
Software Project Management
IS301 – Software Engineering V:
IS301 – Software Engineering Dept of Computer Information Systems
IS301 – Software Engineering V:
IS301 – Software Engineering V:
Fault Tolerance & Reliability CDA 5140 Spring 2006
Software Reliability Definition: The probability of failure-free operation of the software for a specified period of time in a specified environment.
Software Reliability PPT BY:Dr. R. Mall 7/5/2018.
Safety and Risk.
Security Engineering.
IS301 – Software Engineering V:
Software Requirements
Software Reliability: 2 Alternate Definitions
HSE Case: Risk Based Approach.
IS301 – Software Engineering V:
Critical Systems Validation
Critical Systems Specification
IS301 – Software Engineering V:
COP 5611 Operating Systems Spring 2010
Critical Systems Development
Introduction to the Course
Requirements Engineering Processes
Chapter 8 Software Evolution.
Overview Dependability: "[..] the trustworthiness of a computing system which allows reliance to be justifiably placed on the service it delivers [..]"
BHOPAL Industrial Disaster Management Cycle: OECD 2004.
Definitions Cumulative time to failure (T): Mean life:
Presentation transcript:

Critical Systems Specification IS301 – Software Engineering Lecture # 9 – 2004-09-20 M. E. Kabay, PhD, CISSP Assoc. Prof. Information Assurance Division of Business & Management, Norwich University mailto:mkabay@norwich.edu V: 802.479.7937 M. E. Kabay, PhD, CISSP Copyright © 2004 M. E. Kabay. All rights reserved.

Today we will use 18 of Prof. Sommerville’s slides in class Topics covered Risk-driven specification Safety specification Security specification Software reliability specification Today we will use 18 of Prof. Sommerville’s slides in class

Dependability requirements Functional requirements to define error checking and recovery facilities and protection against system failures. Non-functional requirements defining the required reliability and availability of the system. Excluding requirements that define states and conditions that must not arise.

Risk-driven specification

Levels of risk Unacceptable region Risk cannot be tolerated Risk tolerated only if risk reduction is impractical or grossly expensive Acceptable region ALARP region Neglible risk

Risk assessment - insulin pump

Fault-tree analysis A deductive top-down technique. Put the risk or hazard at the root of the tree and identify the system states that could lead to that hazard. Where appropriate, link these with ‘and’ or ‘or’ conditions. A goal should be to minimize the number of single causes of system failure.

Insulin pump fault tree

Control system safety requirements

Copyright © 2004 M. E. Kabay. All rights reserved. The safety life-cycle Copyright © 2004 M. E. Kabay. All rights reserved.

The security specification process

Types of security requirement Identification requirements. Authentication requirements. Authorization requirements. Immunity requirements. Integrity requirements. Intrusion detection requirements. Non-repudiation requirements. Privacy requirements. Security auditing requirements. System maintenance security requirements.

Copyright © 2004 M. E. Kabay. All rights reserved. Reliability metrics Reliability metrics are units of measurement of system reliability. System reliability is measured by counting the number of operational failures and, where appropriate, relating these to the demands made on the system and the time that the system has been operational. A long-term measurement program is required to assess the reliability of critical systems. Copyright © 2004 M. E. Kabay. All rights reserved.

Reliability metrics

Probability of failure on demand This is the probability that the system will fail when a service request is made. Useful when demands for service are intermittent and relatively infrequent. Appropriate for protection systems where services are demanded occasionally and where there are serious consequence if the service is not delivered. Relevant for many safety-critical systems with exception management components Emergency shutdown system in a chemical plant.

Rate of fault occurrence (ROCOF) Reflects the rate of occurrence of failure in the system. ROCOF of 0.002 means 2 failures are likely in each 1000 operational time units e.g. 2 failures per 1000 hours of operation. Relevant for operating systems, transaction processing systems where the system has to process a large number of similar requests that are relatively frequent Credit card processing system, airline booking system.

Mean time to failure Measure of the time between observed failures of the system. Is the reciprocal of ROCOF for stable systems. MTTF of 500 means that the mean time between failures is 500 time units. Relevant for systems with long transactions i.e. where system processing takes a long time. MTTF should be longer than transaction length Computer-aided design systems where a designer will work on a design for several hours, word processor systems.

Availability Measure of the fraction of the time that the system is available for use. Takes repair and restart time into account Availability of 0.998 means software is available for 998 out of 1000 time units. Relevant for non-stop, continuously running systems telephone switching systems, railway signaling systems.

Homework Required By Mon 27 Sep 2004 Write an essay of 100-200 words discussing question 9.1 for 15 points Answer questions 9.2, 9.3 & 9.6 for 10 points each For 20 points, answer question 9.9 in detail. Note the phrase “Giving reasons…” Optional By Monday 4 Oct 2004 Q. 9.8 for 12 points with reasons Q. 9.10 and/or 9.12 @ 2 points each

QUIZ #1 IN CLASS WED 22 SEP 2004 Chapters 1 - 5 REMINDER QUIZ #1 IN CLASS WED 22 SEP 2004 Chapters 1 - 5

Copyright © 2004 M. E. Kabay. All rights reserved. DISCUSSION Copyright © 2004 M. E. Kabay. All rights reserved.