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

Return to: System context

System context

Where is the application boundary, who uses it, and which external systems interact with it?

This system-context view places the application boundary around the legacy Informix-4GL demonstration program and its user-facing menus and forms; internal routines, records, and form artifacts are intentionally excluded. E0007 The application supports customer management, order entry and lookup, mailing-label and accounts-receivable reporting, and main-menu navigation, while several stock, backlog, and order-maintenance options are explicitly unimplemented. E0007E0008

The primary human participant is an application user who operates menus, forms, queries, and reports. E0007 The database is modeled as an external system because the source declares the stores7 database and performs SQL operations against customer, order, item, stock, and state data. E0007 The evidence also identifies printer and operating-system file/exit destinations. E0007E0008

The database integration is source- and configuration-supported, not live-verified. Two published configuration files specify materially different hosts, ports, server names, and credentials, and the evidence does not establish precedence, deployment context, or whether both are used. E0008 A configured dependency or report destination is therefore not treated as proof of a particular runtime deployment.

Diagram

flowchart LR
  nab9812e40cc26eddaf64["Legacy Informix demonstration application (inferred)"]
  n18368ea38cee621e489f["Application user (inferred)"]
  n130eee0c0931718d5369["stores7 Informix database"]
  nbcb1962be9904f8e592b["Printer"]
  n98c007ec415e4d081c5b["Operating system"]
  n18368ea38cee621e489f -->|"User operates application"| nab9812e40cc26eddaf64
  nab9812e40cc26eddaf64 -->|"Application reads and writes database"| n130eee0c0931718d5369
  nab9812e40cc26eddaf64 -->|"Application sends reports to printer"| nbcb1962be9904f8e592b
  nab9812e40cc26eddaf64 -->|"Application uses operating system"| n98c007ec415e4d081c5b

Elements

Legacy Informix demonstration application

Kind: application
Basis: inferred
Description: The bounded application is a legacy Informix-4GL demonstration program with main navigation for Customer, Orders, Stock, Reports, and Exit, plus customer and order workflows and selected reports. E0007E0008 Its boundary excludes internal routines, data records, and binary or generated artifacts. E0007E0008
Evidence: E0007, E0008

Application user

Kind: actor
Basis: inferred
Description: A human user operates the main menu, customer forms, query-by-example searches, order entry, report options, help, and exit actions described by the source and help text. E0007
Evidence: E0007
Goal: Manage customers, enter or find orders, run supported reports, obtain help, and leave the application. E0007

stores7 Informix database

Kind: external_system
Basis: reported
Description: The source declares the stores7 database and customer table, while executable routines select, insert, update, and delete customer and order-related data. E0007 Published configurations reference Informix connectivity, but they disagree about endpoint and credential values, so the active runtime database is unresolved. E0008
Evidence: E0007, E0008

Printer

Kind: external_system
Basis: reported
Description: Supported report output can target PRINTER when the report option is set to printer output. E0007
Evidence: E0007

Operating system

Kind: external_system
Basis: reported
Description: Reports can be directed to an operating-system file, and the main-menu Exit command terminates the program to the operating system. E0007E0008
Evidence: E0007, E0008

Relationships

User operates application

From: Application user
To: Legacy Informix demonstration application
Relation: interacts
Basis: reported
Description: The user selects main-menu commands, enters customer and order data, performs query-by-example searches, selects report destinations, invokes help, and exits through terminal-oriented menus and forms. E0007
Trigger: A user selects a menu command, enters form data, invokes help, or chooses Exit. E0007
Guard: Customer updates and deletions require a selected customer; deletion also requires confirmation and is disallowed when active orders exist. E0007
Information: Customer fields, query criteria, order details, line items, report options, and help requests. E0007
Mechanism: Informix-4GL menus, forms, input fields, query-by-example, and keyboard commands. E0007
Trust change: No authentication, authorization, or other user-trust boundary is established in the supplied evidence. E0008
Control: Help text documents supported operations and explicitly identifies several unimplemented options. E0007E0008
Evidence type: Published source and help documentation; no live interaction was verified. E0008
Evidence: E0007, E0008

