1 / 19

Dependability

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.

jude
Download Presentation

Dependability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


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

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

  3. Other terms

  4. Threats and Means

  5. Development Phase and Faults • the physical world with its natural phenomena, • human developers, some possibly lacking competence or having malicious objectives, • development tools: software and hardware used by the developers to assist them in the development process. • production and test facilities. Fault * prevention ? * tolerance ? * removal ? * prediction ?

  6. Use Phase and Faults • the physical world with its natural phenomena, • 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; • users: entities that receive service from the system at their use interfaces; • providers: entities that deliver services to the system at its use interfaces; • 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. • 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 ?

  7. Elementary Fault Classes

  8. Combined classification

  9. Failure Modes

  10. Means Fault prevention removal prediction or forecasting tolerance

  11. Fault prevention • Systematic procedures • Clean room (Harlan Mills) • Inspection • Reviews

  12. Fault prevention • process (activities) • notations • tools • Careful Design • Conservative Design • robust functionality • testability • tracability

  13. Fault Removal In Development In Use Preventive maintenance Corrective maintenance Fault isolation • Verification and validation • Diagnosis • Correction

  14. Verification Techniques

  15. Test approaches

  16. Fault forecasting • Qualitative evaluation • Quantitative evaluation Models: Markov-processes, Fault-trees, ...

  17. Fault Forecasting • Calculation – analysis of design • Simulation – measurement on design • Test -- measurement on implementation

  18. Means

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

More Related