Keegan Reap
Jeffrey Hertzing
Ken Nakano
Rotan Bosson
Josh Murphy
Michael Bond
Branch (Brandt) Jones
Kylie Kniep
Alan Vo
Chris Kaufman
Kevin Lin
Sami Bouaazzi
Tej Gidvani
Thomas Hagos

Table of Contents:
1.
Introduction
1.1 Project Overview
1.2 Project Deliverables
1.3 Evolution of this document
1.4 References
1.5 Definitions and meanings
2.
Project Organization
2.1 Process Model
2.2 Organizational Structure
2.3 Organizational Boundaries and Interfaces
2.4 Project Responsibilities
3.
Managerial Process
3.1 Management Objectives and Priorities
3.2 Assumptions Dependencies and Constraints
3.3 Risk Management
3.4 Monitoring and Controller Mechanisms
4.
Technical Process
4.1 Methods, Tools and Techniques
4.2 Software Documentation
4.3
Project Support Function
5. Work Packages, Schedule, and Budget
5.1 Work Packages
5.2 Schedule
6
6
6
6
5
6
6
6
5
5
5
3
3
3
3
3
4
4
4
4
5
5
5

1. Introduction
1.1 Project Overview
This Final project plan is to be used for the Android application Remember MEds. The application is a medicine reminder and tracker meant for people with limited memory. This application allows for inputting prescriptions and medicine schedule into the system for reminder notices. The system has functionality for also keeping track of medicines that aren’t strictly on a schedule. Not only does the system remind users when they need to take their medicine, but also when their prescription is running low.
The application has two modes, a caretaker mode and a user mode. The caretaker mode is meant to setup a schedule and input medicines for a user who is unable to do so themself. The user mode is meant for the prescribed patient. This mode is designed to be easy to use and allows the user to keep track of their medicine by reminding them when to take it.
This document is about the plan of action that will be taken to undergo the task of constructing
Remind Meds. This document organizes sections for clear understanding of the parts of the project. The deliverables section includes necessary items for turning in. This document also covers the different definitions encountered in the statements as well as the organizational structure of the team.
1.2 Project Deliverables
1.2.1 – Final project plan
1.2.2 – Phase 1 Interim
1.2.3 – Final project 1
1.2.4 – Phase 2 Interim
1.2.5 – Final Project 2
1.3 Evolution of this document
September 5
October 1
October 17
November 12
December 3/5
9/01/2013 First draft of this document
9/04/2013 Finished first draft for deliverable
9/17/2013 Added more details to Project Responsibilities
9/18/2013 Added Process Model
9/30/2013 Fixed list of team members
10/15/2013 Detailed section 3.1
10/15/2013 Detailed section 3.2
10/15/2013 Detailed section 2.1
10/15/2013 Detailed section 5.2
11/11/2013 Added more to Risks section 3.3
1.4 References

Stephen R. Schach, Object-Oriented Software Engineering 1 st ed. McGraw Hill. 2007.


Unknown Author, (2002), Software Requirements Specifications [online]. Available FTP: upedu.org File: pdf
 http://technet.microsoft.com/en-us/library/cc288751.aspx#section2
1.5 Definitions and meanings
Caretaker – A person responsible for assisting an individual who may be unable to take care of themselves.
Emergency Call – A call sent to the Caretaker in case of emergency
2 Project organization
This project is organized based off of team roles. There are four major teams. Web
Development Team, Brainstorm Team, Documentation Team and Application development team. These teams are not strictly binding, as all members can work on any section of the project.
2.1 Process Model
This group is developing and producing the system using an agile method. Our model benefits by the use of iterations during development, allowing us to achieve a deliverable during each iteration. Iterations may include different meetings at the beginning and throughout as well as a full group meeting at the end to organize deliverables.
2.2 Organizational Structure
The team members are organized as:
Web Development Team:
Tej Gidvani
Ken Nakano
Kylie Kniep
Josh Murphy
Documentation Team:
Jeffrey Hertzing
Chris Kaufman
Keegan Reap
Alan Vo
Michael Bond
Temesxgn Gebrehiwet
Brainstorming Team:
Branch (Brandt) Jones
Kevin Lin
Rotan Bosson
Sami Bouaazzi
Phase Two - Coding Team:
Tej Gidvani
Branch (Brandt) Jones
Josh Murphy
Chris Kaufman

2.3 Organizational Boundaries and Interfaces
All team members will meet at project meetings to discuss progress and priorities. Group members will organize smaller meeting specific to their roles. Online sharing of documents via
Google Drive will store materials.
2.4 Project Responsibilities
Web Development Team
– Responsible for website creation and organization of project presentation.
Brainstorm Team
– Responsible for generating ideas and concepts for the core of the project.
Documentation Team
– Responsible for documenting the project, including requirements and user manual.
Application Development Team
– Responsible for coding and creating the Android application
3 Managerial Processes
3.1 Management Objectives and Priorities
Team Hedgehog is dedicated to delivering Remember MEds on time and having the highest quality software possible. Leadership will be a driving factor in keeping the project on track to achieve excellence and quality for our system.
3.2 Assumptions Dependencies and Constraints
We assume our user has access to a mobile device featuring the Android Operating system as well as a mobile plan to allow calling their caretakers. We assume that there are members of our team that are knowledgeable with undertaking Android development.
3.3 Risk Management
During meetings, the team leader will assess if there are any risks or major issues for the project.
Possible Risks
3.3.1 – Testing hardware fails.
Response: We will have backup systems as well as our virtual machines for testing.
3.3.2 – Team may become unorganized and communication will be hindered.
Response: The team will have meetings to keep communication fluid.
3.3.3 – The meeting location to where the team gathers may be closed or inaccessible.
Response: The group shall have a secondary meeting location.
3.3.4 – Our app may be too similar to an already existing patent
Response: If necessary, change features to be unique to our system
3.4 Monitoring and Controller Mechanisms

Team members will upload their documents and progress onto Google Drive. This is necessary for each team member to view the evolution of the system creation.
4 Technical Processes
4.1 Methods, Tools and Techniques
1.
Google Drive – Cloud storage of documents.
2.
HTML/CSS – Method of creating website.
3.
Adobe Photoshop – Tool for creating images such as the logo.
4.
Microsoft PowerPoint – Tool for creating presentations.
4.2 Software Documentation
Documentation includes a user manual that will be updated as features are added. This will provide the user with a proper guide on how to use the system and to answer foreseeable questions.
4.3 Project Support Function
Project Support will consist of quality assurance, software testing, and management of updates.
Quality assurance will ensure that each feature is correctly implemented and tested. Updates will also be implemented if bugs are found or new features are added.
5 Work Packages, Schedule, and Budget
5.1 Work Packages
1. Final project plan
2. Phase 1 Interim
3. Final project 1
4. Phase 2 Interim
5. Final Project 2
5.2 Schedule
5.2.1 –project plan
5.2.2 – Phase 1 Interim
5.2.3 – Final project 1
5.2.4 – Phase 2 Interim
5.2.5 – Final Project 2
September 5
October 1
October 17
November 12
December 3/5