Given below is the tentative high-level timeline of the project.
This is subject to change. Please follow the weekly project tabs for updated instructions.
| Week | Stage | Activities |
|---|---|---|
| 2 | warmup | Set up prerequisites. Get started on Duke |
| 3 | inception | Continue Phase 1. Decide on a overall project direction (user profile, problem addressed, societal impact, optimize or morph?). |
| 4 | mid-v1.0 | Move towards completing individual contributions to Phase 1 of the project. |
| 5 | v1.0 | Achieve some team tasks in Phase 1. Decide on a overall project direction. Document the requirements of Phase 2. |
| 6 | mid-v1.1 | Conceptualize product and document it as a user guide(draft), draft a rough project plan. Complete Phase 1. |
| 7 | v1.1 | Continue to code in the team repo. Do local-impact changes to the code base. Submit UG for review. |
| 8 | mid-v1.2 | Attempt to do global-impact changes to the code base. Adjust project schedule/rigor as needed, start proper milestone management. |
| 9 | v1.2 | Update UG if necessary. Move code towards v2.0 in small steps, start documenting design/implementation details in DG. |
| 10 | mid-v1.3 | Submit a draft of the DG for review. Continue to enhance features. Make code RepoSense-compatible. Try doing a proper release of your product. |
| 11 | v1.3 | Release as a jar file, release updated user guide, peer-test released products, verify code authorship. Seek code quality comments from your tutor |
| 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.