BPD assessment — gaps, test cases, requirements

Independent Architecture & Scope Guide

About the BPD assessment

A business process document says how a process will run: who does what, in which order, in which app, and where the design leaves the standard. Specforge reads it and works through what a program needs next. First what the document leaves out, which you can add and have written in. Then the requirements it carries, a test case for each step, and the scenarios that string those cases end to end. Each result points back to the line of the document it came from. Specforge does not sell the software or the implementation, so the reading is independent.

Who it's for

Test leads, functional leads and program managers who receive process designs and have to turn them into a test plan. Also finance and audit owners who need to know which requirements have a test behind them before a test cycle is called complete.

What you get

Instant Output
  • A completeness score with a scorecard, topic by topic, where the process area has one
  • The process the document does not cover, and what is missing from its own lists, as counts you can check
  • The regenerated document, with what you added marked as proposals to confirm
  • A requirements traceability matrix: groupings, typed work items and a trace to the tests that cover each one
  • One workbook with every output on its own sheet
  • Test cases on named apps and transactions, ready to download as a spreadsheet
  • Test scenarios within a document and across documents
  • A statement of how much of the test set system tables can evidence
  • The comprehensive BPD: the document with its requirements, test scenarios and test cases written in
  • Two ways to take the testing further: ask for the test execution to be automated on the tool set you own, and have the test results validated from your SAP tables

How it works

8-step end-to-end workflow
  1. 1Step 1
    Upload or paste the documentA Word file is best, because its headings, step tables and requirement lists come through intact. PDF and plain text work too, up to 8 MB. You see the text before anything is assessed.
  2. 2Step 2
    ScoreWhere a process area has a complete set of topics to score against, the assessment opens with a score: one point for each topic the document states with its specifics. Seven areas are scored today: asset accounting, planning and cost accounting, inventory accounting, accounts payable, credit management, commodity settlement and rework processing. A document in another area skips this step and is told why. A topic with no point can be added.
  3. 3Step 3
    GapsThe parts of the process the document does not cover, measured against the requirement corpus for that process area. Every one is listed. Open a gap to see the requirements the corpus holds for it, and add the ones that apply. Then what looks missing from its own lists: a build the register points at that the list does not describe, and whether it says how existing data reaches the new system. That conversion check runs on every document.
  4. 4Step 4
    RewriteThe document is written again with what you added. Each addition is marked as a proposal to confirm, and earns no point until a person confirms it. What you left out stays out, and the steps after this one do not raise it again. The regenerated document downloads as Word or Markdown.
  5. 5Step 5
    RequirementsGenerated from the document that goes forward. The requirements come back as a traceability matrix. Each sub-process is a grouping with one Feature row, and under it a row for every work item: configuration, a custom build, a master record, security, an operating procedure, a training manual. Each row keeps the document's own id and words, and shows the tests that cover it. A field the document makes mandatory is a row too.
  6. 6Step 6
    Test casesOne test case per step, on the Fiori app or transaction code the document names for it, with a precondition, an action and an expected result. Where a step states its postings, the postings are the expected result.
  7. 7Step 7
    Test scenariosThe test cases of each flow strung back to back in the document's order, with the hand-offs between owners and a refusal test at each control point. Assess a second document and the scenarios that run across both appear.
  8. 8Step 8
    CoverageEach test case is sorted by the system table that would prove it ran. Paste journal entries counted by transaction code and you see which cases have postings behind them, which have none, and what was posted that no test names.

Common questions

What is a BPD?
A business process document, also called a business process definition or design. It describes one process area of an implementation: the steps, the apps, the roles, the requirements and the custom builds.
Does it need a particular template?
No. Two common layouts are read: a design-led one with roles, a best-practice flow, gaps and a functional design, and a requirements-led one with a requirement register, key decisions, controls and a test list. Anything it cannot place it leaves out rather than guesses at.
Is a language model writing these test cases?
No. The requirements, gaps, test cases and scenarios are built by rule from the document, so the same document always gives the same result and every line can be traced. The only additions are the ones you choose on the scorecard and in the gaps, and each is marked as a proposal to confirm.
Why does my document have no score?
A score needs a complete set of topics for the process area. Seven exist so far: asset accounting, planning and cost accounting, inventory accounting, accounts payable, credit management, commodity settlement and rework processing. Every other document is assessed in full, without the score.
What is the difference between a test case and a test scenario?
A test case is one component check: a single step run in one app or transaction. A test scenario is a set of test cases strung back to back in the order the process runs.
How does coverage from tables work?
A posting leaves a journal entry that stores its transaction code. Given an extract of journal entries counted by transaction code, each test case that names a posting transaction can be checked against it. Display steps and master data changes leave other traces, and the assessment says which table would show each.
What happens to the document I upload?
It is read to produce the assessment and is not stored on our servers unless you save it. Your work in progress, the document, its assessment and what you added, is kept in your browser tab, so a refresh does not lose it, and it is gone when you close the tab. If you press Save, the document and your work are kept in your account so you can come back to them, until you delete them. Delete removes them for good.