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

Return to: Conceptual information

Conceptual information

What business information does the application manage, and how are those concepts related?

This view models the supplied business and reference concepts as separate entities, using form mappings, extracts, and catalog records as evidence rather than treating the published documents as live runtime verification E0009E0010. Customer, order, item, stock, manufacturer, and state concepts are kept distinct because the evidence assigns them different records, fields, or reference data E0009. The orders.unl extract supports order-record attributes, while syscolatt.unl supports metadata about named table columns rather than business transactions themselves E0009. Relationships are included only where a shared field, explicit form mapping, or catalog record supports them; multiplicities are omitted because the supplied evidence does not establish them E0009E0010.

Diagram

classDiagram
direction TB
  class n7ea909d80d73974d8487["Customer"]
  class n27999823376c86b116ef["Order"]
  class nb430feed980e958e381e["Order Item"]
  class nd26bf3ac890132c0bf72["Stock Record"]
  class n2237015bf221c576f868["Manufacturer"]
  class ncbc8197f42ca363f543b["State"]
  class nb878e08cb879dcd945e1["System Catalog Attribute"]
  n7ea909d80d73974d8487 -- n27999823376c86b116ef : Customer has orders
  n27999823376c86b116ef -- nb430feed980e958e381e : Order contains items
  nb430feed980e958e381e -- nd26bf3ac890132c0bf72 : Order Item references stock
  nd26bf3ac890132c0bf72 -- n2237015bf221c576f868 : Stock Record uses manufacturer
  n7ea909d80d73974d8487 -- ncbc8197f42ca363f543b : Customer uses state
  nb878e08cb879dcd945e1 -- n7ea909d80d73974d8487 : Catalog describes Customer
  nb878e08cb879dcd945e1 -- n27999823376c86b116ef : Catalog describes Order
  nb878e08cb879dcd945e1 -- nb430feed980e958e381e : Catalog describes Order Item
  nb878e08cb879dcd945e1 -- nd26bf3ac890132c0bf72 : Catalog describes Stock Record

Elements

Customer

Kind: entity
Basis: reported
Description: A customer record contains customer number, name, address, city, state, ZIP code, telephone, and in one order form, company information E0009. Customer records can be queried, added, updated, and deleted in the documented application flows E0009.
Evidence: E0009, E0010

Order

Kind: entity
Basis: reported
Description: An order record contains order number, order date, customer number, instructions, backlog, purchase-order number, ship date, ship weight, ship charge, and paid date E0009. The supplied order extract contains 15 visible records with identifiers ranging from 1001 through 1015 and date-like, flag, identifier, numeric, and optional date positions E0009.
Scope: orders.unl extract and stores7 order records
Evidence: E0009

Order Item

Kind: entity
Basis: reported
Description: An order item contains item number, stock number, manufacturer code, quantity, and total price; order forms also display description and unit price for each item row E0009. The order-entry source supports an array of item records and inserts or replaces items associated with an order E0009.
Evidence: E0009

Stock Record

Kind: entity
Basis: reported
Description: A stock record is represented in the displayed extract by six visible fields interpreted as stock number, manufacturer code, description, price, unit, and unit description E0010. The stock data includes sporting-goods descriptions, decimal prices, and case-or-each unit information E0009.
Evidence: E0009, E0010

Manufacturer

Kind: entity
Basis: reported
Description: Manufacturer reference data contains three-letter codes mapped to names, including SMT to Smith, ANZ to Anza, NRG to Norge, HSK to Husky, and HRO to Hero E0009. Stock-selection and stock-list forms expose manufacturer code or manufacturer name alongside stock information E0009.
Evidence: E0009

State

Kind: entity
Basis: reported
Description: State reference records contain a two-letter uppercase code and state name, with examples including AK/Alaska, CA/California, TX/Texas, and NY/New York E0009. State-selection forms map the code and name to the state table and provide repeated selectable rows E0009.
Evidence: E0009

