Analysis #

1. Introduction#

The analysis phase is dedicated to the formalisation of the requirements elicitation. It usually involve talking with a client and documenting your understanding. Amongst the artefact used we can mention user stories and use cases. These are also used to help organise, prioritise and divide the workload.

2. Table of Contents#

• 1. Introduction
• 2. Table of Contents
• 3. Level Specific Guidance
• Level 4
• Level 5
• Level 6

3. Level Specific Guidance#

Level 4#

Level 4 User Stories

• Basic user stories identifying “the actor”, “the narrative”, and “the goal”.

Level 4 Use Case Guidance

• Basic use case diagram and use case descriptions. Use cases identified from user stories.

Level 5#

Level 5 User Stories

Level 5 Use Case Guidance

Level 5 Personas and User Scenarios

• Use Case or User Story or Requirement Specification.
• User stories should include basic indications of acceptance criteria.
• Persona and User Scenario.
• Requirements should be SMART.

MoSCoW Prioritisation Method

• Should be used where possible.

Level 6#

Level 6 User Stories

• Use Case or User Story or Requirement Specification.
• Well defined user stories with clear acceptance criteria, and evidence of traceability.
• end to end traceability (Requirement Traceability Verification Matrix) need to be maintained.