Search for the Right Document
-
Planning and Strategy
-
Requirements
-
- Customer Feedback Report
- Capacity Planning Report
- Stakeholder Input Record Example
- List of Customer Journeys
- Reverse Engineering: Legacy Inventory Management System
- Task Analysis: Customer Support Ticketing System
- Requirements Workshop: Employee Onboarding System
- Mind Mapping Session: Mobile Travel Planning App
- SWOT Analysis: New Food Delivery App
- Storyboarding Session: Mobile Health & Fitness App
- User Story Mapping Session: Online Grocery Shopping Platform
- Focus Group: Requirements Gathering for Fitness Tracking App
- Prototyping Session Example: E-Commerce Website
- Document Analysis Example: Hospital Management System Requirements
- Observation Session: Warehouse Operations
- Survey: E-Learning Platform Requirements
- Workshop Session Example: Requirements Gathering for Mobile Banking App
- Interview Session Example: Requirements Gathering for CRM System
- Event Storming Session: Retail Order Management System
- Generate Requirements from Meeting Transcripts
- Requirements Definition Process Example
- ISO/IEC/IEEE 29148 Systems and Software Requirements Specification (SRS) Example Template
- Show all articles ( 7 ) Collapse Articles
-
- Customer Requirement Document (CRD)
- Customer Journey Map
- Internal Stakeholder Requirement Document (ISRD)
- Internal System Use Case Example: CI/CD System
- User Stories & Acceptance Criteria
- Technical Specification Document Example
- BDD Scenarios Example for User Login
- Non-Functional Requirements Example
- Functional Requirements Specification Example
- Use Case Example: User Login
-
-
Communication
-
Design
- Functional Specification for Inventory Management Workload
- Technical Specification for Inventory Management System
-
- Overview of Design Diagrams
- High-Level System Diagram Standards
- User-Flow Diagram Standards
- System Flow Diagram Standards
- Data-Flow Diagram (DFD) Standards
- Sequence Diagram Standards
- State Diagram Standards
- Flowchart Standards
- Component Diagram Standards
- Network Diagram Standards
- Deployment Diagram Standards
- Entity-Relationship Diagram (ERD) Standards
- Block Diagram Standards
-
Operations
-
-
- Creating a Visualization Dashboard Guide
- Business Outcome Metrics Dashboard Guide
- Trace Analysis Dashboard
- Dependency Health Dashboard
- Guidelines for Creating a Telemetry Dashboard
- Guidelines for Creating a User Behavior Dashboard
- Improvement Tracking Dashboard
- Customer Status Page Overview
- Executive Summary Dashboard Overview
- Operations KPI Dashboard Example
- Stakeholder-Specific Dashboard Example
- Business Metrics Dashboard Example
- System Health Dashboard Example
- Guide for Creating a Dependency Map
-
-
-
- Event Management Policy Example
- Incident Management Policy
- Problem Management Policy
- Example Training Materials for Escalation
- Runbook Example: Incident Management with Escalation Paths
- Escalation Path Document Example
- Incident Report Example: Failed Deployment Investigation
- Incident Playbook Example: Investigating Failed Deployments
- Contingency Plan for Service Disruptions
-
-
-
Testing
-
Development
< All Topics
Print
Use Case Example: User Login
PostedNovember 16, 2024
UpdatedNovember 16, 2024
ByKevin McCaffrey
Use Case ID: UC001
Use Case Name: User Login
Actor(s): Registered User
Description: This use case describes the steps for a registered user to log into the system.
Preconditions:
- The user must have a valid account in the system.
- The user must know their username and password.
Postconditions:
- The user is logged into the system and redirected to their dashboard.
- In case of failed login attempts, the user is notified accordingly.
Main Flow (Basic Path)
- The user navigates to the login page.
- The system displays the login form with fields for the username and password.
- The user enters their username and password into the form.
- The user clicks the “Login” button.
- The system validates the username and password.
- If the credentials are correct, the system authenticates the user and redirects them to their dashboard.
- The use case ends.
Alternative Flows
Alternative Flow 1: Invalid Credentials
- If the system determines that the username or password is incorrect:
- a. The system displays an error message: “Invalid username or password. Please try again.”
- b. The user can choose to re-enter their credentials or reset their password.
- The use case resumes at Step 3 of the Main Flow.
Alternative Flow 2: Account Locked
- If the user has made too many unsuccessful login attempts:
- a. The system locks the account and displays a message: “Your account has been locked due to multiple unsuccessful login attempts. Please reset your password or contact support.”
- b. The user is provided with options to reset the password or contact support.
- The use case ends.
Alternative Flow 3: Forgotten Password
- If the user clicks “Forgot Password”:
- a. The system prompts the user to enter their email address.
- b. The system sends a password reset email with instructions.
- c. The user can reset their password and attempt to log in again.
- The use case resumes at Step 1 of the Main Flow.
Special Requirements
- The system must support common password security measures, such as a minimum password length and special character requirements.
- Login attempts must be logged for security purposes.
Notes
- This use case covers the login process only and does not include registration or account management features.
- Future enhancements may include multi-factor authentication (MFA).
Table of Contents