Prover Diagrams: Difference between revisions

From Event-B
Jump to navigationJump to search
imported>Andy
No edit summary
imported>Mathieu
mNo edit summary
 
(3 intermediate revisions by one other user not shown)
Line 3: Line 3:
These diagrams describe the relationships between classes/interfaces - in terms of access to information in related classes. The diagrams are not fully descriptive like a UML class diagram, but contain sufficient information to begin to understand the structural relationships within the RODIN proof tool. The diagrams were produced as an aid to visualising these relationships in order to better understand the structure.
These diagrams describe the relationships between classes/interfaces - in terms of access to information in related classes. The diagrams are not fully descriptive like a UML class diagram, but contain sufficient information to begin to understand the structural relationships within the RODIN proof tool. The diagrams were produced as an aid to visualising these relationships in order to better understand the structure.


<center>
<gallery>
<gallery>
Image:ProofStatus.png|Proof Status Diagram
Image:ProofStatus.png|Proof Status Diagram
Image:ProofTree.png|Proof Tree Diagram
Image:ProofTree2.png|Proof Tree Diagram
Image:UserSupportDiag.png|UserSupport Diagram
Image:UserSupportDiag.png|UserSupport Diagram
Image:TacticRegistry.png | Tactic UI Registry Diagram
</gallery>
</gallery>
</center>
[[Category:Design]]

Latest revision as of 12:02, 12 August 2009

Entity Relationship Diagrams for the Prover Code

These diagrams describe the relationships between classes/interfaces - in terms of access to information in related classes. The diagrams are not fully descriptive like a UML class diagram, but contain sufficient information to begin to understand the structural relationships within the RODIN proof tool. The diagrams were produced as an aid to visualising these relationships in order to better understand the structure.