UC1::Logon
Overview
This use-case describes the sequence of events necessary to logon to the system
Document History
  1. Current Version:1.3
  2. 1.1: odlingsmee 2006-01-01 Initial Revision
  3. 1.2: odlingsmee 2006-05-23 Upgraded to version 0.2
  4. 1.2: odlingsmee 2006-08-07 Added new alternate flow for scenario where max attempts has been exceeded.
Properties
Basic Flow
  1. The user navigates to the web [RQ13] logon screen.
  2. The system challenges [RQ3] the user for a username [RQ1] and password [RQ2].
    3. odlingsmee; 2006-01-21
    step3:We need to make sure that the website will support SSL encryption [RQ6] such that the user's details are not transmitted in plain text across the web
  3. The user enters their credentials and submits them to the system.
  4. The system validates that the username and password credentials match those stored.
  5. The system loads up the set of privileges appropriate to the user [RQ7].
  6. The system presents the homepage to the user.
  7. The use-case ends
Alternative Flows
Accessing a protected page directly

At step 1 of the Main Flow when The user attempts to access a protected resource but is not logged on or their session has expired

  1. The user navigates directly to a screen within the system website
  2. The system re-directs the user to the logon screen.
  3. The flow of events continues from step 2 of the Main Flow.
Invalid Credentials

At step 4 of the Main Flow when Credentials supplied are not valid

  1. The system determines that the user is still within their permitted logon attempts [RQ5]
  2. The system re-directs the user to the logon screen.
  3. The flow of events continues from step 2 of the Main Flow.
Invalid Credentials - number of attempts exceeded

  1. The system determines that the user has exhausted their permitted logon attempts [RQ5]
  2. The system re-directs the user to an authentication failure screen.
  3. The system alerts the administrator of the failed logon attempts.
  4. The use-case ends
Specific Requirements