This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
I'm new to UML but basically a developer.I have a jsp in which I had 2 functions, one to add and the other to modify an account.Do I need to write two use cases(1.add,2.modify) or just one use case that describes both the functions?.
Originally posted by Jan Cumps: As a Craig Larman adept, I would suggest to use one use case for this goal.
Technically, these are two separate goals that a user wishes to accomplish when interacting with the system, so they are at least conceptually two separate use cases. While there may be some advantage to collapsing them in the short term due to minimized redundant text, I think you're better off working these separately and using "includes" sections for common portions.
I think in general that you want to avoid "if" clauses in a use case. For example, the use case for "add account" may require an external lookup to a credit service, but this would not be appropriate for a "change account" use case.