Author Topic: Requirement - Use Case association  (Read 3370 times)

JackOfShadows

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Requirement - Use Case association
« on: August 22, 2005, 01:48:58 am »
In EA 5.0 I've found how to produce requirement from Use Case, but I see no way to bind Use Case with Requirement that is already presented in my model. Can I do it in EA?
In fact analitics firs collect requirements and only then form Use cases... as I understand this process.

thomaskilian

  • Guest
Re: Requirement - Use Case association
« Reply #1 on: August 22, 2005, 03:26:30 am »
You can link both by
  • drawing a Realize relation from the UC to Req.
  • doing the same using the Relationship Matrix

Can you tell me why you create Requirements from Use Cases? Is it some kind of re-engineering you're doing?

mikewhit

  • EA User
  • **
  • Posts: 608
  • Karma: +0/-0
  • Accessing ....
    • View Profile
Re: Requirement - Use Case association
« Reply #2 on: August 22, 2005, 05:03:41 am »
Sometimes the use cases ARE the effective requirements e.g. "Must be able to display MPEG stream from tuner while copying it to hard drive", and other examples from the consumer world.
« Last Edit: August 22, 2005, 05:04:14 am by mikewhit »

JackOfShadows

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Requirement - Use Case association
« Reply #3 on: August 22, 2005, 05:49:30 am »
Quote
You can link both by
  • drawing a Realize relation from the UC to Req.
  • doing the same using the Relationship Matrix
Can you tell me why you create Requirements from Use Cases? Is it some kind of re-engineering you're doing?

Thank you for the reply, I don't notice Relationship matrix before :)
I don't create requirenment from Use Case :) But I can do it if I'll use UseCase->Properties->Requirenment->Move External  button.

colinc

  • EA User
  • **
  • Posts: 62
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Requirement - Use Case association
« Reply #4 on: August 23, 2005, 11:38:01 pm »
Another reason to want to attach the requirement to other use cases, that I use a lost, is to specify all of the Use Cases that an atomic requirement supports. This helps with tracability...

Colin