• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

sequence diagram granularity

 
Saha Kumar
Ranch Hand
Posts: 218
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello All,

I am finding that it is easier to put the PrepareItinerary and PayItinerary (with credit card) in the same diagram, and to put PayItinerary (with mileage award) in a separate diagram.

Is this an acceptable sequence diagram granularity for assignment submittal?

Thanks in advance.

-Saha
 
Saha Kumar
Ranch Hand
Posts: 218
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The requirements state:

Create either a sequence or collaboration diagram for each use case provided.

Sorry for the question...

-Saha
 
Thomas Taeger
Ranch Hand
Posts: 311
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Saha Kumar:
The requirements state:
Create either a sequence or collaboration diagram for each use case provided.
Sorry for the question...

No, Saha,
your question was quite right in my oppinion!

In UML a Sequence Diagram is shown per scenario/flow of a usecase, not per usecase!

Thomas
 
Saha Kumar
Ranch Hand
Posts: 218
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Thomas,

Thank you for the reply. The way I read the requirements, it seems one sequence diagram per use case. I read other posts, and it seems that everyone has one sequence per usecase.

Previously, I wanted to put: prepareItinerary, priceItinerary, and payItinerary (with credit card), all happy paths in one sequence diagram.

Do you think this is correct?

Thanks in advance.

-Saha
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic