Requirements definition techniques: workflow

Use the requirements definitions techniques in Rational® Requirements Composer to support your development process. This topic presents a workflow that uses the techniques in a sequence: begin with business objectives and build on those by using the descriptive capabilities of the tool set to define requirements through the development of supporting artifacts.

Figure 1 demonstrates how you can apply these requirements definition techniques in the context of a development process. Although there is a flow in developing artifacts, as shown by the numbers in the figure, you can elaborate and describe any of the artifacts in documents at any point in the development process. You can then create requirements directly from selected text in documents. You can modify the sequence to meet the needs of your project and organization. The use of a glossary and terms is not shown, but should be included in your process to support common terminology in your project.

Figure 1. Requirements definition in a business context. Click on any box for more information.
The
image shows the flow of process from identification of business objectives
to business processes, use cases, user interface sketches, screen
flows, and storyboards. All can be referenced and elaborated with
textual documents. Requirements are derived from content within documents. Click this area to get information about uploading artifacts to a repository Click this area to get information about defining business processes Click this area to get information about defining use cases Click this area to get information about sketching the user interface Click this area to get information about creating documents Click this area to get information about creating requirements

Feedback