Deliverables: Risks

Risk Matrix

---

Technical Risks

Risk	Description	Mitigation	Impact	Probability
(T1) Web Connection Failure	Application server fails to connect to the Web.	Test the connection and ensure communication is regained.	Very High	Low
(T2) Database/Web Application Failure	Database/Web App failure may occur due to network settings being offline or unavailable.	Verify the database and software communication through testing. Establish dedicated clustered server environments for both database and web application server clusters to reduce possible downtime of ParkODU.	Very High	Low
(T3) Software Bugs	Software development opens up the possibility for bugs that may reduce functionality of the Web application.	Software updates and debugging techniques will be administered routinely. User Interface/User Experience (UI/UX) Testing Regression testing and continuous integration	Very High	Very Low
(T4) Hardware Failure	Hardware including IR sensors, Garage Signage (optional), may not be functioning or require repair.	Mark spot as hardware malfunction and send a service request to maintenance.	High	Medium
(T5) Failure to Notify User of an Event	ParkODU is not updated with event schedules that may affect garage availability.	Ensure ParkODU is updated with upcoming events. Create a ScheduledTask to poll the event calendar through rest endpoints.	Very High	Low
(T6) Lack of Technical Knowledge	Minimal technical experience and/or programming familiarity needed to develop the application.	Individually improve programming knowledge and provide training to less experienced members in area of deficiency.	Medium	Medium
(T7) Incompatible Input Format	Formatting of input is not compatible with ParkODU.	Verify input formatting compatibility through testing.	Medium	Medium
(T8) Inability to Scale Under Load	As volume or customer count increases the database becomes slow or may fail.	Expanding computing resources to handle the exponential growth of work with the use of database scalability. Establish dedicated clustered server environments for both database and web application server clusters.	Very High	Very Low

---

Customer Risks

Risk	Description	Mitigation	Impact	Probability
(C1) University Implements a Better Solution	The university implements a solution other than ParkODU.	Show the customer how ParkODU’s benefits and features are superior to competing solutions. Offer ParkODU as an open-source solution.	Very High	Very Low
(C2) University Does Not Allow Access to Network	ODU ITS does not allow ParkODU to run on the university’s network.	Some departments within the university run things on their own networks. Customer determines hosting location.	Low	Very Low
(C3) Customer Unable to Maintain Servers/Hardware	Customer will be unable to maintain the hardware utilized by ParkODU.	Customer determines the most effective hardware solution with their implementation for ParkODU.	High	Medium
(C4) University Replaces All Garages and Lots with Other Buildings	All parking garages and lots are replaced by buildings.	Parking will still be essential. The software will allow for reconfiguration as the university changes parking allocations.	Very High	Very Low
(C5) Customer Unwilling to Purchase Hardware	Customer may not agree to purchase hardware.	Software will allow for multiple hardware implementations. ParkODU will allow for manual toggling of parking space availability.	Very High	Medium
(C6) Parking Lot Replaced by Parking Garage	The University builds parking more parking garages in place of parking lots.	Ability to add/edit/delete parking objects.	Low	Low
(C7) Customer Purchases Partially Compatible Technology	Customer purchases detection hardware that does not support a certain functionality, such as count by space.	The software can be reconfigured to support specific customer implementation.	Medium	Medium

---

User Risks

Risk	Description	Mitigation	Impact	Probability
(U1) User is Distracted While Using the Application	User is distracted while using ParkODU.	Provide safety notification. Allow for ParkODU to auto-refresh in order to display current data without any additional user interaction.	High	High
(U2) No Internet Device	The end user does not have access to an internet device, such as a Smartphone or a computer, to use the mobile or web application.	User is able to view occupancy signage while on campus. User can use public resources such as a public library computer to access ParkODU. User can utilize ParkODU’s historical prediction feature to print future projections.	Very High	Very Low
(U3) User Cannot Find a Parking Spot	All parking that is being monitored by the application is full.	Inform the user parking is full and application will notify ODU Parking Services. Provide ODU Parking Services contact information.	Very High	Very Low

---