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 boundary around the desktop order-management application, identifies its interactive user, and shows the database integration supported by the supplied evidence E0011. The application is described as running on Java with a Swing-like user interface and JDBC database access E0011E0014.

Read the application–user relationship as interactive use of the desktop interface, and the application–database relationship as a technically evidenced integration through JDBC and SQL operations E0011. The database identity is not fully consistent across the sources: one source names the stores7 schema, another reports a connection URL using stores_demo, and the repository instructions describe installing stores7 E0011E0013E0014. Runtime verification was not performed; this view reflects published source and document evidence only E0012.

Diagram

flowchart LR
  n96b75dc39206861eb60b["Demo order-management application"]
  na625c6aa4e54e72af90d["Application user (inferred)"]
  nd8715bdc6de6b7cb8b92["Informix database"]
  na625c6aa4e54e72af90d -.->|"User operates application (inferred)"| n96b75dc39206861eb60b
  n96b75dc39206861eb60b -->|"Application accesses database"| nd8715bdc6de6b7cb8b92

Elements

Demo order-management application

Kind: application
Basis: reported
Description: Desktop-based order-management application for customer maintenance, order entry, stock management, and reporting, launched through com.ais.demo.D4_Main E0011E0014.
Evidence: E0011E0014

Application user

Kind: actor
Basis: inferred
Description: Interactive user who operates the desktop forms and prompts; the supplied evidence shows user-facing order, customer, stock, and reporting functions plus an interactive command prompt E0011E0012.
Evidence: E0011E0012
Goal: Use the desktop interface for supported order-management and reporting tasks E0011.

Informix database

Kind: external_system
Basis: reported
Description: Database system accessed through standard JDBC and SQL operations. The evidence associates it with Informix and reports both a stores7 schema and a configured stores_demo database URL, leaving the exact database naming relationship unresolved E0011E0013.
Evidence: E0011E0013E0014

Relationships

User operates application

From: Application user
To: Demo order-management application
Relation: interacts
Basis: inferred
Description: The application exposes desktop forms and interactive prompts for order-management and reporting activities, supporting an interaction between the user and the application E0011E0012.
Evidence: E0011E0012
Trigger: User interaction with the desktop interface or command prompt E0011E0012
Information: Customer, order, stock, report, and command input data E0011E0012
Mechanism: Swing-like forms and application-managed prompts E0011E0012

Application accesses database

From: Demo order-management application
To: Informix database
Relation: interacts
Basis: reported
Description: The application initializes a database connection and performs database interactions through JDBC, including order operations, customer-related queries, stock lookups, and report queries where supported by the supplied source E0011E0012.
Evidence: E0011E0012E0013
Trigger: Application startup and database-backed application flows E0011E0012
Information: Customer, order, order-item, stock, state, and report query data E0011E0013
Mechanism: JDBC through the application database API and SQL statements E0011E0012E0013

Gaps

The exact external database target is unresolved because the evidence reports stores7, stores_demo, and an Informix server configuration without establishing whether these are aliases, schema/database distinctions, or conflicting configurations E0011E0013E0014.

Customer behavior is not independently confirmed because the customer implementation is absent from the supplied evidence, although customer interfaces and callers are present E0012. Stock-management UI is evidenced, but stock CRUD methods are reported as unimplemented E0012.

The supplied material does not establish additional external-system integrations. Report output is described as configurable for file, printer, or screen, but the evidence does not prove a separate printer or file service boundary for this view E0011. The security scope of interactive command execution and the sanitization of query predicates also remain unresolved E0012.

Recovery limitations

• The view includes explicitly marked inference.

Sources

• E0011 — SHA256 be5e6746cc70e5b5af8caf785fb6efb113f28a7ab2080be3603561a173bbcb0c
• E0012 — SHA256 b17ef2d84bcd51af76724530e686489917c4271029456ef08648f9aa518bfa2b
• E0013 — SHA256 112de6889543e63b72f8ca740358ab46bcef10193b22310ea1cdeb85dbf5ba0e
• E0014 — SHA256 e5d61550897f3f357225936593a023fb98f078b01e2cd2c44f20a866fb0a3fef