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 view places the boundary around the legacy Informix-4GL demo application. The supplied source describes customer management, order entry, customer and order lookup, and reporting, while stock maintenance, backlog reporting, stock-list reporting, and order update/delete are described as incomplete. E0008

The application is used through interactive menus, prompts, forms, searches, and confirmation actions. E0009 It connects to and queries the stores7 database, whose tables supply customer, order, item, stock, state, and manufacturer data. E0009 That database is therefore modeled as an external system interaction, not as an internal application component.

The supplied .per files describe forms, while several compiled .frm files could not be analyzed as text; the form sources do not prove identity with the compiled artifacts. E0009E0010 No additional external integration is established by the supplied evidence.

Diagram

flowchart LR
  na6b9885e5eefdf9420de["Legacy Informix-4GL demo application"]
  na82c92860afbd3757ef5["Application User (inferred)"]
  n529c389b6ad117c69ba6["stores7 Database"]
  na82c92860afbd3757ef5 -->|"User operates application"| na6b9885e5eefdf9420de
  na6b9885e5eefdf9420de -->|"Application reads and updates database"| n529c389b6ad117c69ba6

Elements

Legacy Informix-4GL demo application

Kind: application
Basis: reported
Description: The source describes a legacy Informix-4GL demo application supporting customer management, order entry, customer and order lookup, mailing-label reporting, and accounts-receivable reporting. E0008
Evidence: E0008, E0009

Application User

Kind: actor
Basis: inferred
Description: A person interacts with the application through privileged-status prompts, menu commands, customer and order searches, form input, browsing controls, and delete confirmations. E0009
Evidence: E0009
Goal: Manage customers and orders, search records, enter order data, and view available reports. E0008E0009

stores7 Database

Kind: external_system
Basis: reported
Description: The application source connects to a database named stores7; source programs issue customer, order, item, stock, state, and manufacturer queries and updates against it. E0009
Evidence: E0009

Relationships

User operates application

From: Application User
To: Legacy Informix-4GL demo application
Relation: interacts
Basis: reported
Description: The application prompts the user for privilege status, exposes menus, accepts customer and order input, supports search and browsing, and requests confirmation for deletion. E0009
Evidence: E0009
Trigger: A user selects a menu command or enters a response in an application prompt. E0009
Information: Customer details, order details, search criteria, item data, privilege status, and confirmation responses. E0009
Mechanism: Interactive Informix-4GL menus, forms, prompts, and scroll-cursor browsing. E0009
Trust change: The application accepts user-supplied business data and authorization-related input; the evidence does not establish a separate authentication mechanism. E0009
Control: Privileged users receive all menu options, while other users receive only Query, Detail, Switch, and Exit in the main menu. E0009
Evidence type: Source-code description. E0009

Application reads and updates database

From: Legacy Informix-4GL demo application
To: stores7 Database
Relation: interacts
Basis: reported
Description: The application connects to stores7, queries customer and order records, retrieves stock and state information, and inserts, updates, or deletes customer, order, and item records. E0009
Evidence: E0009
Trigger: A user performs a query, adds or modifies data, or requests deletion. E0009
Guard: Some operations require a selected record, privilege-dependent menu access, successful customer lookup, or confirmation. E0009
Information: Customer, order, item, stock, state, manufacturer, pricing, shipping, and payment-related fields. E0009
Mechanism: Informix-4GL database connection, SQL statements, prepared queries, and cursors. E0009
Trust change: The application submits user-entered or calculated values to the database and displays database results; transaction and constraint behavior are not fully established. E0010
Control: Customer deletion is blocked when matching orders exist, and order deletion is blocked when matching items exist; other deletion and transaction behavior has unresolved source-level issues. E0009E0010
Evidence type: Source-code description and qualified source analysis. E0009E0010

Gaps

The evidence does not establish a separate authentication or identity service; the privileged-status prompt sets a local privilege flag based on a y or Y response. E0009

The database schema, foreign-key constraints, transaction behavior, and exact SQL column definitions are not supplied. These omissions leave the reliability of some order and item deletion paths unresolved. E0010

The relationship between the source-level .per forms and the compiled .frm artifacts is unverified because several compiled forms were binary or contained unsupported NUL data. E0009E0010

The supplied material does not establish any external system beyond stores7; additional integrations should not be inferred from referenced files, form definitions, or build artifacts. E0010

Recovery limitations

• The view includes explicitly marked inference.

Sources

• E0008 — SHA256 1713f4e3d42ac5e2af28387ac6ff649f06bbe1683b11869af71326929d6a5f32
• E0009 — SHA256 c4ffb94922eae3cda2f1c6d6b1215da47b424d41fea52db3870783bd43051b30
• E0010 — SHA256 bd29371182d16de63a7651533fa5c84e151a01ea9bf23399f7f6ca0397ab0250