Detail Use Cases and Scenarios
Elaborate on the use cases that have been identified and outlined by detailing the basic and alternative flow steps in
the rich text artifact that has been created in RRC. Use Cases will be elaborated at varying levels of detail
throughout the project lifecycle. One way to determine the order which Use Cases flows should be detailed is to review
associated links, comments, and attribute values in RRC to determine priority.
Update Use Case Model
Throughout the use case elaboration process, continue to refine the use case diagram and the relationship between
multiple use cases and actors. You may identify a very complex use case that is better represented by being split into
two use cases, or perhaps realize that a use case identified previously is better addressed as a flow in another use
case. RRC provides the capabilities to communicate and collaborate on these decisions throughout the project lifecycle
by using the linking and discussion features of the tool. See Working with
comments and Working with links
Capture domain terms
Identify important business terminology as you are detailing the Use Case and link to the project glossary. In RRC,
terms can contain links to new and existing artifacts, related terms, and synonyms. Project team members can continue
to refine the glossary, add comments, and assign attributes to promote consistently throughout the different
requirements artifacts. See Managing terminology and glossaries
Achieve concurrence
Collaborate with the team to finalize the detailed requirements and storyboards and ensure consistency across the
project by adding comments and replies to documents and artifacts in RRC. See Working with comments
Once concurrence is reached and requirements are ready to be formalized, marked requirements can be exported to
RequisitePro for management and traceability. See Managing Requirements with
RequisitePro
|