Preliminary Project Plan

Helping Our People Easily (HOPE)

Team Ramrod Team Leader: Leader: Mike Schwartz (mjs077000) Team Members: Members: Randy Baniqued (rkb012000) Brian Doyle (bpd090020) Bjorn Holm-Pedersen (bbh081000) Andrew Welleck (amw068000)

Phase 1 Preliminary Project Plan CS/SE 4351 Section 001, Fall 2011 http://mikeschwartz.net

1. Introduction 1.1 Project overview This is a project plan to be used for the implementation of the HOPE (Helping Our People Easily) Android mobile application. This application will be designed to make communication with persons with various disabilities easier without being a burden to use. This application will contain features which make it easier to communicate with people who have trouble hearing, trouble talking and trouble remembering things. It will be designed so that the effects of each disability can be lessened so that the disabled person may experience a more-normal lifestyle. There will be three main components to the system; each component will target a specific disability. The first component will assist people who have trouble remembering people or places. This is to be accomplished by associating these hard to remember people or places with pictures because it is believed that that is how many people remember things. The second component will assist those who have difficulty talking or speaking with proper pronunciation of words. This feature could be accomplished by having the user type in what he or she means to communicate instead of trying to sound it out. Finally this program will have a third feature which will assist those people who are hard of hearing. It could be similar to the feature for those who have trouble speaking properly but it will be used by the person talking instead of the disabled person. 1.2 Project deliverables The following are the deliverables for this project: a) Preliminary Project Plan ----------------------b) Interim Project I ----------------------c) Project I Submission ----------------------d) Interim Project II ---------------------e) Project II submission& Demo ----------------------

Deliverable 1 Deliverable 2 Deliverable 3 Deliverable 4 Deliverable 5

1.3 Evolution of this document This is a preliminary document with the scope of the project. 1.4 References 1.5 Definitions, acronyms, and abbreviations HOPE: Helping Our People Easily. This is the name of the project. Android: An operating system produced by Google and used on many mobile devices including cell phones and tablets. Currently this is the most popular cell phone operating system. Disabled Person: This is who the application intends to help. This person may have one or many disabilities that hinder normal communication with those in their immediate surroundings. This person may not always be the operator of the HOPE system but he or she will benefit from its use.  



2. Project organization

2.1 Process model Our design process will be based heavily on the creation of UML diagrams for the project. With good UML diagrams, we will have a basis for the system, a basis for group programming, and a graphical representation of the system for use in this document. We will be using Waterfall model for our project development with few exchanges between intermediate phases. 2.2 Organizational structure The members involved in developing this project are: Randy Baniqued Brian Doyle Bjorn Holm-Pedersen Mike Schwartz Andrew Welleck     

Mike is the Team Leader. 2.3 Organizational boundaries and interfaces 2.4 Project responsibilities All the team members will be involved in all phases of the project life cycle. The Team Leader will change at each deliverable. 3. Managerial process

3.1 Management objectives and priorities The main objective of the management position is to organize the meetings for discussions, check the status of the project, and submit the project on time. 3.2 Assumptions, dependencies, and constraints 3.3 Risk management 3.4 Monitoring and controlling mechanisms 4. Technical process 4.1 Methods, tools, and techniques Astah Community tool will be used to do all UML modeling. The system will be implemented in Java using Eclipse with all necessary Android SDK plugins and emulators. The reason for this is two-fold: our programmers are more familiar with Java than other languages and Java offers easy, effective interfaces will be very useful in this project. Our project team will communicate primarily over email and major project milestones will be updated to http://mikeschwartz.net.

4.2 Software documentation

Aside from the project UML diagrams and any in-app help that will be available, there is no need for any supplementary documentation. 4.3 Project support functions

After the project’s initial publishing, it is unlikely that any additional support will be needed. 5. Work elements, schedule, and budget This project is scheduled to be completed by the end of the Fall 2011 Semester for the final demo. Here is the outline of the timeline of the deliverables: Deliverable 1 due by September 6 th, 2011 Deliverable 2 due by September 29 th, 2011 Deliverable 3 due by October 20 th, 2011 Deliverable 4 due by November 10 th, 2011 Deliverable 5 due by November 29 th, 2011