Exception Handling Flow in Use Cases

Query Information Use Case Name: Query Information
Exceptions:

1. Exception #1:
   • Description of Exception Behavior: Problems on Internet Connection
   • Number of the Event that Identify the Exception: 1 and 2
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The query won't be executed and the system won't be changed
2. Exception #2:
   • Description of Exception Behavior: A problem occurs retrieving data
   • Number of the Event that Identify the Exception: 1.x.i, 2.x.iv
   • Activity of Exception Handling: Warn the user about the problem with a message and the system retrieve the available information
   • Group of valid post-conditions after the Exception: The query won't be executed and the system won't be changed
3. Exception #3:
   • Description of Exception Behavior: An invalid complaint code is entered
   • Number of the Event that Identify the Exception: 2.c.iii
   • Activity of Exception Handling: Warn the user with a message that the number of this complaint is invalid
   • Group of valid post-conditions after the Exception: The screen is showing the principal screen of Query Information
4. Exception #4:
   • Description of Exception Behavior: Consistent data cannot be assured
   • Number of the Event that Identify the Exception: 2.x.ii
   • Activity of Exception Handling: Warn the user with a message, the system abandon the retrieval
   • Group of valid post-conditions after the Exception: The screen is showing the principal screen of Query Information

Complaint Specification, Food Complaint, Animal Complaint, Special Complaint Use Case Name: Complaint Specification
Exceptions:

1. Exception #1:
   • Description of Exception Behavior: Problems on Internet Connection
   • Number of the Event that Identify the Exception: 5.a
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of complaint specification
2. Exception #2:
   • Description of Exception Behavior: Invalid data is entered by the user
   • Number of the Event that Identify the Exception: 5.b
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of complaint specification
3. Exception #3:
   • Description of Exception Behavior: A problem occurs storing the complaint
   • Number of the Event that Identify the Exception: 5.e-5.g
   • Activity of Exception Handling: Warn the user about the problem with a message, and roll-back the complaint entry
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of complaint specification
4. Exception #4:
   • Description of Exception Behavior: Data Consistency cannot be ensured
   • Number of the Event that Identify the Exception: 5.h
   • Activity of Exception Handling: Warn the user about the problem with a message, and roll-back the complaint entry
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of complaint specification

Login Use Case Name: Login
Exceptions:

1. Exception #1:
   • Description of Exception Behavior: Problems on Internet Connection
   • Number of the Event that Identify the Exception: 2
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Login
2. Exception #2:
   • Description of Exception Behavior: Problem when the system was retrieving the employee details
   • Number of the Event that Identify the Exception: 3
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Login
3. Exception #3:
   • Description of Exception Behavior: The system cannot validate the employee (adapted from Healthwatcher - Use cases specification [18])
   • Number of the Event that Identify the Exception: 3
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Login

Register Tables Use Case Name: Register Tables
Exceptions:

1. Exception #1:
   • Description of Exception Behavior: Problems on Internet Connection
   • Number of the Event that Identify the Exception: 5.a
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of complaint specification
2. Exception #2:
   • Description of Exception Behavior: Invalid data is entered by the user
   • Number of the Event that Identify the Exception: 5.b
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of complaint specification

Update Complaint Use Case Name: Update Complaint
Exceptions:

1. Exception #1:
   • Description of Exception Behavior: Error during the retrieve of registered complaints
   • Number of the Event that Identify the Exception: 2, 8
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of update complaint
2. Exception #2:
   • Description of Exception Behavior: Data consistency cannot be ensured
   • Number of the Event that Identify the Exception: 7, 14
   • Activity of Exception Handling: Warn the user about the problem with a message, and roll-back the complaint entry
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of complaint specification
3. Exception #3:
   • Description of Exception Behavior: Problems on Internet Connection
   • Number of the Event that Identify the Exception: 3, 6, 9, 12
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of update complaint
4. Exception #4:
   • Description of Exception Behavior: Error during the update of complaint
   • Number of the Event that Identify the Exception: 15
   • Activity of Exception Handling: Warn the user about the problem with a message, and roll-back the complaint entry
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of update complaint

Register New Employee Use Case Name: Register New Employee
Exceptions:

