Why Study with PlanetCert?
The Latest Questions
Practice questions and exam topics aligned with the current exam objectives.
Detailed Explanations
Go beyond the answer. Master the material with comprehensive learning and professional explanations for every concept.
AI-Powered Insights
Personalized preparation guidance that adapts to your performance and identifies weak spots automatically.
Exam Information
Official specifications published by BCS
Exam Format
60 min
40
26/40 (65%)
Practitioner
Registration
BCS Online Proctored, Pearson VUE, or online proctoring
Validity
No expiry (certificate valid indefinitely)
No formal recertification required - certificate does not expire
PC-BA-RE Exam Topics and Domains
PC-BA-RE is organized into 6 weighted domains.
1
Requirements Definition as a Service
5%
Describe the elements that form the requirements definition service
Service descriptionService value propositionService activitiesService techniques
- Describe what a requirement is
- Describe the requirements definition service including its Value Proposition, Activities and Techniques as per the Business Analysis Service Framework (BASF)
Describe stages of the RE framework and how to plan the approach
Stages of the Requirements Engineering frameworkPlanning the requirements approach
- Describe every stage of the RE Framework - Elicitation, Analysis, Documentation, Validation and Management
- Describe the types of activities the Business Analyst undertakes at each stage
- Describe considerations when planning for a Requirements Engineering activity
- Analyse a given scenario and explain which stage of the RE framework is applicable
2
Eliciting Requirements
20%
Explain the relevant strengths and limitations of elicitation techniques in terms of stakeholder knowledge types and behaviours
WorkshopsInterviewsDocument analysisScenariosStorytellingPrototypes (low and high fidelity)ObservationUser role analysis
- Explain how different methods of elicitation are executed
- Explain how each method supports extraction of different types of knowledge (tacit and explicit)
- Describe potential outcomes when each elicitation technique is applied
- Understand the combination of techniques needed for appropriate volume and depth of information
Explain the use of prototyping to elaborate requirements
Selecting the appropriate type of prototypeVisualisation of requirementsIncrease stakeholder understandingManaging expectations when using a prototypeExtended use of prototypes to support analysis and documentation
- Explain which type of prototype might be appropriate for a given scenario
- Describe how to use a prototype effectively
- Identify anticipated outcomes of prototyping
Analyse a given scenario and apply appropriate elicitation techniques
How to select an appropriate elicitation techniquePlan and prepare for technique useExplain execution of techniqueDescribe the anticipated outcome/output
- Analyse a given scenario and apply appropriate elicitation techniques
- Select, plan, execute and describe outcomes of elicitation techniques
3
Documenting Requirements
25%
Describe the different requirement types
Business requirements (general, technical)Solution requirements (functional, non-functional)
- Describe the different types of requirements
- Review a given requirement and identify the type
Explain how requirements are documented and apply best practice to authoring and capturing requirements
Diagrammatic documentationText-based documentationSelecting the appropriate style(s) of documentation
- Explain the different styles of requirements documentation
- Apply best practice to requirements authoring
- Provide requirements in an easily accessible format
- Select appropriate documentation for the project approach
4
Analysing Requirements
25%
Explain the purpose of analysing requirements
Issues contributing to poorly articulated or incomplete requirementsTasks undertaken as part of requirements analysisGoal of analysing requirements
- Explain types of issues that might be encountered following requirements elicitation
- Explain why issues may occur
- Describe how to assess whether output from requirements analysis is complete, well organised and appropriately documented
Analysing requirements - refine a set of requirements
Unravelling multiple requirementsChecking for overlapping or duplicate requirementsRemoving conflictsEvaluating feasibilityConfirming relevance of the requirementChecking for solutionsConfirming quality of expression
- Describe a technique to refine a set of requirements for a given scenario
- Identify issues within a scenario
- Describe techniques appropriate to resolve issues in a requirements set
Analysing requirements - refine an individual requirement
INVEST criteria for user storiesQuality criteria for individual requirements
- Define a requirement statement for a given scenario ensuring it meets quality characteristics
- Explain why a requirement does not meet quality criteria
Explain additional methods used to analyse and organise requirements
Slicing/splitting requirementsAnalysing Business RulesCategorising requirementsRequirements HierarchyPrioritising requirementsModelling to analyse requirements
- Explain different methods of requirements analysis
- Explain the purpose of each type of analysis and what it achieves
- Explain why and how requirements should be organised in readiness for validation
5
Validating Requirements
10%
Explain the purpose of validating requirements
Objective of validating requirementsConfirm requirements are accurateValidate alignment to business goals, project objectives and scopeAgree requirements are suitable for solution design and buildLinear projects: acceptance criteria for UATAgile projects: requirements form basis for further elaboration
- Explain the purpose of validating requirements
- Justify the need for validation
- Describe the consequences if requirements are not validated
Explain the roles and responsibilities of stakeholders during requirements validation
Roles in the validation review group
Explain the roles and responsibilities of the review group during requirements validation
Explain different approaches to requirements validation
Informal review - Agile/LinearFormal review - Agile/LinearPossible outcomes of requirements validationThe two stages of Agile requirements validation
- Explain the reasoning for various approaches to requirements validation
- Explain when validation should occur in the requirements engineering framework
- Describe how a validation review would be planned and executed for a given scenario
- Describe the action to take for each possible outcome
6
Managing Requirements
15%
Explain the rationale of requirements management, and the elements of requirements management
Rationale for when requirements management occurs in the RE FrameworkIdentificationCross-referencingOrigin and ownershipSoftware supportChange controlConfiguration managementMaintaining traceability
- Explain the purpose and rationale of requirements management
- Describe the main elements of requirements management
Managing changes to requirements
Change control processPossible outcomes: implement or rejectImpact of change to configuration management
- Apply a change control process to a given scenario
- Explain how a change would impact artefacts subject to configuration management
How do I earn this certification?
Passing PC-BA-RE earns the BCS Practitioner Certificate in Requirements Engineering certification. It sits in the Business Analysis track.
Current Level Exams
- PC-BA-BAP - BCS Practitioner Certificate in Business Analysis Practice
- PC-BA-MBP - BCS Practitioner Certificate in Modelling Business Processes
- PC-SMT - BCS Practitioner Certificate in Systems Modelling Techniques
- PC-SDE - BCS Practitioner Certificate in Systems Development Essentials
- PC-DME - BCS Practitioner Certificate in Data Management Essentials
- PC-BMBA - BCS Practitioner Certificate in Benefits Management and Business Acceptance
Next Level Options
Alternative Paths
- IREB Certified Professional for Requirements Engineering (CPRE) Foundation Level Industry-standard alternative RE certification; holders are exempt from BCS RE module for Diploma purposes
- IIBA Certified Business Analysis Professional (CBAP) Comprehensive BA certification; CBAP holders are exempt from RE module and knowledge module for the BCS Diploma
- BCS Professional Certificate in Agile Business AnalysisComplementary Agile-focused BA certification
Practice with Precision
The PlanetCert Simulator mirrors the real exam environment with authentic questions and timed pressure.
How to study for this exam?
The most effective way to prepare for PC-BA-RE is by using the PlanetCert Simulator to practice questions and review detailed explanations.
What's changed on this exam?
Current Status
ACTIVE
Updates
- Requirements Engineering Framework (RE Framework) Updated in V6.1 Core framework used throughout the syllabus. Five stages: Elicitation, Analysis, Documentation, Validation, Management. • Release date: 2025-10-01
- Business Analysis Service Framework (BASF) As per Business Analysis 4th Edition Domain 1 focuses on the Requirements Definition service within the BASF. Understanding the service description, value proposition, activities and techniques is testable.
- Agile Requirements Practices Updated alignment with Agile methodologies Exam tests Agile-specific concepts including user stories, product backlogs, INVEST criteria, Agile validation (two stages), slicing requirements, and WSJF prioritisation.
Who should take this exam?
- BCS Foundation Certificate in Business Analysis (knowledge from this precedes this certificate)
- Good standard of written English
Related practice tests
- AIDBABCS Advanced International Diploma in Business Analysis
- TM12BCS Certified Tester Advanced Level (2012)
- EC-AIBCS Essentials Certificate in Artificial Intelligence
- FC-AgileBCS Foundation Certificate in Agile
- FC-ACDBCS Foundation Certificate in Architecture Concepts and Domains