Book a Demo

Author Topic: Use case- change log  (Read 4875 times)

sanlew96

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Use case- change log
« on: May 28, 2007, 12:26:51 am »
Can anybody help with me the following problems

1. Change log for each of the use case (should maintain the reviewer and the previous authors also)
2. Numbering of each of the steps in the use case and auto numbering it
3. Can we connect the scenarios into a diagram

This is used for use case writing for retail banking. So we need to know the extensive functionality

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Use case- change log
« Reply #1 on: May 30, 2007, 01:05:04 pm »
If you are a registered user, have a look at the Beta for EA 7 at the auditing feature for tracking changes.  I don't have any suggestions for the other two.

peter.zrnko

  • EA User
  • **
  • Posts: 253
  • Karma: +0/-0
    • View Profile
Re: Use case- change log
« Reply #2 on: May 30, 2007, 08:30:43 pm »
Quote
3. Can we connect the scenarios into a diagram


You can attach a note to the use case and "Link this note to an element feature" and select a scenario. In this way you can see tha scenario in a diagram and eventualy copy it to another diagram (Paste as link).

If you are looking for a way to establish a relationship between a scenario and some other element, then it's not possible. Maybe it's because a scenario is not an UML element , it's just a way to discribe an use case similar to discribing it in a note. (from the point of view of UML, de facto a scenario is much nore than a note)
You can only make a relationship between an UC and an element e.g. a realize link and eventualy write a note in this relationship..
Peter

sanlew96

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Use case- change log
« Reply #3 on: May 30, 2007, 09:50:59 pm »

Thanks for the info guys. For change log we sre planning to use the document artifact element. We will create a document with Serial Number, Use case number, scenario number, details, author and date. We can also have a reviewer Name and date. This will be attached to the summary use case. Dont want to use 7.0 till it is stable. We have our product (Core banking) delivery in december and so we cant wait till version 7 comes out in the market.