Embedded Files
Requirements of a User Story
“A user story briefly explains:
- The person using the service (actor)
- What the user needs the service for (narrative)
- Why the user needs it (goal)
[…] They’re a way of organising your work into manageable chunks that create tangible value, and can be discussed and prioritised independently” (HM Government, 2013). These stories are used to divide the software development down into more manageable development chunks known as sprints. These stories will be used in the design section to create ‘Use Case’ diagrams.
User Story
The user should be able to access the User Guardian tool online. Once within the tool the user should be able to manipulate pre-loaded application data to set SoD rules for a single application, and then produce an exception report showing any user access compliance breaches.
User Case Diagram
The user case diagram is shown in Figure 17.
Figure 17 - User Case Diagram
Precondition
The User Guardian tool is pre-populated with a data for an application and the associated users and their access attributes.
References
HM Government, 2013. Writing user stories. [Online]
Available at: https://www.gov.uk/service-manual/agile/writing-user-stories.html
[Accessed 21 August 2013].
Page updated
Google Sites
Report abuse