1 / 23

Process

Process. ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August 2011. System Analysis and Definition. Determining the Hazards and risks. Determining the SIL and the PFx.

onella
Download Presentation

Process

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. Process ITV Model-based Analysis and Design of Embedded Software Techniques and methods for Critical Software Anders P. Ravn Aalborg University August 2011

  2. System Analysis and Definition

  3. Determining the Hazards and risks

  4. Determining the SIL and the PFx

  5. Safety Requirements Allocation

  6. Planning and Specification

  7. Realisation, validation & integration

  8. Software – at last

  9. Completing the cycle

  10. Requirements and Realisation Our JOB

  11. Software development cycle

  12. Requirements

  13. Design and Development

  14. Detailed Design

  15. Unit testing

  16. Integration testing (model based?)

  17. A note on safety functions ”Distinguish consistently between: the end-to-end safety function that is supported by one or more elements and (2) the element safety function of each of the supporting elements.” IEC 61508-3 7.4.2.11 NOTE

  18. Techniques and Measures

  19. Mechanisms in design

  20. More Mechanisms

  21. Testing

  22. Exercise – is it theV-model? 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 A rational Design Process – or how to fake it Heninger & Parnas, 1979

  23. Exercise – OOAD in Context • Requirements Specification • 1.1 System Definition • 1.2 Problem Domain Structure • 1.3 Application Domain Structure • Architecture • Modules • Implementation • 5. Test

More Related