Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: Capability hierarchy
Capability hierarchy
In this document
Which business abilities exist, and which are parts of others?
This view models the documented business abilities as a small acyclic hierarchy. The top-level grouping is inferred from evidence describing a menu-driven application covering customers, orders, stock, and reports; the source does not explicitly declare a capability taxonomy or parent-child menu nesting E0004. The four supplied business topics are retained as distinct capabilities E0004.
“Documented” does not mean runtime-verified here. Customer deletion rules, order-entry behavior, stock-option status, and report availability are primarily supported by help text, while interface declarations establish API surfaces rather than implemented behavior E0004. Backlog and stock-list reporting are explicitly documented as unimplemented, and stock add/find/update/delete options are likewise documented as unimplemented E0004E0006.
Diagram
Preparing diagram…
View Mermaid diagram source
flowchart TD
n67685fb570bde18b2bf8["Business operations (inferred)"]
na8ba2fb61eee071397a8["Customer maintenance"]
n84f07d9e391787a003bb["Order entry"]
n713d39dd2f2273bbc3f2["Stock management"]
n12b44b3163d300583214["Reporting"]
n67685fb570bde18b2bf8 -.->|"Business operations contains customer maintenance (inferred)"| na8ba2fb61eee071397a8
n67685fb570bde18b2bf8 -.->|"Business operations contains order entry (inferred)"| n84f07d9e391787a003bb
n67685fb570bde18b2bf8 -.->|"Business operations contains stock management (inferred)"| n713d39dd2f2273bbc3f2
n67685fb570bde18b2bf8 -.->|"Business operations contains reporting (inferred)"| n12b44b3163d300583214
Elements
Business operations
Kind: capability
Basis: inferred
Description: Umbrella business capability inferred from the documented menu-driven coverage of customers, orders, stock, and reports E0004.
Evidence: E0004
Customer maintenance
Kind: capability
Basis: reported
Description: Customer management covers documented customer add, find, update, and delete options. Deletion is documented as requiring confirmation and being blocked when the customer has active orders; the supplied evidence does not independently verify the runtime implementation E0004E0005E0006.
Evidence: E0004E0005E0006
Order entry
Kind: capability
Basis: reported
Description: Order entry is documented for existing customers and supports a scrolling line-item display with up to ten items. Order interfaces also declare order operations, totals, stock lookup, invoice, and report-related methods, but declarations do not establish complete implementation E0004E0005.
Evidence: E0004E0005
Stock management
Kind: capability
Basis: reported
Description: Stock management is represented by documented add, find, update, and delete options, but the help entries state that these options are currently not implemented. A stock interface declares add, query, update, and delete methods, which is evidence of an API surface rather than successful runtime behavior E0004E0005E0006.
Evidence: E0004E0005E0006
Reporting
Kind: capability
Basis: reported
Description: Reporting includes documented menu or interface coverage for labels and accounts receivable, while backlog and stock-list reporting are explicitly stated to be currently unimplemented. Report-interface methods and menu entries do not prove successful report generation E0004E0006.
Evidence: E0004E0006
Relationships
Business operations contains customer maintenance
From: Business operations
To: Customer maintenance
Relation: contains
Basis: inferred
Description: Customer maintenance is treated as a part of the broader business-operations grouping because the source describes customer management as one of the application’s menu-driven business areas E0004.
Evidence: E0004
Business operations contains order entry
From: Business operations
To: Order entry
Relation: contains
Basis: inferred
Description: Order entry is treated as a part of the broader business-operations grouping because the source describes order management and documented order-entry behavior as an application business area E0004E0005.
Evidence: E0004E0005
Business operations contains stock management
From: Business operations
To: Stock management
Relation: contains
Basis: inferred
Description: Stock management is treated as a part of the broader business-operations grouping because the source identifies stock as a distinct application menu and interface responsibility, despite documenting its options as unimplemented E0004E0005E0006.
Evidence: E0004E0005E0006
Business operations contains reporting
From: Business operations
To: Reporting
Relation: contains
Basis: inferred
Description: Reporting is treated as a part of the broader business-operations grouping because the source identifies reports as a distinct menu and interface responsibility, while qualifying the implementation status of specific reports E0004E0006.
Evidence: E0004E0006
Gaps
The source does not explicitly define a capability hierarchy or state that the four business areas share a parent; therefore, the “Business operations” grouping and all four containment relationships are inferred rather than directly reported E0004. No evidence establishes deeper parent-child relationships within customer maintenance, order entry, stock management, or reporting E0004E0006.
The evidence distinguishes declared interfaces, generated forms, and help or example text from executable runtime behavior. In particular, order update/delete operations are declared but documented as unimplemented, while backlog and stock-list reports are explicitly documented as unimplemented E0004. The supplied material also leaves database wiring, transaction execution, report generation, and several retained UI artifacts unresolved E0004E0006.
Recovery limitations
- The view includes explicitly marked inference.
Sources
- E0004 — SHA256
a7fa93a436c487d708267db6e5038c7415b98377a56232869519d6206a15e7e9 - E0005 — SHA256
cfb82f0c080e892e5b3b987574f1d65c56b7570c8650880e99078a02ca651535 - E0006 — SHA256
caaf28b181903beefb938762690d58ef2027cc70e645ab30a05ee9158cf684c0
Harten documentation of the Informix 4GL and Java source repository, from the retained 17 October 2026 export. The exact upstream revision analysed is not established. Source findings do not establish runtime behaviour or equivalence between the implementations.
Evidence identifiers are retained for traceability. The underlying analysis records are not included in this public edition; credential values are redacted. About this case study.