1. Import Data
Id: UC1
Actors: User and System
Preconditions:
User has already logged into the system
Brief Description:
Data is imported into the system from external data sources
Flow of events:
1 Use case begins when user logs into the system or selects the import data button
2 System ensures current user has appropriate roles
2.1 If roles are not appropriate:
2.1.1 Use case ends
3 Current actor is determined:
3.1 If actor is user:
3.1.1 User is prompted to select data sources to import
3.1.2 Use case continues at step 3 when user hits import button
3.2 If actor is system
3.2.1 System selects data sources to import from configuration settings
4 System imports selected data sources into system
4.1 If faculty data is a selected data source
4.1.1 <<extends>> Get Faculty Data
4.2 If schedule is selected
4.2.1 <<extends>> Get Schedule
4.3 If course list is a selected data source
4.3.1 <<extends>> Get Course List
5 Use case ends
Alternative flows and exceptions:
User actor can cancel at any time prior to step 2.1.2
Post Conditions: Data from selected data sources is imported into the system

2. Get Faculty Data
Id: UC2
Actors: User and System
Preconditions:
User has already logged into the system
Brief Description:
Data is imported into the system from faculty data sources
Flow of events:
1 System ensures current user has appropriate roles
1.1 If roles are not appropriate:
1.1.1 Use case ends
2 System retrieves current faculty data
3 Current faculty data is merged into the system:
3.1 If a faculty member exists in system but not in current faculty data
3.1.1 Faculty member is removed from the system
3.2 If a faculty member exists in current faculty data and not in system
3.2.1 Faculty member is created in the system
4 All faculty members in the system have their data updated to reflect current faculty
data
5 Use case ends
Post Conditions: Data from faculty data source is merged into the system
Get Schedule
Id: UC3
Actors: User and System
Preconditions:
User has already logged into the system
Brief Description:
Data is imported into the system from faculty data sources
Flow of events:
1 System ensures current user has appropriate roles
1.1 If roles are not appropriate:
1.1.1 Use case ends
2 System retrieves current schedule
3 Current schedule is merged into the system:
3.1 If a item exists in system but not in current schedule
3.1.1 Item is marked for review by the system
3.2 If an item exists in current schedule and not in system
3.2.1 Item is created in the system
3.2.2 Item is marked for review
4 Use case ends
Post Conditions: Data from faculty data source is merged into the system

3. Get Course List
Id: UC3
Actors: User and System
Preconditions:
User has already logged into the system
Brief Description:
Data is imported into the system from faculty data sources
Flow of events:
1 System ensures current user has appropriate roles
1.1 If roles are not appropriate:
1.1.1 Use case ends
2 System retrieves current course data
3 Current course data is merged into the system:
3.1 If a course exists in system but not in current course data
3.1.1 Course is removed from the system
3.2 If a course exists in current course data and not in system
3.2.1 Faculty member is created in the system
4 All courses in the system have their data updated to reflect current course data
5 Use case ends
Post Conditions: Data from course data source is merged into the system
Export Data
Id: UC4
Actors: User
Preconditions:
User has already logged into the system
Brief Description:
Schedule information is sent from the system to designated external systems
Flow of events:
1 Use Case begins when user selects the export data button on the screen
2 System ensures current user has appropriate roles
2.1 If roles are not appropriate:
2.1.1 Use case ends
3 System Exports Schedule data to designated system
4 Use case ends
Post Conditions: Data from system is merged into designated external systems

4. Create Report
Id: UC5
Actors: User
Preconditions:
User has already logged into the system
Brief Description:
Report on any problems in the system data is created
Flow of events:
1 Use Case begins when user selects the create button on the screen
2 System ensures current user has appropriate roles
2.1 If roles are not appropriate:
2.1.1 Use case ends
3 New report is created
4 System reviews all system data
4.1 Items in violation of business rules are marked for review
4.2 All items marked for review are added to report
5 Use case ends
Post Conditions: Report is created and User is transferred to View Report use case
View Report
Id: UC6
Actors: User
Preconditions:
User has already logged into the system
Brief Description:
Report on any problems in the system data is created
Flow of events:
6 Use Case begins when user selects the view report button on the screen
7 System ensures current user has appropriate roles
7.1 If roles are not appropriate:
7.1.1 Use case ends
8 All reports are displayed on the screen
9 If a user selects a report
9.1 Details of report are displayed
10 Use case ends
Post Conditions: Report is created and User is transferred to View Report use case