1 / 11

Using SOA Patterns to promote understanding across disciplines

Using SOA Patterns to promote understanding across disciplines. A. Patterson University College Cork Coastal & Marine Research Centre EGU 2012 – Vienna – 2 6 April 2012. NETMAR. Architecture Fundamental decisions Meet quality attributes Patterns Solution + context

tavia
Download Presentation

Using SOA Patterns to promote understanding across disciplines

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using SOA Patterns to promote understanding across disciplines A. Patterson University College Cork Coastal & Marine Research Centre EGU 2012 – Vienna – 26 April 2012

  2. NETMAR

  3. Architecture Fundamental decisions Meet quality attributes Patterns Solution + context Service Oriented Architecture Set of patterns Business logic (getting stuff done) Definitions

  4. OO v SOA • NERC Vocabulary Server • OO View • REST calls, returning XML representing terms • Service View • Governance • Authoritativeness • Provenance • Mapping

  5. Composite Front End (Portal) How do you we interact with multiple services, get an integrated, cohesive user interface and still preserve SOA principles and modularity benefits? Rotem-Gal-Oz - SOA Patterns

  6. Multiple User Domains Ice pilots Oil slick monitoring Oceanography Coastal Atlas

  7. Service Host • There needs to be a way to easily configure services, and avoid duplicating the effort of mundane tasks such as setting listeners, and wiring components, for each service.

  8. Multiple Disciplines • Geographical / Earth Sciences • WPS, Grass GIS modules • Biological • Taverna, MyExperiment

  9. PBAR • Patterns Based Architecture Reviews • Harrison, Avgeriou, IEEE Software • Focused stakeholder conversation • Agile approach to architecture • Checklist based on ATAM General Scenarios • Software Engineering Institute

  10. Conclusion • Architecture guides conversation • Emphasise added value over interfaces • Concrete guidance • Agile architecture • Bridge between IT and domain experts

  11. Thank you, any questions? A. Patterson University College Cork Coastal & Marine Research Centre A.Patterson@UCC.ie

More Related