• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

detail level of sequence diagram

 
Yiu Wing Tsang
Ranch Hand
Posts: 30
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am going to complete the sequence diagram but feel doubts during revising my sequence diagram.

In the sequence diagram, I draw the "normal" path as described in the use case. But is it also necessary to draw all the possible paths (error, exception path) as well?
e.g. in Pay for Itinerary, what if mileage availability is not enough, do we need to show how to the system acts for this path? I think there are many paths other than the normal one.

Therefore I would like to ask how details do the sequence diagrams are needed? as it is just worth 12 points, I would prefer to focusing on the normal path is just enough, how do you think?
 
Ricardo Ferreira
Ranch Hand
Posts: 156
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yiu,

Since the architecture assignment is about to design an complete solution, you should consider to detail the idea behind all use cases. If some company or customer hire you to do some architecture job, you'll try to design a perfect solution, to meet your customer needs.

Related to the assignment, I've used to much details in my sequence diagrams, and I could be approved for this. But, you must address the essence of the architecture, that is create an COMPLETE solution, and not only one, that will garantee your approval in the certification.

"You you are about to do something, to the best. If you are about the be something, be the best"

Best Regards
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic