Project Overview
The project is the main driving force of
this class. You will follow the Rational Unified Process (RUP) software
lifecyle, use the object-oriented design process as outlined in the text,
and use Rational Rose CASE tools to design and prototype a significant
software product of interest to you. We will go through the RUP three
times.
Milestones
Milestones
Due dates: see calendar
- Iteration 1 through RUP: January 14 - February 11, 2004
- Iteration 2 through RUP: February 11 - March 24, 2004
- Iteration 3 through RUP: March 24 - May 5, 2004
- Milestones within each RUP (each will be emphasized more or less
with each iteration)
- Project Startup and Plan
- Weekly status reports
- Team meeting with Dr. Povinelli.
- Requirements Analysis
- Design
- Software Review
- Software Prototype and presentation
- Peer Evaluation Form
Good projects?
Your project must design and develop a significant piece of software. A good project
- Gives you the opportunity to demonstrate object-oriented design tools and techniques. Scan through the text right away to see what you will be doing, and select a project to which those techniques apply
- Is interesting to you. Don't consciously choose a boring project.
- Is real. Don't make up something. Consider a project that might have commercial or shareware potential.
- Has a sponsor. You may not have as much content knowledge as you might think. Look for a real client, a local firm, a local nonprofit organization, or a faculty member with whom you can work.
- Looks good on your resume. You will want to show copies of project deliverables at an interview, and you may want Dr. Povinelli to write a letter of reference discussing your project work.
A good project is probably not
- related to another class or your Senior Design project
- a static set of web pages
- a game
- too small
- too large
I hope you have better ideas, but here are a few of mine:
|
|