Changes between Version 22 and Version 23 of BluePrint/CAPBroker/GUIDesign

Timestamp:

08/29/15 02:31:10 (10 years ago)

Author:

Nuwan Waidyanatha

Comment:

fixed the diagram size, was too big

BluePrint/CAPBroker/GUIDesign

@@ -28 +28 @@
 This is essentially a state machine, whereby an alert message can transition from msgType to another. Here are the possible sequences:
 
+==== Transition combinations ====
+
 ||=No: =||=       Transition   ||=         Remarks      =||
 ||1)  || Alert ---> [[BR]]Update ...[[BR]] Update --->[[BR]] Cancel || '''Cancel''' means the event was disregarded and it was a false alarm [[BR]] example - ''heavy rains cause a rain gauge to automatically trigger flash-flood alert, then the alert is incidentally updated by mistake, until finally the authorities realize it was a malfunction and issue a cancelled'' ||
@@ -42 +44 @@
 example, ''we may issue SMS alerts to [n] people and expect them to Ack. If and Ack is not received then we may recast the message to those who did not receive the message. Don't worry about this part, it's a project of it's own.''
 
-[[Image(http://eden.sahanafoundation.org/raw-attachment/wiki/BluePrint/CAPBroker/GUIDesign/FlowChartSambroGui.png)]][[BR]]
+==== State transition diagram ====
+
+[[Image(http://eden.sahanafoundation.org/raw-attachment/wiki/BluePrint/CAPBroker/GUIDesign/FlowChartSambroGui.2.png)]][[BR]]
 
 'Cancel' and 'All clear' acts like a sink. They are where every msgType would ultimately go.