University of Utah

School of Computing

Software Engineering Laboratory

CS 4500 Spring Semester, 2008
WEB 2230 TH 2:00-3:20
Instructor: Thomas C. Henderson

Announcements

Week 16 (21-24 Apr 2008)

Last week of class!
Final Report Due: 24 April 2008 [See Final_Report.html in the Guidelines for Documents and Deliverables; note that it has been updated.]
Demo Day: 9am - noon; 24 April in WEB 130. Locations have been assigned to teams; you will demo your project to people who attend (other students, faculty, visitors). A set of faculty will judge and rank the projects; a set of prizes will be awarded based on the ranking. Feel free to invite your sponsors! We will have donuts and drinks in the morning, and serve pizza during the award ceremony.
Here is this year's Demo Day Brochure

Week 15 (14-18 Apr 2008)

Only 1 more week left!
Product Release Due This Friday (18 April 2008) [This is just your final release on the team web site.]
Final Report Due: 24 April 2008 [See Final_Report.html in the Guidelines for Documents and Deliverables; note that it has been updated.]
Demo Day: 9am - noon; 24 April in WEB 130. Locations have been assigned to teams; you will demo your project to people who attend (other students, faculty, visitors). A set of faculty will judge and rank the projects; a set of prizes will be awarded based on the ranking. Feel free to invite your sponsors! We will have donuts and drinks in the morning, and serve pizza during the award ceremony.
Remember that when you get an evaluation and feedback on something (WMR, document, etc.), you may update it for a regrade.
Individual logs are due one last time: Monday 21 April.
Team Management Reports are due one last time: Monday 21 April.

Week 14 (7-11 Apr 2008)

Only 2 more weeks left!
VVR and Stage 3 Release Due This Friday (11 April 2008)
If you have a sponsor, then a formal presentation to the sponsor is required by this Friday (11 April); please send me a pdf of the presentation.
Each team must submit to me its request for a location in the Demo Day lab layout by Monday next week (14 April)
Each team must create a description of their project for the Demo Day brochure
Put a link to your team's brochure info at the top level in your web page by Monday (April 14)
Take a look at last year's Demo Day brochure
Remember that when you get an evaluation and feedback on something (WMR, document, etc.), you may update it for a regrade.
Individual logs must be updated at least once a week (bad log keeping will influence individual grades).
Team Management Reports must be posted weekly.

Week 13 (31 Mar - 4 Apr 2008)

Only 3 more weeks left!
VVR and Stage 2 Release Due This Friday (4 April 2008)
Remember that when you get an evaluation and feedback on something (WMR, document, etc.), you may update it for a regrade.
Individual logs must be updated at least once a week (bad log keeping will influence individual grades).
Team Management Reports must be posted weekly.

Week 12 (24-28 Mar 2008)

Only 4 more weeks left!
Each team needs to address issues raised with VVP, VVR and Stage 1 Release
Remember that when you get an evaluation and feedback on something (WMR, document, etc.), you may update it for a regrade.
Individual logs must be updated at least once a week (bad log keeping will influence individual grades).
Team Management Reports must be posted weekly.

Week 11 (17-21 Mar 2008)

SPRING BREAK!

Week 10 (10-14 mar 2008)

For information on Stage 1 Release, see Chapter 16 in the Recommended Text (Software Project Survival Guide)
VVR and Stage 1 Release Due this Friday!
Next Week is Spring Break: Have Fun!
Only 4 more weeks after Spring Break

Remember that when you get an evaluation and feedback on something (WMR, document, etc.), you may update it for a regrade.
Individual logs must be updated at least once a week (bad log keeping will influence individual grades).
Team Management Reports must be posted weekly.

Week 9 (3-7 Mar 2008)

Please note, that as I described the first week of class, you are expected to put in 8-10 hours per week on this course, and that should be reflected in your individual logs.

Remember that when you get an evaluation and feedback on something (WMR, document, etc.), you may update it for a regrade.
Individual logs must be updated at least once a week (bad log keeping will influence individual grades).
Team Management Reports must be posted weekly.

Week 8 (25-29 Feb 2008)

Remember that when you get an evaluation and feedback on something (WMR, document, etc.), you may update it for a regrade.
Individual logs must be updated at least once a week (bad log keeping will influence individual grades).
Team Management Reports must be posted weekly.

