Download presentation
Presentation is loading. Please wait.
Published byThomasine Hicks Modified over 8 years ago
1
An EMERGENCY PREPAREDNESS Application For George Mason University Faculty
2
TABLE OF CONTENTS INTRODUCTIONS CONCEPT PRODUCT DETAILS DESIGNING INFORMAL MODELS MODELS AND STORYBOARD PROTOTYPE TESTING PROTOTYPE SCOPE
3
Who is Group D?
4
CONCEPT Overview Our assignment Research Devices Client
5
Overview “Are You Prepared?” application Informational portal Provide user-friendly training Crisis situation preparation for faculty Emergency button that alerts security/911 immediately and pinpoints the location of the user via the device’s GPS locator system
6
Our Assignment Problem: Faculty ill-prepared in the face of an emergency Lack of mandatory training Degree of technological skills Solution Design a readily available application Offers multiple aspects of training Supplies on the spot notification alert authorities
7
RESEARCH Average duration of an Active Shooter incident in Institutions of Higher Education (IHE) is 5-8 minutes The average response time of campus and local law enforcement on a large campus is 13-18 minutes 22% of faculty surveyed felt they had an adequate knowledge base of emergency procedures National movement towards creating a ‘Disaster Resilient University’ (DRU) atmosphere
8
Devices Smart Phones (iPhones, Androids, etc.) Tablets (iPads, etc)
9
Client George Mason University Faculty George Mason University Community
10
PRODUCT DETAILS Personas Data Collection Methods Flow Diagrams WAAD
11
Individual Personas Dr. Steven Matthews: New hire full-time faculty No prior emergency training Would use this app during an emergency Willing to devote personal time for training Low self-efficacy for handling a classroom emergency Has a mobile device
12
Data Collection Methods Interviews with GMU faculty Interviews with emergency staff at GMU and Fairfax County Surveys administered to faculty Current faculty emergency handbook
13
Flow Design Two parts Training section: Faculty can use app for protocol Simulation section to test their knowledge Currently faculty can use booklet Emergency section: Panic button to call/text 911 Immediate access to protocols Current resource Mason alerts & booklets
14
WAAD WAAD created for SME included: Resources for faculty Protocols GMU could require to ensure faculty understands correct procedures WAAD created for faculty included: What They Know What They Should Know Emotion Potential Usefulness Suggestions
15
DESIGNING INFORMAL MODELS Models Work Roles Work Role Characteristics
16
Design Informing Models Models to extract interaction design requirements: User Models Social Models Usage Models Task Structure Models Task Interaction Models Work Environment Models Hierarchical Task Inventory 3 different models: Usage Scenario Model Step-by-step Interaction Model The Essential Use Case Task Interaction Model Artifact Model
17
Work Roles GMU Faculty Police (including Campus Police), Fire, & EMS Web Administrators
18
Work Role Characteristics 1226 W Grand Parkway S 214 Katy, Texas 77494
19
PROTOTYPE SCOPE Hierarchical Task Inventory Barrier Summary Design Process Ideation & Sketching
20
Hierarchical Task inventory Relationships of actions in fulfillment of aspects of two main user tasks: 1. Knowledge Preparedness through simulated practice 2. Emergency Assistance by a notification system
21
Barriers Summary # TriggerGoalBarrier 1. A non-mandatory training session is open. To know the procedure and protocol of dealing with emergency situations Current training is optional and not a mandatory requirement 2. Faculty is offered with the opportunity to train themselves To view and use the simulative practice in the app Faculty may lack incentives and motivation 3. Faculty is trying to use the app but can’t have access to the content To have access to the content at any location Limited Wi-Fi or cellular signal on campus 4. Faculty member uses the app to find the most relevant, updated protocols for an emergency event. To prepare faculty with the latest protocols, training methods, and tools in a mobile app in the case of an emergency app Attrition of web administrators may hinder its functionality and relevancy over the app’s lifespan Ten barriers were identified affecting our targeted user group
22
Design Process
23
Ideation & Sketching Ideation process consisted of two stages 1.Idea extraction from contextual research 2.Group discussion, discourse “chewing on design ideas”
24
MODELS AND STORYBOARD Mental Models Storyboard
25
Mental Models Designer’s Mental Model Engaging training simulations anchored in realistic scenarios App should feel like a portal and a tool Simple and convenient Not intended to replace, but to supplement User’s Mental Model Useful Accessible Prepared and empowered
26
Storyboards The following storyboard was inspired by interviews with faculty and SMEs It depicts the current gap in faculty training
28
PROTOTYPE TESTING Process Results Lessons Learned and Resulting Changes
29
Testing Process Collected reactions and suggestions from potential users and instructional designers Focused on gathering feedback on navigation, usefulness, and ease
30
Results Clean things up Learning curve Navigational difficulties Confusion
31
Lessons Learned & Resulting Changes Added app tutorial Removed vague buttons across bottom of screen Added screen to better organize tutorial, training, and emergency functionality Clearer language and icons to indicate what every function does
32
PROTOTYPE Training Emergency
33
Are You Prepared?
34
Protocol
41
Training
42
Simulations
46
PROTOTYPE Training Emergency
50
Protocol
51
Emergency
53
Map
54
Map Locator
56
Team Roles
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.