1. TRITON - An event driven SOA architecture MSIS 2010 - Jakob Engdahl, Statistic Sweden Jakob.engdahl@scb.se

2. 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

3. 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

4. Each process needs input in form of data and or metadata to execute Each process results in data and/or metadata after execution Input and output Data Metadata Data Metadata

5. Not only micro and macro data Business objects Manual investigation New answers (micro data) Survey information Questionnaire Edited answers (micro data) Process data Variable list

6. Business objects Survey Sample Answers Comments

7. 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

8. Traditional SOA – Business object focus Manual investigation Check data Web collection tool Questionnaire Rules for data checks Sample objects Micro data Permission

9. Traditional SOA – Business process focus Manual investigation Check data Subject matter 1 Subject matter 2 Web collection tool

10. Event driven SOA with choreography Manual investigation Check data Web collection tool Subject matter 1 Subject matter 2

11. Event driven SOA with orchestration Manual investigation Check data Subject matter 1 Subject matter 2 Web collection tool Communication platform

12. 2016-06-1112 Information-flows Information flows between processes Each subject matter can orchestrate their information-flow

13. Information flow - Survey Manual investigation Check data Web collection tool Communication platform

14. Triton – All functions Communication platform Web collection tool Manual investigation Check data Duplicate management Scanning Interview system Imputing Administration Update contact information Print Deliver answers Load sample Process data Reports Shell application

15. Collaboration More difficult to collaborate with the logic ”in between” the functions Collaboration possible when creating IT-tools for specific processes

16. 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” Information Architecture

17. Questions MSIS 2010 - Jakob Engdahl, Statistic Sweden Jakob.engdahl@scb.se ?