ECE 452 - Introduction to Software Engineering

Spring 2002

Project Overview

• Project Overview:
  The objective of the course project is to apply software engineering techniques presented in the lectures to the design and implementation of a web-based 3-tier (client, server, database) software system. The projects will span all stages of the software process and will be worked on by teams of 5 students. The project grade will be based on intermediate progress reports, a final project report, and intermediate and final project presentation.

• Project Proposal:
  A project proposal (1 page) must be submitted by each team on 02/05. The proposal should clearly outline the scope of the project, and should list the members of the team, assignment of team members to each of the 3 tiers of the software system, and a team leader who will serve as the spoke-person/contact-person.

• Time Log:
  Each team member is required to maintain a log of time spent on project work. The log should be broken up into categories; e.g. time spent reading the textbook or articles, time spent in meeting, time spent devising specifications, etc. A summary of individual time logs must be submitted with each project report. Project reports will not be graded without time logs from each team member.

• Project Web Page:
  Each team should maintain a web page that contains a describtion of the project, the development schedule, current status as well as links to the documents submitted during the course.

• Project Reports & Presentations:
  Three reports will be required - a tentative schedule is listed below. Details of what is expected in each report will be presented in class.

  A short project presentation (in addition to the demonstration) will be required for each deliverable. This presentation may be given by a single member of the team or by the entire team (tag presentation). The objective of the presentation is to introduce the system to potential customers.

  Further details about the final project report and presentation will be given in class.

• Project Submissions Schedule (tentative):
  
  1. 02/05 - Project Proposal
  2. 02/26 - Project Statement (Problem definition, Plan & Schedule, Intermediate & Final Deliverables)
  3. 04/02 - Intermediate Project Deliverable (Analysis, Design, Testing)
  4. 05/03 - Final Project Deliverable (Analysis, Design, Testing)

• Project Assessment:
  The project will account for 50% of you final grade. Your grade will be based on the quality of work produced, not on the time spent (use your energy wisely). About 50% (of the 50%) will be depend on how the team functioned as a group. It is very important that project reports be submitted on time (to enable the project to stay on schedule and to give me time to evaluate your work). Late work will be penalized.

• Notes on Documentation:
  Although project reports will not be directly graded on writing style, organizing your thoughts and writing clearly will enable me to get more out of your reports. It is important that each report have only one editor even though it will contain contributions from all the team members. Also, each team member must edit at least one report. The responsibility of the editor include turning in the final document, setting deadlines for individual submissions, and incorporating individual submissions into a single coherent and complete document.