Use Cases - UC-09 Systems

• User must be logged
• User must have ROLE_ADMINISTRATIVE

1. User request to remove a system
2. System will check for associated licenses and warn the user to confirm license removal (sustem should note the number of licenses to be removed (
   1. User accepts to remove the system
      1. System removes the associated licenses and the system. 
   2. User dismiss changes
3. System returns to 'systems' list @see UC-09d SystemManagement-FindSystems

System will raise and exception if primary key does not exist.

System will raise and exception if customer ownership is not being satisfied.

• User must be logged
• User could have ROLE_ADMINISTRATIVE or ROLE_PRODUCT_MANAGER

1. User request for a list of users.
2. System will query database using provided parameters
3. System will return the result list.

None

• User must be logged
• User must have ROLE_ADMINISTRATIVE

1. User requests to unblock a blocked users by number of failed logins exceeded from users list.
2. System will update user.
3. System will return to the users list.

System will raise and exception if primary key does not exist.

• Users with role ROLE_ADMINISTRATIVE may reset passwords from other users

1. User requests to reset a password
   1. If role is ANONYMOUS (not logged)
      1. System returns recovery form.
      2. Users sends current username or email
      3. System generates a new password and it will send the new password to the provided email y username and email matches
   2. If role is ROLE_ADMINISTRATIVE_USER
      1. System returns recovery form for selected user
      2. Admin User sets new user password.
      3. System sends the new password to the user email.(no validation performed)
   3. Other logged users
      1. System returns recovery form
      2. User sets the new password and the old current password.
      3. System changes the password and notifies user y current password matches.

System will raise and exception if primary key does not exist.

1. User requests to sign in
2. System returns login form
3. User sets username and password
4. System validates credentials and check user block status
   1. If user is blocked system will be warned about and credentials will be ignored. 
   2. If the credentials match then user is redirected inside the portal. 
   3. If the credentials did not match user will be warned about that invalid credentials.
      System may track that invalid login attemp over that username. If max login attemps is reached user account must be blocked.

System will raise and exception if user is blocked

System will raise and exception if user credentials are wrong