Verification Matrix — Session Management

Implements:

• REQ-CONN-002 Single Session Per User

Requirement → Scenario Index

Requirement Ref	Requirement (short)	Scenario IDs
REQ-CONN-002: Single Session
EDR-1	Session conflict dialogue displayed	TC-CONN-SESSION-002
EDR-2	Cancel preserves original session	TC-CONN-SESSION-003
EDR-3	Continue invalidates original session	TC-CONN-SESSION-004
UNW-1	Invalidated session cannot perform actions	TC-CONN-SESSION-005, TC-CONN-SESSION-006

Scenarios (at a glance)

ID	Title	Type
2. Single Session Management (REQ-CONN-002)
TC-CONN-SESSION-002	Session conflict dialogue on second login	Positive
TC-CONN-SESSION-003	Cancel keeps original session active	Positive
TC-CONN-SESSION-004	Continue invalidates original session	Positive
TC-CONN-SESSION-005	Invalidated session cannot lock on workers	Negative
TC-CONN-SESSION-006	Invalidated session cannot manage protection	Negative

Scenario details

1. Single Session Management (REQ-CONN-002)

TC-CONN-SESSION-002: Session conflict dialogue on second login

• Arrange
  • User is logged in on Device 1
• Act
  • User attempts to log in on Device 2
• Assert
  • Session conflict dialogue displayed on Device 2
  • Dialogue shows clear warning about potential data loss
  • Two options presented: "Cancel" and "Continue"
  • Warning specifically mentions offline devices
  • Visual emphasis on potential consequences

TC-CONN-SESSION-003: Cancel keeps original session active

• Arrange
  • User is logged in on Device 1
  • User attempts login on Device 2
  • Session conflict dialogue displayed
• Act
  • User selects "Cancel" on Device 2
• Assert
  • Device 2 remains unauthenticated (returns to login screen)
  • Device 1 session remains active and functional
  • Device 1 can continue performing actions
  • No disruption to Device 1 session

TC-CONN-SESSION-004: Continue invalidates original session

• Arrange
  • User is logged in on Device 1
  • User attempts login on Device 2
  • Session conflict dialogue displayed
• Act
  • User selects "Continue" on Device 2
• Assert
  • Device 2 successfully authenticates
  • Device 1 session immediately invalidated
  • Device 1 shows session expired message or redirects to login
  • Device 1 cannot perform any further actions
  • Device 2 is now the active session

TC-CONN-SESSION-005: Invalidated session cannot lock on workers

• Arrange
  • Site Protector logged in on Device 1
  • SP performs session takeover on Device 2 (Device 1 session invalidated)
• Act
  • On Device 1, SP attempts to lock on worker via QR code
• Assert
  • User prompted to log in again
  • No worker lock-on occurs
  • No data corruption

TC-CONN-SESSION-006: Invalidated session cannot manage protection

• Arrange
  • RPO logged in on Device 1
  • RPO performs session takeover on Device 2 (Device 1 session invalidated)
• Act
  • On Device 1, RPO attempts to activate PWA or authorise worksite
• Assert
  • Action blocked with clear error message
  • Error indicates session has expired
  • User prompted to log in again
  • No protection state changes occur
  • No data corruption

---