Team Project Schedules Management Guide

1. 7. Team Project SchedulesSeptember 22, 2004 CSE 498, Collaborative Design Wayne Dyksen Brian Loomis Department of Computer Science and Engineering Michigan State University Fall 2004

2. Things To Do • Edit the following slides… • Include your architecture illustrated slide from Monday. You may use an updated version of your architecture if you’ve refined your architecture. • Add the major milestones to the slides titled Project Schedule. There are three such slides. You may use less and you may use more. The three are just there as a template. Of course, edit the team number and name. And, edit the “1 of 3” in the titles. • Included are example slides for the basketball project. Don’t worry, these milestones correspond to the milestones from last semester but with dates from this semester. So, they’re no particular help to the basketball project for this semester. • Look on the web at our Meeting Schedule. You’ll notice dates for prototype displays (10/11) and final presentations (12/01). Naturally, your schedule should reflect these deadlines. • When your team has completed the slides, do two things… • Email them to me by 2:00pm 9/22. I will try again to put them into one presentation. • Put them on your website somewhere so you can get to them on-line (in case I’m not able to get to your presentation.)

3. Architecture Illustrated • Include here your architecture slide from Monday’s class. • If your team has refined your Architecture Illustrated slide, you may use the latest illustration. • Before talking about your project schedule, give a brief reminder summary of your project architecture using this slide. • Be ready to refer back to this slide for questions. Team 7: Motorola

4. Project Schedule (1 of 3) • One or Two Word Description • Goal: One line description… • Date: • One or Two Word Description • Goal: One line description… • Date: • One or Two Word Description • Goal: One line description… • Date: • One or Two Word Description • Goal: One line description… • Date: Team 7: Motorola

5. Project Schedule (2 of 3) • One or Two Word Description • Goal: One line description… • Date: • One or Two Word Description • Goal: One line description… • Date: • One or Two Word Description • Goal: One line description… • Date: • One or Two Word Description • Goal: One line description… • Date: Team 7: Motorola

6. Project Schedule (3 of 3) • One or Two Word Description • Goal: One line description… • Date: • One or Two Word Description • Goal: One line description… • Date: • One or Two Word Description • Goal: One line description… • Date: • One or Two Word Description • Goal: One line description… • Date: Team 7: Motorola

7. Architecture Illustrated Team 6: MSU Basketball Example From Last Semester

8. Project Schedule (1 of 3) • Game Clock • Goal: Prototype game clock as service. • Date: 09/20 • Wireless Network • Goal: Setup and test ad hoc wireless network. • Date: 09/20 • Accessing the Database • Goal: Prototype multi-user access to Database. • Date: 09/20 • Database Schema • Goal: Complete database schema. • Date: 10/04 Team 6: MSU Basketball

9. Project Schedule (2 of 3) • Stat Collection Interfaces • Goal: Prototype all stat collection interfaces. • Date: 10/06 • Prototype Demos • Goal: Complete prototype demos for class. • Date: 10/11 • Database Integration • Goal: Integrate stat collection with database. • Date: 10/18 • Clock Integration • Goal: Integrate stat collection with game clock. • Date: 10/18 Team 6: MSU Basketball

10. Project Schedule (3 of 3) • Database Queries • Goal: Prototype database querying. • Date: 10/25 • Stat Display Interfaces • Goal: Prototype all stat display interfaces. • Date: 11/01 • Integration and Testing • Goal: Complete integration and testing. • Date: 11/15 • Delivery and Demo • Goal: Deliver and demo final product. • Date: 12/01 Team 6: MSU Basketball