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

Return to: Integration data flow

Integration data flow

Who sends which information to whom, in which direction, and through what mechanism?

This view traces supported information movement among the desktop modules, shared state, database, forms, and report-output boundary. The application is described as a Swing-oriented desktop application with Customer, Orders, Stock, Reports, and Exit commands; framework behavior is not independently available in the supplied material E0001E0002. “Sends” represents a documented or explicitly qualified transfer of commands, records, query results, shared values, or report output. It does not imply that the receiving operation is fully implemented.

Customer persistence and order insertion have source-level evidence involving SQL and database objects E0001E0002. Order update and deletion, stock CRUD, and backlog or stock-list reporting are exposed as interfaces or menu capabilities but are documented or observed as unimplemented, so no successful data flow is modeled for them E0002E0004. Shared-state and form relationships are marked inferred where the evidence shows data structures or UI artifacts without proving the runtime wiring E0002E0004.

Diagram

flowchart LR
  n93ce7f8da213abe966f7["D4_Main"]
  nbeb315584561928f9da4["Customer module"]
  n40fdd235ba106aad4a15["Orders module"]
  n2bcd4d445c98b418cfb4["Stock module"]
  n5a734c3cab79b3c0c356["Reports module"]
  n1c6c5406dbef594e24fb["Customer forms"]
  nd565d904c2c9d42a4948["Order forms"]
  ndc84b1a52a3692faed0e["Shared application state (inferred)"]
  n787d17f38ddccc0e1196["stores7 database"]
  nfd213ee064dd05e41798["Report output channels (inferred)"]
  n93ce7f8da213abe966f7 -->|"Main menu dispatches Customer command"| nbeb315584561928f9da4
  n93ce7f8da213abe966f7 -->|"Main menu dispatches Orders command"| n40fdd235ba106aad4a15
  n93ce7f8da213abe966f7 -->|"Main menu dispatches Stock command"| n2bcd4d445c98b418cfb4
  n93ce7f8da213abe966f7 -->|"Main menu dispatches Reports command"| n5a734c3cab79b3c0c356
  n1c6c5406dbef594e24fb -.->|"Customer forms provide customer input (inferred)"| nbeb315584561928f9da4
  nd565d904c2c9d42a4948 -.->|"Order forms provide order input (inferred)"| n40fdd235ba106aad4a15
  nbeb315584561928f9da4 -->|"Customer module persists customer records"| n787d17f38ddccc0e1196
  n787d17f38ddccc0e1196 -->|"Database returns customer query results"| nbeb315584561928f9da4
  n40fdd235ba106aad4a15 -->|"Orders module persists order data"| n787d17f38ddccc0e1196
  n787d17f38ddccc0e1196 -->|"Database returns order data"| n40fdd235ba106aad4a15
  ndc84b1a52a3692faed0e -.->|"Shared state supplies order context (inferred)"| n40fdd235ba106aad4a15
  n5a734c3cab79b3c0c356 -->|"Reports module emits report output"| nfd213ee064dd05e41798

Elements

D4_Main

Kind: component
Basis: reported
Description: Main entry component that starts the application, selects the stores7 database alias, and creates commands for Customer, Orders, Stock, Reports, and Exit E0001E0002.
Evidence: E0001, E0002

Customer module

Kind: component
Basis: reported
Description: Customer component supporting customer entry, query and browsing, update, deletion checks, and database persistence E0001E0002.
Evidence: E0001, E0002

Orders module

Kind: component
Basis: reported
Description: Orders component with implemented order creation, line-item handling, customer-based order viewing, transaction attempts, and invoice generation; update and delete handlers are unimplemented in the retained implementation E0002.
Evidence: E0001, E0002, E0004

Stock module

Kind: component
Basis: reported
Description: Stock component with menu handlers for add, query, update, and delete, each reported as unimplemented; stock data can nevertheless be preloaded and selected during order processing E0002.
Evidence: E0001, E0002

Reports module

