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 as an acyclic hierarchy: broad menu-level abilities contain narrower implemented abilities where the supplied source supports that relationship. The main menu identifies Customer, Orders, Stock, and Reports as distinct operational areas E0001. The model treats customer management, order creation and lookup, and two report types as implemented; it does not treat placeholder operations as implemented capabilities E0002E0007.

“Stock management” is retained as a capability because the application exposes a stock-management area, but its add, find, update, and delete operations display unimplemented warnings E0001E0002E0007. Backlog reporting, stock-list reporting, order update, and order deletion are excluded as implemented child capabilities because the executable source and help text identify them as unimplemented E0002E0007. This is a document-based recovery, not live runtime verification; framework, schema, and some artifact behavior remain outside the evidence E0002.

Diagram

flowchart TD
  neb2a7625d9ae399f31bb["Customer management"]
  na89b8bead66f3e470d6c["Customer creation"]
  ndcc38a3b6599a310975b["Customer lookup"]
  n3657781bf772b1fc3a32["Customer update"]
  n5d06224ca143a2e74dd6["Customer deletion"]
  n9e2301e36c6ae7bca93f["Order entry"]
  n61838f5011dbb745d47f["Order creation"]
  n4efbb745585883c6c527["Order lookup"]
  n33b827faa4473b095970["Stock management"]
  ndc34a4486f8167910d3e["Reporting"]
  nf493b29ae289938fcff5["Mailing-label reporting"]
  n13e939a91ccdbe4a3c03["Accounts-receivable reporting"]
  neb2a7625d9ae399f31bb -->|"Customer management includes creation"| na89b8bead66f3e470d6c
  neb2a7625d9ae399f31bb -->|"Customer management includes lookup"| ndcc38a3b6599a310975b
  neb2a7625d9ae399f31bb -->|"Customer management includes update"| n3657781bf772b1fc3a32
  neb2a7625d9ae399f31bb -->|"Customer management includes deletion"| n5d06224ca143a2e74dd6
  n9e2301e36c6ae7bca93f -->|"Order entry includes creation"| n61838f5011dbb745d47f
  n9e2301e36c6ae7bca93f -->|"Order entry includes lookup"| n4efbb745585883c6c527
  ndc34a4486f8167910d3e -->|"Reporting includes mailing labels"| nf493b29ae289938fcff5
  ndc34a4486f8167910d3e -->|"Reporting includes accounts receivable"| n13e939a91ccdbe4a3c03

Elements

Customer management

Kind: capability
Basis: reported
Description: Implemented customer creation, query and browsing, update, deletion, help, and state selection are reported for the customer area E0002E0007.
Evidence: E0002E0007

Customer creation

Kind: capability
Basis: reported
Description: Customer entry inserts customer data into the customer table and supports repeated entry in the original source E0002E0007.
Evidence: E0002E0007

Customer lookup

Kind: capability
Basis: reported
Description: Customer query and browsing support selection and navigation through matching customer records E0002E0007.
Evidence: E0002E0007

Customer update

Kind: capability
Basis: reported
Description: Updating a selected customer executes an update against the matching customer record E0002E0007.
Evidence: E0002E0007

Customer deletion

Kind: capability
Basis: reported
Description: Customer deletion requires a selected customer, checks for related orders, requests confirmation, and deletes only after confirmation E0002E0007. The evidence describes the user-facing condition as active orders, while the reported query counts all matching orders E0002.
Evidence: E0002E0007

Order entry

Kind: capability
Basis: reported
Description: The orders area provides implemented order creation with customer selection or creation, header fields, line items, transaction handling, and invoice generation E0002E0007.
Evidence: E0002E0007

Order creation

Kind: capability
Basis: reported
Description: New orders can collect order date, purchase-order information, shipping instructions, and up to ten line items, then insert the order and its items in a transaction E0002E0007.
Evidence: E0002E0007

Order lookup

Kind: capability
Basis: reported
Description: Orders can be queried for a customer and displayed with their associated items E0002E0007.
Evidence: E0002E0007

Stock management

