Changes between Version 21 and Version 22 of BluePrint/CAPBroker/UseCases
- Timestamp:
- 01/21/16 17:19:21 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/CAPBroker/UseCases
v21 v22 18 18 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.The process flow is intuitive from the use-case diagram as well. 19 19 20 === Process Flow === 21 20 22 ||'''Process''' || '''Description''' || 21 23 ||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 Implementer would '''assign event type''', '''assign warning priority''', and '''assign location''' to a ACK. We may not require that low priority messages for certain event types in some location are acknowledged and are simply informative alerts. || … … 25 27 [[br]][[br]] 26 28 29 === Use Case Diagram === 30 27 31 [[Image(http://eden.sahanafoundation.org/raw-attachment/wiki/BluePrint/CAPBroker/UseCases/use_case_request_ack.png)]] 32 28 33 == Report SOP Status == 29 34 Often first-responders must follow a Standard Operating Procedure (SOP). The use case diagram describes the process for creating SOP check-lists and requesting that each first-responder update the status of the SOP. 30 35 31 === = Process Flow ====36 === Process Flow === 32 37 ||'''Process''' || '''Description''' || 33 38 ||create SOP check-lists ||The implementers will generate a set of SOP check-lists that are event and first-responder specific. SOPs for the police with evacuation procedures for a given event are different from the SOPs medical technicians would follow with tracking emergency patients. || … … 38 43 39 44 40 === = Use-case Diagram ====45 === Use-case Diagram === 41 46 [[Image(http://eden.sahanafoundation.org/raw-attachment/wiki/BluePrint/CAPBroker/UseCases/use_case_report_SOP_status.2.png)]] 42 47 43 === = Attributes ====48 === Attributes === 44 49 NOTE - this is simply a list of attributes and is not a database table. Developers must convert this to a normalized database with related tables. 45 50 [[Image(http://eden.sahanafoundation.org/raw-attachment/wiki/BluePrint/CAPBroker/UseCases/SOP_Check_List_ERD.png)]]
