Skip to content

Requirements Engineering and Traceability Training Course

Traceable requirements training for analysts and product owners: elicit, model, write user stories and control change with a matrix linking needs to tests.

This 1-week course has 50 dates from November 2026 to November 2027 in 24 cities and live online. The next session runs 23 – 27 November 2026 in Munich. Fees per participant run from 3,300 £ (Amman) to 7,900 £ (New York) in a classroom, and from 1,900 £ live online.

See dates and book Download brochure (PDF) Training for your team

Duration
1 Week
Next start
Munich
Scheduled dates
50
Classroom cities
24
Classroom fee from
3,300 £
Online fee from
1,900 £

When and where does this course run?

Showing 1–20 of 50 dates

November 2026

December 2026

January 2027

February 2027

March 2027

April 2027

Can’t find a suitable date? Tell us what you need.

What does this course cover?

Requirements Engineering and Traceability is a 1-week training course for business analysts and product owners who leave with a traceable requirements baseline linking each need to its source, acceptance test and approved changes. Organisations now release software and process changes in short cycles, so a requirement that cannot be traced back to a need or forward to a test quickly becomes rework. Jupiter Prime Training delivers this course in requirements engineering and traceability.

Why Requirements Engineering and Traceability Matter Now

Three pressures shape requirements engineering today. Iterative release cycles mean requirements change weekly, and without traceability nobody can say which tests or designs a change touches. Auditors and quality functions in sectors such as healthcare, banking and utilities expect evidence that each delivered feature answers an approved need. Sponsors want scope decisions explained, not asserted. Teams that trace well absorb change calmly; others discover gaps at acceptance, when fixes cost most. The course rests on recognised requirements engineering practice: elicitation, modelling, validation and baseline control.

Who Gains Most from Requirements Engineering and Traceability

  • Analysts who run interviews, observation and joint sessions to draw out stakeholder needs
  • Product owners who turn needs into a prioritised backlog of user stories with acceptance criteria
  • Practitioners who build use case, data and process models to expose missing or conflicting requirements
  • Specialists who maintain requirements catalogues and link them to designs and tests
  • Coordinators who assess change requests against an agreed requirements baseline

The gain is greatest when an analyst and product owner from one product attend together.

Requirements Engineering and Traceability Capabilities

Participants turn loose wish lists into testable requirements followed from origin to acceptance.

  • Apply elicitation techniques suited to each stakeholder group — choice of interview, observation or prototype
  • Specify functional and non-functional requirements with clear acceptance criteria — test design
  • Build use case, class and state models that reveal gaps — design sign-off
  • Write and split user stories with INVEST checks — sprint planning
  • Build a traceability matrix linking source, requirement and test — audit and acceptance
  • Assess change requests for impact on baselined requirements — change board approval

Key Requirements Engineering and Traceability Terms

  • Requirements Elicitation — Drawing out needs from stakeholders through interviews, facilitated sessions, observation, document study and prototyping.
  • Requirements Catalogue — A structured record holding each requirement with its identifier, source, owner, priority, status and acceptance criteria.
  • User Story — A short statement of a need from a user's viewpoint, paired with acceptance criteria that confirm it is met.
  • Non-Functional Requirement — A quality the solution must show, such as performance, security, usability or availability, rather than a behaviour.
  • Traceability Matrix — A table linking each requirement backward to its source and forward to designs, tests and changes.
  • Requirements Baseline — The approved set of requirements at a point in time, changed only through controlled change requests.

Requirements Engineering and Traceability Day by Day

Day 1: Requirements in Their Business Context

  • Requirements Engineering Framework — Linking Elicitation, Analysis, Validation and Control
  • Stakeholder Identification and Viewpoints — Deciding Whose Needs Shape Scope
  • Business, Stakeholder and Solution Requirements — Separating Levels of Need
  • Well-Formed Requirement Characteristics — Judging Clarity, Testability and Feasibility
  • Scope Context Diagram — Fixing System Boundaries Before Detailed Elicitation

