Back to Milestone 1
You can also view the
original Word DOC saved as HTML.
3/13/03
Operational prototype of the new database to handle the calendar of events.
4/8/03
Operational prototype of the new database to handle the information about the organization’s contacts.
4/22/03
Operational prototype of the new database to handle the library of paper references located in the organization’s office.
Fully operational system with all parts integrated through a web-based UI.
M. Num. Name Date Due Expected Work Completed Leader ------- ------------------ -------- ----------------------- ------------ 1 Project Proposal 2/18/03 Schedule work for JasonLong and Preliminary each team member; Project Plan schedule goals; analyze all milestones 2 Requirements 2/27/03 Review the DanaChampion Definition; Updated problem and Project Plan proposed solution, and define the requirements for the project 3* Database 3/13/03 Analysis, design, DaveLanzer Application and testing of Analysis; Updated Calendar DB; Project Plan Updated project plan 4* Database 4/8/03 Analysis, design, JasonLong Application Design; and testing of Updated Project Contacts DB; Plan Updated project plan 5* Database 4/22/03 Analysis, design, DaveLanzer Application and testing of Implementation, Library DB; Testing, and Updated project plan Performance Improvement 6 Application 5/6/03 Training, DanaChampion Turnover and Final Documentation, Project Presentation and Final Project Presentation
* We have modified the Milestone structure to better fit our iterative design process. All concepts and procedures for the assigned milestones 3, 4, and 5, are combined to create three milestones with the three parts included in each one. Each of the three milestones is now used for complete development of one database using the analysis, design, and testing criteria.
JasonLong will lead the team through Milestone 1.
This part of the project requires much careful planning and allocating of team resources, skills, and time. Through this period we will be laying out a preliminary schedule of work for the semester to be sure we stay on target. We also will be looking over all six of the milestones to be sure our goals are realistic and that the scope of the project is not to great for the given amount of time for completion.
During this time we also restructured our Milestone process (as described below the project organization timetable) to modify Milestones 3, 4, and 5 into three prototyping stages: Milestone 3 includes analysis, design, and testing of the Contacts database; Milestone 4 includes analysis, design, and testing of the Calendar database; and Milestone 5 includes analysis, design, and testing of the Library database.
Meeting notes DanaChampion 2 hours Project proposal JasonLong 4 hours Preliminary project plan DaveLanzer 4 hours Create presentation JasonLong 1 hour Milestone completion summary DanaChampion < 1 hour
Deliverables:
DanaChampion will lead the team through Milestone 2.
This phase will build the foundation for the project. While frequently meeting with our contact (Michele Leaman), we will be conducting a thorough requirements analysis to discover all the details concepts that will need to be involved in our proposed solution. Finally, we will define the project in its three parts in terms of our newly accepted requirements. These requirements will be generally defined in the beginning and more specifically defined during the requirements’ respective milestones.
We will also be updating our project plan.
Requirements document All 6 hours (each) Updated project plan JasonLong < 1 hour Project meeting notes DanaChampion 1 hour Milestone completion summary DaveLanzer < 1 hour
Deliverables:
Alt. Milestone 3: Calendar Database Prototyping; Updated Project Plan
DaveLanzer will lead the team through Milestone 3.
Having defined a broad solution to the problem of the Women’s Caucus’ paper operations, we must now take a careful look at each individual part of the project and determine how good our solution is and how helpful it will be in the future. We start by looking at the process of identifying and recording calendar information. At this stage, we will concentrate on the analysis, design, and prototyping of the calendar database.
Preliminary ER logical schema design and data dictionary DanaChampion 4 hours Business rules DaveLanzer 3 hours Preliminary DFD process design JasonLong 2 hours Database selection All 1 hour (each) Database prototype All 3 hours (each) Preliminary Web-based UI Dave, Jason 2 hours (each) Analysis traceability matrix (ER and DFD) DanaChampion 1 hour Updated project plan JasonLong < 1 hour Updated SRS DanaChampion < 1 hour Meeting notes DanaChampion 1 hour Milestone completion summary DaveLanzer < 1 hour
Deliverables:
Alt. Milestone 4: Contacts Database Prototyping; Updated Project Plan
JasonLong will lead the team through Milestone 4.
We now must look at the process of identifying and recording contact information. For this milestone, we will concentrate on the analysis, design, and prototyping of the contacts database. This database will be used to hold the contact information for all people who speak about a given topic or who have access to or maintain resources concerning a specific topic.
Updated ER logical schema design and data dictionary DaveLanzer 2 hours Updated DFD process design JasonLong 1 hour Updated database prototype All 3 hours (each) Updated Web-based UI DanaChampion 2 hours Updated analysis traceability matrix DanaChampion 1 hour Design/UI traceability matrix Dana, Dave 1 hour Database normalization and rationale DaveLanzer 2 hours Implementation of Calendar Dana, Jason 5 hours (each) Implementation of Contacts DaveLanzer 5 hours Updated project plan DaveLanzer < 1 hour Updated SRS DanaChampion < 1 hour Meeting notes DanaChampion 1 hour Milestone completion summary JasonLong < 1 hour
Deliverables:
Alt. Milestone 5: Library Database Prototyping; Updated Project Plan
DaveLanzer will lead the team through Milestone 5.
We now must look at the process of identifying and recording library and reference information maintained by the Women’s Caucus. For this milestone, we will concentrate on the analysis, design, and prototyping of the library database. This database will be used to hold the library and reference information for all of the packets of information maintained by the Women’s Caucus.
Updated DFD process design JasonLong 1 hour Updated Web-based UI JasonLong 2 hours Implementation of Calendar Jason, Dana 5 hours Implementation of Contacts DaveLanzer 5 hours Implementation of Library DaveLanzer 5 hours Implementation traceability matrix DanaChampion 1 hour Performance Improvements DaveLanzer 1 hour M5 Implementation Status DanaChampion < 1 hour M6 Intentions Document DanaChampion < 1 hour Database test plan JasonLong 3 hours Updated project plan DanaChampion < 1 hour Meeting notes DanaChampion 1 hour Milestone completion summary DanaChampion < 1 hour
Deliverables:
DanaChampion will lead the team through Milestone 6.
The final project report and presentation will be a culmination of all of the work done on the system database project throughout the semester including problems encountered along the way, unexpected successes, and an evaluation of things we could have done differently in our approach to the project.
Database test results Dave and Dana 2 hours (each) Final testing DaveLanzer 3 hours Create documentation JasonLong 3 hours Training DanaChampion 3 hours Revisions to application All 2 hours Create presentation All 4 hours Milestone completion summary DanaChampion < 1 hour
Deliverables:
| Page Execution took real: 17.609, user: 10.620, sys: 0.490 seconds |