Cora final meeting


Published on

CORA (COmmon Reference Architecture) ESSnet final meeting presentation
CORA was funded by Eurostat to start defining an architecture to improve software sharing

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Cora final meeting

    1. 1. <ul>CORA ESSNet final results </ul>
    2. 2. this material is distributed under the Creative Commons &quot;Attribution - Share Alike – 3.0&quot; licence, available at the following website
    3. 3. <ul>short history </ul><ul><li>MSIS – 2008/2010: Task Force on Sharing Software, SAB, sessions on “Sharing Software”
    4. 4. 2009 Statistical work programme of the Commission : CORA definition
    5. 5. ITDG 2008: CORA announcement, countries involved: ch, dk, it, lv, nl, no, se
    6. 6. ITDG 2009: CORA presentation and start </li></ul>
    7. 7. <ul>CORA activities </ul><ul>four meetings: Kick-off meeting in Luxembourg (October 2009) WPs Leader Meeting in Amsterdam (January 2010) Intermediate Meeting in Rome (March 2010) </ul><ul>Final Meeting in Luxembourg (today): to present results to Eurostat and to other NSIs </ul>
    8. 8. <ul>WP2 state-of-the-art </ul><ul>Architectures and software adopted by NSIs Questionnaire designed and distributed to 42 NSIs : response rate 79% - 33 of 42 Questionnaire and attached documents analysis: which dissemination level (no privacy statement) Several tools declared “shared” … usage level? Little usage of statistical business process model Set of requirements definition </ul>
    9. 9. <ul>WP2 state-of-the-art </ul><ul>(del 2.1) Questionnaire (del 2.2) Requirements for Business Architecture from NSIs: BPM, strategy and tools shared/sharable (del. 2.3) Interesting review of collected documents on BPM , IT organization, architectures and IT strategy (to-be-defined dissemination, delivery to Eurostat) </ul>
    10. 10. <ul>WP3 technical architecture </ul><ul>Architecture principles: </ul><ul><li>Architecture model must be platform-independent
    11. 11. The production of statistics is to be described solely in terms of services calling services (SOA)
    12. 12. A service only uses services in the layer directly positioned under its own (layered approach)
    13. 13. Layers can be subdivided in terms of functionality (GSBPM) </li></ul>
    14. 14. <ul>WP3 technical architecture </ul><ul>Two dimensional approach (del. 3.1): Dim 1 : construction -> layers: figures, time-series, statistic, population, unit, variable, representation Dim 2 : functional -> GSBPM 9 sub-processes Software prototype added to WP3 goals: architecture proof of concept needed -> 2 prototypes developed in different environments (Java and .Net) </ul>
    15. 15. <ul>WP3 technical architecture </ul><ul>(del 3.2) </ul><ul><li>Common Generic Service Interface defined
    16. 16. Implementation guidelines: how to get them to work
    17. 17. Projects within Statistics Sweden and Statistics Netherlands described: some form of implementation of ideas developed within CORA. </li></ul>
    18. 18. <ul>WP3 technical architecture </ul><ul>(del 3.3) </ul><ul><li>Instruction manual with the simple example of a monthly transport statistic
    19. 19. Grid template for ppt and odp </li></ul>
    20. 20. <ul>WP4: organizational architecture </ul><ul><li>Commercial and Legal Foundations for the Exchange of Software between Statistical Offices (licences, sharing and business models, TCO, help for legal questions)
    21. 21. Requirements Checklist for CORA tools
    22. 22. Recommendations for CORA tools (tools by defined categories/requirements) </li></ul>
    23. 23. <ul>WP5: Project Dissemination </ul><ul><li>CORA web site and wiki
    24. 24. Software inventory managed by SAB (!!)
    25. 25. Training courses (ESTP) on the project products
    26. 26. Creative Commons licence for CORA deliverables </li></ul>
    27. 27. <ul>final remarks + </ul><ul><li>rich results in only 12 months: thank you!
    28. 28. importance of work atmosphere (... fun)
    29. 29. flexibility: adjustments needed (eg prototype)
    30. 30. flexibility: + side-effects unexpected (eg sw inventory)
    31. 31. cooperation with other bodies (SAB) and with Eurostat
    32. 32. cooperation tools usage: wiki & web </li></ul>
    33. 33. <ul>final remarks - </ul><ul><li>administrative load too heavy: every project implies too many administrative tasks (we don't have administrative staff)
    34. 34. flexibility vs procedures
    35. 35. not homogeneous commitment by partners
    36. 36. more face-to-face meetings needed </li></ul>
    37. 37. <ul>future </ul><ul><li>CORE (COmmon Reference Environment) starting: needed coordination with SDMX ESSnet and other bodies (GSBPM, HLG, METIS, other networks, ...)
    38. 38. SAB to continue CORA works: software repository management and implementation
    39. 39. More exchanges between CORE and Eurostat (and NSIs)
    40. 40. Cooperation with OSOR portal: to be developed </li></ul>
    41. 41. <ul>thank you! </ul>