Schedule and Deadlines

Reading

• Chap. 1 - 5

Weekly Deadlines

Every week you will need to do several things

• Write a weekly report detailing the actions of your team for the week.
• Install the weekly report in your project Web pages by midnight Sunday so I can read it on Monday.

Semester Deadlines

Items are due by class time on the dates indicated.

2/3 Client Contract

• give signed copy to team boss (instructor)
• put copy in WWW teampage

2/3 Info to Boss

• make team homepage (outline for now)
• on Web page put
  • project name and short project description
  • team member names
  • mailto links for each team member name
  • client name

2/3 January timesheets due to boss

• In general, your timesheet for a month will be due the first class after the month is over.

• outline major tasks, assign team member responsibilities
• timeline for each task start/completion
• hand in Gantt chart and other supporting docs (timeline, task tree, etc.) on paper to boss
• put in Work-breakdown structure, PERT Chart, Gantt chart, etc. in Web pages
• If you use software to generate these documents, indicate the name of the package(s)

• put HTML version in project Web pages
• hand in signed paper copy for the record.

• all online info for this version
• outline major tasks, assign team member responsibilities
• timeline for each task start/completion
• hand in Gantt chart and other supporting docs (timeline, task tree, etc.) on paper to boss
• put in Work-breakdown structure, PERT Chart, Gantt chart, etc. in Web pages
• If you use software to generate these documents, indicate the name of the package(s)

• put HTML version in project Web pages
• format and context will be reviewed in class

3/7, 3/9 Mid-semester Presentations

• each team will give a short (10 minutes max) presentation in class
• the goal is to inform us of what you are trying to do (as opposed to how you will do it)
• describe the application domain in which you are working, and the problem you are solving
• give system implementation parameters (language, platform, etc.)
• give screen mockups for your user interface
• explain the system functionality (user-manual stuff)
• anything else you think the class would be interested in
• allow time to answer a few questions

3/13 to 3/17 Spring Break

3/21 (Cont.) Mid-semester Presentations

• each team will give a short (10 minutes max) presentation in class
• the goal is to inform us of what you are trying to do (as opposed to how you will do it)
• describe the application domain in which you are working, and the problem you are solving
• give system implementation parameters (language, platform, etc.)
• give screen mockups for your user interface
• explain the system functionality (user-manual stuff)
• anything else you think the class would be interested in
• allow time to answer a few questions

4/4 March individual timesheets due to boss

4/11 Implementation Manual

• contains information needed by maintainers of your product
• include interface specifications for your modules
• include various design diagrams as appropriate for your problem: class diagrams, activity diagrams, interaction diagrams, state transition diagrams, entity-relationship diagrams
• include analysis of the module coupling and cohesion in your design
• include description of the USES relation for your design
• describe your system integration strategy (build plan) and your testing processes (test plan)... document your test scaffolding

4/27, 5/2, 5/4 Final Project Presentations

• in class, each team will present the working product
• we will select at random, in class on demo day, the 4 teams that go on the first day
• do a demo, or bring a video tape of the product ``in action''
• this is your chance to shine... so make the most of it
  • discuss the successes of your team... what worked well
  • discuss pitfalls and roadblocks you encountered along the way
  • discuss interesting technical problems and your solutions
  • present whatever you want that explains your project
  • whatever you think is important to include in your time slot
• 15 minutes max per team: practice, and be on time
• remember to leave time for questions
• each team member will participate
• you may use the Web, Powerpoint, plastic slides, 35mm, paper, videotape, etc.
• try out your technology BEFORE the class time
• allow technology startup time in your timing

5/2 April individual timesheets due to boss

Final project documentation due to boss: Sunday 5/07, 11:59 pm

• finish all required Web information
  • completed project web homepage
  • Final version of contract
  • Final version of schedule
  • Final version of User Manual
  • Final version of Technical Manual
  • Documented code , nicely organized (indexed, table of contents, etc.) dintinguish clearly between code you wrote and code you "found", and clearly indicate individual authorship
  • all weekly reports caught up
  • in-class presentations if they were electronic (PowerPoint, HTML, etc.)
• Product Package
  • Create two notebooks... to contain a few paper items
  • one for Client, one for Boss
  • copy of the final contract on paper
  • copy of the final schedule on paper
  • unpacking directions on paper
  • tar files, zip files, self-extracting archives can all stay stored on dept server for me...
  • Client notebook should not have the reports that the Boss gets but client notebook may need to have the product on diskette... as needed by the client. Client notebook may also need manuals on paper... depends on clients' desires.
• Team: final report
  • 2-4 pages, in the Boss notebook only
  • tell how the project went overall, what you learned, what you would do differently next time, what worked, what didn't. All team members should agree generally with the information in this report... discuss it as a team.
• Individual: final report
  • Your personal report is between you and the instructor
  • hand it in directly to the instructor, or seal in individual envelopes and include all with the boss notebook
  • 1-2 pages
  • Report on any differences you have with the team report... do you disagree with any of the material there? Give your personal take on the class and the project. What kind of experience did you have? What would you do differently nect time? Anything you have to say can go here.
  • Rate your team members (not yourself) by allocating 100 points among them, according to your estimation of their contribution to the project. Explain/justify your allocation by discussing the cooperation, contributions, participation, attendence at meetings, reliability, skills, etc. of each person.