1 / 11

Run-Time Blue Print module

Run-Time Blue Print module. MSL. RTBP: a distributable set of configuration data. (from plenary presentation). Application Layer (AL). RTBP. OSL. RTBP is a bit different from other modules. It is static data. The guarantees it provides relate to properties of that data only.

odetta
Download Presentation

Run-Time Blue Print module

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. Run-Time Blue Print module 13/09/06

  2. MSL RTBP: a distributable set of configuration data (from plenary presentation) Application Layer (AL) RTBP OSL 13/09/06

  3. RTBP is a bit different from other modules. • It is static data. The guarantees it provides relate to properties of that data only. • The software modules that interpret the data are responsible for guaranteeing configuration of the system in line with it. • This is, on each stack, the GSM, OSL, MSL and device drivers. 13/09/06

  4. MSL Path of RTBP Data through a single stack. Application Layer (AL) • Some RTBP Data passes through, and some is interpreted; • Blue Print Services • Generic System Manager • Operating System • Module Support Layer Core • Device Driver(s) OSL OS GSM RTBP BP S Core DD 13/09/06

  5. MSL Dependencies between the Stack and RTBP • Each of the modules on each stack is dependant on the RTBP • Blue Print Services • Generic System Manager • Operating System • Module Support Layer Core • Device Driver(s) Application Layer (AL) A1 A2 OSL GSM OS RTBP BP S Core Plus (red lines) the applications that use the system after it has been configurated are dependent on the configuration being correct, so on the RTBP data being correct. DD That would be a lot of contracts!!!! 13/09/06

  6. More Optimal Approach – No contracts. • Rather than declare all these dependencies in the DGRs, we • analyse the DGRs in every module to identify them (and “remove” them from the DGR). • Collect them into guarantees that need to be supported by the RTBP module • Create checklists that will provide evidence that can be argued to support the guarantees. • Discard the guarantees (actually keep for traceability) • Argue instead that the entire checklists are good and that they have been applied. 13/09/06

  7. GSN Goals in RTBP module • The RTBP is correct; i.e. the configuration matches the master system configuration diagram (which was the red lines). • The RTBP is valid; i.e. that it is implementable by the system (which was all the black lines). 13/09/06

  8. End of Presentation 13/09/06

  9. Validity Argument 13/09/06

  10. Correctness Argument 13/09/06

  11. Checklist Sample 13/09/06

More Related