Short, simple and limited description of the desired functionality seen from a user's perspective
Description
Also called user story.
It is atomic in nature, i.e. can not be divided without losing its value. It must be possible to develop incrementally for 2-3 weeks and it must be possible to implement it independently of other stories and still make a contribution to the whole.
Usually described with a short name and in text form in the format "As <roll> I need <function> to <goal>".
On closer inspection, a story can turn out to be more complex than originally thought and then it is transformed into a feature and the functionality is broken down into stories.
Example
Examples of stories:
- Book an interview
- As a recruiter, I need to be able to book candidates for interviews in my calendar so that I can plan my time effectively.
- Check invoice line
- As a buyer, I need to be able to check invoiced items against what has actually been delivered so that we do not pay for goods that we have not received.
Link
View types
Application Context Description (ACD)
Application Context Model (ACM)