1 / 26

4 th SDL and MSC Workshop SAM’04 Ottawa 1st-4th June 2004

4 th SDL and MSC Workshop SAM’04 Ottawa 1st-4th June 2004. Alkiviadis Yiannakoulias NTUA ayian@telecom.ece.ntua.gr. Presentation Layout. Design issues Top level system design Use of tool chain (SAFIRE) Implementation Testing / Validation Documentation Demonstration Summary.

alair
Download Presentation

4 th SDL and MSC Workshop SAM’04 Ottawa 1st-4th June 2004

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. 4th SDL and MSC Workshop SAM’04 Ottawa1st-4th June 2004 Alkiviadis Yiannakoulias NTUA ayian@telecom.ece.ntua.gr

  2. Presentation Layout • Design issues • Top level system design • Use of tool chain (SAFIRE) • Implementation • Testing / Validation • Documentation • Demonstration • Summary

  3. Design issues

  4. Design issues (Contd.) • The door is allowed to be open for a maximum period, once the correct code is entered (Max_Open_Duration_Tmr). • An alarm is generated when the door is not closed within the allowed time. • Time to open or close the door has a maximum value (Transition_Tmr). • Solenoid aborts releasing of lock procedure if door is not moving within the allowed time (Guard_Tmr).

  5. Design issues (Contd.) • Time is always displayed in the console. • ACS Commands: • Stay Open: Allow door to be open for longer. Information needed: • Time (HH:MM), • Access Code • Close Now: 15 seconds to close door • Supervisor mode

  6. Supervisor Mode Commands • Double-check safety procedure, • Change supervisor code, • Statistics for: • #Times door open outside, • #Times door open inside, • When was last opened and how long • Set time, • Exit.

  7. Design issues (Contd.) • Use of query mechanism to get door state, for controller state transitions • Reduce number of states • Data Hiding • Reset procedure initializes configuration parameters and ACK completion • Improve testability

  8. Top-Level Design DOOR_BT

  9. Top-Level Design

  10. Solenoid Process

  11. ACS Process

  12. ACS Process (Contd.)

  13. Door Process

  14. Design summary • Clear organization • Hierarchical structure • Data hiding • Use of types • Reuse of design information • Simple language elements

  15. Documentation of Test Harness

  16. Test harness (UI)

  17. Test harness (SIM)

  18. Documentation of Test Suite / Test Purposes

  19. Test Case Sample (Door_Opening_TC)

  20. Test Case Sample (Contd.)

  21. Test Report

  22. Test Report

  23. System Execution Trace

  24. Summary of results • All test scenarios executed (PASS) • Test coverage • All main transitions: timeouts and normal behavior • Each transition has been tested independently • Assumes no interaction between transitions (reasonable as no global variables)

  25. Conclusions • Maximum usage of tool chain has minimized the effort for: • Design, Testing, Documentation • Interesting challenge on how to keep design simple and use all the tool features to maximize automation

More Related