Functional Requirements Use Case

Designed by: [YOUR NAME]

Company: [YOUR COMPANY NAME]

I. Use Case Identification

• Use Case ID: [USE CASE ID]

• Title: [TITLE OF THE USE CASE]

• Creation Date: [DATE CREATED]

• Last Updated: [LAST UPDATED DATE]

• Scope: [SCOPE OF THE USE CASE]

• Level: [LEVEL - "SUMMARY" OR "SUBFUNCTION"]

II. Stakeholders and Actors

• Primary Actor: [PRIMARY ACTOR]

• Secondary Actors: [SECONDARY ACTORS]

• Stakeholders: [STAKEHOLDERS]

III. Preconditions

Conditions that must be true or the events that must have occurred before the use case is triggered:

• User is accessing the website for the first time

• The user has not yet registered an account

IV. Postconditions

Conditions that must be true or the events that must occur after the use case is completed:

• User account is successfully created

• User receives a confirmation email

V. Use Case Description

A narrative description of the sequence of actions and interactions between the actors and the system:

Trigger Event: User clicks on "Register" button

Normal Flow:

1. User navigates to the registration page

2. User fills out the registration form with required information

3. User clicks on "Submit" button

4. System validates the user inputs

5. System creates a new user account

6. System sends a confirmation email to the user

Alternative Flows:

• User attempts to register with an existing email address

• System prompts the user to use a different email address

• User retries registration with a different email address

Exceptions:

• System encounters a technical error during account creation

• User submits incomplete registration form

VI. Special Requirements

Any requirements that are not covered by the standard functionality of the system:

• User password must meet minimum complexity requirements

• Email confirmation link must expire after 24 hours

VII. Assumptions and Dependencies

Assumptions:

• Users have access to a valid email address for account verification

Dependencies:

• Dependent on email service provider for sending confirmation emails

VIII. Frequency of Use

Estimate of how often the use case is initiated and by whom:

• Frequent, initiated by website visitors

IX. Miscellaneous

Any other information relevant to the use case:

Notes: New users are required to agree to the website's terms and conditions during registration

Issues: Potential delay in email delivery for confirmation emails

Use Case Templates @ Template.net