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 the documented business abilities as an acyclic hierarchy of capabilities, separating customer, order, stock, and reporting concerns. The source identifies these as distinct operational modules, while the parent-child relationships below are inferred from the operations grouped within each module rather than explicitly declared as a hierarchy E0001 E0004.

Implemented behavior is distinguished from menu entries, interface declarations, help text, or documented intent. In particular, customer operations and order creation/viewing have implementation evidence, while stock operations and several order and report operations are explicitly unimplemented in the retained Java source E0002. Conflicting help documentation describes some unimplemented operations as available, so those capabilities remain represented with their implementation status qualified E0003 E0004.

Diagram

flowchart TD
  n61f8ef5db077a36408c5["Customer management"]
  n2d580640433500e0ba5f["Customer creation"]
  n0f2477723fd100f696da["Customer query and browse"]
  nf32034ead98af007606b["Customer update"]
  n37fa309ebc09d831c841["Customer deletion"]
  n355ab7d073075271e772["Order entry"]
  nabf31ab9163eceb564a6["Order creation"]
  nd21b915d6a72de522de5["Line-item entry"]
  n085d3d065896fab81b49["Customer-based order viewing"]
  nb0a0b96f1c46adad31fc["Order update"]
  ncff37461cab42aeec573["Order deletion"]
  n7a494ee8459b5a587562["Stock management"]
  neffdc62e146a9d4a79b7["Reporting"]
  n56c456a8eabe05581730["Mailing-label reporting"]
  n1e09518c6c3813484bc1["Accounts-receivable reporting"]
  n6abc3ec621a30fc8f22c["Backlog reporting"]
  na95a19fcd1aad416c567["Stock-list reporting"]
  n61f8ef5db077a36408c5 -.->|"Customer management includes customer creation (inferred)"| n2d580640433500e0ba5f
  n61f8ef5db077a36408c5 -.->|"Customer management includes customer query and browse (inferred)"| n0f2477723fd100f696da
  n61f8ef5db077a36408c5 -.->|"Customer management includes customer update (inferred)"| nf32034ead98af007606b
  n61f8ef5db077a36408c5 -.->|"Customer management includes customer deletion (inferred)"| n37fa309ebc09d831c841
  n355ab7d073075271e772 -.->|"Order entry includes order creation (inferred)"| nabf31ab9163eceb564a6
  n355ab7d073075271e772 -.->|"Order entry includes line-item entry (inferred)"| nd21b915d6a72de522de5
  n355ab7d073075271e772 -.->|"Order entry includes customer-based order viewing (inferred)"| n085d3d065896fab81b49
  n355ab7d073075271e772 -.->|"Order entry includes order update (inferred)"| nb0a0b96f1c46adad31fc
  n355ab7d073075271e772 -.->|"Order entry includes order deletion (inferred)"| ncff37461cab42aeec573
  neffdc62e146a9d4a79b7 -.->|"Reporting includes mailing-label reporting (inferred)"| n56c456a8eabe05581730
  neffdc62e146a9d4a79b7 -.->|"Reporting includes accounts-receivable reporting (inferred)"| n1e09518c6c3813484bc1
  neffdc62e146a9d4a79b7 -.->|"Reporting includes backlog reporting (inferred)"| n6abc3ec621a30fc8f22c
  neffdc62e146a9d4a79b7 -.->|"Reporting includes stock-list reporting (inferred)"| na95a19fcd1aad416c567

Elements

Customer management

Kind: capability
Basis: reported
Description: The customer module covers customer creation, querying and browsing, updating, deletion, help, and state selection. Customer deletion is constrained by related-order checks, although the evidence does not establish whether those checks identify only active orders E0001 E0002.
Evidence: E0001 E0002

Customer creation

Kind: capability
Basis: reported
Description: Customer creation is implemented through customer input followed by insertion into the customer data set E0002.
Evidence: E0002

Customer query and browse

Kind: capability
Basis: reported
Description: Customer querying and browsing are implemented with ordered results and navigation actions including next, previous, first, last, select, and quit E0002.
Evidence: E0002

Customer update

Kind: capability
Basis: reported
Description: Customer updates are implemented through an update operation addressed by customer number E0002.
Evidence: E0002

Customer deletion

Kind: capability
Basis: reported
Description: Customer deletion is implemented with a related-order count check before deletion. The source message refers to active orders, but the reported query counts all orders for the customer; the intended business rule is unresolved E0002.
Evidence: E0002

Order entry

Kind: capability
Basis: reported
Description: The Orders module provides order creation with header data, line items, transaction handling, and invoice generation, and also provides customer-based order viewing E0001 E0002.
Evidence: E0001 E0002

Order creation

Kind: capability
Basis: reported
Description: Order creation includes customer selection or creation, header input, line-item collection, order insertion, item insertion, commit or rollback handling, and invoice generation E0002.
Evidence: E0002

Line-item entry

Kind: capability
Basis: reported
Description: Order entry collects line items through a tabular input flow; the help documentation describes up to ten line items in a scrolling entry array E0002 E0003.
Evidence: E0002 E0003

Customer-based order viewing

Kind: capability
Basis: reported
Description: The order module supports selecting and viewing orders for a customer E0002.
Evidence: E0002

Order update

Kind: capability
Basis: reported
Description: Order update is a declared or menu-level capability, but the retained implementation displays an unimplemented message. Help documentation also describes update-order as currently unimplemented E0002 E0003.
Evidence: E0002 E0003

Order deletion

Kind: capability
Basis: reported
Description: Order deletion is a declared or menu-level capability, but the retained implementation displays an unimplemented message. Help documentation also describes delete-order as currently unimplemented E0002 E0003.
Evidence: E0002 E0003

