The Cycle 1 analysis document should contain the following items:
- Title page, including project name, team designation, and names of team members.
- Table of contents.
- Project (Cycle 1 and Cycle 2) requirements:
- Include any additions or clarifications elicited from the client.
- Include any optional requirements that you plan to attempt.
- Consider all of the categories outlined in the text and use a format similar to
those used in the
Software Development Lab.
- Use cases:
- High-level use cases for Cycle 2 requirements.
- Expanded essential use cases for Cycle 1 requirements.
- Include use case diagrams in your CASE Tool model and use case text in Microsoft Word.
- Domain model:
- Include concepts, attributes, and associations.
- Document in one or more UML class diagrams drawn using a CASE tool.
- System behavior:
- System sequence diagrams (CASE Tool), with use case references or text.
- Contracts for system operations (e.g., Word).
- Glossary of terms:
- Similar in concept to that described in 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", dated, and explained 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 Cycle 1
of the project.) Include summary
totals by team member, by phase, and for the entire project.
- Copies of the time tracking sheets (or other form of recording) of all
team members.
- Your CASE tool model file.