User story, Use case and Expand use case

What’s the meaning of user story, use case and Expand use case

Let’s first understand what’s the meaning of user story, use case and Expand use case.

User Story- A user story is a brief, straightforward feature description written from the viewpoint of the person who wants the new capability—typically, a system user or customer.

As a < type of user >, I want < some goal > so that < some reason >

For example, I want to write the user story, for Sign Up in an online event booking platform.

US-001 Sign Up: As a new user, I want to easily sign up for the platform using a

simple and intuitive signup form so that I can access the platform's features and services.

Use Case- A use case diagram is a visual representation of the numerous ways in which people (actors) and systems could interact (the various use cases).

Figure 1: Use Case Diagram of the Online Event Booking System

Use Case (High level) format:

– Use case: name of use case. Should be meaningful.

– Actors: list of actors including initiator

– Type: a. primary, secondary or optional b. essential – Description: brief overview of the process/service

Example:

Use Case ID	001
Use Case Name	Sign Up
Type	Primary
Actors	Customer
Description	This use case begins when customer want to sign up the online portal to book the event.

Expand Use case format –

– Use case: name of use case. Should be meaningful.

– Actors: list of actors including initiator (use Capital)

– Trigger: User goal that “causes” use case

– Purpose: (system) intention of the use case – Summary: brief overview of the process/service

– Type: primary, secondary, or optional

– Cross reference: related use cases, SRS functional requirements, other documents

– Pre-conditions (assumptions)and post-conditions may be specified. These are discussed later.

Example:

Use case ID	UC-001
Use case Name	Sign Up
Actors	Customer
Created By	Prince
Purpose	To register new customer who can book an event
Summary	Customer wants to register with us, so that he/she can book an event
Type	Primary
Cross reference
Pre-conditions	Customer shouldn’t exist.
Post-conditions
Process	Step	Action
	1	This use case begins when customer wants to register
	2	The customer enters page details on input forms like (customer name, Email Id, Date of Birth etc.) and click submit button
	3	System checks the required inputs.
	4	System validates register details
	5	Create a new customer and show success message
Variations	3.a	Required input details. Show required field warning message if customer name and email id missing
	4.a	Validate location name. Show error message if customer email id already exists.