Hope (Helping Our People Easily) Mobile Phone Application System Software Project Management Plan Phase 2 Final se 4351 Section 001 Team Name: Team Awesome



Download 52.58 Kb.
Date conversion07.07.2017
Size52.58 Kb.

HOPE



HOPE (Helping Our People Easily) Mobile Phone Application System

Software Project Management Plan

Phase 2 Final
SE 4351

Section 001

Team Name: Team Awesome

Member’s Name

Email Address

David Pederson

dip091000@utdallas.edu

Weston Wofford

wbw081000@utdallas.edu

Eric Ly

eric.ly@utdallas.edu

Aakash Patel

ahp091020@utdallas.edu

Saad Ahmed

sxa054100@utdallas.edu

Angela Neff

aen072000@utdallas.edu

Amanda Lim

arl092020@utdallas.edu


Team Website: https://sites.google.com/site/utdhope001/

Version 2.0 11/29/2011



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 people that have difficulties with hearing, vision, speech impairment, and memory loss. In the past, devices such as hearing aids have been designed and implemented by Augmentative and Alternative Communications (AAC). However, this technology proves to be costly. Our goal is to provide our customers with an all encompassing solution, thus integrating all these features into a single device. The key to our success lies in the recent advent of mobile devices with their sophisticated software and hardware capabilities. Our project will focus 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 understood universally by smart phone users.
1.2 Project deliverables
● Initial Structuring (September 6, 2011)

○ Preliminary Software Project Management Plan

● Phase 1 Interim (September 29, 2011)

○ Revised Software Project Management Plan

■Meeting Minutes

○ Interim System Requirements Specifications (Iteration 1)

○ Interim Software Requirements Specifications (Iteration 1)

○ Slide-show depicting:

■Understood customer requirements

■Progress on deliverables

■The product’s features

○ Hard copy of preliminary project plan (this document)

● Phase 1 Final (October 20, 2011)

○ Revised Software Project Management Plan

■Meeting Minutes

○ System Requirements Specification (Iteration 1)

○ Software Requirements Specification (Iteration 1)

○ Prototype (Iteration 1)

● Phase 2 Interim (November 10, 2011)

○ Revised Software Project Management Plan

■Meeting Minutes

○ Interim Revised System Requirements Specifications (Iteration 2)

○ Interim Revised Software Requirements Specifications (Iteration 2)

● Phase 2 Final (November 29, 2011)

○ Final Software Project Management Plan

■Meeting Minutes

○ Revised System Requirements Specifications (Iteration 2)

○ Revised Software Requirements Specifications (Iteration 2)

○ Prototype (Iteration 2)

○ Slide-show depicting the planned product’s features


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.

i) Product information/Features

ii) Definitions, acronyms, abbreviation

iii) Schedules

iv) Roles assigned


1.4 Reference

i) Team’s website http://sites.google.com/site/utdhope001/

ii) Instructor’s website http://www.utdallas.edu/~chung/CS4351/syllabus.htm

1.5 Definitions, acronyms, and abbreviations

i) AAC – Augmentative and Alternative Communication

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

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

iv) OS- Operating System

v) HOPE – Helping Our People Easily



2. Project organization

2.1 Process model

We are going to develop this application using the agile method. The major advantages of this method is that it is iterative and incremental; therefore, the progress will come in incremental steps. In addition, we will use the UML diagrams to model the design.





2.2 Organizational structure

Our team consists of the following 7 members:



Member’s Name

Email Address

David Pederson

dip091000@utdallas.edu

Weston

wbw081000@utdallas.edu

Eric Ly

eric.ly@utdallas.edu

Aakash Patel

ahp091020@utdallas.edu

Saad Ahmed

sxa054100@utdallas.edu

Angela Neff

aen072000@utdallas.edu

Amanda Lim

arl092020@utdallas.edu


2.3 Organizational boundaries and interfaces

The team leader will make sure that the group meets when required, to be specified as necessary. Meetings will occur in person, or tasks will be assigned with a due date. These meetings will serve to allow members to discuss ideas and assist each other with any difficulties they may encounter throughout the project, as well as monitoring the tasks that are assigned, ensuring they 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. Saad Ahmed will serve as the group leader in phase 2.


3. Managerial process

3.1 Management objectives and priorities
Our management main objective is to assist people with disabilities with loss of loss of hearing, low sight, and memory with the deliver of an Android application. Throughout our system design, we will make sure our application is maintaining two objectives “ensuring the software is built correctly” and “ensuring we are building the correct software.”

3.2 Assumptions, dependencies, and constraints
Some project assumptions:

i) All members will participate and complete tasks before deadline.

ii) The project is feasible and fairly inexpensive
Some dependencies:

i) The devices that uses our software should have sufficient hardware resources.

ii) Budget

iii) Time


3.3 Risk management
Ensuring that documentation is heavily used in the design will assist other team members to understand what has been implemented. By using documentation we can discuss and solve problems encountered in group meeting.

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

i) The workload will be divided fairly to the 7 members of the team.

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

iii) This project is scheduled to be completed by November, 29th 2011 for the final demo. Here is the outline of the timeline of the deliverables:

Preliminary Management Plan due by 09/06/2011

Interim Deliverable of Project 1 due by 09/29/2011 – 10/04/2011

Final Deliverable of Project 1 due by 10/20/2011

Interim Deliverable of Project 2 due by 11/10/2011



Final Deliverable of Project 2 due by 11/29/2011 – 12/01/2011


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

    Main page