| | 3 | We provide a methodology and a set of evaluation instruments to be used in evaluating the implementation. |
| | 4 | |
| | 5 | == Introduction == |
| | 6 | Sahana Alerting and Messaging Broker (SAMBRO) is designed foster Cross-Agency Situational-Awareness in support of improving Institutional Responsiveness to All-Hazards: http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO . SAMBRO offers an all-hazard all-media approach whereby consistent, concise, and controlled alerts and warnings are disseminated through multiple channels. |
| | 7 | |
| | 8 | To evaluate the performance of SAMBRO and the underlying Common Alerting Protocol (CAP) content standard and procedures, we are introducing an objective and subjective evaluation method. The evaluation is specific to early warning and alerting. Alerting Authorities (Publishers) and warning recipients like the public and first-responders (Subscribers) can interconnect through the SAMBRO for improving their institutional responsiveness. |
| | 9 | |
| | 10 | == Methodology == |
| | 11 | |
| | 12 | We have broken the SAMBRO Early Warning System (EMS) dissemination subsystem activities into two components; namely Publishers and Subscribers. Publishers are essentially authorized alerting organizations who would originate or relay a warning/alert message. Both Publishers and Subscribers will undergo a series of tests to determine their aptitude to: |
| | 13 | publish effective CAP-enabled messages |
| | 14 | Subscribe to actionable (or inactionable) CAP-enabled alert/warning messages |
| | 15 | operationalize a cross-agency situational-awareness platform |
| | 16 | |
| | 17 | We are applying two Human Computer Interaction (HCI) evaluation methodologies: |
| | 18 | Technology Acceptance Model (TAM) |
| | 19 | Goal Oriented HCI |
| | 20 | Technology Acceptance Model (TAM) |
| | 21 | TAM provides insights on the ease of use and usability of the technology presented to the users. This applies to both Publishers and Subscribers. This is a subjective analysis of the intervention. |
| | 22 | Goal Oriented HCI |
| | 23 | There are two elements to the Goal Oriented HCI: |
| | 24 | Objectively analyze the functional transition |
| | 25 | Subjectively analyze the functional transition |
| | 26 | |
| | 27 | Screen Capture |
| | 28 | We will install a screen capture software. The screen capture software will capture the behaviour of the user and the sequence of executing each process. This will provide the evaluators with insights of the ease of use and usability of the system. It may relate to the level or training and expectation of the user’s aptitude. |
| | 29 | Focus Group Discussion |
