Address Book Project (PDF)




File information


This PDF 1.4 document has been generated by Google / , and has been sent on pdf-archive.com on 21/10/2016 at 20:01, from IP address 128.223.x.x. The current document download page has been viewed 1847 times.
File size: 91.27 KB (9 pages).
Privacy: public file
















File preview


Address Book Project
John Brodnax, Riley Brogan, Brenda Heng, Will Stidhem, and George Wang

Our Approach
-

Assigned Roles
-

-

Meetings
-

-

Where and when would work for team.
Easier communication.

Schedule
-

Riley

Addressing each member’s strengths and weaknesses.
Each role had a primary and at least one backup.

Tasks based off of meetings and software design.
Developed tasks for each iteration so that we could complete the project in a timely manner

Iterations
During our initial meetings, we proposed that we would have three major iterations
for developing our application. Each iteration required planning, documented
requirements, analysis, design, and testing before continuing on to the next
iteration.
1.
2.
3.

Riley

Back-end code
Front-end/GUI
Connecting both ends together.

Our Address Book Project
-

Project capabilities:
-

Contain multiple address books, where each address book saves its own entries including
options for adding, deleting, editing, sorting by zip, and sorting by name. Each book can be
dynamically searched by name. Our program also has the capability to import and export
whole books by writing and reading them from txt files.

-

DEMO

Riley & Will

Why our program is implemented the way it is
-

Customer meetings and project requirements
-

-

Will

First meeting:
- Brought an outline of a GUI implementation
- Customer gave feed back
- Made requested changes
Second meeting:
- Brought back new outline of GUI with initial customer requirements.
- Showed customer some simple demos and checked that outcomes were satisfactory.
- Received feedback and made final changes to the program

Lessons Learned
-

Inefficient project planning:
-

Brenda

Lack of documentation of action items
Lack of details on group schedule
Responsibilities were unevenly distributed
Redistribution of tasks was necessary to complete all final action items

Effectiveness of Project Plan
-

Initially followed schedule closely in the first two weeks of the project
Second half had more conflicts than expected and delayed the tasks that
could be completed by other members
Lack of documentation resulted in miscommunication about what tasks
needed to be completed
Work needed to be redistributed among other members
-

Brenda

Documentation spread to two other members from project manager
Roles were changed within the first couple of meetings
Documentation and more testing needed to be completed last minute

Risks
-

Our preliminary risks:
-

-

Other risks encountered:
-

John

Not finishing on time.
Not properly assigning or understanding goals.
Unsatisfactory team member participation.

Not getting things done on schedule.
Tying the front and back together took a little more work than we thought it would.
Uneven distribution of work, one member had a heavier workload than others

Plan for improving process for project 2
-

George

Make a more detailed plan at the beginning of the project.
Prepare more thoroughly for meetings with the customer.
Be more specific when allotting responsibilities.
Address more possible risks so we can be ready for them.






Download Address Book Project



Address Book Project.pdf (PDF, 91.27 KB)


Download PDF







Share this file on social networks



     





Link to this page



Permanent link

Use the permanent link to the download page to share your document on Facebook, Twitter, LinkedIn, or directly with a contact by e-Mail, Messenger, Whatsapp, Line..




Short link

Use the short link to share your document on Twitter or by text message (SMS)




HTML Code

Copy the following HTML code to share your document on a Website or Blog




QR Code to this page


QR Code link to PDF file Address Book Project.pdf






This file has been shared publicly by a user of PDF Archive.
Document ID: 0000497599.
Report illicit content