Upload
branden-stanley
View
67
Download
0
Embed Size (px)
DESCRIPTION
System of Records Architecture. A case study Dr. Lawrence Chung Software Architecture and Design. Agenda. SOR Architecture Salient Features Components & Architectural Styles used Conclusion. SOR Architecture. Why moving to a new Architecture? - PowerPoint PPT Presentation
Citation preview
Shakesh Jain 1
System of Records Architecture
A case study
Dr. Lawrence ChungSoftware Architecture and Design
Shakesh Jain 2
Agenda
SOR Architecture Salient Features Components & Architectural Styles used Conclusion
Shakesh Jain 3
SOR Architecture
Why moving to a new Architecture? the current environment, is at its capacity in terms of roles,
relationships, contracts and new products it can support. To succeed with the Network endeavors, system infrastructure needs to be built to support the Financial Network. This initiative will provide flexible access and maintenance of Financial Network information and data to support future growth.
Consolidated Field area was introduced keeping in view the inconsistencies involved in the current systems and is a step towards maintaining a consistent data that is to be made available to the enterprise.
Some terminology Outbound: Any information that goes out of Siebel is called Outbound Inbound: Any information that comes into Siebel is called Inbound.
Shakesh Jain 4
SOR Architecture ( cont….)
Legacy Sync
CompareUpdate DistOrg
CF Update Server
FIMS and AGY/MANT
Inquiry Services
Supra
field
Fieldrpt Jobs
PLI Server
Field Updt Server
Siebel - UI
OutboundInbound
Event Listener
Shakesh Jain 5
Salient Feature
In-transition Architecture migration from Legacy system to Siebel will be done part-by-part. In
order to achieve this various processes (CF components) have been put in place
purpose of the components - to maintain consistency of data in both Legacy and Siebel system
Also, to maintain a Consolidated database (DistOrg-Sybase) having consistent latest data, which the whole enterprise can use for different business related scenarios
Shakesh Jain 6
Components & Architectural Styles used
Data Infrastructure (CF) components Siebel CDM (External to CF) Legacy Systems (External to CF) CF Update Server Legacy Synchronizer Inquiry Services
Asynchronous Communication Compare Update Processes CF-Siebel Event Listener
Implicit Invocation
Shakesh Jain 7
Conclusion
Need for in-transition architecture Legacy and Siebel applications
using/maintaining consolidated database Questions?
Thank You