CS-489 Phase 1 Analysis Report
The phase 1 analysis document should contain the following items:
- Title page, including project name, team number, and names of team members.
- Table of contents.
- Project (phase 1 and phase 2) requirements:
- Include any additions or clarifications elicited from the client.
- Include any optional requirements that you plan to attempt.
- Use a format similar to that of Chapter 5 in the textbook.
- Use cases:
- High-level use cases for project (phase 1 and phase 2) requirements.
- Expanded essential use cases for phase 1 requirements.
- Include use case diagrams in your Rose model and use case text in Microsoft Word.
- Conceptual model:
- Include concepts, attributes, and associations.
- Document in one or more Rose class diagrams.
- System behavior:
- System sequence diagrams (Rose), with use case references or text.
- Contracts for system operations (Word).
- Glossary of terms:
- Similar in concept to that described in Chapter 12 of the textbook, though you may use
any reasonable format.
- This glossary should be expanded and updated throughout the project.
- Issue list:
- A list of questions to be asked, decisions to be made, topics to be investigated, etc.
- This list is to be maintained throughout the project; items should be marked
"complete" when they are resolved, but not removed from the list.
- Project management information (see process details):
- Time spent on the project to date, by team member and phase. (It is likely that all the
effort to date will be in the "planning" phase of phase 1 of the project; sorry
about the duplicate meaning of "phase".)
- Copies of the time tracking sheets (or other form of recording) of all team members.
This page was last updated on September 23, 1998. Send comments to Mark Sebern.