1. Exception #1
   • Description of Exception Behavior: Incomplete Data Entry (adapted from Healthwatcher - Use cases specification [18])
   • Number of the Event that Identify the Exception: 2
   • Activity of Exception Handling: Warn the user that he/she has missing/incorrect data
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Register New Employee
2. Exception #2
   • Description of Exception Behavior: Problems on Internet Connection
   • Number of the Event that Identify the Exception: 4
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Register New Employee
3. Exception #3
   • Description of Exception Behavior: The Employee is already entry
   • Number of the Event that Identify the Exception: 5
   • Activity of Exception Handling: Warn the user that already has this employee subscribed on the system and abandon the entry
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Register New Employee
4. Exception #4
   • Description of Exception Behavior: Data consistency cannot be ensured
   • Number of the Event that Identify the Exception: 6
   • Activity of Exception Handling: Warn the user about the problem with a message, and roll-back the complaint entry
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Register New Employee
5. Exception #5
   • Description of Exception Behavior: Error when the system was storing the new employee's details
   • Number of the Event that Identify the Exception: 6
   • Activity of Exception Handling: Warn the user about the problem with a message, and roll-back the complaint entry
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Register New Employee

Update Employee Use Case Name: Update Employee
Exceptions:

1. Exception #1
   • Description of Exception Behavior: Password is missing or invalid (adapted from Healthwatcher - Use cases specification [18])
   • Number of the Event that Identify the Exception: 2
   • Activity of Exception Handling: Warn the user that he/she has missing/invalid password
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Update Employee

Update Health Unit Use Case Name: Update Health Unit
Exceptions:

1. Exception #1
   • Description of Exception Behavior: Problem when the system was retrieving the information of the health unit
   • Number of the Event that Identify the Exception: 2, 8
   • Activity of Exception Handling: Warn the user that he/she has missing/incorrect data
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Update Health Unit
2. Exception #2
   • Description of Exception Behavior: Problems on Internet Connection
   • Number of the Event that Identify the Exception: 3, 6, 9, 12
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Update Health Unit
3. Exception #3
   • Description of Exception Behavior: Data consistency cannot be ensured
   • Number of the Event that Identify the Exception: 7, 13
   • Activity of Exception Handling: Warn the user about the problem with a message, and roll-back the complaint entry
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Update Health Unit
4. Exception #4
   • Description of Exception Behavior: Error when the system was storing the update of the health unit
   • Number of the Event that Identify the Exception: 14
   • Activity of Exception Handling: Warn the user about the problem with a message, and roll-back the complaint entry
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Update Health Unit

Change Logged Employee Use Case Name: Change Logged Employee

1. Exception #1
   • Description of Exception Behavior: On step 2, in case the password or the employee is not valid, an error message should be shown (adapted from Healthwatcher - Requirements [18]).
   • Number of the Event that Identify the Exception: 2
   • Activity of Exception Handling: Warn the user about the problem with a message
   • Group of valid post-conditions after the Exception: The screen is back to the main screen of Login

Drug Complaint Specification Use Case Name: Drug Complaint Specification
Exceptions:

1. Exception #1:
   • Description of Exception Behavior: Problems on Internet Connection
   • Number of the Event that Identify the Exception: 2, 5
   • Activity of Exception Handling: Warn the user about the problem
   • Group of valid post-conditions after the Exception: The data could not be saved
2. Exception #2:
   • Description of Exception Behavior: Database is not Accessable
   • Number of the Event that Identify the Exception: 2, 5
   • Activity of Exception Handling: Warn the user about the problem and ask him/her to access the system in a few minutes
   • Group of valid post-conditions after the Exception: The data could not be saved

Find Information on Website Use Case Name: Find Information on Website
Exceptions:

1. Exception #1:
   • Description of Exception Behavior: Problems on Internet Connection
   • Number of the Event that Identify the Exception: 2
   • Activity of Exception Handling: Warn the user about the problem
   • Group of valid post-conditions after the Exception: The data can't be showed
2. Exception #2:
   • Description of Exception Behavior: Database is not Accessable
   • Number of the Event that Identify the Exception: 2
   • Activity of Exception Handling: Warn the user about the problem and ask him/her to access the system in a few minutes
   • Group of valid post-conditions after the Exception: The data can't be showed

Receive Alerts via Feeds Use Case Name: Receive Alerts via Feeds
Exceptions:

1. Exception #1:
   • Description of Exception Behavior: Problems on Internet Connection
   • Number of the Event that Identify the Exception: 2, 4
   • Activity of Exception Handling: Warn the user about the problem
   • Group of valid post-conditions after the Exception: The subscribe can't be commited
2. Exception #2:
   • Description of Exception Behavior: Database is not Accessable
   • Number of the Event that Identify the Exception: 4
   • Activity of Exception Handling: Warn the user about the problem and ask him/her to access the system in a few minutes
   • Group of valid post-conditions after the Exception: The subscribe can't be commited