Milestone 3

CSC 333 Project Status Report                                                                                  

Project Name: HELP
Team Members: Dave Hess, Robert Lusk, Ria Ghose

Team Lead: Ria Ghose

Date Report Submitted: March 11, 2004
Time Period Reporting On: March 2nd – March 11th

1.      Progress Made

We now have a UML data model showing the major working of the system. This helps us gain a better understanding of the system. We have been able to incorporate some of the items requested by HELP into the data model, like the drop down menus. The business rules also add a new standard to the project, besides they abide by the HELP requirements.

Our low-fidelity prototype gives us an understanding of how the system will look like once implemented.

 

2.      Plans for Upcoming Time Period Until Next Status Report Due

We will begin work on milestone 4. We will focus on the deliverable of increment 1 which includes creating the physical database. At this point we will also work on designing the GUI.

3.      Issues Resolved

The entities in our table clear the way for physical database design. Our issue with creating a separate person and client table have been resolved (fro details see UML diagram). 

4.      New Issues to be Addressed

Although we have tried to modify the milestone 2 for the functional requirements, we are not sure we have it done correctly. 

 

 

 

 

 

Milestone 3 Completion Document

Milestone Completion Summary for CSC333 (Spring, 2004)

· Milestone Number: 3

Team Name: HELP ministries

Team Members (and Roles, including leader):

Dave Hess: (LEAD)—Visited HELP and helped with writing the UML Data Model and project update.

Ria Ghose: Documentations, completion summary, business rules, team notes

Robert Lusk: Rework System overview

Due Date: 2004-3-11

Summary of Results of Milestone: 3

We have decided on and implemented our data model in UML. We have also chosen the technology stack we are going to be using for the project. We have tried to update and better the SRS from previous milestone. In addition, we have the following done:

·        We have an UML data model.

·        A list of business rules

·        A data dictionary

·        Low-fidelity prototype

Strengths of Milestone: 3

·        The UML gives us a better understanding of the system and we can visualize the requirements of the project due to the data model

Weaknesses of Milestone: 3

·        Our SRS from milestone 2 is not as strong, even after changes made to it. This may affect us later on.

Project Status:

Green

 

Effort:

UML design – Dave
Data dictionary – Dave and Ria
Business Rules – Dave and Ria
Low -fidelity prototype and database selection – Ria, Bobby, Dave
Project meeting notes – Ria and Dave
Completion summary – Ria
Modifying SRS – Ria and Dave

Updating Website – Dave