Requirements modeling and analysis 1. This deliverable is a requirements analysis report. For both this deliverable and the later ones in the project, there will be two major parts: a product plus a quality assurance part. The QA part describes your analysis of the product to ensure validity.
(Due date: Thursday, 10/21/99)2. The product part of the report should contain the following:
a) List of requirements objects produced by a FAST review with the customer. Include in addition to the objects: the services they provide, constraints such as cost, and prose minispecs for the associated subsystems.
b) requirements models. You can include as many different kinds as you like, but you must include:
Other possibilities include: decision tables, data flow diagrams, etc.
- Requirements data dictionary.
- CRC tables, class trees, scenarios, event trace tables, object state diagrams.
3. Validation
a) Walkthrough. Have one team member walkthrough typical scenarios for the system in front of the rest if the group, including the customer. The walkthrough describes how the objects in the system are used to support the required capabilities. If different team members are responsible for different parts, they can each do their own part.
b) Check your different models for completeness and consistency
c) Design high level user oriented tests that you will use to convince the customer that the system has the desired functionality
d) Prepare defect reports to describe each of the problems you found during QA.