• Post Reply Bookmark Topic Watch Topic
  • New Topic

Use Cases  RSS feed

 
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi folks,

When we draw sequences diagrams for each use case, how do you mention that you "jump" towards another sequence diagrams ?

i mean since use cases are nested (prepare itinerary --> price itinerary and so on ...) and some come in the middle of others ( log in use case, create profile use case (NOT DETAILED IN ASSIGNEMENT) ), how to you represent that ?

For the log in and create profile use cases, do you draw any diagrams ???

tery
 
Ranch Hand
Posts: 333
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just answering only part of your ques !!!

Originally posted by tery valencia:
Hi folks,

For the log in and create profile use cases, do you draw any diagrams ???

tery



Yes. According to the "deliverables" section, you have to provide a sequence/collaboration diagram for each usecase provided.
 
tery valencia
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Giju George:
Just answering only part of your ques !!!



Yes. According to the "deliverables" section, you have to provide a sequence/collaboration diagram for each usecase provided.



Ok but there is no description given for these two use cases ( log in and create profile ). Does it infer you hace to write it yourself ?

tery
 
Ranch Hand
Posts: 223
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Since there is no detailed description for the two use cases I don't draw diagrams for them. In the component diagrams you can assume the neccessary components for the use cases but you won't be able to specify a dynamic flow since you have no detailed description.
Browsing the forum, it seems a lot of people took that approach.

D.
 
tery valencia
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by David Follow:
Since there is no detailed description for the two use cases I don't draw diagrams for them. In the component diagrams you can assume the neccessary components for the use cases but you won't be able to specify a dynamic flow since you have no detailed description.
Browsing the forum, it seems a lot of people took that approach.

D.



Ok , david,
but how do you refer to a use case in a sequence diagram ?

i mean in the Prepare itinerary, you need the "log in" use case (unknown), the "create profile" use case (unknown) and the price itinerary use case (known) and to finish, the "Pay itinerary" use case (known).

Since i want to create a sequence diagram for each, and not a unreadable giant diagram which will kill me , how can i do ?

I dont know if i explain it the right way... so much pain

tery
 
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
SQD needs to be Component to Component interaction.
SQD should tell only the Complex aspect. Not the simple aspect (account creation. Pricing is little complex)
SQD scores 12 marks only.

Cocentrate more on component diagram.
 
David Follow
Ranch Hand
Posts: 223
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
leevisa is right.
Draw your SQDs on a component basis and come up with some meaningful methods for the two components (e.g. LoginManager and AccountManager).

D.
 
Ranch Hand
Posts: 531
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A use case can "include" or "extend" another use cases. Include cases that are an essential part of the including case and extend cases that are options that enhance the extending case.
 
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!