Note that the use case may not be the actual place where you describe the
activity that takes place when you process the file. Processing the file
may be something that the user doesn't actually understand. Use cases
describe things that the user understands.
Therefore, I'd say that you have three different use cases (because the user
will view each of these interactions as having a different motivation or
reason for using them). Each will simply end with a part of the scenario
that says " the file is submitted for processing (use case 99) and the
user's view changes to XXX"
A seperate use case, written from either the technical viewpoint, the
auditor's viewpoint, or the operations manager's viewpoint, can describe the
activities that will occur when a file is processed.
Hope that helps,
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.