Changes between Version 11 and Version 12 of BluePrint/CAPBroker/UseCases

Timestamp:

01/21/16 07:43:27 (9 years ago)

Author:

Nuwan Waidyanatha

Comment:

--

BluePrint/CAPBroker/UseCases

@@ -29 +29 @@
 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.
 
+==== Process Flow ====
 ||'''Process''' || '''Description''' ||
 ||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. ||
@@ -35 +36 @@
 ||update SOP check-list ||The first-responder would click on the link, login, and complete the check-list (questionnaire) and save it. They may update the SOP at various stages of the SOP. For example, the police might update the SOP indicating they have begun evacuating people. Once the evacuation is complete, they would count the number of people and update the SOP check-list with the people count. ||
 ||record SOP status ||The process will '''get SOP check-list ID''', '''get subscriber''' (or Person ID) and '''get CAP identifier''' (i.e. message id) to update the status of the check-list with the information provided by the first-responder ||
-[[br]][[br]]
 
+
+==== Use-case Diagram ====
 [[Image(http://eden.sahanafoundation.org/raw-attachment/wiki/BluePrint/CAPBroker/UseCases/use_case_report_SOP_status.png)]]
+
+==== Attributes ====
+||'''Attribute''' ||'''Data Type''' ||'''Description''' ||
+|| || || ||
+
+
 == Report SOP Status ==