Day 2: Eliciting Needs from Stakeholders

  • Structured Interview Plan — Choosing Questions for Each Stakeholder Group
  • Observation and Shadowing — Capturing Tacit Knowledge Users Rarely Mention
  • Facilitated Requirements Session — Resolving Conflicting Needs Across Departments
  • Low-Fidelity Prototyping — Testing Interface Assumptions With Users Early
  • Elicitation Notes to Draft Requirements — Converting Raw Findings Into Statements

Day 3: Analysing and Modelling Requirements

  • Use Case Diagram and Descriptions — Exposing Actor Goals and Alternative Flows
  • Class Model of Business Entities — Clarifying Data Rules and Relationships
  • State Transition Model — Revealing Missing Rules for Entity Life Cycles
  • MoSCoW Prioritisation — Agreeing What Enters the First Release
  • Non-Functional Requirement Templates — Setting Measurable Quality Thresholds

Day 4: Documenting, Validating and Controlling Requirements

  • Requirements Catalogue Structure — Recording Identifier, Source, Owner and Status
  • User Stories With INVEST Checks — Splitting Epics Into Deliverable Items
  • Acceptance Criteria in Given-When-Then Form — Linking Needs to Tests
  • Requirements Review and Walkthrough — Catching Ambiguity Before Design Starts
  • Change Request Impact Analysis — Deciding Whether a Baseline Change Proceeds

Day 5: Practising the Traceable Requirements Baseline

  • Case Elicitation Plan — Applying Day Two Techniques to a Realistic Scenario
  • Case Model Set — Reusing Use Case and Class Models From Day Three
  • Traceability Matrix Build — Linking Sources, Requirements, Stories and Tests
  • Simulated Change Board — Defending an Impact Assessment Under Questioning
  • Traceable Requirements Baseline — Completing the Approved Pack for Hand-Over

Applying Requirements Engineering and Traceability After the Course

  • Audit one live backlog or catalogue against the well-formed characteristics, then add missing sources and acceptance criteria to the highest-priority items.
  • Set up a traceability matrix for a current release and use it to assess the next change request before the change board meets.

Requirements Engineering and Traceability Questions (FAQ)

What is requirements engineering and traceability, and why does it matter now?

Requirements engineering and traceability is the disciplined capture, modelling, validation and control of requirements, each linked to its source and tests. It matters now because short release cycles change requirements constantly, and only traced requirements show what each change affects.

Which roles gain most from requirements engineering and traceability training?

Business analysts and product owners gain most, especially those who maintain catalogues or backlogs or prepare change requests.

How does requirements engineering and traceability differ from a business analysis foundations course?

It goes deeper into one stage of analysis. A foundations course surveys the whole discipline; this course concentrates on requirements, with traceability throughout.

What do you bring back from requirements engineering and traceability training?

You bring back a completed requirements pack for a realistic case, including models, a catalogue, user stories with acceptance criteria and a traceability matrix.

Requirements Engineering and Traceability: The Way Forward

The traceable requirements baseline built during the course first informs which change requests a change board can approve without destabilising a release. Analysts, product owners and test leads use it to agree scope. After its first use, the matrix granularity deserves a fresh look: tracing too finely slows updates, while tracing too coarsely hides the impact of change.

Questions about dates, fees and booking

When does this course next run?

The next session runs 23 – 27 November 2026 in Munich. It is one of 50 dates scheduled up to November 2027.

Where is this course held?

In a classroom in 24 cities: Munich, Muscat, Doha, Madrid, Kuala Lumpur, Singapore, Paris, Sharm El-Sheikh, and more. It is also scheduled as live online sessions.

Can I attend this course online?

Yes. 2 dates are scheduled as live online sessions; the next runs 21 – 25 March 2027, from 1,900 £ per participant.

How long is the course?

1 Week. Each date shows its start and end dates.

How much does the course cost?

Fees per participant run from 3,300 £ (Amman) to 7,900 £ (New York) in a classroom, and from 1,900 £ live online. Each date shows its own fee.

Is there a brochure for this course?

How do I book a place?

Choose a date above and select Register, or send us an enquiry.

Can this course be run for our team?

Yes. Tell us the number of participants and your preferred dates and city through our training request form.

More ways to train