Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.

Return to: Capability hierarchy

Capability hierarchy

Which business abilities exist, and which are parts of others?

This view models business abilities rather than technical components or screens. The main menu separates Customer, Orders, Stock, and Reports, supporting four distinct top-level business capabilities. E0001 Customer maintenance and order creation/viewing are supported by retained implementation evidence, while stock operations and some report options are present as documented or menu-level abilities but are explicitly unimplemented. E0002 E0003 The hierarchy therefore distinguishes implemented reporting from report options whose existence is documented but whose delivery is not established. E0002 E0004

Diagram

flowchart TD
  n22b619d324e78eb781e2["Customer management"]
  nf2a199793621e1aa82f9["Customer maintenance"]
  n93e97e5f9bbb031c6af2["Order entry"]
  n08dac1c3dddab026f08d["Order creation"]
  nd05f79993c8acd5cf06d["Customer order lookup"]
  n36acc450b67d06a8ae85["Stock management"]
  n5afda8a487f3f5113882["Reporting"]
  n741834085dbf9624afd9["Mailing-label reporting"]
  n0dc16612d38b11f7ff27["Accounts-receivable reporting"]
  n451575148c2a8318791a["Backlog reporting"]
  n27f7a1082d14090e615a["Stock-list reporting"]
  n22b619d324e78eb781e2 -.->|"Customer management includes customer maintenance (inferred)"| nf2a199793621e1aa82f9
  n93e97e5f9bbb031c6af2 -->|"Order entry includes order creation"| n08dac1c3dddab026f08d
  n93e97e5f9bbb031c6af2 -->|"Order entry includes customer order lookup"| nd05f79993c8acd5cf06d
  n5afda8a487f3f5113882 -->|"Reporting includes mailing-label reporting"| n741834085dbf9624afd9
  n5afda8a487f3f5113882 -->|"Reporting includes accounts-receivable reporting"| n0dc16612d38b11f7ff27
  n5afda8a487f3f5113882 -->|"Reporting includes backlog reporting"| n451575148c2a8318791a
  n5afda8a487f3f5113882 -->|"Reporting includes stock-list reporting"| n27f7a1082d14090e615a

Elements

Customer management

Kind: capability
Basis: reported
Description: Business ability for creating, locating, updating, and deleting customer records; the retained implementation also supports browsing customer query results and state selection. E0001 E0002
Evidence: E0001, E0002

Customer maintenance

Kind: capability
Basis: reported
Description: Customer-focused maintenance ability covering customer creation, query or browse, update, deletion, help, and state selection. E0002
Evidence: E0002

Order entry

Kind: capability
Basis: reported
Description: Business ability for entering orders with headers and line items, including customer selection or creation and invoice generation. E0001 E0002
Evidence: E0001, E0002

Order creation

Kind: capability
Basis: reported
Description: Order-entry ability with substantive implementation for collecting line items, inserting the order and items, committing or attempting rollback, and generating an invoice. E0002
Evidence: E0002

Customer order lookup

Kind: capability
Basis: reported
Description: Ability to select and view orders for a customer; order update and deletion are not established as implemented and are explicitly described as unimplemented in the retained evidence. E0002 E0004
Evidence: E0002, E0004

Stock management

Kind: capability
Basis: reported
Description: Business ability represented by stock add, find, update, and delete options, but each retained handler emits an unimplemented warning. Preloaded stock data and stock selection for orders do not establish stock maintenance functionality. E0002
Evidence: E0001, E0002

Reporting

Kind: capability
Basis: reported
Description: Business ability for producing reports, with retained implementation evidence for mailing labels and accounts receivable; backlog and stock-list reporting are documented or exposed as options but explicitly unimplemented. E0001 E0002 E0004
Evidence: E0001, E0002, E0004

Mailing-label reporting

Kind: capability
Basis: reported
Description: Implemented report ability for producing mailing labels, with output modes documented for file, printer, and screen. Exact report lifecycle behavior remains dependent on absent framework evidence. E0002
Evidence: E0002

Accounts-receivable reporting

