Team 52

Coffee Cart Rewards Management System for Android

Risk List
Version <1.2>

Coffee Cart Rewards Management System for Android

Version:
1.2
Date: 06/Jul/14

Risk List
RiskAssessment.pdf

Revision History
Date

Version

Description

Author

25/Jun/14

1.0

Inception Phase

Laura Pike

29/June/14

1.1

Revised after review with team

Laura Pike

06/July/14

1.2

Revised for Elaboration Phase

Laura Pike

Confidential

Team 52, 2014

Page 2 of 5

Coffee Cart Rewards Management System for Android

Risk List
RiskAssessment.pdf

Version:
1.2
Date: 06/Jul/14

Table of Contents
1.

2.

Introduction

1.1
1.2
1.3
1.4
1.5

4
4
4
4
4

Purpose
Scope
Definitions, Acronyms, and Abbreviations
References
Overview

Risks
2.1

Confidential

Risk Planning Table

Error! Bookmark not defined.

Team 52, 2014

Page 3 of 5

Coffee Cart Rewards Management System for Android

Version:
1.2
Date: 06/Jul/14

Risk List
RiskAssessment.pdf

Risk List
1.

Introduction

1.1

Purpose
This document addresses the risks identified during the development of the BeanTracker system. A
description of each risk can be found in the Risks section of the document.

1.2

Scope
The risks addressed in the document are for the first iteration of the BeanTracker, a coffee cart rewards
system.

1.3

Definitions, Acronyms, and Abbreviations

1.4

References
Vision Document, 6300Sum14Pro ject2\Deliverable1\vision.pdf
Project Plan, 6300Sum14Project2\ Deliverable1\ProjectPlan.pdf
M icrosoft Word Templates for RUP

http://sce.uhcl.edu/helm/RationalUnifiedProcess/wordtmpl/index.htm#sdp
1.5

Overview
The Risks section, noted below, describes the identified risks of the system, their rank, impact risk
exposure, type/indicator, mitigation strategy,and contingency for each risk. The risk rank is an indicator of
the magnitude of the risk to the project; the smaller the number the lower the risk. Impact number is a
weight indicating impact on the project; the smaller the number the lower the risk. The exposure is
calculated by multiplying the rank with the impact. The type or indicator describes how the risk occurred or
is about to occur. The mitigation strategy describes what will be don e on the project to reduce the impact of
the risk. Finally, contingency describes what the course of action will be if the risk occurs , such as an
alternate solution or a reduction in functionality.

2.

Risks

2.1

Risk Planning Table

Requirements

Rank

RISK 1: New database 5

to hold customer
information, menu
items, purchase
history, and preorders to be created
RISK 2: Customer can 4
have only 1 VIP card

RISK 3: Customer
awarded 1 VIP point
per dollar spent
Confidential

Impact Risk
Exposure
5
25

16

12

Team 52, 2014

Type/Indicator Mitigation
Strategy
Technology
Address
during
Elaboration
Phase

Trigered by a
purchase
request

Contingency

Address
during
Elaboration
Phase
Addressed
during
Elaboration
Page 4 of 5

Coffee Cart Rewards Management System for Android

Version:
1.2
Date: 06/Jul/14

Risk List
RiskAssessment.pdf

RISK 4: Customer is
upgraded to GOLD
level if 500 points are
earned in 30 days.

12

Trigered by a
purchase
request

RISK 5: Customer is
permanently
upgraded to GOLD
level if 5000 points
are earned.
RISK 6: Daily preorder slots can not
exceed 5 or 3 if the
item is a bestseller.

Trigered by a
purchase
request

Trigered by a
purchase
request

Risk 7: The software

system will run on
Android devices.

Risk 8: Implementing
a shared database
with web interface

RISK 9: Update SDK to 5

2.3

25

Technology

RISK 10: Ability to

communicate (or not
communicate with
team members)
RISK 11: PC Hardware

25

Technology /
Logistics

25

Technology

Confidential

Team 52, 2014

phase test
cases
Addressed
during
Elaboration
phase test
cases
Addressed
during
Elaboration
phase test
cases
Addressed
during
Elaboration
phase test
cases
Addressed
during the
Inception
phase
Vision
document
Will be
implemented in
a future release
of BeanTracker
(codename
BeanTracker+)
Addressed
during the
Elaboration
phase
Addressed
during the
Elaboration
phase

Backup email,
Piazza, GitHub

GitHub
repository,
backups

Page 5 of 5