1 / 18

Compositional Design and Verification of Componen t- Based Information Systems

C. Compositional Design and Verification of Componen t- Based Information Systems. Jan Martijn van der Werf. Organizations cooperate. Bob. Charley. “Who-knows-who” not transitive!. Alice. Dave. Organizations deliver services. Bob. Charley. Alice. Dave.

Download Presentation

Compositional Design and Verification of Componen t- Based Information Systems

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. C. Compositional Design and Verification of Component-Based Information Systems Jan Martijn van der Werf

  2. Organizations cooperate Bob Charley “Who-knows-who” not transitive! Alice Dave

  3. Organizations deliver services Bob Charley Alice Dave

  4. Component-based information system Process Data Process Process Process Data Data Data Process Data Process Data

  5. Verification vs. design • Verification: • Go and do what you want, check when finished • Correctness by design: • Follow my rules, and it is correct vs.

  6. Compositional verification of soundness • Components form a service tree • Components only know their direct neighbors C A B D E = soundness of component F = condition on communicating pair of components

  7. Compositional verification of soundness

  8. Compositional verification of soundness Soundness not sufficient for pairwise verification!

  9. Compositional design: refinement rules! • Stepwise refinement • Each step preserves soundness • Refinement rules: • Within component • Outsourcing • Over components

  10. Process + Data = Prototype + +

  11. Compositional design and verification of Component-based information systems • Framework for component-based information systems • Compositional verification of interaction • Compositional design of interaction • Petri nets extended with data • Message passing • Data transactions • Process + data  prototype • Re-engineering by process mining

  12. C Compositional Design and Verification of Component-Based Information Systems Jan Martijn van der Werf

  13. Components and their composition • Soundness: always possible to finish properly(disregarding interfaces) H a a b b c c d d I G G e e

  14. Correctness by design • Refinement within a component

  15. Correctness by design • Refinement over components

  16. Correctness by design • Outsource refinement

  17. Sufficient conditions for

  18. Sufficient conditions for soundness • Identical communication: • B+C behaves like B on interface with A • Alternating communication block: • B+C has same communication blocks as B • Elastic communication: • B+C may send earlier and receive later than B B B+C B B+C B B+C

More Related