system of records architecture n.
Download
Skip this Video
Download Presentation
System of Records Architecture

Loading in 2 Seconds...

play fullscreen
1 / 7

System of Records Architecture - PowerPoint PPT Presentation


  • 358 Views
  • Uploaded on

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?

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'System of Records Architecture' - branden-stanley


Download Now An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
system of records architecture

System of Records Architecture

A case study

Dr. Lawrence Chung

Software Architecture and Design

Shakesh Jain

agenda
Agenda
  • SOR Architecture
  • Salient Features
  • Components & Architectural Styles used
  • Conclusion

Shakesh Jain

sor architecture
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

sor architecture cont

Siebel - UI

Outbound

Inbound

Event Listener

CF Update Server

Compare

Update

Inquiry Services

DistOrg

field

FIMS and

AGY/MANT

Field Updt Server

Legacy Sync

FieldrptJobs

PLI Server

Supra

SOR Architecture ( cont….)

Shakesh Jain

salient feature
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

components architectural styles used
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

conclusion
Conclusion
  • Need for in-transition architecture
  • Legacy and Siebel applications using/maintaining consolidated database
  • Questions?

Thank You

Shakesh Jain