• 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
  • Tim Cooke
  • paul wheaton
  • Jeanne Boyarsky
  • Ron McLeod
Sheriffs:
  • Paul Clapham
  • Liutauras Vilda
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

should refine use-cases

 
Ranch Hand
Posts: 80
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Preparing part II. I've been thinking about the use-cases and sequence diagrams. The use cases show some alternative scenarios, but there are much more. Some of them are pretty obvious like:

- what if two customers book the same seat at the same time? When are seats locked?

My idea is to ignore all this scenarios in my sequence diagrams since I don't know FBN policy, and just design a sequence diagram that matches what the use-cases say + assumptions I made while designing class and components diagrams. Maybe I'll add some notes about the most relevant scenarios ommitted.

Do you share my point? Anyone succeded with this strategy?
 
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Eduard,

Just write your assumptions, I think that would be fine and enough.

Assumptions, could be: DB takes care of currency.

Lucy
 
It will give me the powers of the gods. Not bad for a tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
reply
    Bookmark Topic Watch Topic
  • New Topic