Stock management

Kind: capability
Basis: reported
Description: The stock module exposes add, query, update, and delete operations, but each retained handler reports that it has not been implemented. Stock records may nevertheless be preloaded and selectable during order entry E0002.
Evidence: E0002

Reporting

Kind: capability
Basis: reported
Description: The reporting module provides report operations for mailing labels, accounts receivable, backlog, and stock lists, but only the first two have implementation evidence in the retained Java source E0001 E0002.
Evidence: E0001 E0002

Mailing-label reporting

Kind: capability
Basis: reported
Description: Mailing-label reporting contains report logic and supports file, printer, or screen output modes, subject to limitations in the external report framework E0002.
Evidence: E0002

Accounts-receivable reporting

Kind: capability
Basis: reported
Description: Accounts-receivable reporting contains report logic and supports file, printer, or screen output modes, subject to limitations in the external report framework E0002.
Evidence: E0002

Backlog reporting

Kind: capability
Basis: reported
Description: Backlog reporting is documented and exposed as a report operation, but the retained implementation explicitly reports that it has not been implemented E0002 E0003.
Evidence: E0002 E0003

Stock-list reporting

Kind: capability
Basis: reported
Description: Stock-list reporting is documented and exposed as a report operation, but the retained implementation explicitly reports that it has not been implemented E0002 E0003.
Evidence: E0002 E0003

Relationships

Customer management includes customer creation

From: Customer management
To: Customer creation
Relation: contains
Basis: inferred
Description: Customer creation is one of the operations reported for the customer module, so it is modeled as a child capability of customer management E0001 E0002.
Evidence: E0001 E0002

Customer management includes customer query and browse

From: Customer management
To: Customer query and browse
Relation: contains
Basis: inferred
Description: Querying and browsing customer records are reported as customer-module operations, so they are modeled under customer management E0001 E0002.
Evidence: E0001 E0002

Customer management includes customer update

From: Customer management
To: Customer update
Relation: contains
Basis: inferred
Description: Updating customer records is reported as a customer-module operation, so it is modeled under customer management E0001 E0002.
Evidence: E0001 E0002

Customer management includes customer deletion

From: Customer management
To: Customer deletion
Relation: contains
Basis: inferred
Description: Deleting customer records is reported as a customer-module operation, so it is modeled under customer management E0001 E0002.
Evidence: E0001 E0002

Order entry includes order creation

From: Order entry
To: Order creation
Relation: contains
Basis: inferred
Description: The order module’s substantive implemented flow is order creation, including headers, items, persistence, and invoicing E0002.
Evidence: E0002

Order entry includes line-item entry

From: Order entry
To: Line-item entry
Relation: contains
Basis: inferred
Description: Line-item collection is a step within the documented order-entry flow E0002 E0003.
Evidence: E0002 E0003

Order entry includes customer-based order viewing

From: Order entry
To: Customer-based order viewing
Relation: contains
Basis: inferred
Description: Customer-based order selection and viewing are reported as operations of the Orders module E0001 E0002.
Evidence: E0001 E0002

Order entry includes order update

From: Order entry
To: Order update
Relation: contains
Basis: inferred
Description: Order update is exposed by the Orders module, but its implementation is explicitly unimplemented; the relationship represents the module’s declared capability surface, not delivered functionality E0002 E0003.
Evidence: E0002 E0003

Order entry includes order deletion

From: Order entry
To: Order deletion
Relation: contains
Basis: inferred
Description: Order deletion is exposed by the Orders module, but its implementation is explicitly unimplemented; the relationship represents the module’s declared capability surface, not delivered functionality E0002 E0003.
Evidence: E0002 E0003

Reporting includes mailing-label reporting

From: Reporting
To: Mailing-label reporting
Relation: contains
Basis: inferred
Description: Mailing-label reporting is one of the report operations identified for the reporting module and has implementation evidence E0001 E0002.
Evidence: E0001 E0002

Reporting includes accounts-receivable reporting

From: Reporting
To: Accounts-receivable reporting
Relation: contains
Basis: inferred
Description: Accounts-receivable reporting is one of the report operations identified for the reporting module and has implementation evidence E0001 E0002.
Evidence: E0001 E0002

Reporting includes backlog reporting

From: Reporting
To: Backlog reporting
Relation: contains
Basis: inferred
Description: Backlog reporting is exposed as a reporting operation, but the retained implementation and help documentation characterize it as unimplemented E0002 E0003.
Evidence: E0002 E0003

Reporting includes stock-list reporting

From: Reporting
To: Stock-list reporting
Relation: contains
Basis: inferred
Description: Stock-list reporting is exposed as a reporting operation, but the retained implementation and help documentation characterize it as unimplemented E0002 E0003.
Evidence: E0002 E0003

Gaps

The evidence does not provide an explicit business-capability hierarchy; the parent-child edges are therefore inferred from module boundaries and operation groupings rather than directly declared E0001 E0004.

Order update and deletion, stock management operations, backlog reporting, and stock-list reporting have conflicting documentation: interfaces, menus, or help text expose them, while retained implementations report them as unimplemented E0002 E0003 E0004.

The intended meaning of “active orders” in customer deletion is unresolved because the reported query counts all orders associated with the customer E0002. The supplied evidence also does not establish whether stock selection during order entry constitutes a standalone stock-management capability or only supporting data access E0002.

Further source or runtime evidence would be required to confirm the authoritative hierarchy, distinguish declared capabilities from delivered capabilities, and resolve the contradictory documentation.

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