Author Topic: Activity Diagram - Level of Detail  (Read 1352 times)


  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Activity Diagram - Level of Detail
« on: June 09, 2004, 08:10:28 am »

I was wondering how others are handling this. In my case, I have certain Use Cases which have common actions such as add, edit and delete.  For these Use Cases, I have charted out the activities once and added a diagram note stating this applies to Use Case X, Y and Z. Is this the best way to do this? I like this approach because if you add another type of validation or any other activity, you only have to change it in one place. Any thoughts or comments would be appreciated.


« Last Edit: June 09, 2004, 08:27:02 am by CSharpGuy »


  • Guest
Re: Activity Diagram - Level of Detail
« Reply #1 on: June 09, 2004, 12:55:47 pm »
you might think of having a generalization where you specify he CRUD in one use case and draw the generalization from the specialized use cases to this one. Care should be taken since only in very few cases you have a real generalization when you deal with use cases. Probably you should have look here