Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Level of Detail

 
Julio Cesar Marques
Ranch Hand
Posts: 80
BSD Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi guys!

I'm asking before bored some examiner

How many details has to exist in my sequence diagrams? In my case a simple use case (4 actions) is reaching 30 steps and it's not finished yet!
What is safe to remove in these diagrams and what should I keep?

Thanks!
 
Mike Degteariov
Ranch Hand
Posts: 145
8
Java Mac MySQL Database Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey Julio,

I had a "Team Doctor" assignment, and I found that proper implementation of its use cases required pretty long sequences.

Do not want to scare you or anything, but some of my sequence diagrams had more than 60 steps.
 
K. Tsang
Bartender
Posts: 3585
16
Android Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Further to Mike said, it also somewhat depends on how many classes the use case will use. Mentioning the key points for each method is key.

For me one of my use case has like 2 steps (basic flow), turns out like 5 "high level" program flow which become like >10 classes
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic