Top Banner
Dependability ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August 2011
19

Dependability

Feb 23, 2016

Download

Documents

Orji Friday Oko

Dependability . ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August 2011. Basic Concepts. Availability : readiness for correct service. Reliability : continuity of correct service. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Dependability

Dependability

ITV Model-based Analysis and Design of Embedded SoftwareTechniques and methods for Critical Software

Anders P. RavnAalborg University

August 2011

Page 2: Dependability

Basic Concepts

• Availability: readiness for correct service.• Reliability: continuity of correct service.• Safety: absence of catastrophic consequences.• Confidentiality: absence of unauthorized disclosure of

information• Integrity: absence of improper system alterations.• Maintainability: ability to undergo modifications.

Page 3: Dependability

Other terms

Page 4: Dependability

Threats and Means

Page 5: Dependability

Development Phase and Faults

1. the physical world with its natural phenomena,

2. human developers, some possibly lacking competence or having malicious objectives,

3. development tools: software and hardware used by the developers to assist them in the development process.

4. production and test facilities.Fault * prevention ? * tolerance ? * removal ? * prediction ?

Page 6: Dependability

Use Phase and Faults1. the physical world with its natural phenomena,2. administrators (including maintainers): entities (humans or other systems) that

have the authority to manage, modify, repair and use the system; some authorized humans may lack competence or have malicious objectives;

3. users: entities that receive service from the system at their use interfaces; 4. providers: entities that deliver services to the system at its use interfaces;5. infrastructure: entities that provide specialized services to the system, such as

information sources (e.g., time, GPS, etc.), communication links, power sources, cooling airflow, etc.

6. intruders: malicious entities that attempt to exceed any authority they might have and alter service or halt it, alter the system’s functionality or performance, or to access confidential information. Examples include hackers, vandals, corrupt insiders, agents of hostile governments or organizations, and malicious software.

Fault * prevention ? * tolerance ? * removal ? * prediction ?

Page 7: Dependability

Elem

entary

Fault

Classes

Page 8: Dependability

Combined classification

Page 9: Dependability

Failure Modes

Page 10: Dependability

Means

Faultpreventionremoval

prediction or forecasting tolerance

Page 11: Dependability

Fault prevention

• Systematic procedures• Clean room (Harlan Mills)• Inspection• Reviews

Page 12: Dependability

Fault prevention

• Careful Design

• Conservative Design

• process (activities)• notations

• tools

• robust functionality• testability• tracability

Page 13: Dependability

Fault Removal

In Development1. Verification and validation2. Diagnosis3. Correction

In Use• Preventive maintenance• Corrective maintenance• Fault isolation

Page 14: Dependability

Verification Techniques

Page 15: Dependability

Test approaches

Page 16: Dependability

Fault forecasting

• Qualitative evaluation• Quantitative evaluation

Models: Markov-processes, Fault-trees, ...

Page 17: Dependability

Fault Forecasting

• Calculation – analysis of design

• Simulation – measurement on design

• Test -- measurement on implementation

Page 18: Dependability

Means

Page 19: Dependability

Exercise• Where would you add prevention, removal and forecasting

in a V-model process?• What would you add?

Requirements Spec --------------------------- Accpt. Test Report Acceptance Test Spec

Architectural Spec ------------------------ Integr. Test Report Integration Test Spec

Module Interface Spec Module Spec ------------------- Module Test Report

Module Test Spec

Program Source text