Now you want to look at where the data changes will originate and where these changes need to be sent to allow users to access.
Will the changes only be made at one site?
At what sites will data changes be made?
Are these sites where changes are not allowed at the site, but will receive changes from other sites?
Will a site have to pass changes that it receives from an originating site to other sites?
Are there any special handling rules at each individual site depending on what data is received and from where?
Part of this step is also to determine if the change flow is unidirectional or bidirectional. A unidirectional change flow means that between two sites, changes are only made at one site and sent to the other site. A bidirectional change flow means that changes can be made at either of the two sites and are sent to the other site.
Network pathing is also essential to your design. In many systems, there may not be a direct network connection between the source and target database...