Navigation and screen hierarchy in SCADA systems - Step-by-Step Execution

Process Flow - Navigation and screen hierarchy

Start at Main Screen

↓

Select Navigation Option

↓

Load Target Screen

↓

Display Screen Content

↓

User Interacts or Navigates Back

↓

Navigate to Another Screen

↓

Return to Previous Screen

↓

End or Repeat

This flow shows how a user starts at the main screen, selects navigation options, moves through screens in a hierarchy, and can interact or go back.

Execution Sample

SCADA systems

MainScreen -> Select Menu -> Load Screen -> Display Content -> User Action

This sequence represents moving from the main screen through navigation to a target screen and interacting with it.

Process Table

Step	Current Screen	User Action	Next Screen	Screen Loaded	Notes
1	Main Screen	Select 'Settings'	Settings Screen	Yes	User chooses Settings from main menu
2	Settings Screen	Select 'Network'	Network Screen	Yes	User drills down to Network settings
3	Network Screen	Press Back	Settings Screen	Yes	User returns to Settings screen
4	Settings Screen	Press Back	Main Screen	Yes	User returns to Main screen
5	Main Screen	Select 'Status'	Status Screen	Yes	User navigates to Status screen
6	Status Screen	No action	Status Screen	Yes	User views status, no navigation
7	Status Screen	Exit Application	None	No	User closes the application

💡 User exits application at step 7, ending navigation.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	Final
Current Screen	Main Screen	Settings Screen	Network Screen	Settings Screen	Main Screen	Status Screen	Status Screen	None
Screen Loaded	Main Screen Loaded	Settings Screen Loaded	Network Screen Loaded	Settings Screen Loaded	Main Screen Loaded	Status Screen Loaded	Status Screen Loaded	None

Key Moments - 3 Insights

Why does the screen change back to 'Settings Screen' at step 3 instead of going directly to 'Main Screen'?

Because the user pressed Back from 'Network Screen', which returns to the immediate previous screen 'Settings Screen' as shown in execution_table row 3.

What happens if the user does not perform any action on the 'Status Screen'?

The screen remains on 'Status Screen' with no navigation change, as shown in execution_table row 6 where 'No action' keeps the screen loaded.

How does the system know when to stop navigation?

When the user exits the application, navigation ends, indicated in execution_table row 7 with 'Exit Application' and no next screen loaded.

Visual Quiz - 3 Questions

Look at the execution table, what is the current screen after step 2?

A Main Screen

B Settings Screen

C Network Screen

D Status Screen

💡 Hint

Check the 'Current Screen' column at step 2 in the execution_table.

At which step does the user return to the Main Screen after navigating away?

A Step 3

B Step 4

C Step 5

D Step 6

💡 Hint

Look for when 'Current Screen' changes back to 'Main Screen' in the execution_table.

If the user pressed Back at step 6 instead of no action, what would be the next screen?

A Main Screen

B Settings Screen

C Status Screen

D Network Screen

💡 Hint

Consider the navigation hierarchy and back action from 'Status Screen' in the variable_tracker.

Concept Snapshot

Navigation starts at a main screen.
User selects options to move through screens.
Each screen loads content based on selection.
Back action returns to previous screen.
Exit ends navigation.
Screens form a hierarchy for user flow.

Full Transcript

This visual execution traces navigation in a SCADA system screen hierarchy. The user begins at the Main Screen and selects options to move to other screens like Settings and Network. Each step shows the current screen, user action, and next screen loaded. Back actions return to the previous screen, maintaining a clear navigation path. When the user exits, navigation ends. Variables track the current screen and loaded screen at each step, helping understand screen transitions. Key moments clarify why screens change as they do and when navigation stops. Quizzes test understanding of screen states and navigation flow based on the execution table and variable tracker.