Application reads and writes database

From: Legacy Informix demonstration application
To: stores7 Informix database
Relation: interacts
Basis: reported
Description: The source declares stores7, maps customer forms to the customer table, and implements SQL-based customer, order, item, stock, and state access. E0007 Informix JDBC and database properties are also published, but conflicting configurations prevent identification of the runtime endpoint. E0008
Trigger: Application startup loads state and stock data; customer, order, search, update, delete, and report operations issue database work. E0007
Guard: Customer deletion is blocked when matching orders exist; order insertion commits only after order and item inserts succeed and rolls back on failure. E0007 Customer insertion has no explicit post-insert status check in the cited source. E0008
Information: Customer, order, item, stock, and state records, plus query criteria and report selections. E0007
Mechanism: Informix-4GL SQL and configured Informix JDBC connectivity. E0007
Trust change: No runtime connection, authentication result, or successful transaction was verified from the published material. E0008
Control: Order transaction commit/rollback and customer-deletion checks are described; configuration precedence and credential handling remain unresolved. E0007E0008
Evidence type: Source declarations, SQL behavior, and configuration excerpts; not live inspection. E0007E0008
Evidence: E0007, E0008

Application sends reports to printer

From: Legacy Informix demonstration application
To: Printer
Relation: interacts
Basis: reported
Description: Mailing-label and accounts-receivable reports support printer output, with the report destination selected through report options. E0007
Trigger: The user selects printer output and runs a supported report. E0007
Guard: The report must be one of the implemented report functions, such as mailing labels or accounts receivable; backlog and stock-list reporting are not implemented. E0007E0008
Information: Customer mailing-label data or accounts-receivable report data. E0007
Mechanism: Report output directed to the PRINTER destination. E0007
Trust change: No printer availability, delivery, or completion is established. E0008
Control: The user chooses file, printer, or screen output for the current session. E0007
Evidence type: Published executable-source findings; no printer execution was verified. E0008
Evidence: E0007, E0008

Application uses operating system

From: Legacy Informix demonstration application
To: Operating system
Relation: interacts
Basis: reported
Description: Report functions can write output to an operating-system file, and the main-menu Exit command terminates the program to the operating system. E0007E0008
Trigger: The user selects file report output or Exit. E0007
Guard: File output prompts for a filename and supplies documented defaults such as labels.out or ar.out when no filename is entered. E0007
Information: Report output and the requested program-termination action. E0007
Mechanism: File destination handling and program exit. E0007
Trust change: No file-permission result, path resolution, or process-termination observation is established. E0008
Control: Report destination is selected through the report-options menu; Exit clears the screen before terminating. E0007
Evidence type: Published source and help documentation; no operating-system behavior was live-verified. E0007E0008
Evidence: E0007, E0008

Gaps

The evidence does not establish which conflicting database configuration is active, whether the configured endpoint is reachable, or whether the published credentials are valid at runtime. E0008

The application’s deployment host and the runtime loading of generated Java artifacts, binary forms, orderform, state_list, and stock_sel are unresolved. E0008 Their absence from the supplied evidence is not proof that they are absent from the application. E0008

No authentication, authorization, user identity, printer availability, operating-system permissions, successful database session, or completed external interaction was demonstrated. E0008 Follow-up should identify the authoritative runtime configuration, deployment declarations, form artifacts, and execution evidence for each external boundary.

Recovery limitations

• The view includes explicitly marked inference.

Sources

• E0007 — SHA256 ce6dd2b00b79f008ecb98935db9ed709c044218bcdd4143008d56d06a04cff97
• E0008 — SHA256 1713f4e3d42ac5e2af28387ac6ff649f06bbe1683b11869af71326929d6a5f32