• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Pay for Itenary

 
Senthil Rajendran
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

As per the use case there is no actor for pay itenary use case. Prepare Itenary use case calls / executes pay for itenary, which is just going to calculate the price of an itenary.

in this case is it valid if I show my interaction starting from itenary, which <<creates>> price itenary -> Segment -> ..... etc

And also do I need to depict anything about security in the diagrms or describe about its implementation in the document ?

Any help is greatly appreciated.

Senthil
 
Senthil Rajendran
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
SCEA passouts suggestions please ...
 
Ganesh Krishnan
Ranch Hand
Posts: 42
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Senthil,

As far I think, u can build a sequence diagram for the pay for itinerary and then you can give a UML note in the price itinerary that ...at this stage pay for itinerary would be called...

Regarding security, i dont think we need to show it in the diagrams.. we can explain all our non-functional requirement in the document itself. But.. always you can attach a note if you find the information would make sense to the grader

Hope this helps.

Ciya,
Ganesh.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic