Usecase: Synchronization Use case ID Use case name Actor Description Trigger Pre-condition Post-condition Normal flow UC001

Login Process manager This use case describes how a user logs into the System. In synchronization mode None If the use case was successful, the actor is now logged into the system. If not the system state is unchanged. This use case starts when an actor wishes to log into the system. The system requests that the actor enter his/her name and password. The actor enters his/her name and password. The system validates the entered name and password and logs the actor into the system. If in the basic flow the actor enters an invalid name and/or password, the system displays an error message. The actor can choose to either return to the beginning of the Basic Flow or cancel the login, at which point the use case ends.

Alternative flows

Exceptions Includes Priority Frequency of use Business rule Special requirement Assumption Note and issues

High

Use case ID Use case name Actor Description

Trigger Pre-condition Post-condition

UC002 Backup data Process manager The use case in this section describes how to add distributed Backup capability to provide automatic failover for the primary server or head primary server. In synchronization mode A server instance must be able to perform automatic failover to a backup server instance in the event of failure. It is also desirable for the backup server to be able to be actively running to perform other server tasks to maximize server resources while it is also waiting to pick up the workload of a failed server. There are two deployed channels that contain two process flows: Using a file listener to pick up a batch of files containing records and then compare with data on server. Using a file listener to pick up the file compared and then backup

Normal flow

Alternative flows

them to standard formats. In the event of a failure: A server instance is installed on a different machine with the same configuration as the primary. This server is designated as the backup server instance. Deploy the same channels to the backup server but put them in the Stopped and Inactive states. Deploy a Backup listener. Finally, update the primary server to include a Backup setting that points to the backup server.

Exceptions Includes Priority Frequency of use Business rule Special requirement Assumption Note and issues

High BR1

Use case ID Use case name Actor Description

Trigger Pre-condition Post-condition Normal flow

UC003 Synchronization data Process manager The use case in this section describes how to add distributed Synchronize capability to provide automatic synchronize between the primary server and head primary server. In synchronization mode Log into system successful, processing synchronizes will begin. This use case starts when an actor wishes to log into the system in every morning. Checking version data synchronized Sysnchronizing data between the head server and the brand servers In the event of a failure: Show errors Log errors Stop process synchronization and exit Send errors to technical

Alternative flows

Exceptions Includes Priority Frequency of use Business rule Special

High BR1

requirement Assumption Note and issues Business rule Code BR1 BR2 BR3 BR4 Business rules If processing backup or sysnchronize was problem, system will stop and exit When timing process is too long, processing will be restart process. Use case