Roadmap
The BABOK counts six knowledge areas. We seriously cover three, and we bite into two more. Here is where we stand, what comes next, and what we will not build.
Where we stand
Business needs
Strategy Analysis, 6.1 Analyze Current StateThe problem to solve and the value expected, written down before any solution.
Requirements
RADD, 7.1 Specify and Model RequirementsRequirements tied back to the need they serve, rather than a flat list.
Use cases
10.47 Use Cases and ScenariosActors, main scenario and alternatives, for the BAs who do not write in stories.
Meeting preparation
Elicitation and Collaboration, 4.1 Prepare for ElicitationTechniques 10.50 Workshops, 10.25 Interviews and 10.43 Stakeholder List, Map, or Personas.
User stories
RADD, 7.1 Specify and Model RequirementsTechniques 10.48 User Stories and 10.1 Acceptance and Evaluation Criteria. INVEST and Gherkin come from the Agile Extension v2 (§7.21 and §7.2), not from BABOK v3.
Process modelling
RADD, 7.1 Specify and Model RequirementsTechnique 10.35 Process Modelling, BPMN notation, with a 2.0 export already laid out.
Consistency across deliverables
5.1 Trace RequirementsWhat contradicts itself from one deliverable to the next. The matrix now has its own entry.
Traceability matrix
5.1 Trace Requirements, 7.4 Define Requirements ArchitectureFrom the need to the process step, with orphan requirements and uncovered needs. Links are observed, never invented.
Version history
5.2 Maintain RequirementsEvery regeneration archives the previous state and compares against it. A history cannot be backfilled.
Work plan
Business Analysis Planning and Monitoring, 3.1 Plan Business Analysis ApproachThe tasks to expect, cross-checked against your deliverables. This is not progress tracking: nothing knows where your project stands.
Challenge mode
10.37 Reviews, 7.2 Verify, 7.3 ValidateThe critique of a finished deliverable, not yet separating verification from validation.
What comes next
In rough order of value. No dates: a dated roadmap is a promise, and we would rather ship than promise.
- 1
Non-functional requirements
10.30 Non-Functional Requirements AnalysisThe classic omission, and the one that costs the most late. Performance, security, availability, compliance: the requirements module accepts them, but nothing yet asks you for them while it would still be cheap.
- 2
Business rules and decision modelling
10.9 Business Rules Analysis, 10.17 Decision ModellingBusiness rules sit scattered across documents and are rarely formalised. DMN is an OMG standard, exactly like BPMN: the same product pattern as our current export.
- 3
Document analysis
10.18 Document AnalysisA BA never starts from nothing: they start from specs, minutes, contracts. Elicira does start from nothing. That is inconsistent, and fixing it would also feed the project context.
- 4
Strategy analysis
6.1 Analyze Current State, 6.2 Define Future State, 10.40 Root Cause AnalysisThe upstream work that separates the senior BA from the story writer. The business needs module covers its entrance; the future state, root cause analysis and change strategy remain untouched.
What we will not build
The BABOK lists fifty techniques. Some of them an AI should not touch, and pretending otherwise would only make the rest less credible.
Observation (10.31)
You have to be in the room. An AI will not be.
Estimation (10.19) and financial analysis (10.20)
Language models are unreliable on numbers, and these techniques need your real data. A confidently invented figure would be worse than an empty field.
Benchmarking (10.4) and vendor assessment (10.49)
Requires current market data we do not have.
Data mining (10.14)
This is not a language model’s job. Other tools do it better.
IIBA professional development hours
The certification handbooks require a human facilitator and an assessment. No software alone can grant them, and we will never claim otherwise.
References point to the BABOK Guide v3, still the current edition, and to the Agile Extension v2 where the agile techniques actually live. Elicira is not affiliated with, nor endorsed by, the IIBA.