1 / 8

CS 499 Software Development Project Overview

CS 499 is part of a two-course sequence where teams complete a software development project. Attendance is mandatory. The course schedule includes formal and informal team meetings, with three project releases and follow-up activities. Grading is based on individual responsibilities.

oprah-charles
Download Presentation

CS 499 Software Development Project Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS 499 Course Overview CS 499 is the second course in a two-course sequence in which teams complete the software development project that they began in CS 425. Attendance at all class meetings is required. On days when your team is not scheduled to formally meet with the instructor in EB 1010, your team is expected to meet informally in EB 2029, where you may be joined by the instructor later in the 75-minute class period.

  2. CS 499 Schedule With twelve exceptions, this course will be conducted as formal meetings with one team on Mondays and the other team on Wednesdays. Most Mondays, the Metamorphosis team will meet in EB 1010 for formal meetings. Most Wednesdays, the Metamorphosis team will meet in EB 2029 for informal meetings. Most Mondays, the CryptKeeper team will meet in EB 2029 for informal meetings. Most Wednesdays, the CryptKeeper team will meet in EB 1010 for formal meetings.

  3. Three Releases Your project will be completed in three releases, with some additional follow-up afterwards. • Release 1 • Initial code & documentation • Specifications required: week of 8/28 • Completed release due: week of 9/18 • Release 2 • More thorough code & documentation • Specifications required: week of 9/18 • Completed release due: week of 10/16 • Release 3 • Complete code & documentation • Specifications required: week of 10/16 • Completed release due: week of 11/13 • Follow-Up • Peer reviews: week of 11/27 • Faculty presentation: week of 12/4 • Post-mortem discussion: week of 12/11

  4. Release 1 Schedule

  5. Release 2 Schedule

  6. Release 3 Schedule

  7. Follow-Up

  8. CS 499 Grading Each assignment must contain a clear specification of the individual responsibilities of each team member. Grade Breakdown:

More Related