• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Question regarding FBN Use Case

 
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello all,
I started to stare at the assignment about a week ago. Just for fun I decided to try to follow UML methodology and see how it goes. Incentive for the "fun" is that I like to go for SCEA later(if I feel confident enough). Since I cannot show figures in this post, I'll do my best to explain it in words.
I know it is not necessary or required to follow this technique for the "Developers" certification, but I appreciate all your comments.
*****************
use case 1: Book Flight
use case 2: View Flight Details
use case 3: Search Flight
use case 4: Choose operating Mode

(Book Flight) <<includes>> (View Flight Details)
(View Flight Details) <<includes>> (Search Flight)
Draw a line from Actor to use case 1
Draw a line from Actor to use case 2
Draw a line from Actor to use case 3
Draw a line from Actor to use case 4
The is slightly different from the use case described in Max Habibi's book, for a similar problem.
Question 1: Any comments on the <<includes>> part in my use cases? (Absent in Max Habibi's book)
*******************
For the Book Flight use case, I wrote the following flow of events:
(1) Main flow of events:
The use case starts when the customer enters the flight origin and flight destination. The available flight information is then displayed. The customer selects a particular flight and enters number of seats. The use case ends when the customer clicks on the "submit" button.

(2) Exceptional flow of events.
Customer can change the flight origin or flight destination before submitting. Use case restarts.
(3) Exceptional flow of events.
Customer can change the number of seats before submitting.Use case restarts.
(4) Exceptional flow of events.
Customer can cancel the transaction at any time by pressing the "Cancel" button. There will be no flight booking done. The use case ends.
(5) Exceptional flow of events.
Customer can cancel the transaction at any time by pressing the "Cancel" button. There will be no flight booking done. The use case ends.
(6) Exceptional flow of events.
The number of seats available on the flight is less than the number of seats requested by the customer. The system displays alert message. The system does not commit the entry. The use case restarts.
I have written similar use cases for the "Choose Operating mode" also but not posting it here. (Just for brevity)

Any comments?
Thanks again...
Arun
 
Ranch Hand
Posts: 2937
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


Since I cannot show figures in this post


Anything is possible when you are a cowboy (use the image button):
<-- ServerFactory
<-- LockManager
<-- GUI
Eugene.
[ January 21, 2003: Message edited by: Eugene Kononov ]
 
ranger
Posts: 17347
11
Mac IntelliJ IDE Spring
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Eugene, I really like your GUI, it looks very pretty.

3) Exceptional flow of events.
Customer can change the number of seats before submitting.Use case restarts.
(6) Exceptional flow of events.
The number of seats available on the flight is less than the number of seats requested by the customer. The system displays alert message. The system does not commit the entry. The use case restarts.


Use case shouldn't restart, it goes back a step or two only. They still could keep the search criteria the same
and then the search is not re-performed.


(4) Exceptional flow of events.
Customer can cancel the transaction at any time by pressing the "Cancel" button. There will be no flight booking done. The use case ends.
(5) Exceptional flow of events.
Customer can cancel the transaction at any time by pressing the "Cancel" button. There will be no flight booking done. The use case ends.


Duplicate exceptions.
Mark
 
Arun Bommannavar
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Mark,
Thanks for the feedback.
I didn't pay attention to cut-and-paste and that showed (as duplicate 4 and 5).
5 should have addressed the case of customer closing the application GUI.
I agree with your comments on 3 and 6.
***************
Eugene,
I am pretty new around here and learning everyday. Thanks for the tip on showing graphics

I'll look around for freebie tool for UML drawing and use that next time. Thanks again.
Regards
Arun
 
John Smith
Ranch Hand
Posts: 2937
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


I'll look around for freebie tool for UML drawing and use that next time. Thanks again.


UML Pad is very simple and free.
Eugene.
 
Squanch that. And squanch this tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic