Date dues: RUP1 - Wednesday, February 11, 2004; RUP2 -Wednesday, March 24, 2004; RUP3 - Friday, April 30, 2004 at 11:59pm
Follow the general homework directions. Make sure you cite all your references and contacts.
What to turn in
All artifacts of this phase of the Rational Unified Process including, but not limited to:
- The following documents must be combined into a RUP Phase X Report
(where X is replaced by the current phase number), including a brief
introduction/overview of the report. Each document will be a section in
the RUP Phase X Report.
- Include a brief description of the contributions of each member
- Requirements Analysis Document
- System Design Document
- Object Design Document
- Software Review Document
- Software Test Document
- Code Section
- This section will include all the code needed to generate the system
- The following items will be turned in on a CD.
- All Rose artifacts in original electronic format. (Just copy the appropriate Rose files and directories.)
- All code and makefiles. This is to allow recompilation of the executable.
- Executables and all necessary supporting installation components. This should be something I can easily install on my machine for testing.
- Other things you may consider turning in if they are appropriate to a particular phase of the project may include: user manuals, help files, user evaluations of the software, amongst other artifacts you consider important.
Class presentation
You will give an oral management presentation on your project after each RUP phase. This will be on the day the report is due, except for phase three when the report will be given on Wednesday, April 28, 2004. The report is to be 10 minutes long. Note: I WILL make you stop at the end of your time. Your presentation should have two components of approximately equal importance:
- Client-centered: Think of this part as a presentation to your client.
Talk about
- the business problem you are solving
- how your project will appear in use to solve the problem
- benefits to the business - how have you helped
- Process-centered: Think of this part as a presentation to the head
of the software development firm (your hypothetical employer). Talk about
- the development process you went through
- project rationale - why did you do what you did
- lessons learned
You may talk a little about the technologies you used if you wish, but the client probably does not care HOW you worked your magic. The head of your company probably does not care about the details of the technology either, unless there are lessons there that can improve productivity on future projects.
Peer Evaluation Form
The Peer Evaluation Form is due at the same time the RUP Phase Report is due, download it, fill it out, and turn it in.
Criteria for the group project evaluation:
- A report that meets expectations will receive a B. A 'B' report will be a good report that documents all the necessary information about the this RUP phase. The other artifacts will also be good. An 'A' project must be excellent and exceed expectations in all aspects. I will grade each section of the report and other software artifacts. Note: simply filling out every section of every report is not what I am looking for. A shorter high quality report will fair better than a longer low quality report.
- Since the emphasis of the RUP process evolves with each phase, it is not
reasonable to give each section of the document equal weighting during each
phase. Also, different projects will progress further into the RUP process
depending on their size and complexity. To honor the organic nature of the
RUP process, I will adjust the percentage weight of each component of the
project based on my evaluation of where you are in the larger RUP evolution.
- Brief description of the contributions of each member (2%)
- Requirements Analysis (RUP1: 40-50%, RUP2: 15-25%, RUP3: 0-10%)
- System Design Document (RUP1: 5-15%, RUP2: 20-30%, RUP3: 15-25%)
- Object Design Document (RUP1: 5-10%, RUP2: 15-25%, RUP3: 15-25%)
- Software Review Document (15%)
- Software Test Document (RUP1: 0-10%, RUP2: 0-10%, RUP3: 0-10%)
- Code, makefiles, executables, prototypes (RUP1: 0-10%, RUP2: 10-20%, RUP3: 25-35%)
- Rose artifacts (3%)
- Some criteria I will use include:
- Clear understanding of the RUP process
- Continuation and smoothness of transition from Requirements to Analysis to Design to Coding
- Effectiveness of using ROSE including code generation/reverse engineering
- General quality of the work, including Use-Case View, Logic View, Component View
- Completeness of the work - are all necessary issues addressed?
- General quality of report
- Cohesion of teamwork