It's all about the answers!

Ask a question

How to create use cases in Rational Requirements Composer?

Edward Close (111) | asked Nov 14 '12, 1:02 p.m.

Can someone direct me to where I can find information on how to create use cases in Rational Requirements Composer?

I am currently evaluating this tool and cannot find a way to do this and it is a critical requirement.

I need the ability to create use cases with the typical use case fields (name, id, overview, actors, preconditions, post conditions, trigger, extensions, alternate paths). Also need the ability to import use cases. Not sure if that is possible yet.

3 answers

permanent link
Daniel Moul (4.9k1318) | answered Nov 14 '12, 3:34 p.m.
  1. First, you need to have an Analyst license assigned to your user ID and author/analyst role in the project. 
  2. Then (assuming you are talking about textual use cases) your project needs an artifact type defined called "Use Case Description" (or whatever you want to call it) with format = text 
  3. Then create an artifact of type Use Case Description and add the headings and default attribute values you care about.  Save it as a template.
  4. Then create a new Use Case description and apply the template when creating it.

If you want use case diagram as well, then you need another artifact type with format = use case diagram

You need project administrator role to do most of the above.

The simplest way to experience this is to use the Money That Matters sample project, which has some example use case artifacts defined, and more can easily be created.  Alternatively, you can create a new project and select the use case driven development template (I don't remember the exact project template name; if you don't see that in the list, choose "traditional development").

Note that there are three levels of granularity you can use. The "right" one depends on your methodology: at what level do you want to manage the use cases (i.e. have attributes, link to tests, development implementation tasks, etc)?
  1. Whole use case is one document (the simplest to implement and the one described above)
  2. Each flow is a separate requirement artifact, and they are embedded in another artifact which provides the combined view (this approach makes it easy to assign one flow to a test case or implementation task)
  3. Each paragraph is a separately managed artifact (typically organized in a module; this is new in 4.0.1)

You can import use cases in Word, RTF, or OpenDocument Text formats.  You can import and leave them in their native format, or you can convert each one to native RRC text as one artifact, or you can parse them into pieces automatically as you import them.

permanent link
Bruce Korn (1912) | answered Dec 11 '12, 2:38 p.m.
Also, for general and specific information about creating use cases, please see the following help topic

"Defining use cases"  at:

Bruce Korn

permanent link
M Kevin McHugh (1557) | answered Dec 31 '12, 5:34 p.m.
What if the team wants to constrain any Use Case requirement type to that format?  Is there a way to limit or at least default a requirement type to a particular artifact template?

Your answer

Register or to post your answer.