Topics covered in this module:
Objective: To demonstrate how to use RequisitePro outlines to create requirements documents and to create requirements in those documents.
This module shows you how to use RequisitePro to document your requirements. Before you do that, however, you typically will have spent some time and energy in defining the problem you expect your project to solve, determining its causes, and identifying the features of a solution. These activities involve getting input from a variety of stakeholders (people who are affected by or have an interest in the project). You can do that by running workshops, conducting interviews, distributing questionnaires, and prototyping.
Using these techniques, you should be able to determine the project requirements as well as the attributes of those requirements, such as importance to customer, difficulty, risk, and stability.
By the time you are ready to document your requirements, you should have a statement that (a) identifies the problem and who is affected by it, (b) defines the impact of it, and (c) explains what would constitute a solution.
(For more information about a process you can follow when you start a project that will involve managing requirements, click here.)