GUI: add button to obstruct door + add figures and such to assignment HTML

This commit is contained in:
Joeri Exelmans 2024-11-29 11:14:13 +01:00
parent fffd65370f
commit 8ffb3e097f
15 changed files with 497 additions and 8 deletions

View file

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:notation="http://www.eclipse.org/gmf/runtime/1.0.2/notation" xmlns:sgraph="http://www.yakindu.org/sct/sgraph/2.0.0">
<sgraph:Statechart xmi:id="_KuVP4GBDEe2R-oGCKnTAVw" specification="// DO NOT CHANGE&#xA;@EventDriven&#xA;@SuperSteps(no)&#xA;@ParentFirstExecution&#xA;&#xA;// DO NOT CHANGE THE SEMANTICS&#xA;@EventDriven&#xA;@SuperSteps(no)&#xA;@ParentFirstExecution&#xA;&#xA;&#xA;interface:&#xA;&#x9;// DOT CHANGE THE INTERFACE&#xA;&#xA;&#x9;// You can use these values in your Statechart&#xA;&#x9;// and in your tests:&#xA;&#x9;const LOW: integer = 0&#xA;&#x9;const HIGH: integer = 1 &#xA;&#x9;const LOW_LVL: integer = 500&#xA;&#x9;const HIGH_LVL: integer = 1500&#xA;&#xA;&#x9;in event requestLvlChange&#xA;&#x9;in event waterLvl: integer&#xA;&#x9;in event resume&#xA;&#x9;&#xA;&#x9;in event doorObstructed: integer&#xA;&#xA;&#x9;out event setRequestPending: boolean&#xA;&#x9;out event setSensorBroken&#xA;&#x9;out event openFlow: integer&#xA;&#x9;out event closeFlow: integer&#xA;&#x9;out event openDoors: integer&#xA;&#x9;out event closeDoors: integer&#xA;&#x9;out event greenLight: integer&#xA;&#x9;out event redLight: integer&#xA;&#x9;&#xA;internal:&#xA;&#x9;// You are allowed (and probably should)&#xA;&#x9;// declare internal events and internal variables&#xA;&#x9;// in this section..." name="LockController">
<sgraph:Statechart xmi:id="_KuVP4GBDEe2R-oGCKnTAVw" specification="// DO NOT CHANGE&#xA;@EventDriven&#xA;@SuperSteps(no)&#xA;@ParentFirstExecution&#xA;&#xA;// DO NOT CHANGE THE SEMANTICS&#xA;@EventDriven&#xA;@SuperSteps(no)&#xA;@ParentFirstExecution&#xA;&#xA;&#xA;interface:&#xA;&#x9;// DOT CHANGE THE INTERFACE&#xA;&#xA;&#x9;// You can use these values in your Statechart&#xA;&#x9;// and in your tests:&#xA;&#x9;const LOW: integer = 0&#xA;&#x9;const HIGH: integer = 1 &#xA;&#x9;const LOW_LVL: integer = 500&#xA;&#x9;const HIGH_LVL: integer = 1500&#xA;&#xA;&#x9;in event requestLvlChange&#xA;&#x9;in event waterLvl: integer&#xA;&#x9;in event resume&#xA;&#x9;&#xA;&#x9;in event doorObstructed&#xA;&#xA;&#x9;out event setRequestPending: boolean&#xA;&#x9;out event setSensorBroken&#xA;&#x9;out event openFlow: integer&#xA;&#x9;out event closeFlow: integer&#xA;&#x9;out event openDoors: integer&#xA;&#x9;out event closeDoors: integer&#xA;&#x9;out event greenLight: integer&#xA;&#x9;out event redLight: integer&#xA;&#x9;&#xA;internal:&#xA;&#x9;// You are allowed (and probably should)&#xA;&#x9;// declare internal events and internal variables&#xA;&#x9;// in this section..." name="LockController">
<regions xmi:id="_Kuavc2BDEe2R-oGCKnTAVw" name="main region">
<vertices xsi:type="sgraph:State" xmi:id="_BZTF4GTzEe22Ao6AjWtBXA" name="O" incomingTransitions="_dzToYGTzEe22Ao6AjWtBXA">
<regions xmi:id="_BZTs8mTzEe22Ao6AjWtBXA" name="r1">