170 likes | 338 Views
TRITON - An event driven SOA architecture. MSIS 2010 - Jakob Engdahl, Statistic Sweden Jakob.engdahl@scb.se. Background. Process orientation Expensive data collection and data editing process Problem with a lot of old stovepipe systems A vision for a service oriented architecture.
E N D
TRITON - An event driven SOA architecture MSIS 2010 - Jakob Engdahl, Statistic Sweden Jakob.engdahl@scb.se
Background • Process orientation • Expensive data collection and data editing process • Problem with a lot of old stovepipe systems • A vision for a service oriented architecture
Requirements on architecture • Supports each process and activity with data and metadata • Has a service oriented form • Is metadata driven • Meets quality requirements such as stability, security etc • Gives the subject matters the possibility of choosing relevant services and functions • Lessens the dependence between the process services • Helps create a overview of the progress of the process • Does not require unique adapters between each subject matter and function
Input and output • Each process needs input in form of data and or metadata to execute • Each process results in data and/or metadata after execution Data Data Data Metadata Metadata Metadata Metadata
Business objects • Not only micro and macro data New answers (micro data) New answers (micro data) Editedanswers (micro data) Survey information Manual investigation Process data Questionnaire Variable list
Business objects Survey Sample Answers Comments
Deciding Architecture • Four forms of architecture was discussed • Traditional SOA with Business object focus • Traditional SOA with Business process focus • Event driven SOA with Choreography • Event driven SOA with Orchestration • Each architecture form was analyzed based on the requirements
Traditional SOA – Business objectfocus Web collectiontool Check data Manual investigation Sampleobjects Rules for data checks Questionnaire Micro data Permission
Traditional SOA – Business process focus Subjectmatter 1 Subjectmatter 2 Web collectiontool Check data Manual investigation
Event driven SOA with choreography Subjectmatter 1 Web collectiontool Check data Manual investigation Subjectmatter 2
Event driven SOA with orchestration Subjectmatter 1 Subjectmatter2 Communication platform Web collectiontool Check data Manual investigation
Information-flows • Information flows between processes • Each subject matter can orchestrate their information-flow
Information flow - Survey Communication platform Web collectiontool Check data Manual investigation
Triton – All functions Imputing Duplicate management Print Updatecontact information Scanning Web collectiontool Manual investigation Check data Administration Interview system Loadsample Process data Reports Shell application Deliver answers Communication platform
Collaboration • More difficult to collaborate with the logic ”in between” the functions • Collaboration possible when creating IT-tools for specific processes
Information Architecture • More information than micro data is needed to execute an activity • Information model is not dependent on architecture or technology • ”Generic Statistical Business Information Model”
Questions ? • MSIS 2010 - Jakob Engdahl, Statistic Sweden • Jakob.engdahl@scb.se