Week 7 (18-22 Feb 2008)

The VVP-info file has been added to the CS4500 guidelines directory.
The VVP 1 is due 22 Feb 2008.
Remember that when you get an evaluation and feedback on something (WMR, document, etc.), you may update it for a regrade.
Individual logs must be updated at least once a week (bad log keeping will influence individual grades).
Team Management Reports must be posted weekly.

Week 6 (11-15 Feb 2008)

Here's what's expected filled out in the SDS version 2:

> 3. Detailed description of components
>
> NOTE: This section is the main focus in version 2.0 of the
> SDS, the detailed design. This section will provide most of the basis
> for implementing the product.

If you delivered exactly what's requested, it would be possible to hand it to some other development team wo implement the system. What I am looking for is that your team has a deep enough design to get a Stage 1 release by the first week of March.
Remember that when you get an evaluation and feedback on something (WMR, document, etc.), you may update it for a regrade.
Individual logs must be updated at least once a week (bad log keeping will influence individual grades).
Team Management Reports must be posted weekly.

Week 5: No Announcements

Week 4

The Project Plan is due Thursday 31 Jan. Do not email it to me! Please put it on your project web page.
The SRS is due Tuesday 5 Feb (next week). It should also be placed on your project web page.
Individual logs must be updated at least once a week (bad log keeping will influence individual grades).
Team Management Reports must be posted weekly.

Week 3

Blue indicates new as of 26 Jan 2008:

I have sent ratings of the WMRs out to all teams; I will re-grade them if you update them by the end of the weekend and let me know.

Red indicates new as of 23 Jan 2008:

Each team needs to put a description of their project on the web page.
There is a revised version of the Weekly Management Report; each team needs to redo their WMR to adhere to this.
The Needs section of the WMR should describe things needed from TCH or the sponsor.

All teams should have their project assigment; please reference it on your project web page.
All team projects' URL is now on this webpage (see below)
Individual logs must be updated at least once a week.
Team Management Reports must be submitted weekly.
Project Plan is due soon; let me know if there are questions.
The project SDS is required in a couple of weeks; start working on that as well.

Week 2

Grades given on Bids/Web Pages
Teams must have their webpage up and running with:

Team Name
Team Members Names
Weekly Reports
Individual Logs
Deliverables

Bids
Others (e.g., start Project Plan)

There should be something in personal logs
Individual Grades affected by subscription to cs4500 mailing list

Week 1

Teams must be formed by the end of the first class (8 Jan 2008)
Subscribe to cs4500 by Friday (11 Jan 2008).
Send the name of the team and team members to tch by Wednesday (9 Jan).
Attendance required in class all Week 1 (8,10 Jan).
Bids for projects are due by 11 Jan 2008 (midnight).

New (9 Jan 2008):

Some new external projects will be presented in class Thursday by Erik Brunvand and Jay Lepreau - both SoC faculty members.

Overview of Course / Links

Course Objectives

Engineer (n): a designer or builder of engines
Engineer (vt): to lay out, construct, or manage as an engineer
Engineering (n): the art of managing engines

This course is the senior software engineering lab course. According to the CS department class catalog this course involves:

Development of significant software systems by small student groups, with emphasis on applying sound, disciplined software engineering practice.

Because of the prerequisites for the course, we assume that you have had lots of opportunities to learn sound, disciplined software engineering practice. Now here's your chance to show off a little on a significant project. Show us what you can do!

Instructor

· Thomas C. Henderson, Professor

· E-Mail: tch@cs.utah.edu

· Phone: 801-581-3601

· Fax: 801-581-5843

· Office Hours: By appointment 3450 MEB (arrange by email).

· TA: None

· Recommended (Not Required) Book for class: Software Project Survival Guide, McConnell
You can contact me with questions by email at: teach-cs4500@cs
Subscribe! to the class mailing list: cs4500@cs

Prerequisites

The prerequisite is successful completion of CS 3500.

Course Description

This offering of the course will be structured in terms of deliverables.

Teams

Teams must have 3 or 4 members and must be formed by the end of class (8 Jan 2008).

Bids

Each team must submit 2 or 3 bids on projects by 11 Jan 2008.

Possible Projects

There are 3 possible types of projects:

