AD_Topic_9

8/11/2019 AD_Topic_9

1/5

Topic 9 Requirements Definition and Prioritisation Agile Development

V1.0 Visuals Handout Page 1

V1.0

Agile Development

Topic 9:

Requirements Definition and Prioritisation

Requirements Definition and Prioritisation Topic 9 - 9.2

Topic 9 Coverage

This topic will cover:

What is a requirement?

Defining the requirements

V1.0

Requirements and modelling

The Requirement Lifecycle


What is a Requirement?Group Exercise

List as many words or phrases as you can

that mean requirement.

V1.0

8/11/2019 AD_Topic_9

2/5




What is a Requirement?

In simple terms, a requirement is a:

- feature

- function

V1.0

- serv ce

- constraint

that the solution needs to perform or exhibit.


Defining the Requirements

Define a requirement along with its Acceptance

Criteria as measurable targets at all levels.

Give it a unique ID

Keep details of:

V1.0

- source

- owner

- business benefit

- priority

- other?


Functional Requirements Functional requirement is what , not how .

Make it SMART

- Specific

- Measurable

- Achievable

V1.0

-

- Timely

Wording - functional requirement:

- We need the ability to

- As a I need in order to

Not in conflict with, or overlapping, other requirements.

8/11/2019 AD_Topic_9

3/5




Non-Functional Requirements

Non-functional requirements are about how well

we do the functional requirements, i.e. with what:

security

availability

portability

external interfaces

design constraints

performance

V1.0

maintainability response time

etc. (see notes)

May be global or related to just one functional

requirement.

May need extra time in the plan!


Structure of RequirementsRequirement Decomposition

Feasibility:

- A very high level set of requirements is established

Foundations:

- A high level set of prioritised requirements is established

a PRL

V1.0

- User stories

Exploration and Engineering:

- Each requirement may decompose into more detailedrequirements

- At some point, it may not need to be written down, butevolved as part of i terative development (prototyping)


Requirements and Modelling

Make a

reservation

Amend a

reservation

Make aconferencebooking

Handle

Reservations

R1

R1.1.1

W

M

S

R1.1

R1.2

M

V1.0

Produceoccupancy

report

Cancel areservation

ake anindividualbooking

. .

R1.1.2

R1.1.3

M

C

8/11/2019 AD_Topic_9

4/5




Requirements in the Atern Lifecycle

OutlinePlan

DeliveryPlan

TimeboxPlan(s)

LessLess

Typically

8/11/2019 AD_Topic_9

5/5




The Requirement Lifecycle Each requirement must be subject to:

Elicitation- Workshops, model-building, interviews, observation,

scenarios

Analysis

V1.0

- ea s c m guous om na on o requ remen sAligned with business?

Validation

- Prototypes, reviews, models, testing

Management

- Traceability, stability, change management


Summary

What is a requirement?

Functional and non-functional requirements

V1.0

equ remen s n e ern ecyc e

Requirements and modelling

The Requirement Lifecycle


Topic 9 Requirements Definition and

Prioritisation

NCC Education LimitedV1.0

Any Questions?

Documents

AD_Topic_9