Use Cases

Use Cases define the processes that the application will provide to satisfy the needs of the actors that will use this application.

Each use case is defined in a step-by-step listing of what the user will see and do while using that particular portion of the ACME application.

This is a list of the use cases that you will find on the following pages:

1. User Login (also referred to as ACME Startup)
2. User - Add
3. User - List
4. User - Edit
5. User - Delete
6. Group - Add
7. Group - List
8. Group - Edit
9. Group - Delete
10. Become Administrator
11. Job - New
12. Job - List
13. Job - Open
14. Job - Save
15. Job - Delete
16. Job Clear Lock
17. ACME - Exit
18. Database - Add
19. Database - List
20. Database - Delete
21. Database - Edit

• External User Login
  • Notes
  • Actors
  • Pre-Conditions
  • Access Control is not Enabled
    • Post-Conditions
  • Alternative Path #1, Access Control is Enabled
    • Post-Conditions
  • Alternative Path #2, Security Enabled, Administrator Logs In
    • Post-Conditions
  • Alternative Path #3, User Selects a Different Database During Login
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Add User Account
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path: Create a New User Account
  • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• List User Accounts
  • Notes
  • Actors
  • Pre-Conditions
  • Flow of Events: Administrator
    • Post-Conditions
  • Flow of Events: Non-Administrator
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Edit User Account
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path: Administrator Edits User Account
    • Post-Conditions
  • Alternative Path #2, External User Changes Their Account Information
  • Post-Conditions
  • Other Requirements
• Delete a User Account
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path: Administrator Deletes One User Account
    • Post-Conditions
  • Alternate Path #1: Administrator Deletes More Than One User Account
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Add Group Account
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path: Administrator Adds a Group
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• List Groups
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path: User Displays a List of Groups
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Edit a Group
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path: Administrator Edits a Group
    • Post-Conditions
  • Alternate Path #1: Non-Administrator Views Group Information
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Delete a Group
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path: Administrator Deletes One Group
  • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Enable/Disable Security
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path: Enabling Security
    • Post-Conditions
  • Basic Path: Disabling Security
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Become Administrator
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path: Become Administrator
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Creating a New ACME Job
  • Notes
  • Actors
  • Priority
  • Status
  • Pre-Conditions
  • Basic Path: No job is currently open in the ACME Editor
    • Post-Conditions
  • Alternative Path #1, Already a "clean" job open in the ACME Editor
    • Post-Conditions
  • Alternative Path #2, Already a "dirty" job open in the ACME Editor
    • Post-Conditions
  • Sub Use Case - Prompt User for Job Information
  • "Used" Use Cases
  • Other Requirements
• Search/List ACME Jobs
  • Notes
  • Actors
  • Pre-Conditions
  • Non-Administrator Selects the Search/List Option
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Open a ACME Job
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path - No job is open in the ACME Editor
    • Post-Conditions
  • Alternative Path #1, There is already a "clean" job open in the ACME Editor
    • Post-Conditions
  • Alternative Path #2, Already a "dirty" job open in the ACME Editor
    • Post-Conditions
  • Sub Use Case: Open Job in New Editor
  • "Used" Use Cases
  • Other Requirements
  • Issues
• Save a ACME Job
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path: User Saves Job
    • Post-Conditions
  • Alternative Path #1, The Save As ... option
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
  • Issues
• Delete a Job
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path - User deletes one job
    • Post-Conditions
  • Alternative Path #1, User selects multiple jobs to delete
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Clone a ACME Job
• Clear Job Lock
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path - Administrator Clears a Job Lock
  • Alternate Path #1 - Non-Administrator Clears a Job Lock
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
  • Issues
• Exiting the Application
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path: One Editor Frame is Open
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Add a ACME Database
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Delete Database Alias
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• Edit a ACME Database Alias
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements
• List Known Database Aliases
  • Notes
  • Actors
  • Pre-Conditions
  • Basic Path
    • Post-Conditions
  • "Used" Use Cases
  • Other Requirements