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

Return to: Actor journeys

Actor journeys

Who is trying to achieve what, and which actions and handoffs lead to the outcome?

This view models two documented operator journeys: customer maintenance and order entry. The evidence describes menu/help behavior and form structures, but does not prove that the Java runtime executes every documented step. E0004 E0005 Customer deletion is conditional on confirmation and the absence of active orders, while order update and deletion are explicitly described as unimplemented. E0004 The actor identity, controller wiring, database execution, and runtime handoffs are not established. E0005 E0006

Diagram

flowchart TD
  n73f140448dfb40d4df86["Application operator (inferred)"]
  nb6e8af7d092c218f44b4["Customer maintenance"]
  n3e537728b73bda46f683["Customer record maintained"]
  nc9d94775dbd94558dc42["Select existing customer"]
  n403a371b88360c2b78bc["Enter new order"]
  n8e9dcb69f46ad56806c7["New order documented"]
  n73f140448dfb40d4df86 -->|"Begin customer maintenance"| nb6e8af7d092c218f44b4
  nb6e8af7d092c218f44b4 -->|"Maintain customer result"| n3e537728b73bda46f683
  n73f140448dfb40d4df86 -->|"Begin order entry"| nc9d94775dbd94558dc42
  nc9d94775dbd94558dc42 -->|"Proceed to order entry"| n403a371b88360c2b78bc
  n403a371b88360c2b78bc -->|"Complete documented order entry"| n8e9dcb69f46ad56806c7

Elements

Application operator

Kind: actor
Basis: inferred
Description: An application operator is inferred from the menu-driven customer and order functions described in the help material. E0004
Evidence: E0004, E0005
Goal: Maintain customer records and enter orders for existing customers. E0005

Customer maintenance

Kind: action
Basis: reported
Description: The documented customer journey provides add, find, update, and delete options. Deletion requires confirmation and is blocked when the customer has active orders; runtime implementation is not independently verified. E0004 E0005
Evidence: E0004, E0005
Owner: Application operator

Customer record maintained

Kind: outcome
Basis: reported
Description: Customer maintenance is documented as supporting customer record changes, subject to the active-order deletion restriction. E0004 E0005
Evidence: E0004, E0005

Select existing customer

Kind: action
Basis: reported
Description: The documented order-entry flow adds new orders for existing customers. E0005
Evidence: E0005
Owner: Application operator

Enter new order

Kind: action
Basis: reported
Description: Order entry is documented as accepting order details and up to ten line items; the supplied evidence does not prove that the Java runtime performs the documented persistence. E0004 E0005
Evidence: E0004, E0005
Owner: Application operator

New order documented

Kind: outcome
Basis: reported
Description: The help material documents adding a new order for an existing customer, but the underlying database operation and transaction wiring remain unverified. E0005 E0006
Evidence: E0005, E0006

Relationships

Begin customer maintenance

From: Application operator
To: Customer maintenance
Relation: starts
Basis: reported
Description: The documented menu exposes customer add, find, update, and delete operations for the operator. E0004 E0005
Evidence: E0004, E0005
Trigger: Selecting a customer-maintenance operation. E0004
Guard: Customer deletion requires confirmation and cannot proceed for a customer with active orders. E0004 E0005
Information: Customer identity and customer address/contact fields are represented by the supplied customer forms. E0004
Mechanism: Menu/help documentation and form artifacts; runtime wiring is not established. E0004 E0005
Trust change: None established.
Control: Confirmation and active-order deletion restriction are documented controls, not runtime-verified controls. E0004 E0005
Evidence type: Help/documentation and generated form structure. E0004 E0005

Maintain customer result

From: Customer maintenance
To: Customer record maintained
Relation: achieves
Basis: reported
Description: The help material presents customer add, find, update, and delete functions as customer-maintenance capabilities, with the deletion exception noted above. E0004 E0005
Evidence: E0004, E0005
Control: Customer deletion is documented as requiring confirmation and as being blocked for customers with active orders. E0004 E0005
Evidence type: Help/documentation; successful runtime completion is not established. E0004 E0005

Begin order entry

From: Application operator
To: Select existing customer
Relation: starts
Basis: reported
Description: The documented order-entry journey is for adding a new order for an existing customer. E0005
Evidence: E0005
Trigger: Choosing order entry. E0004 E0005
Guard: An existing customer is required by the documented flow. E0005
Information: Customer number and order-related fields are represented in the supplied form artifacts. E0004 E0006
Mechanism: Menu/help documentation and generated form artifacts; executable handoff is not established. E0004 E0006
Trust change: None established.
Control: Existing-customer precondition is documented; its runtime enforcement is not established. E0005
Evidence type: Help/documentation and generated form structure. E0004 E0005

Proceed to order entry

From: Select existing customer
To: Enter new order
Relation: next
Basis: reported
Description: The documented flow proceeds from an existing customer to entry of a new order. E0005
Evidence: E0005
Information: Order number/date, customer number, shipping instructions, backlog, purchase-order number, shipping details, and paid date are represented in the order artifacts. E0004 E0006
Mechanism: Order form artifacts and help documentation; controller sequencing is not supplied. E0004 E0006
Evidence type: Help/documentation and generated form structure. E0004 E0005

Complete documented order entry

From: Enter new order
To: New order documented
Relation: achieves
Basis: reported
Description: Order entry is documented as supporting up to ten line items, but database insertion, transaction execution, and successful persistence are not proven. E0004 E0005 E0006
Evidence: E0004, E0005, E0006
Guard: The evidence documents an example transaction with rollback and commit, but identifies it as Informix-4GL example material rather than confirmed Java runtime behavior. E0004 E0006
Information: Line-item structures include item number, stock number, manufacturer code, description, quantity, price, and total. E0006
Mechanism: Generated order-form structures and documented order-entry examples. E0004 E0006
Trust change: None established.
Control: Transaction behavior is documented but not runtime-verified. E0004 E0006
Evidence type: Help/documentation and generated form structure. E0004 E0006

Gaps

The actor’s specific organizational identity and ownership are not established; “Application operator” is an inference from menu-driven behavior. E0004 The evidence does not establish executable controller sequencing, database connectivity, SQL execution, transaction wiring, or successful order persistence. E0005 E0006 Customer deletion rules and order-entry behavior are documented, but their Java runtime implementation is unverified. E0004 E0005 Order update and deletion are declared in an interface but explicitly described as unimplemented, so they are not modeled as successful journey transitions. E0004 The supplied material also contains missing form and framework coverage, including order-entry and state-selection artifacts, limiting confidence in complete journey reconstruction. E0004 E0006

Recovery limitations

• Ownership, mechanism or boundary controls remain explicitly unverified.
• The view includes explicitly marked inference.

Sources

• E0004 — SHA256 a7fa93a436c487d708267db6e5038c7415b98377a56232869519d6206a15e7e9
• E0005 — SHA256 cfb82f0c080e892e5b3b987574f1d65c56b7570c8650880e99078a02ca651535
• E0006 — SHA256 caaf28b181903beefb938762690d58ef2027cc70e645ab30a05ee9158cf684c0