Version 3 (modified by 9 years ago) ( diff ) | ,
---|
CAP Broker Use Cases
Table of Contents
This page accommodates all the micro-evel use caases associated with the warning functions facilitated through http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO SAMBRO].
Acknowledge Message
The use case diagram describes how at the time of implementation, the Admin (Implementer) generated subscriber group, termed as first-responders, are assigned to acknowledge (ACK) to a message and the process of recording those acknowledgements.
Process | Description |
Assign a ACK to group | First we must get subscriber groups and select the desired group. These groups are created by the Implementer. Second the ACK can be associated with an event type, warning priority, and a location. We may not require that low priority messages for certain event types in some location are acknowledged and are simply informative alerts. |
Report SOP Status
Attachments (4)
-
use_case_request_ack.png
(55.8 KB
) - added by 9 years ago.
Acknowledgement request use case
-
use_case_report_SOP_status.png
(70.0 KB
) - added by 9 years ago.
SOP Checklist use-case
-
use_case_report_SOP_status.2.png
(70.2 KB
) - added by 9 years ago.
SOP Checklist use-case
-
SOP_Check_List_ERD.png
(7.4 KB
) - added by 9 years ago.
SOP Checklist entity relationship diagram
Download all attachments as: .zip
Note:
See TracWiki
for help on using the wiki.