| Project
Progression
|
| Gantt
Chart of Project Schedule |
|
Week No: |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
| Project
Planning |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Tools
Familiarization |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Requirement
Analysis |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Software
Design |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Implementation |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Testing |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Buffer
/ Demo |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Legend: |
|
|
|
|
|
|
|
|
|
|
| Proposed
Progress » |
|
|
|
|
|
|
|
|
|
|
| Actual
Progress » |
|
|
|
|
|
|
|
|
|
|
|
Week
1: (17 Jan 2002 - 23 Jan 2002)
- Established project team and assigned each team member to
his/her role and responsibility in designing project
software.
Team members are published in Project
Members page.
- Formulated project requirements and proposed the project
for another team.
(Details: Project
Request)
- Received project requirements we will be working with from
another team.
(Details: Project
Requirements)
- Established project schedule as a guide for our project
development process.
(Details: Project
Schedule)
|
Week
2: (24 Jan 2002 - 30 Jan 2002)
- Analyzed first phase of the project specification
using Object Oriented Analysis (OOA) approach. The Use
Case diagram will be published after the final
phase analysis in week 3.
- Familiarized the use of Rational Rose
as our project modeling software.
- Familiarized the use of Microsoft Access 2000
& Visual Basic Applications (VBA) as our project
implementation programming languages.
|
Week
3: (31 Jan 2002 - 06 Feb 2002)
- Completed Use Case diagram. (View)
- Starting to work on UML Class Diagram
analysis.
|
Week 4: (07
Feb 2002 - 11 Feb 2002)
- Completed UML Class diagram
analysis. (View)
- Analysed the UML Class diagram
further to obtain UML Collaboration diagram
and UML Sequence diagram.
- Completed ER Diagram. (View)
|
Week
5: (14 Feb 2002 - 20 Feb 2002)
- Completed UML Collaboration diagram
and UML Sequence diagram. (View)
- Assigned tasks to each project member for each class to be
implemented.
It was decided to use Microsoft Access 2000
and Visual Basic Applications (VBA) to implement this project. All project members will focus on
their assigned tasks due to the timing constraint.
- Completed Normalization. (View)
- Created Microsoft Access 2000 database.
- Set the relationship between database tables. (View)
|
Week 6: (21
Feb 2002 - 06 Mar 2002)
- Each member was initially assigned to do a small part of program and
thus everyone tried to familiarize with Microsoft
Access 2000 and VBA.
- There were many meetings called as we encountered many
obstacles due to integration problems. The problems were
resolved by keeping to the development role.
- There were a reshuffling of tasks assigned to the group
members as we found the old tasks were not suitable and
effective. (View)
|
Week 7: (07
Mar 2002 - 13 Mar 2002)
- Design of test case in progress.
- Programming near completion.
- Compilation and generation of online report in progress.
|
Week 8: (14
Mar 2002 - 20 Mar 2002)
- Design of test case completed.
- Programming and Integration completed.
- Testing in progress.
- Compilation and generation of online report in progress.
- Creation of Online Help in progress.
|
| Week 9: (21
Mar 2002 - 28 Mar 2002)
|