The first step is developing a use case is defining a set of actors. While it will normally be a “user”, it might also be “an automated/scheduled system”, “an administrator”, etc.
There will likely be different actors in the system, or different roles that the same person might play.
When building the use case you need to be aware of several aspects:
- Who is the primary actor?
- Is there a secondary actor?
- What preconditions are needed?
- What task is being performed?
- What exceptions are acceptable?
- Are there other ways to perform this task?
- What will the system produce, acquire, or change?
- Does the actor have to configure the system based upon external information?
- Does the actor need to know about changes once this this task is completed?
Developing Use Cases was originally found on Access 2 Learn
One Comment
Comments are closed.