Industry Sponsored: Descriptions given by local companies who act as clients (see project descriptions in industry); any team working on a project in cooperation with an external sponsor (other professor, company, etc.) must follow the guidelines for an industrial project.
Internally Sponsored: Prof. Henderson proposes a map analysis system (see internal)
Self Sponsored: A team may propose a project; this will require approval, and Prof. Henderson will act as client.

Meetings

Once teams are formed, and projects are picked, the rest of the course will be largely lecture-free. Instead, each group will meet whenever requested to meet by Professor Henderson, or after requesting a meeting and arranging a meeting time. Attendance at these update meetings will be mandatory.

Each team must turn in a Weekly Management Report by Monday noon each week; this is done by posting it on the team web page.

Deliverables

In addition to the update meetings, you will be required to maintain and make available the following deliverables during the semester (details on formats of documents, etc. can be found in Guidelines link above):

Bids on 2 or 3 projects
Individual Logs detailing work on project
Project Plan
Software Requirements Specification
Software Design Specification (2 versions: v1: high-level design and v2: detailed design)
Verification and Validation Planning
Verification and Validation Results
Staged Releases
Product Release
Final Report
Legacy Turn-In Materials

Note that you must deliver reports in a format that I approve. One specific document deliverables and formats can be found at formats for this class - they are based on a class at the University of Texas. You are not to follow these formats blindly; you must tailor them to your specific project needs (however, you must be able to defend your deliverables and modify them upon request). If you would like to use another software development methodology (e.g., agile programming, etc.), you must arrange a meeting to discuss the details and get approval.

Software Used to Support Class

Students can use whatever platform they like to develop their projects. A UNIX environment is available in the CADE lab, and an NT environment is available in the NT lab. Your choice of platform and development environment should be justified in your group meetings.

Assignments

Each team will be assigned a project, hopefully from their ordered list of preferences. Each of the sponsors will present their projects on the first day of class to help you choose your preferences. The schedule for assignments is as follows:

Date	Particularly Appropriate Reading	Assignments	Assignments Due
		Team meeting with prof every 2 weeks
Week 1: Jan 8-10	Chapters 1-4, 18	(1) Form team (2) Make bids (3) Start logs (4) Create project website	(1) Team formed (2) Bids submitted (11 Jan by midnight)
Week 2: Jan 15-17	Chapters 5-7	(1) Project Plan (2) SRS	(1) Updates to logs
Week 3: Jan 22-24	Chapters 8-9	(1) SDS (both versions) (2) VVP	(1) Project Plan (Thursday 31 Jan)
Week 4: Jan 29-31	Chapters 10-13
Week 5: Feb 5-7	Chapters 14-18	(1) VVR (2) Stage 1 Release	(1) (logs updates) (2) SRS, v1 (Tuesday 5 Feb) (3) SDS, v1 (Friday 8 Feb)
Week 6: Feb 12-14			(1) SDS, v2 (Friday 15 Feb)
Week 7: Feb 19-21			(1) VVP (Friday 22 Feb)
Week 8: Feb 26-28			(logs updates)
Week 9: Mar 4-6
Week 10: Mar 11-13		(1) VVR (2) Stage 2 Release	(1) VVR (2) Stage 1 Release (Friday 14 March (logs updates)
Week 11: Mar 18-20		Have fun!
Week 12: Mar 25-27			(logs updates)
Week 13: Apr 1-3		(1) VVR (3) Stage 3 Release	(1) VVR (2) Stage 2 Release (Friday 4 April) (logs updates)
Week 14: Apr 8-10		(1) Product Release	(1) VVR (3) Stage 3 Release (3) Formal Presentation to Industry Sponsor (Friday 11 April)
Week 15: Apr 15-17		(1) Final Report (2) Demo	(1) Product Release (Friday 18 April)
Week 16: Apr 22			(1) Final Report (2) Demo (Thursday, 24 April)
24 April 2005			Demo Day 9-noon WEB 130

Grade

Bi-Weekly Meetings, Logs	10%
Documents	30%
Project Web Page	20%
Final Project & Demo	40%

Grades will be based on these percentages except for the following:

If a deliverable is missing, that will cause drop in class grade by one letter grade (i.e., grade for class on all work - 1 letter grade)
For each deliverable, there will be 2 fixit rounds allowed; i.e., if I ask for a modification, you can make them and still get an A.
Individuals logs will be counted toward their grade only - not the group.