CS3733-D05 Project

The course project constitutes a significant portion of your grade. This page contains the information, often via links to other pages, you need for your project and any other helpful information I can think of. Please Let me know if you find an error or omission, or if you have a suggestion for improvement.

General Description

You are going to implement a computer system to manage a parking facility. This facility contains new, revolutionary technology as described to you by Russell Customer at the March 18 class meeting. Russell's description is your starting point. There is much more to do than you might be able to implement in a seven-week course. However, it is your responsibility to manage the scope of the project so that you deliver high-quality working software in the time allocated. You need to work with Russell, Professor Pollice, and other stakeholders to prioritize the requirements and features that will go into your system. Mr. Draco, the vice-president of software says "if you build it, it had better work."

You can meet all of the project stakeholders by viewing the stakeholders' page.

Your team's assignment

Mr. Draco assigned Gonzo the task of creating an initial breakdown of the system. You saw this in class. Gonzo is responsible for the overall architecture, design and implementation of the components or parts of components that interface with the specialized hardware system, and provide technical expertise to the team.

Artifacts

You will produce several artifacts for the project. Some will be required by the instructor, some will be required by the development process your team chooses to adopt. There are three types of artifacts:

Code artifacts. This is the source code, object code, and any other code-like artifact you produce to implement components.
Process artifacts. These artifacts are non-code artifacts that enable someone to understand what you are building, how you are building it, the status of your project, and so on.
Your project log or diary. This should be a document that identifies the project team's decisions, problems, solutions, and other information that will help the project staff understand what you problems you are encountering, the work that is done, and

Source Code from Gonzo

The latest source code from Gonzo is in this file.

User stories

Russell's user stories can be found here. These are the user stories that are available to all teams. Each team may have other interactions with Russell that they are responsible for documenting in their project space on SourceForge.

Project Presentation

Project presentations should be 30 minute presentations based upon the template provided. You should add as much as you need, but make sure you address all of the areas identified in the template. Each team member should participate in delivering the presentation.

Modified: 22-Mar-2005 3
Gary Pollice