Kind: component
Basis: reported
Description: Reports component with source-level implementations for mailing labels and accounts receivable, while backlog and stock-list reporting are reported as unimplemented E0002E0004.
Evidence: E0001, E0002, E0004

Customer forms

Kind: component
Basis: reported
Description: Generated customer UI artifacts expose customer number, name, company, address, city, state, ZIP, and phone fields, including a configured phone mask E0004.
Evidence: E0003, E0004

Order forms

Kind: component
Basis: reported
Description: Generated order UI artifacts expose order number, date, customer number, shipping instructions, backlog, purchase-order number, ship date, weight, charge, and paid date fields E0004.
Evidence: E0003, E0004

Shared application state

Kind: store
Basis: inferred
Description: Application-level shared state is represented by a HashMap containing customer and order objects, item, stock, and state arrays, counts, and the report print option; lifecycle, persistence, and thread safety are not established E0001E0002.
Evidence: E0001, E0002

stores7 database

Kind: store
Basis: reported
Description: Database target selected by the application through the stores7 alias; the schema is not supplied, although source references customer, orders, items, stock, manufacturer, and state tables E0001E0002.
Evidence: E0001, E0002

Report output channels

Kind: component
Basis: inferred
Description: Report output boundary covering file, printer, and screen modes represented by print_option values f, p, and s; the external report factory and lifecycle are not supplied E0002.
Evidence: E0002

Relationships

Main menu dispatches Customer command

From: D4_Main
To: Customer module
Relation: sends
Basis: reported
Description: The main menu provides a Customer command that dispatches work to the Customer module E0001E0002.
Evidence: E0001, E0002
Information: Customer command.
Mechanism: Menu command dispatch; the framework implementation is not supplied E0001E0002.

Main menu dispatches Orders command

From: D4_Main
To: Orders module
Relation: sends
Basis: reported
Description: The main menu provides an Orders command that dispatches work to the Orders module E0001E0002.
Evidence: E0001, E0002
Information: Orders command.
Mechanism: Menu command dispatch; the framework implementation is not supplied E0001E0002.

Main menu dispatches Stock command

From: D4_Main
To: Stock module
Relation: sends
Basis: reported
Description: The main menu exposes a Stock command and the Stock module defines corresponding handlers, although those handlers report that operations are unimplemented E0001E0002.
Evidence: E0001, E0002
Information: Stock command.
Mechanism: Menu command dispatch; no successful stock-operation transfer is established E0002.

Main menu dispatches Reports command

From: D4_Main
To: Reports module
Relation: sends
Basis: reported
Description: The main menu provides a Reports command that dispatches report operations to the Reports module E0001E0002.
Evidence: E0001, E0002
Information: Reports command.
Mechanism: Menu command dispatch; the framework implementation is not supplied E0001E0002.

Customer forms provide customer input

From: Customer forms
To: Customer module
Relation: sends
Basis: inferred
Description: Customer form artifacts expose the fields used by customer data entry, while the Customer module calls customer input routines and performs customer operations E0002E0004. The supplied evidence does not prove the exact event or binding path between the forms and module.
Evidence: E0002, E0004
Information: Customer identity, address, contact, state, and ZIP values.
Mechanism: Generated UI and framework field binding; exact mechanism unknown E0004.

Order forms provide order input

From: Order forms
To: Orders module
Relation: sends
Basis: inferred
Description: Order form artifacts expose order and charge fields, while the Orders module collects order headers and line items E0002E0004. The exact runtime binding between the generated forms and order methods is not established.
Evidence: E0002, E0004
Information: Order header values, shipping details, customer reference, charges, and payment-related fields.
Mechanism: Generated UI and framework field binding; exact mechanism unknown E0004.

Customer module persists customer records

From: Customer module
To: stores7 database
Relation: sends
Basis: reported
Description: Customer creation inserts into customer, updates use an UPDATE customer ... WHERE customer_num = ?, and deletion checks related orders before deleting E0001E0002.
Evidence: E0001, E0002
Information: Customer records and customer updates; deletion requests are conditional on the related-order check E0002.
Mechanism: Java SQL calls using database statements and result wrappers; exact schema and framework behavior are missing E0001E0002.
Control: Deletion is prevented when the related-order count is nonzero, although the query counts all orders rather than demonstrably only active orders E0002.