Kind: capability
Basis: reported
Description: A stock-management area exposes add, find, update, and delete operations, but each reported operation is currently a stub that displays an unimplemented warning E0001E0002E0007.
Evidence: E0001E0002E0007

Reporting

Kind: capability
Basis: reported
Description: The reports area exposes mailing-label, accounts-receivable, backlog, and stock-list options, with implemented logic established only for mailing labels and accounts receivable E0001E0002E0007.
Evidence: E0001E0002E0007

Mailing-label reporting

Kind: capability
Basis: reported
Description: Mailing-label reporting selects customers and supports file, printer, and screen destinations E0002E0007.
Evidence: E0002E0007

Accounts-receivable reporting

Kind: capability
Basis: reported
Description: Accounts-receivable reporting selects orders with a null paid date and supports file, printer, and screen destinations E0002E0007.
Evidence: E0002E0007

Relationships

Customer management includes creation

From: Customer management
To: Customer creation
Relation: contains
Basis: reported
Description: Customer creation is implemented as an operation within the customer area E0002E0007.
Evidence: E0002E0007

Customer management includes lookup

From: Customer management
To: Customer lookup
Relation: contains
Basis: reported
Description: Customer query and browsing are implemented operations within the customer area E0002E0007.
Evidence: E0002E0007

Customer management includes update

From: Customer management
To: Customer update
Relation: contains
Basis: reported
Description: Updating a selected customer is implemented within customer management E0002E0007.
Evidence: E0002E0007

Customer management includes deletion

From: Customer management
To: Customer deletion
Relation: contains
Basis: reported
Description: Deleting a selected customer is implemented as a customer-management operation, subject to related-order checks and confirmation E0002E0007.
Evidence: E0002E0007

Order entry includes creation

From: Order entry
To: Order creation
Relation: contains
Basis: reported
Description: The implemented add-order flow is the order-entry operation that collects headers and line items and persists the order E0002E0007.
Evidence: E0002E0007

Order entry includes lookup

From: Order entry
To: Order lookup
Relation: contains
Basis: reported
Description: Customer-based order selection and viewing are provided by the orders area alongside order creation E0002E0007.
Evidence: E0002E0007

Reporting includes mailing labels

From: Reporting
To: Mailing-label reporting
Relation: contains
Basis: reported
Description: Mailing-label generation is an implemented report operation in the reports area E0002E0007.
Evidence: E0002E0007

Reporting includes accounts receivable

From: Reporting
To: Accounts-receivable reporting
Relation: contains
Basis: reported
Description: Accounts-receivable generation is an implemented report operation in the reports area E0002E0007.
Evidence: E0002E0007

Gaps

The evidence conflicts on breadth of functionality. One supplied overview describes order update and deletion, all four report types, and stock operations as supported, while the detailed executable-source assessment reports those operations as explicit stubs E0001E0002. The detailed source and help evidence support the narrower interpretation used here, but the conflict should remain recorded E0003E0007.

The model does not establish a parent relationship between the four top-level abilities because the evidence presents them as separate main-menu modules rather than as parts of one another E0001E0007. It also does not model backlog reporting, stock-list reporting, order update, or order deletion as implemented capabilities because the supplied source identifies them as unimplemented E0002E0007.

The precise meaning of “active orders” in the customer-deletion rule is unresolved: the reported query counts all orders for the customer, while the message refers to active orders E0002. Framework behavior, database schema semantics, and runtime confirmation are also missing E0001E0002.

Recovery limitations

• Some identified concepts have no supported connection.

Sources

• E0001 — SHA256 26c6795c3bc4cc1018c05a3a14a9e8bfd1a7ac99525d062262c695930de1f2d0
• E0002 — SHA256 94dd964106462ec595f965ac2acdca80c48d31234c90d9f93ef18c5d0f26cf01
• E0003 — SHA256 d6724e53cd2df11bbcdc4c2e6b8487fa7ffa2317a121b3ebae2594a6130343e0
• E0007 — SHA256 ce6dd2b00b79f008ecb98935db9ed709c044218bcdd4143008d56d06a04cff97