Requirements Tree Diagram is based on certain finite rules. There rules form a road map to the Requirements Tree Diagram. The rules are as follows:
- A Generic Requirement can be split into a Specific Requirements. Generic Requirement can be abstract in nature whereas Specific Requirement must be concrete one.
- Requirements are related to each other. There cannot be any requirement in isolation which is not related with at least a single another requirement. Following relationships may exist between requirements:
- Generalization
- Composition
- Pre-Condition
- Includes Relationship
- Extends Relationship
- Requirements can be associated with external entities called as Actors. For simplicity, requirements can also be associated with other classifiers in the system.
- Each Requirement must have
- Some input
- Action to be taken on input i.e. processing logic
- Desired Output.
- Relationships/properties of a higher level requirement in hierarchy are by default applicable to lower level requirements and to deviate from them, the same has to be explicitly indicated for the lower level requirement.
No comments:
Post a Comment