Types of demand in RequisitPro
There are four different types of requirements in RequisitPro:
l Features and vision describes the characteristics and prospects of the product
l Stakeholder Requests Requaried demand refers to the information collected from the system-related participants, it is not necessarily a need, which can be the material or a record of the seminar.
l Supplements Requirements Target Systems must meet operating conditions and compatibility, performance, etc.
l Use Cases use examples describe a series of operations performed by the system, as well as the traffic, conditions, and special needs involved in these operations.
General steps for managing demand
1. Collection of materials in the meeting site, the user survey process, summarize it in the Stakeholder Requests.
2. Correct the target system involved in the professional terms and vocabulary to form the glossary of the demand instructions (Glossary).
3. Analyze the original demand materials of the user, which can be directly lit and created as Stakeholder Request directly in the documentation for some parts that are considered to be demand.
4. Determine the characteristics of the target system, describe the foreground of the target system, similarly, you can create a series of Feature Request directly in the foreground document.
5. After business analysis [1], determine the use case of the target system, and write detailed use case regions.
6. From the original needs and preliminary analysis, identify the specific requirements that cannot be included in a certain USE-CASE requirement.
7. (Optional) When you create a StakeHolder Request or Feature Request, you can build a demand relationship between demands by specifying a Parent Request, creating a demand system for a tree.
8. Use the tracking Matrix to determine the transfer relationship between StackHolder Request -> Feature Requests -> Use Castes.
9. However, when the demand changes, use IMPAct Analysis, through the above tracking matrix, the change is analyzed.
