ENG 203_6C

ENG 203_6C - ENG 203:SYSTEM ARCHITECTURE System Engineering...

Info iconThis preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
ENG 203:SYSTEM ARCHITECTURE 01/20/12 1 System Engineering in an Acquisition Context John M. Borky 2009 - all rights reserved Engineering 203 System Architecture Dr. Mike Borky mborky@aol.com (Cell) 505 453-0496 © John M. Borky 2009 – all rights reserved
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
ENG 203:SYSTEM ARCHITECTURE 01/20/12 2 Session 6 – Service-Oriented Architecture Lectures: 6A – General SOA Principles 6B – SOA Elements 6C – Implementing SOA 6D – Modeling with SoaML John M. Borky 2009 - all rights reserved
Background image of page 2
ENG 203:SYSTEM ARCHITECTURE 01/20/12 3 Lecture 6C – Techniques and Standards for Implementing SOA John M. Borky 2009 - all rights reserved
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
ENG 203:SYSTEM ARCHITECTURE 01/20/12 4 Second Generation Web John M. Borky 2009 - all rights reserved The evolution of SOA has been heavily influenced by underlying principles and assumptions of what is often called the Second Generation of the Web (Web 2): • The client is the server The user experience is the service The service is the added value The fragments are the file The participants are the architecture The peer contributions are the application Similarly, a list of Web 2 characteristics would usually include: Platforms (Windows, SOA, Open Source, etc.) are more important than applications Web 1 hyperlinks (pointers to Web sites) evolve to become participant contributions and collaboration (Open Source, Wikis, Blogs) Value moves up the stack; services are more important than software Algorithmic data management is the key; Google search is the exemplar • Participants/clients become virtual servers; E-Bay is the exemplar • A “long tail” of many small users offers more opportunity than a few big users • Files consist of fragments on many servers that are assembled dynamically • Pages and links become dynamic, based on ever-changing content Periodic software releases become continuous updates
Background image of page 4
ENG 203:SYSTEM ARCHITECTURE Web Services Framework (WSF) and Web 2 Services (WS-*) (1) Messaging/Notification: WS-Addressing – provides transport standardization independent of transport protocols WS-ReliableMessaging – provides QoS features for guaranteed delivery or failure notification of SOAP messages and serves as a fundamental WS-* extension for many other specifications WS-Notification Framework: WS-Base Notification establishes standard interfaces used by services on either end of a notification exchange WS-Brokered Notification – standardizes the broker intermediary used to send and receive messages on behalf of publishers and subscribers WS-Topics – standardizes delivery of notification messages to services that have subscribed to topics WS-Eventing – standardizes an event-oriented model for Pub/Sub WS-MetadataExchange – standardizes request messages, including WSDL, schema, policy, and other information 01/20/12 John M. Borky 2009 - all rights reserved 5
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 14

ENG 203_6C - ENG 203:SYSTEM ARCHITECTURE System Engineering...

This preview shows document pages 1 - 6. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online