User Tools

Site Tools


A2: Actors and User Stories [06]

This artefact contains the specification of the actors and their user stories, serving as agile documentation of project requirements.

An Actor models a type of role played by an entity that interacts with the system being specified. This may include persons (not just the end-user), and other entities external to the system. Actors are always external to the system being modelled; they are never part of the system [Ambler04] .

A User Story is a high-level definition of a requirement containing only the necessary information so that the developers can produce a reasonable estimate of the effort required to implement it [Ambler04] . A user story, a brief description of a potential interaction with the system by one of its users, focuses only on interaction requirements and not on the technical aspects of the design of the system. The user stories have a priority (high or essential, medium or conditional, and low or optional) indicating the need to be included in the design implementation stages and project. A team of expert analysts also includes an estimate of the effort required for its implementation.

Each user story must follow the template [Dennis10] :

“As a [user], I want [function], so that [value]”

The Supplementary requirements are also presented in an Annex to A2.

This annex contains business rules, technical requirements and other restrictions on the project:

  • A business rule defines or constrains one aspect of the business, with the intention of asserting business structure or influencing business behaviour;
  • Technical requirements are concerned with the technical aspects that the system must meet, such as performance-related issues, reliability issues and availability issues;
  • A restriction on the design limits the degree of freedom in the search for a solution [Ambler04 ].

A2: MediaLibrary example | A2 template | A2 checklist

teach/lbaw/artefacts/a02.txt · Last modified: 27/02/2020 15:08 by Correia Lopes