• 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

Split original use cases

 
Ranch Hand
Posts: 101
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi folks,
about you, is it too dangerous, for this exam, split one use case in two use cases? for example: "add row to table" use case. i want to split this use case in "search table" and "add row"?

Thank you in advance
 
Ranch Hand
Posts: 133
Eclipse IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

giuseppe fanuzzi wrote:Hi folks,
about you, is it too dangerous, for this exam, split one use case in two use cases? for example: "add row to table" use case. i want to split this use case in "search table" and "add row"?

Thank you in advance



What's the reason behind this? I did split one use case when creating sequence diagram because it was too long to express it one diagram.
 
giuseppe fanuzzi
Ranch Hand
Posts: 101
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Krzysztof,
it's exactly the same reason.
there are two use cases and i would split not only the sequence diagram, but the use cases.
In these use cases, in the sequence diagrams i have two stateless and 4 interactions with user.
i think that splitting use cases implies more reusability and readability, and not modify the original requirements.
reply
    Bookmark Topic Watch Topic
  • New Topic