Database returns customer query results

From: stores7 database
To: Customer module
Relation: sends
Basis: reported
Description: Customer browsing executes a customer query and navigates returned rows through next, previous, first, last, select, and quit operations E0002.
Evidence: E0002
Information: Customer records returned by a customer query.
Mechanism: SQL query, ResultSet, and record wrappers E0001E0002.
Guard: The query predicate is built through Construct; its escaping and safety behavior are unknown E0002.

Orders module persists order data

From: Orders module
To: stores7 database
Relation: sends
Basis: reported
Description: Order creation begins a transaction, inserts an order, obtains a serial number, inserts item rows, and commits; rollback is attempted when order or item insertion reports failure E0002.
Evidence: E0001, E0002
Information: Order header, generated order identity, and line-item records.
Mechanism: Database transaction, SQL insertion, serial-number retrieval, commit, and rollback calls E0002.
Control: The completeness of rollback and status handling depends on missing DBHelper and ErrorHandler implementations E0002.

Database returns order data

From: stores7 database
To: Orders module
Relation: sends
Basis: reported
Description: The Orders module supports selecting and viewing orders for a customer and retrieves a serial number during order insertion E0002.
Evidence: E0002
Information: Customer-associated order records and generated order serial number.
Mechanism: SQL queries and database result handling; the exact schema is unknown E0001E0002.

Shared state supplies order context

From: Shared application state
To: Orders module
Relation: sends
Basis: inferred
Description: Shared state contains customer, order, item, stock, and state values that are used across the application; the supplied material supports shared application state but does not prove the exact access path into the Orders module E0001E0002.
Evidence: E0001, E0002
Information: Current customer and order context, item arrays, stock values, state values, and counts.
Mechanism: Application-level HashMap keyed through Application.GLOBALS_KEY; lifecycle and synchronization are unknown E0002.

Reports module emits report output

From: Reports module
To: Report output channels
Relation: sends
Basis: reported
Description: Implemented mailing-label and accounts-receivable reports select file, printer, or screen output using the global print option E0002.
Evidence: E0002
Information: Mailing-label or accounts-receivable report rows and formatted output.
Mechanism: Report factory and output lifecycle external to the supplied source; exact delivery mechanism is unknown E0002.
Guard: Backlog and stock-list output is not modeled as a successful flow because the corresponding handlers are explicitly unimplemented E0002E0004.

Gaps

The supplied evidence does not establish the exact runtime wiring between generated forms, framework fields, and module methods E0004. The implementations of the framework, database helper, error handler, report factory, and database schema are absent, limiting confidence in binding, SQL safety, transaction guarantees, report completion, and output delivery E0001E0002.

The customer deletion control is semantically unresolved: the message refers to active orders, but the shown query counts all orders for the customer E0002. The order-total calculation is also unresolved because a 1.1 multiplier appears alongside separately described 6.5% tax and 3.5% shipping calculations E0002.

Declared or documented update and delete order operations, stock CRUD, backlog reporting, and stock-list reporting are not supported as successful information flows because the retained implementation or help evidence identifies them as unimplemented E0002E0004. The supplied material also does not prove persistence, lifecycle, thread safety, or cross-session behavior for shared application state E0002.

Recovery limitations

• Ownership, mechanism or boundary controls remain explicitly unverified.
• The view includes explicitly marked inference.

Sources

• E0001 — SHA256 26c6795c3bc4cc1018c05a3a14a9e8bfd1a7ac99525d062262c695930de1f2d0
• E0002 — SHA256 94dd964106462ec595f965ac2acdca80c48d31234c90d9f93ef18c5d0f26cf01
• E0003 — SHA256 d6724e53cd2df11bbcdc4c2e6b8487fa7ffa2317a121b3ebae2594a6130343e0
• E0004 — SHA256 a7fa93a436c487d708267db6e5038c7415b98377a56232869519d6206a15e7e9