• Post Reply Bookmark Topic Watch Topic
  • New Topic

Split original use cases

 
giuseppe fanuzzi
Ranch Hand
Posts: 99
  • Mark post as helpful
  • send pies
  • 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
 
Krzysztof Koziol
Ranch Hand
Posts: 133
Eclipse IDE Java Spring
  • Mark post as helpful
  • send pies
  • 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: 99
  • Mark post as helpful
  • send pies
  • 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.
 
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads
https://coderanch.com/t/674455/Thread-Boost-feature
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!