Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: Conceptual information
Conceptual information
In this document
What business information does the application manage, and how are those concepts related?
This view models the business information named in the supplied evidence: customers, orders, order line items, stock, manufacturers, states, and invoices. E0011 E0013 It treats shared records and reference data as separate semantic concepts rather than as implementation modules or deployment components. E0012 The supplied source indicates that order entry uses customer and stock information, while invoice records combine order, item, stock, and manufacturer data. E0011 E0013
The relationships below are limited to connections supported by named fields, described flows, or explicit aggregation statements. Database table definitions, exact keys, and complete cardinalities are not established in the supplied evidence. E0011 E0012 Customer behavior is especially limited because the customer implementation is absent from the supplied evidence. E0012
Diagram
Preparing diagram…
View Mermaid diagram source
classDiagram
direction TB
class n82d5752984bfc593de5b["Customer"]
class n5870f1004c1e2491cf17["Order"]
class n75f89cf1f6a2c1c4133a["Order line item"]
class n0c54467e8a90a3c56a20["Stock item"]
class n64879fb7e1fe329e2967["Manufacturer (inferred)"]
class n31aa153118fb49ae9303["State"]
class ncf4a0557d11fc1b1623b["Invoice"]
n82d5752984bfc593de5b -- n5870f1004c1e2491cf17 : Customer places order
n5870f1004c1e2491cf17 -- n75f89cf1f6a2c1c4133a : Order has line item
n75f89cf1f6a2c1c4133a .. n0c54467e8a90a3c56a20 : Line item identifies stock (inferred)
n0c54467e8a90a3c56a20 .. n64879fb7e1fe329e2967 : Stock item has manufacturer (inferred)
n82d5752984bfc593de5b .. n31aa153118fb49ae9303 : Customer uses state (inferred)
ncf4a0557d11fc1b1623b -- n5870f1004c1e2491cf17 : Invoice summarizes order
ncf4a0557d11fc1b1623b -- n75f89cf1f6a2c1c4133a : Invoice includes line item
Elements
Customer
Kind: entity
Basis: reported
Description: Customer profiles contain customer identifiers, personal names, company names, and address details including city, state, and ZIP code. E0013 Customer information is used by order-related flows and mailing-label reporting. E0011 E0012
Evidence: E0011 E0013
Order
Kind: entity
Basis: reported
Description: An order contains order-number, order-date, purchase-order-number, and shipping-instruction information. E0013 The order-entry flow validates a customer, collects order-header data, accepts line items, calculates totals, and commits the order and its items when the required operations succeed. E0011 E0012
Evidence: E0011 E0012 E0013
Order line item
Kind: entity
Basis: reported
Description: Order entry supports multiple line items, performs stock lookups, and inserts the items as part of order creation. E0011 Invoice records include item number, stock number, quantity, and total-price information. E0013
Evidence: E0011 E0013
Stock item
Kind: entity
Basis: reported
Description: Stock records contain stock number, manufacturer code, manufacturer name, description, unit price, and unit description. E0013 Stock data is loaded into bounded in-memory reference data, with evidence of capacity for 30 stock rows; stock CRUD methods are present as menu options but are unimplemented in the supplied range. E0012
Evidence: E0012 E0013
Manufacturer
Kind: entity
Basis: inferred
Description: Manufacturer is a distinct business concept represented by manufacturer code and manufacturer name on stock records and invoice records. E0013
Evidence: E0013
State
Kind: entity
Basis: reported
Description: State reference data provides two-character state codes mapped to full state names for address validation. E0013 State records are loaded into bounded in-memory data with capacity for 50 state rows. E0012
Evidence: E0012 E0013
Invoice
Kind: entity
Basis: reported
Description: Invoice records aggregate order, item, stock, and manufacturer information, including pricing, quantities, shipping details, descriptions, unit data, and manufacturer names. E0013 The invoice flow generates a detailed report for a specific order. E0011
Evidence: E0011 E0013
Relationships
Customer places order
From: Customer
To: Order
Relation: relates_to
Basis: reported
Description: The order-entry flow validates a customer before collecting and committing order data, and order retrieval queries orders for a specific customer. E0011 The exact customer-to-order key and multiplicity are not established. E0011 E0012
Evidence: E0011 E0012
Order has line item
From: Order
To: Order line item
Relation: relates_to
Basis: reported
Description: Order creation inserts the order header and then inserts its items, and the invoice model contains both order-level and item-level fields. E0011 E0013
Evidence: E0011 E0013
Line item identifies stock
From: Order line item
To: Stock item
Relation: relates_to
Basis: inferred
Description: Order entry performs stock lookups for line items, and invoice records associate item quantities and prices with a stock number. E0011 E0013 The supplied evidence does not establish whether the stock number is a formal key or whether every stock item may appear on multiple orders. E0012
Evidence: E0011 E0012 E0013
Stock item has manufacturer
From: Stock item
To: Manufacturer
Relation: relates_to
Basis: inferred
Description: Stock records carry manufacturer code and manufacturer name, while invoice records carry manufacturer code and manufacturer name alongside stock information. E0013 A separate manufacturer record structure is not supplied. E0013
Evidence: E0013
Customer uses state
From: Customer
To: State
Relation: relates_to
Basis: inferred
Description: Customer address data includes a state field, and state lookup data maps two-character codes to full state names for address validation. E0013 The supplied evidence does not establish whether state is stored as a formal foreign-key relationship. E0012 E0013
Evidence: E0012 E0013
Invoice summarizes order
From: Invoice
To: Order
Relation: relates_to
Basis: reported
Description: The invoice flow produces an invoice for a specific order, and invoice records include order number, order date, purchase-order number, shipping instructions, shipping date, and shipping charge. E0011 E0013
Evidence: E0011 E0013
Invoice includes line item
From: Invoice
To: Order line item
Relation: relates_to
Basis: reported
Description: Invoice records include item number, stock number, quantity, total price, unit price, unit, and unit description, supporting an invoice relationship to order-line information. E0013
Evidence: E0013
Gaps
The exact database schema, key definitions, and relationship multiplicities are not documented in the supplied Java evidence, so no multiplicities are asserted. E0011 E0012 Customer validation, creation, selection, and status behavior remain unresolved because the declared customer interface is present but its implementation is absent. E0012
The evidence supports stock and state as shared, bounded in-memory reference data, but it does not establish whether those records are authoritative database entities, how refresh works, or how overflow is communicated to users. E0012 Manufacturer is inferred from fields rather than supported by a supplied standalone manufacturer record. E0013 The evidence also does not establish whether an invoice is persisted business information or only a generated report record. E0011 E0013
Recovery limitations
- The view includes explicitly marked inference.
Sources
- E0011 — SHA256
be5e6746cc70e5b5af8caf785fb6efb113f28a7ab2080be3603561a173bbcb0c - E0012 — SHA256
b17ef2d84bcd51af76724530e686489917c4271029456ef08648f9aa518bfa2b - E0013 — SHA256
112de6889543e63b72f8ca740358ab46bcef10193b22310ea1cdeb85dbf5ba0e
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.