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.
Date30.06.2017
Size35.31 Kb.
#22225


HOPE (Helping Old People Easily) Phone Application System

Preliminary Project Plan
(Phase 0)


SE 4351
Section 001


Team Name: HelpSoft 9

Member’s Name

Email Address

Aaron Jacobs

Npcomplete29@gmail.com

Allen Helton

allen@student.utdallas.edu

Chris Mudd

thechrisman@gmail.com

Jeff Allain

jiffyall@yahoo.com

Jessi Cardosa

Jxc1288@student.utdallas.edu

Matthew Jacobs

Maj076000@utdallas.edu

Prerak Patel

Prerak.patel@student.utdallas.edu

Richard Vanderdys

Richardv3@student.utdallas.edu

Saurav Shrestha

Saurav2220@gmail.com

Team Website: www.utdallas.edu/~maj076000

Version 1.0 09/01/2010



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, acronyms, and abbreviations


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 controlling mechanisms


4. Technical process
    4.1 Methods, tools, and techniques
    4.2 Software documentation
    4.3 Project support functions


5. Work elements, schedule, and budget

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. Project deliverables




  1. Preliminary Project Plan Deliverable 0

  2. Requirements Gathering Deliverable 1

  3. Requirements Analysis Deliverable 2

  4. Architectural Design Deliverable 3

  5. Component/Object Specification Deliverable 4

  6. Coding Deliverable 5

  7. System Testing Deliverable 6

  8. Final Software Release/ Presentation Deliverable 7

    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.



  1. Product information/Features

  2. Definitions, acronyms, abbreviation

  3. Schedules

  4. Roles assigned

Revision History:

Reviser(s)

Date

Addition/Changes/ETC

Saurav Shrestha

9/1/10

Filled in Introduction, Project Organization, and Managerial Process.

Matthew Jacobs

9/1/10

Added Cover Page, Table of Contents, Technical Process, and Schedule.



    1. Reference



  1. Teams website www.utdallas.edu/~maj076000

  2. Instructors website http://www.utdallas.edu/~chung/CS4351/syllabus.htm



    1. Definitions, acronyms, and abbreviations



  1. AAC – Augmentative and Alternative Communication

  2. Android – Operating system by Google which is compatible with various mobile devices.

  3. Android emulator- mimics the Android OS in the developer’s PC.

  4. Assistive person – Individual assisting the patient

  5. OS- Operating System

  6. HOPE – Helping Old People Easily

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:




Aaron Jacobs (Phase 1 leader)

Allen Helton

Chris Mudd

Jeff Allain

Jessi Cardosa

Matthew Jacobs

Prerak Patel

Richard Vanderdys

Saurav Shrestha


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



Product Name

Purpose

Eclipse

To create the programs to run on the Android Emulator.

Microsoft PowerPoint

To create presentations used to present the deliverables during the Interim and Final Phases of Project 1 and 2.

Microsoft Word

To create the documents needed for the deliverables.

Rational Rose

Create UML and Sequence Diagrams

    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.

    4.3 Project support functions

All project support documents will be completed in applicable project phases.


5. Work elements, schedule, and budget


  1. The workload will be divided fairly to the 9 members of the team.

  2. The group leader will be changed throughout the project however; every member will assist in completing the project.

  3. This project is scheduled to be completed by December, 2nd 2010 for the final demo. Here is the outline of the timeline of the deliverables:
    Preliminary Management Plan due by 09/02/2010
    Interim Deliverable of Project 1 due by 09/30/2010 – 10/05/2010
    Final Deliverable of Project 1 due by 10/21/2010
    Interim Deliverable of Project 2 due by 11/11/2010
    Final Deliverable of Project 2 due by 11/30/2010 – 12/02/2010




Download 35.31 Kb.

Share with your friends:




The database is protected by copyright ©ininet.org 2022
send message

    Main page