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

Return to: C12 — Recovered Requirements Catalogue — topic detail

Evidence-qualified interpretation

Requirement: Evidence-qualified interpretation

The strongest direct findings are the Java/Swing-style form layer, the use of Form, ScreenRecord, FieldGroup, and TextBox, the JXTable structures in Orderform and State_List, and the declared customer, order, state, stock, item, and invoice-related fields. E0006

The help file supports documented behavior for query-by-example, customer deletion restrictions, state selection, order-entry descriptions, keyboard help, transaction examples, stock-option status, and report-menu entries. Runtime implementation is not established for those behaviors unless matching executable wiring is present, and the supplied range generally does not show it. E0004 E0006

The principal unresolved boundary is between generated UI and record artifacts, documentation or Informix-4GL examples, and executable business logic. In particular, the evidence does not establish live database execution, transaction handling, running-total calculation, state-validation callbacks, concurrent-access behavior, or successful backlog and stock-list report generation. E0004 E0006