User Story as I know it
User Story
Atlassian: A user story is an informal, general explanation of a software feature written from the perspective of the end user. Its purpose is to articulate how a software feature will provide value to the customer.
User stories are a few sentences in simple language that outline the desired outcome. They don’t go into detail. Requirements are added later, once agreed upon by the team.
ProductPlan: A user story is a small, self-contained unit of development work designed to accomplish a specific goal within a product.
User stories (1) are easy for anyone to understand; (2) represent bite-sized deliverables that can fit in sprints, whereas not all full features can; (3) help the team focus on real people, rather than abstract features; (4) build momentum by giving development teams a feeling of progress.
Use Case
A use case often describes several additional steps:
The preconditions required before the use case can begin
The main flow of events (also called the basic flow) desribe a user’s path, step by step, to completing an action with the product
Alternate and exception flows, meaning variant paths a user might take with the product to complete the same or similar goal
Possibly a visual diagram depicting the entire workflow
The Story
TechTarget: Knowing that users stories do not replace use cases or technical requirements documentation, a user story can be considered a starting point to a conversation that establishes the real product requirement.
Examples:
As a bank customer, I want to withdraw money from an ATM so that I’m not constrained by opening hours or lines at the teller’s.
As a user, I want to upload photos so that I can share photos with others.
As an administrator, I want to approve photos before they are posted so that I can make sure they are appropriate.
As a social media manager, I want to tag the photos under specific categories so that I can filter and search the photos for future use.
These examples are the user stories as their initial state, only bullet points listed. Then the lifecycle starts as followed:
Hope this helps!