Kind: capability
Basis: reported
Description: Implemented report ability for producing accounts-receivable reports, with output modes documented for file, printer, and screen. Exact report lifecycle behavior remains dependent on absent framework evidence. E0002
Evidence: E0002

Backlog reporting

Kind: capability
Basis: reported
Description: Report option present in the documented reporting scope, but the retained help and implementation evidence state that backlog reporting is currently unimplemented. E0002 E0004
Evidence: E0002, E0004

Stock-list reporting

Kind: capability
Basis: reported
Description: Report option present in the documented reporting scope, but the retained help and implementation evidence state that stock-list reporting is currently unimplemented. E0002 E0004
Evidence: E0002, E0004

Relationships

Customer management includes customer maintenance

From: Customer management
To: Customer maintenance
Relation: contains
Basis: inferred
Description: The main menu exposes Customer as a business module, while the retained customer implementation groups creation, query, update, deletion, help, and state selection as customer operations. This supports treating customer maintenance as a part of customer management. E0001 E0002
Evidence: E0001, E0002

Order entry includes order creation

From: Order entry
To: Order creation
Relation: contains
Basis: reported
Description: The Orders module exposes order addition, and the retained add-order flow performs customer selection or creation, header input, line-item collection, database insertion, transaction completion, and invoice generation. E0001 E0002
Evidence: E0001, E0002

Order entry includes customer order lookup

From: Order entry
To: Customer order lookup
Relation: contains
Basis: reported
Description: The retained order implementation provides customer-based order selection and viewing through its order retrieval flow. E0001 E0002
Evidence: E0001, E0002

Reporting includes mailing-label reporting

From: Reporting
To: Mailing-label reporting
Relation: contains
Basis: reported
Description: The Reports module includes a mailing-label option, and the retained report implementation contains mailing-label report logic. E0001 E0002
Evidence: E0001, E0002

Reporting includes accounts-receivable reporting

From: Reporting
To: Accounts-receivable reporting
Relation: contains
Basis: reported
Description: The Reports module includes an accounts-receivable option, and the retained report implementation contains accounts-receivable report logic. E0001 E0002
Evidence: E0001, E0002

Reporting includes backlog reporting

From: Reporting
To: Backlog reporting
Relation: contains
Basis: reported
Description: Backlog reporting is part of the documented reporting menu and interface surface, but the retained evidence explicitly says the option is not implemented. E0001 E0002 E0004
Evidence: E0001, E0002, E0004

Reporting includes stock-list reporting

From: Reporting
To: Stock-list reporting
Relation: contains
Basis: reported
Description: Stock-list reporting is part of the documented reporting menu and interface surface, but the retained evidence explicitly says the option is not implemented. E0001 E0002 E0004
Evidence: E0001, E0002, E0004

Gaps

The evidence does not establish a broader parent capability such as an application-wide “business management” capability, so no such relationship is modeled. E0001 E0002 The evidence conflicts on some broad descriptions: one account says order update and deletion and all four report types are supported, while retained implementation or help evidence identifies order update/delete, backlog reporting, and stock-list reporting as unimplemented. E0001 E0002 E0004 Stock management is likewise a documented business area, but its CRUD handlers are stubs. E0002 The supplied material does not establish whether customer order lookup should be a child of Customer management, Order entry, or both; it is placed under Order entry because the retained implementation describes it as an order flow. E0002 Runtime verification, complete interface coverage, and framework behavior are absent, so capability status remains bounded by published source and documentation rather than live inspection. E0002 E0004

Recovery limitations

• Some identified concepts have no supported connection.
• The view includes explicitly marked inference.

Sources

• E0001 — SHA256 26c6795c3bc4cc1018c05a3a14a9e8bfd1a7ac99525d062262c695930de1f2d0
• E0002 — SHA256 94dd964106462ec595f965ac2acdca80c48d31234c90d9f93ef18c5d0f26cf01
• E0003 — SHA256 d6724e53cd2df11bbcdc4c2e6b8487fa7ffa2317a121b3ebae2594a6130343e0
• E0004 — SHA256 a7fa93a436c487d708267db6e5038c7415b98377a56232869519d6206a15e7e9