aspose file tools*
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Split original use cases Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Split original use cases" Watch "Split original use cases" New topic
Author

Split original use cases

giuseppe fanuzzi
Ranch Hand

Joined: Sep 18, 2006
Posts: 99
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


GiUsEpPe (SCJP, SCWCD, SCBCD, IBM OOAD, SCEA/OCMJEA 5)
Krzysztof Koziol
Ranch Hand

Joined: Nov 19, 2006
Posts: 133

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
giuseppe fanuzzi
Ranch Hand

Joined: Sep 18, 2006
Posts: 99
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.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Split original use cases