Link between project requirements and use case diagrams

[MatthiasVDE]

I'm busy with the setup of a repository in order to generate documentation.

For each project we have a separate project package. The starting point are requirements. We have a package called 'Requirements', with underneath four child packages (Functional Requirements, Non-Functional Requirements, Architectural Requirements and Security Requirements). In each of that packages there's a requirement diagram and a sub package with the requirement elements.

Each project can have multiple use case diagrams, so my question is: what's the best practice to link those requirements to de use case diagrams? Or better, how can I link my 'project' to the requirements and the use case diagrams? What's the best starting point to generate documentation? The project folder, or a diagram?

[qwerty]

I have seen <<realize>>, <<satisfy>> and simple <<trace>> dependencies. IIRC there are also profiles supporting RM (but I'm not really in that part of the business).

q.

[jfzouain]

Hi

The best way to do this, is to drag and drop the requirements into the Use Case when is open in the Use case Diagram.
It gets link right away.
So when you run the Documentation or your Requirement Relationship Matrix it will show linked.

I published an eBook to do all this and much more at Leanpub.com

https://leanpub.com/uml-erpworkshop

[MatthiasVDE]

Hi

The best way to do this, is to drag and drop the requirements into the Use Case when is open in the Use case Diagram.
It gets link right away.
So when you run the Documentation or your Requirement Relationship Matrix it will show linked.

I published an eBook to do all this and much more at Leanpub.com

https://leanpub.com/uml-erpworkshop

Thx I'll take a look.

For now, I used composite diagrams but that isn't a preferred solution.