System Catalog Attribute

Kind: entity
Basis: reported
Description: A system catalog attribute records a table name, column name, numeric attributes, flag-like values, and optionally a condition E0009. The extract includes catalog entries for customer, orders, items, and stock columns, including conditional metadata for items.total_price E0009.
Evidence: E0009

Relationships

Customer has orders

From: Customer
To: Order
Relation: relates_to
Basis: reported
Description: Order forms bind orders.customer_num, and customer deletion is blocked when matching orders exist, supporting a customer-to-order association E0009. The order-entry flow obtains a customer before accepting order data E0009.
Evidence: E0009

Order contains items

From: Order
To: Order Item
Relation: relates_to
Basis: reported
Description: Order-entry logic inserts an order and its items, queries an order together with its items, and deletes items using the selected order number E0009. The catalog extract also identifies items.order_num and order columns E0009.
Evidence: E0009

Order Item references stock

From: Order Item
To: Stock Record
Relation: relates_to
Basis: reported
Description: The order form maps an item row's stock number to items.stock_num, displays stock description and unit price, and the item-entry logic retrieves description and unit price using stock number and manufacturer code E0009.
Evidence: E0009

Stock Record uses manufacturer

From: Stock Record
To: Manufacturer
Relation: relates_to
Basis: reported
Description: Stock records contain a manufacturer-code field in the displayed source interpretation, and stock forms display manufacturer names alongside stock descriptions and prices E0010E0009. The supplied manufacturer extract maps the codes to names E0009.
Evidence: E0009, E0010

Customer uses state

From: Customer
To: State
Relation: relates_to
Basis: reported
Description: Customer forms bind the state field to customer.state, while the state-help function selects a state code from state reference records and assigns it to the customer record E0009.
Evidence: E0009

Catalog describes Customer

From: System Catalog Attribute
To: Customer
Relation: relates_to
Basis: reported
Description: The catalog extract contains a record for the customer table's city column and identifies table and column metadata in the same representation used for the other business tables E0009.
Evidence: E0009

Catalog describes Order

From: System Catalog Attribute
To: Order
Relation: relates_to
Basis: reported
Description: The catalog extract contains order-column records for order_num, order_date, po_num, and ship_instruct, with numeric attributes and flags E0009.
Evidence: E0009

Catalog describes Order Item

From: System Catalog Attribute
To: Order Item
Relation: relates_to
Basis: reported
Description: The catalog extract identifies item columns including item_num, order_num, stock_num, manu_code, quantity, and total_price E0009.
Evidence: E0009

Catalog describes Stock Record

From: System Catalog Attribute
To: Stock Record
Relation: relates_to
Basis: reported
Description: The catalog extract identifies stock columns including description and unit_price E0009.
Evidence: E0009

Gaps

The supplied evidence conflicts on the interpretation of the first fields in stock.unl: one finding says the first field contains manufacturer codes, while the displayed records and second-opinion analysis interpret the fields as stock number followed by manufacturer code E0009E0010. The latter interpretation is used here, but the conflict remains unresolved.

The evidence does not provide complete schema definitions, foreign-key constraints, or authoritative column types, so the relationships do not establish database-enforced integrity or multiplicity E0010. The possible relationship between items.order_num and orders.order_num is supported by field names and deletion logic, but whether it is enforced by a foreign key is unknown E0010. The supplied documents also do not establish whether the binary .frm files are semantically identical to the corresponding .per definitions E0010.

The order extract has no visible header row, and the semantic meaning of every position is not fully established from the extract alone E0009. The stock interpretation should therefore be verified against authoritative schema or source definitions before being treated as definitive E0010.

Sources

• E0009 — SHA256 c4ffb94922eae3cda2f1c6d6b1215da47b424d41fea52db3870783bd43051b30
• E0010 — SHA256 bd29371182d16de63a7651533fa5c84e151a01ea9bf23399f7f6ca0397ab0250