To expedite your project implementation, you will be given some sample code (AddressBook-Level1 to AddressBook-Level4, shown as AB1 to AB4 in the diagram above). You can use AB1 to AB3 to ramp
up your tech skills in preparation for the project. AB4 is to be used as the basis for your project.
AB4 is the version you will use as the starting point for your final project. Some of the work you do in AB1 to AB3 can be ported over to AB4 and can be used to claim credit in the final project.
Given below is the high-level timeline of the project.
| Week | Stage | Activities |
|---|---|---|
| 3 | inception | Decide on a overall project direction (user profile, problem addressed, optimize or morph?). |
| 4 | mid-v1.0 | Decide on requirements (user stories, use cases, non-functional requirements). |
| 5 | v1.0 | Conceptualize product and document it as a user guide(draft), draft a rough project plan. |
| 6 | mid-v1.1 | Set up project repo, start moving UG and DG to the repo, attempt to do local-impact changes to the code base. |
| 7 | v1.1 | Update UG and DG in the repo, update project plan in repo, attempt to do global-impact changes to the code base. |
| 8 | mid-v1.2 | Adjust project schedule/rigor as needed, complete repo set up, start proper milestone management. |
| 9 | v1.2 | Move code towards v2.0 in small steps, start documenting design/implementation details in DG. |
| 10 | mid-v1.3 | Continue to enhance features. Make code RepoSense-compatible. Try doing a proper release. |
| 11 | v1.3 | Release as a jar file, release updated user guide, peer-test released products, verify code authorship. |
| 12 | mid-v1.4 | Tweak as per peer-testing results, draft Project Portfolio Page, practice product demo. |
| 13 | v1.4 | Final tweaks to docs/product, release product, demo product, evaluate peer projects. |
More details of each stage is provided elsewhere is this website.