| ID | Task Name | Start | Finish | Notes |
|---|
| 1 | Project Proposal | Mon 9/22/03 | Fri 10/10/03 | A project proposal contains the following pieces of information (if applicable): Project title, High level description/abstract (What the system/project will do), Customer information (contact, location, etc.), Team profile (Skills, names, cognates, why
each member cares about the project, etc.), Benefit statement (What good
things will happen, or what bad things won't happen), Draft project plan (What
model you'll try and follow, rough schedule) |
| 2 | Team Formation | Mon 9/22/03 | Fri 10/24/03 | Even if you have not proposed a project yet, you could form a team. |
| 3 | Project Selection | Mon 9/29/03 | Fri 10/24/03 | We (the course instructors) will evaluate and determine the best/most appropriate projects. You may be asked to attend a meeting about this to help us decide. |
| 4 | Requirements Analysis | Mon 9/29/03 | Fri 12/5/03 |
The requirements analysis expands upon the proposal and identifies: features
of the proposed system, priorities for the functionalities that are required,
existing state of things to demonstrate your depth of knowledge, validation
plan for determining whether you've accomplished the goals of the project,
prototypes/sketches used to elicit the requirements, project plan - you know
more, so it should be more detailed |
| 5 | Design | Mon 11/17/03 | Fri 1/30/04 |
The design seeks to map out what you will actually construct. This may vary
based on project types, but the level of detail for your design should aim at
making the implementation an unambiguous process. Also, you end up identifying
everything that needs to be built in this stage, so your project plan should
reflect a detailed work-breakdown-structure that identifies who will do what
by when. |
| 6 | Implementation | Mon 12/1/03 | Fri 4/9/04 | The goal here is to be building the system, whatever it is. |
| 7 | Validation | Mon 3/1/04 | Fri 4/16/04 | This might be system testing, or user testing of your system. Again, you'll want to build it into the plan. |
| 8 | Documentation | Mon 2/23/04 | Fri 4/23/04 | Not every system will have documentation required, but if it does this is when the work typically occurs. The documentation may be for other developers, not for users. This may be online help, or a formal document, depending on the type of project you
are doing. |
| 9 | Delivery | Mon 3/29/04 | Fri 4/23/04 | You want to finish your project in this timeframe. To satisfy the course requirements you will need to demonstrate it to the instructors, even if it is not complete at the time of the demonstration. You will need to provide two written documents.
The first is a two page abstract that describes your project to an uninformed
person. Think of it as something we would post on the website for customers,
parents, and future classes. The second is a longer version of the abstract
that provides more details about the project, including team/process issues. |
| 10 | Capstone Fair | Mon 4/26/04 | Fri 4/30/04 |
We will have a day (or days) that you will present your project in an open
environment in the building. Most likely this will take shape as a kind of
science fair with posters, etc. We'll encourage other faculty to visit,
business leaders, maybe even your parents - who knows. |
|