CS 160: Software Engineering

GREEN SHEET ADDENDUM

Sections 1 and 2

Spring Semester 2008

Department of Computer Science
San Jose State University
Instructor: Prof. Ron Mak

Section 1: Tuesdays and Thursdays, 7:00 – 8:15 pm, MacQuarrie Hall, room 225

Section 2: Tuesdays and Thursdays, 8:30 – 9:45 pm, MacQuarrie Hall, room 225

Office hours: Tuesdays and Thursdays, 5:30 – 6:45 pm

Office location: Duncan Hall, room 282

E-mail: mak@cs.sjsu.edu (e-mail preferred over phone)

Phone: (408) 533-2726 (cell)

Project description

A major portion of the coursework will be the class projects. The projects provide an opportunity to apply immediately the material taught in the classes and from the textbook.

Students can form their own project teams, subject to the following minimum criteria:

• Each team has 4-6 members.
• Once teams are formed, students may not move from one team to another without the instructor’s permission.
• Each team can choose to develop its own software product, or it can develop the default class product (described below).
• The team’s product must be sufficiently substantial so that it would take the entire team working fulltime between a semester and a year to completely develop it.
• Since it is not expected that a team would actually complete the product by the end of the semester, the product’s development must have well-defined early milestones in the project schedule that can be achieved during the semester.
• One of the early milestones must be a prototype that will be demonstrated to the rest of the class.
• Each team can choose its implementation technologies, such as Web or desktop GUI, type of backend storage, etc. based on the skills of the team members.
• At the end of the semester, each team will demo its product as far as it is completed.
• During each oral presentation, one or more team members can do the presentation.
• During a team’s presentation, the members of the rest of the class will play the roles of advisors or customers for the team’s products.

Default class product

A project team can choose instead to develop this software product: The Online Textbook Rental Service.

• The service rents course textbooks to students.
• Students who use the service must create accounts.
• Students search an online database of available textbooks.
• Students reserve books online.
• Students pay rent online.
• Books are checked out when rented and checked back in when returned.
• The service obtains upcoming textbook requirements from professors.

This is minimum set of requirements. Each team should add its own ideas to turn it into a winning product that would take a full year to develop.

Project deliverables

Except for the individual post mortem assessment, each artifact and presentation is a team deliverable; i.e., all the members of each team work together to deliver one copy of each artifact per team, and each team presentation is a group effort by its members. All team members should be present during a presentation, although who actually does the presentation can be decided by the team. (Due dates are subject to change with adequate notice.)

Artifact or Presentation	Due
Problem statement [2-4 pp., see Bruegge Figure 4-17]	Feb 5
Use cases (10-12 cases, UML diagram and descriptions) Preliminary functional specification [see Bruegge Fig. 4-16]	Feb 7
Conceptual design document [4-6 pp.]	Feb 12
Conceptual design review and prototype demo	Feb 12, 14
“Final” functional specification	Feb 19
Project schedule	Feb 21
“Final” design document	Mar 13
“Final” design review	Apr 1, 3
Code review	Apr 15, 17
Test plan	Apr 24
Product demo	May 6, 8
Individual post mortem assessment [3-4 pp.]	May 13

Project grade

Each student’s project grade will be determined by the quality of the team’s artifacts and presentations and by his or her participation in producing the work. (Who worked on what can be tracked by the project management tools.)

Participation also includes playing the role of advisor or customer to the teams giving presentations. Therefore, class attendance is especially important during presentation days.

At the end of the semester, each student will individually write a post mortem assessment (3-4 pp. single-spaced) of his or her project, which will include:

· a description of what he or she learned from being on the team

· a self evaluation of his or her own work on the team

· an evaluation of the other team members

Therefore, each student’s project grade will be weighted as follows:

40%	quality of the team’s artifacts and presentations
30%	individual student’s participation
30%	individual student’s written post mortem assessment