This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
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.
SCJP 5.0, SCWCD 5.0, SCBCD 5.0, SCEA/OCMJEA 5.0
Joined: Sep 18, 2006
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.