Book a Demo

Author Topic: Method impact  (Read 4895 times)

Steve_Straley

  • EA User
  • **
  • Posts: 183
  • Karma: +0/-0
    • View Profile
Method impact
« on: February 18, 2004, 01:30:13 pm »
Hi everyone (long time I know)...

Does anyone have a suggestion for how a model needs to be put together to yield results for the following question:

Let's say I have a method of a class that I am about to change.   How would I find all of the Use Cases that could potentially be impacted by such a change; and, subsequently, how would I know what Test Scripts that need to be re-runned should such a change be implemented?

I look forward to some great suggestions...

Cheers,

Steve
Steve Straley

thomaskilian

  • Guest
Re: Method impact
« Reply #1 on: February 18, 2004, 10:43:20 pm »
I would normally take a Use Case Realization (Collaboration) that points via Realize Association to your use case. Inside the Collaboration you have Sequence Diagrams with your classes. Thus you have the connection. (I learned this from a Rose tutorial - propably it's RUP, right?)

Cheers,

Thomas

CJ

  • EA User
  • **
  • Posts: 288
  • Karma: +0/-0
    • View Profile
Re: Method impact
« Reply #2 on: February 19, 2004, 07:14:20 am »
G'day g'day,

Good question, never really thought about it.

My gut says:
Traceability and the Relationships Matrix IF you setup your methods as interfaces so that you can build relationships to specific methods.

Don't know how well that would work...
Cheers and best regards.