Book a Demo

Author Topic: requirement coverage  (Read 14409 times)

rdekleijn

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
requirement coverage
« on: January 10, 2010, 10:47:14 pm »
Hi all,

In my view you cover the requirements with a use case.
Can somebody give a detailed explanation on how I can relate requirements to an use case?

I just have sparx (Desktop edition) 7.5.850

I look forward to a reply.
Regards,
Roy

son-of-sargasso

  • EA User
  • **
  • Posts: 122
  • Karma: +0/-0
    • View Profile
Re: requirement coverage
« Reply #1 on: January 10, 2010, 11:54:52 pm »
There is really, really, really a lot of information on this. So much that I guess you'd be best off by using the Search the Forum box, just up there.

Or if that's just too hard, then, I guess, well, what can I say, oh well .... RTFM.

zzzzzzzzzzzz
b

mod: Oh, by the way welcome to the EA universe, but please try the normal avenues before resorting to the banal.
« Last Edit: January 10, 2010, 11:57:21 pm by barrydrive »

rdekleijn

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: requirement coverage
« Reply #2 on: January 11, 2010, 12:01:07 am »
Maybe you can give me a brief explanation or link where I can find this information.


QUESTION: is it true that you have to create requirements from a use case diagram? (creating internal requirement?) Why isn't this the other way around?

OR,

Do I have to create a Traceability diagram?


Regards,
Roy
« Last Edit: January 11, 2010, 03:18:06 am by rdekleijn »

RoyC

  • EA Administrator
  • EA Practitioner
  • *****
  • Posts: 1297
  • Karma: +21/-4
  • Read The Help!
    • View Profile
Re: requirement coverage
« Reply #3 on: January 11, 2010, 09:25:13 am »
There is a Help manual integrated with EA. To open it, select the Help | Help Contents menu option.

Alternatively, look at the UML Tool Guide on the Sparx Systems website (which is effectively the same Help accessed through a different channel). Start here: http://www.sparxsystems.com/uml_tool_guide/index.html

In either case, look at the Start UML Modeling section for an overview of how you build a model. Then look up Use Cases, Requirements, Use Case Diagrams, Requirements Diagrams and Traceability in the index.

For your specific questions:

You can create Use Cases and, in the course of doing that derive the various types of requirement. Or, you can get lists of requirements from the user groups, project sponsors and so on, record them in EA and then design Use Cases to realize those requirements. There is a lot of discussion about these processes on the forum, so search for the key words and see what the arguments are.

You generally link a Use Case element and a Requirement element using a Realize connector, but that would depend on how you were setting up your model. No, you do not HAVE to create a Traceability diagram - it is, however, good model management to structure your model and create Traceability diagrams in such as way as to quickly show how the model is developing, or should develop.

No, you do not create requirements from a Use Case diagram. Internal requirements are actually the responsibilities of the entity represented by the element, and do not usually define the information represented by a Requirement element. However, sometimes the two overlap, and you might decide that an internal responsibility actually covers something common to several elements, in which case you can convert it to an external Requirement element.

As bruce suggests, you probably need to do some reading to put these points into perspective, but after that feel free to ask more questions. bruce himself has been known to be extremely helpful, in between spraying his fruit trees (I just hope, bruce, that the searing heat has left you with fruit trees to spray. Some of my trees have gone.)
Best Regards, Roy

marcelloh

  • EA User
  • **
  • Posts: 192
  • Karma: +0/-0
    • View Profile
Re: requirement coverage
« Reply #4 on: January 18, 2010, 05:57:57 pm »
A quick way to link requirements to use cases:
alt-v x
That will bring up the relationship matrix.
sources: your req's
type: all
link type: realisation
target: your use cases
type: use cases
direction: target->source
(you can save this as a standard profile on the right)

You can see on this matrix which req is linked to which UC.
If you want another link (or delete one), rightclick... and Voila  ;)

The drag & drop thing for adding requirements to various UC's is quite unhandy (in my opinion). When you drop stuff, you can't see that you succeed. Let's say you have a phone call in between..., you don't know where you stayed in the dag&drop process. So the matrix is for me the way to go, and the way I teach EA overhere ;-)