CS 121 Project Timetable
General Note
- The following table outlines certain checkpoints.
- It does not mean that all work toward the checkpoint is done only in the week between it and the previous checkpoint.
- In other words, plan ahead.
As soon as possible
- Elect a leader or contact who will be my primary communication point.
- (Less urgent) decide on a name for your team.
Other Requirements
- All work will be in machine-readable form (no hand-written documents, please).
- You must use a version control system (RCS, CVS, etc.) for source and documents and use Make or equivalent.
- Tests should be automated where feasible.
Mon. 3/27 (Assignment 8)
- Your team’s proposal should be complete.
- It will be presented in class (9 min. limit).
- The proposal should describe:
- The product
- The intended users and platform
- General requirements (not necessarily detailed use-cases)
- Your team organization
- Life cycle model you will be using
- General idea of approach (not detailed schedule)
Establish a web page
- Here you will maintain (i.e. keep up-to-date) various written items for the project:
- Proposal
- Change log (for requirements, plan, etc.)
- SRS
- Project plan, schedule, work breakdown structure
- Design document
- Testing plan
Mon. 4/3 (Assignment 9)
- Your requirements analysis should be complete. You should have a first drafts of the schedule and design.
- Present analysis in class (9 min. limit).
- The analysis should be self-contained and include:
- Product description and intended users
- Requirements, including detailed use-cases and clarifying scenarios
- Draft of a detailed development schedule, from design through validation and testing
- Draft work breakdown structure
Mon. 4/10 (Assignment 10)
- Your design should be complete. You may have done some exploratory protytping.
- Present design in class (up to 20 mins.).
- The design should:
- Relate to the SRS, esp. use cases.
- Use UML (class diagrams at a minimum; other diagrams as deemed useful)
- Take eventual testing into consideration.
- Present implementation work breakdown structure and schedule (with staff assignments).
Mon. 4/17 (Assignment 11)
- This assignment will be on formal program verification.
- It is not part of the project.
- Please consider this advanced notice and prepare accordingly.
Mon. 4/24 (No Class)
- Mon. - Wed. are HMC presentation days and no classes are scheduled.
- You may wish to attend some of the presentations, especially the CS Clinic presentations on Tuesday, many of which entail software development.
- You may also wish to devote some of the time to project implementation.
Mon. 5/1 (Assignment 12)
- A good portion of your development work should be done.
- Your team should give a code walkthrough of one or two key components.
- You have up to 20 mins., so this may spill into Wed. 5/3.
Thur. 5/11 (Final Presentation)
- This is during the time the final exam is scheduled, 8:00 a.m. - noon.
- Overview of the project, actual development compared with plan, shared wisdom, etc.
- Demonstrate of your product