What is an Actor?

An actor is a user with a specific role. We identify actors to help us determine the actions that different users will undertake as a part of their business.


A co-ordinator is a user whose role is to manage the years available for auditing within the system, and the questions for each year. The co-ordinator will also create and manage accounts for audit clients (see below).

 Audit Client

The audit client is the user who will answer questions for a given year.


The auditor is the user responsible for auditing the responses given by the audit client. They will use the system to review answers provided as well as input further information related to their audit.

 Sprint Cycles

 What is a Sprint Cycle?

A Sprint Cycle is a two week period of development. A Sprint Cycle may involve any number of developers and at the end of the Sprint Cycle a set of stories will be completed according to acceptance criteria and will be showcased to persons from the business as necessary.

 How does a Sprint Cycle work?

The sprint will start with a "kickoff" meeting where it is decided what resources are available and what stories will be developed. The number of stories developed during this period is based on available developer time and complexity of the work. Each sprint has a start and end date. After the showcase the development team have a debrief and go over any issues that occurred during this sprint.

 Sprint Cycle showcase dates

Showcase 1: 2nd April

Showcase 2: 16th April

Showcase 3: 30th April

Showcase 4: 14th May

Showcase 5: 28th May

Showcase 6: 11th June

Showcase 7: 25th June



What is a Use Case?

A Use Case is used to describe what a system should do from a user's point of view.  It shows the interaction between an actor and the system being developed.  In the Use Cases this interaction is shown in the Basic Flow, Alternative Flow and Exceptional Conditions.  All the Use Cases start with an introduction which outlines what the Use Case is describing.  Following on are the actors, pre-conditions, trigger and post-conditions.   From this point we see the interaction between the user and system (described above).  The Business Rules outline all the things that must happen during this interactions, while the data elements represent what will be on the page.  The data elements shown both labels, and fields that will need data entered.  Where data is to be entered, there are also a set of validation rules which will need to be followed.  The message section shows the details of any messages that will be represented during the user's interaction with the system.

 Use Cases

Each Use Case is represented by a number which can be attributed to a specific user story.



Nice example:

1. Introduction

This use case details the login functionality of the “PRA Audit Tool” application. Coordinators can enter the site by logging into the site for performing different operations. Coordinators are users who work at Archives New Zealand.

 2. Actor

A staff member who has a PRA coordinator role at xxxxxxxxxxx New Zealand.

 3. Pre-Conditions

Coordinators have an account defined in Active Directory.

 4. Trigger

A coordinator needs to login to the system to perform any tasks.

 5. Post-Conditions

The coordinator can now perform tasks within the bounds of their granted authority.

 6. Basic Flow: User Login

  1. Coordinator goes to login page for the PRA Audit Tool application.
  2. System displays a login form.
  3. Coordinator enters username and password and submits.
  4. System validates the login details entered by the user.
  5. System redirects the authenticated user to the home page.

 7. Alternate Flow

 8. Exceptional Condition

 8.1 Authentication Failure
  1. User enters an incorrect username/password combination.
  2. System displays an appropriate error message when authentication fails.

 9. Business Rules


 10. Data Elements Details

No. Data Item Default Value Data Type Mandatory Validation Rules Validation Message
1 Username Blank Text Field Yes    
2 Password Blank Text Field Yes

 11. Message Detail Section

No. Scenario Message
1 Authentication failure
Invalid username or password. Please try again.