Hope (Helping Old People Easily) Phone Application System Preliminary Project Plan (Phase 0) se 4351 Section 001 Team Name: HelpSoft 9
Download 35.31 Kb.
|
- Navigate this page:
- Table of Contents: 1. Introduction
- 5. Work elements, schedule, and budget 1. Introduction
- Project deliverables
- 1.3 Evolution of this document
- Revision History: Reviser(s)
- Definitions, acronyms, and abbreviations
- 2. Project organization 2.1 Process model
- 2.2 Organizational structure
- 2.3 Organizational boundaries and interfaces
- 3. Managerial process 3.1 Management objectives and priorities
- 3.2 Assumptions, dependencies, and constraints
- 3.3 Risk management
- 3.4 Monitoring and controlling mechanisms
- Product Name Purpose
- 4.2 Software documentation
|
HOPE (Helping Old People Easily) Phone Application System Preliminary Project Plan (Phase 0) SE 4351 Section 001 Team Name: HelpSoft 9
Team Website: www.utdallas.edu/~maj076000 Version 1.0 09/01/2010
1. Introduction 1.1 Project overview The purpose of this project is to help elderly people that have difficulties with hearing, low vision, speech impairment, unclear speech, and memory loss. In the past, devices such as hearing aids, hearing boards etc have been designed and implemented by Augmentative and Alternative Communications (AAC) however; these equipments prove to be costly. Our goal is to provide our customers with an “all in one solution” thus integrating all these devices features into one single device. The key to our success lies in the recent advent of mobile devices with their sophisticated computer like software and hardware capabilities. Our project will be focused on using the Android platform for smart phones. This system will be implemented on a mobile device which consists of a helpful user interface containing icons, pictures, sounds, speech and text easily understood by the elderly.
1.3 Evolution of this document The following sections of this document will change over time depending on various factors and issues encountered by the group.
Revision History:
2. Project organization 2.1 Process model The software development methodology we will follow is the agile technique. The key benefit of this method is that it is iterative and incremental; hence, progress will come in incremental steps, and it is iterative (unlike waterfall method), so we can go back and change previous designs if necessary. Further, the project will be modeled using UML diagrams so we have a good idea of our system design. 2.2 Organizational structure Our team consists of the following 9 members:
2.3 Organizational boundaries and interfaces The team leader will be responsible for ensuring that the group meets at least once a week to discuss ideas and assist each other with challenges throughout the project and also monitor that tasks are completed on deadlines. 2.4 Project responsibilities This project will be developed with the contribution of all our members. The deliverables have not been assigned to a person specifically yet, however, every member will contribute throughout the project. Aaron Jacobs will serve as the group leader in phase 1. 3. Managerial process 3.1 Management objectives and priorities The objective of management is to deliver a Android application that helps people with disabilities such as loss of hearing, how sight and memory. To insure that the system design is correct management will constantly answer the two questions “are we building the software correctly” and “are we building the correct software”. 3.2 Assumptions, dependencies, and constraints Some project assumptions: i) All members will participate and complete tasks before deadline. ii) All members will have access to Java, Android Emulator, and Rational Rose Software. iii) The project is feasible and fairly inexpensive. iv) The elderly will be able to learn the system and use it with ease. Some dependencies: i) The devices that uses our software should have sufficient hardware resources. ii) Budget iii) Time 3.3 Risk management The design should be implemented and documented (e.g. comments) to insure that the project is understandable to others in the team. Some problems encountered can be discussed and solved in the group meetings. All the work done will be uploaded to the website hence everybody will have a copy of the system. 3.4 Monitoring and controlling mechanisms The work will be constantly updated to the website and members will test for errors in design and also code using test cases. 4. Technical process 4.1 Methods, tools, and techniques
4.2 Software documentation Software Documentation includes the Preliminary Project Plan, Requirements Elicitations, Requirements Analysis, Design, Test Plan, and User Manual, and others as needed along the development of the project. All project support documents will be completed in applicable project phases. 5. Work elements, schedule, and budget
Directory: ~chung -> CS4351 -> Presentations10F -> HelpSoft9 -> Phase%201 CS4351 -> Team Awesome hope Phase%201 -> Weekly Android irc with Android developers ~chung -> Editor Version Comment CS4351 -> Hope (Helping Our People Easily) Mobile Phone Application System wrs document Phase 2 Final se 4351 Section 001 Team Name: Team Awesome CS4351 -> Hope (Helping Our People Easily) Mobile Phone Application System Software Project Management Plan Phase 2 Final se 4351 Section 001 Team Name: Team Awesome CS4351 -> Hope (Helping Our People Easily) Mobile Phone Application System Final Phase se 4351 Section 001 Team Name: Team Awesome Download 35.31 Kb. Share with your friends:
|