jQuery in Action, 3rd edition
The moose likes OO, Patterns, UML and Refactoring and the fly likes Use Case Diagrams Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "Use Case Diagrams" Watch "Use Case Diagrams" New topic

Use Case Diagrams

Aravindan Ramanujam

Joined: Aug 27, 2004
Posts: 10
I'm working on a rewrite of a current application. I'm using the use case diagrams and specifications to capture the requirements. I've a scenario where the actor keys in details to the system and the validation and processing(Lot of business rules) of those details are happening in the cobol modules in the backend. The results are given to the actor and he keys in the credit card details. That is again authorised / validated in the backend.

I would like to know how to represent the backend processes in the use case diagram. The question is should it be represented in Use Case diagram or not?

Anyways I'll be having all the rules listed out in my Use Case Specification under Special Requirements.

Thanks for your help !!!

- Aravindan -
Scott Ambler
Ranch Hand

Joined: Dec 12, 2003
Posts: 608
The act of doing this processing should be captured in the use case. There would be two actors involved, one for the person and one (or more) for the back-end system(s).

For examples of how to write system use cases, and other models, see www.agilemodeling.com/artifacts/

- Scott

<a href="http://www-306.ibm.com/software/rational/bios/ambler.html" target="_blank" rel="nofollow">Scott W. Ambler</a><br />Practice Leader Agile Development, IBM Rational<br /> <br />Now available: <a href="http://www.ambysoft.com/books/refactoringDatabases.html" target="_blank" rel="nofollow">Refactoring Databases: Evolutionary Database Design</a>
Aravindan Ramanujam

Joined: Aug 27, 2004
Posts: 10
Thanks Scott !!!
I agree. Here's the link: http://aspose.com/file-tools
subject: Use Case Diagrams
It's not a secret anymore!