Visual Models for Software Requirements Review: Worth It for CBAP?
Is Visual Models for Software Requirements by Joy Beatty and Anthony Chen worth reading for CBAP in 2026? What it teaches, how it maps to BABOK v3, and who should skip it.
Visual Models for Software Requirements by Joy Beatty and Anthony Chen is worth reading if you already write requirements and want to model them, and it is a useful companion for Certified Business Analysis Professional (CBAP) candidates who study the modelling tasks of BABOK v3. It is not a CBAP study guide and it is not a first book for beginners. Read it after a general requirements book, and use it for the Requirements Analysis and Design Definition chapter.
As of October 2026, the book is still the first edition (Microsoft Press, July 2012). We found no later edition on the publisher pages [1][12] or on the authors' company page, which still presents the models as current [4].
Visual models for software requirements: the book in brief
The book is a 480-page handbook that teaches a set of 22 visual models, called the Requirements Modeling Language (RML), for finding, checking and communicating requirements [1][2].
Item
Detail
Authors
Joy Beatty, Anthony Chen
Edition
1st edition
Publisher
Microsoft Press (Developer Best Practices series)
Published
15 July 2012
Pages
480
Level
Intermediate: the authors assume you can already write requirements
Best for
Business analysts and product managers on IT, SaaS and cloud projects
The authors say the book is based mostly on IT, software-as-a-service and cloud projects, and less suited to shrink-wrapped consumer software or marketing-driven product management. They also point beginners to a general requirements book first [2]. Our count of the contents list gives 22 models in four groups: 5 objectives models, 4 people models, 7 systems models and 6 data models [1].
Key ideas from the book
The core idea is that a complete system matters more than a pile of well-written individual requirements, and pictures help you see what is missing.
Objectives, people, systems and data models answer different questions: why are we doing this, who does the work, how does the system behave, and what information does it hold [1][2].
Models find gaps that lists hide. The authors argue that long lists of requirement lines are hard to review, and that visual models are easier to check for missing and conflicting items [2]. Beatty repeats this in an interview: models organise information into small groups, so reviewers spot what is absent [6].
Models do not replace text. Developers and testers still need written requirements, so the models sit beside the text and are not a substitute for it [6].
A requirements mapping matrix ties it together. The matrix links requirements to process steps and other models. Beatty calls the completeness check its strongest feature, and says it also helps you find and move out the affected requirements when scope changes [5].
Choose models by project phase and project type. The authors suggest checking the five phases (Envision, Plan, Develop, Launch, Measure) and the project's characteristics against all four categories, then defining a requirements architecture and piloting it on a small part of the project [3].
A short starting kit. For most IT projects the authors suggest starting with four models: process flows, a requirements mapping matrix, display-action-response models for screens, and data dictionaries [2].
What helps for the CBAP exam
The book is built on its own language, so it supports CBAP indirectly: it gives you worked practice for the modelling techniques that BABOK v3 names.
CBAP facts, according to the International Institute of Business Analysis (IIBA): 120 case-study and scenario-based multiple-choice questions in 210 minutes; 7,500 hours of work experience in the last 10 years and 35 professional development hours in the last four years; exam fee USD 350 for members and USD 505 for non-members, plus a USD 145 application fee [10]. Last verified: October 2026. IIBA's BABOK page still points to version 3 [11].
The table below is our own mapping of book models to BABOK v3 sections. It is a study aid, not an official crosswalk, and the fit is closest where the names match.
Book model (RML)
Closest BABOK v3 technique or task
Process flow
10.35 Process Modelling
Use case
10.47 Use Cases and Scenarios
Roles and permissions matrix
10.39 Roles and Permissions Matrix
Org chart
10.32 Organizational Modelling
Ecosystem map
10.41 Scope Modelling (closest fit)
System interface table
10.24 Interface Analysis
Decision table, decision tree
10.17 Decision Modelling
Data dictionary
10.12 Data Dictionary
Data flow diagram
10.13 Data Flow Diagrams
Business data diagram
10.15 Data Modelling
State table, state diagram
10.44 State Modelling
KPI model
10.28 Metrics and KPIs
Feature tree
10.22 Functional Decomposition (closest fit)
Requirements mapping matrix
Task 5.1 Trace Requirements
Two warnings for exam use. First, always answer in BABOK terms: the exam does not test RML names, and some book models, such as the display-action-response model, have no direct BABOK technique. Second, the book says little about Strategy Analysis or Solution Evaluation, so it will not help with chapters 6 and 8.
Public feedback on this particular book is thin, so we separate what we found by who is speaking.
A reader comment (2013). The only reader comment we found on a business analysis resource site calls the book "Good reference material for experienced BA." and suggests it as new material for anyone considering a business analyst career [7].
The co-author, in practice (2022). Beatty writes that she moved from long lists of "shall" statements to visual modelling, and says the mapping matrix can reveal problems early instead of late in a project [5]. She is the book's author, so read this as the method's best case.
The co-author, in an interview (2012). She says "Pictures are easy, words are hard." and names the business objectives model as the most important one, because it ties features to business goals and supports scope cuts [6].
An independent business analyst (2013, updated 2023). A working analyst describes a rough domain model built in about two hours that gave stakeholders shared language, and says visual models make the requirements process faster [8]. She does not review this book; her experience supports the method in general.
A practitioner's catalogue of models (2021). The same analyst lists 22 visual models from ten years of work at six companies and notes that no project needs all of them [9]. This matches the book's advice to select models for the project [3].
We searched for Reddit and forum threads about the book and found none that discuss it directly. We also could not read the book's public reader ratings, so we do not quote them. If you have used the models on a real project, that evidence is missing from the public record.
Strengths and weaknesses
The book's strength is a usable catalogue of models; its weakness is that it is a catalogue.
Strengths
Covers objectives, people, systems and data in one consistent language, so models link to each other.
Gives a way to choose models by phase and project type instead of drawing everything [3].
The mapping matrix is a practical answer to "did we miss anything?" [5].
The publisher says the language has been used on hundreds of large-scale projects [1], and the authors' company still promotes it [4].
Weaknesses
Published in 2012, so it predates current product discovery and AI-assisted analysis.
Uses its own names, which can clash with BABOK vocabulary under exam pressure.
The authors' company sells related training, so the method has a commercial owner [4].
Little independent evidence of results: most public praise comes from the authors themselves [5][6].
Who should read it and who can skip it
Read it if you write or review requirements every week and want models beyond a basic process flow.
Read it if you are:
A business analyst with a year or more of experience who wants to model data, rules and interfaces, not only workflows.
A CBAP candidate who finds Requirements Analysis and Design Definition abstract and wants examples.
A product manager or Product Owner on an IT project with several teams and many stakeholders.
Skip it or read later if you are:
New to requirements. The authors themselves recommend starting with a general book [2].
In the last month before the CBAP exam. Spend that time on the BABOK Guide and scenario questions.
Working only on short product experiments, where heavy modelling adds little.
What to read alongside it
Pair it with one general requirements book and one techniques reference.
Start with our best business analysis books list, where Visual Models for Software Requirements is one of four top picks.
Is Visual Models for Software Requirements still relevant in 2026?
For the core idea, yes. Process flows, data dictionaries, state models and traceability matrices have not changed much. The book is a 2012 first edition, so it does not cover newer discovery or AI-assisted practices [1].
Is the book enough to pass CBAP?
No. CBAP questions are written around the BABOK Guide and scenarios [10]. The book gives you practice with several modelling techniques, but you still need the Guide and scenario practice.
What is the Requirements Modeling Language (RML)?
RML is the authors' set of 22 visual models in four groups: objectives, people, systems and data. ArgonDigital, the authors' company, offers a free download of the models and templates [4].
Should I read this or Software Requirements by Wiegers and Beatty first?
Read the general book first. The authors of Visual Models recommend a general requirements book for beginners [2]. Come to this book when you want to model, not just write.
Do I need all 22 models on a project?
No. The authors suggest selecting models by project phase and characteristics [3], and an independent analyst also notes that no project needs every model [9].
