Source-derived document; reported behaviour, inference and evidence gaps are identified in the text.
Return to: 02 — Business Capability Map — topic detail
Stock management
In this document
Capability: Stock management
The stock module defines handlers for adding, querying, updating, and deleting stock records, but each handler reports that the option has not been implemented. The menu and method surface therefore exist without corresponding stock CRUD behavior in the retained implementation. E0001 E0002
Stock records are nevertheless preloaded into application data, and order entry can select stock items. Preloaded or selectable stock data does not establish that operators can create, modify, or delete stock records. The stock interface and related forms provide evidence of intended inventory scope, while the operational handlers remain stubs. E0002 E0004
The help material describes stock maintenance as allowing addition, lookup, modification, and removal of items. That documentation conflicts with the source implementation, which is the stronger evidence for delivered behavior in this snapshot. E0003 E0004
Capability: Stock management
The declared ID4_Stock.java.svn-base interface contains stock add, query, update, and delete methods. Separately, help entries 401–404 state that stock add, find, update, and delete options are “currently not implemented.” The interface establishes an API surface, while the help establishes a conflicting documented status; neither, by itself, proves a working stock-management flow. E0004 E0005 E0006
Stock1.java.svn-base provides structured record-oriented UI evidence involving manufacturer name, stock description, unit, and unit price, with FieldGroup, GridBagLayout, and ScreenRecord objects named stock, manufact, and s_stock. The supplied evidence does not identify a JTable, JXTable, or GridColumnModel in this form, so describing it as a visible table or grid would overstate the finding. E0005 E0006
Capability: Stock management
The stock menu offers add, find, update, delete, and exit commands. Each of the four stock-maintenance functions displays “This option has not been implemented” with the RED attribute. The help text independently documents Add-stock, Find-stock, Update-stock, and Delete-stock as not implemented, while Exit returns to the main menu. E0007 E0008
The main startup routine loads stock records through a join on stock and manufacturer details, orders them by stock number, stores them in p_stock starting at index one, stops after the count exceeds thirty, and records stock_cnt. The source’s pre-check increment and post-check decrement appear intended to retain at most thirty records, but correctness depends on cursor-loop and Informix-4GL array-bound semantics. No out-of-bounds failure is established. E0007 E0008
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.