FIT2001 W4 - Investigating and Documenting System Requirements

What is a Model?

An approximate, simplified representation of the real item being built.

What is a User Story?

A short, simple description of a product feature in the perspective of the user. Goes into the product backlog

What is the correct structure of a User Story?

As a … I want to … so that …

What are the benefits of using User Stories?

• Keep attention on user goals

• Avoid technical details

• Understandable language

• Simple documentation

Define the INVEST quality checklist for user stories

• Independent - Can be developed separately

• Negotiable - Leaves room for discussion

• Valuable - Provides value to customer

• Estimable - Can estimate the work required

• Small - Fits within a sprint

• Testable - Has acceptance criteria

What are Acceptance Criteria?

Requirements that must be met to mark a user story as complete

What is a Story Map?

Arrangement of user stories into a model that explains system functionality. Identifies holes or alternatives which may have been missed individually

What is a Release?

A collection of functionality that makes sense to deliver at the same time. Can include stories from different epics and contain multiple sprints.

Identify the Activity Diagram elements

1. Swimlane

2. Start

3. Action

4. Flow

5. Decision

6. Guard condition

7. Fork

8. Join

9. End