معماری سرویس گرا (2)

صفحه 1:
What is a Service Oriented Architecture? Prof. Paul A. Strassmann George Mason University, November 19, 2007 

صفحه 2:
۱۷۵۵/۸۵ sense out of this. How do! do that? 

صفحه 3:
Purpose of Architecture: To Manage Interdependencies Suppliers Logistics nancial Outsourcing Dealers Pa ۳ it énance Customer inane 2۳۳ 0 

صفحه 4:
Directions of System Architecture 2050 - 2010 2000 - 1990 1980 - 1960 مهف ۰0۰ 6۰0 ۰0-۰0 6-0 یلا۰0 ۱ س<) م۰0 ‎“Dara Orci‏ سم ما۰ ۱ قات صصص ‎*Portd Orewertviyy *Ooversd‏ اما ‎“E01 Pte Tremere *Rechicee Orueniviy‏ ) سجو(* ‎4 ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ 

صفحه 5:
Interoperability - Number of Data Sources a Data Interoperability Expands as Response Time 4,000 Billion 1 Billion 40 Milion 100,000 4,000 400 2025 Data 2015 2005 1995 1975 1955 Shrinks 10 Mion ۳ 3 2 3 soon an oO E100 2 8 ‏ع‎ ‎8 1,000 2 1 4 1004 

صفحه 6:
Interoperability Does not Scale 56 3 Interoperability: Generation ‏...یروط‎ Missions for National nymper of Data Security Systems pn 1 4958-1975 | Automate Separate 100 Applications 2 1975-1995 | Automate Separate 1,000 Processes ۲ Integrate Processes 3 1995 - 2005 ‏عا مو حا لد‎ 100,000 Integrate Functions 531 4 2005 - 5 within an Organization 10 Million Innovate Processes 5 5 2015 - 0 Ke Neadad 1 Billion 

صفحه 7:
What is a Service Oriented Architecture (SOA)? ¢ Amethod of design, deployment, and management of both applications and the software infrastructure where: - All software is organized into business services that are network accessible and executable. - Service interfaces are based on public standards for interoperability. 

صفحه 8:
Key Characteristics of SOA * Quality of service, security and performance are specified. ¢ Software infrastructure is responsible for managing. * Services are cataloged and discoverable. * Data are cataloged and discoverable. ¢ Protocols use only industry standards. 

صفحه 9:
What is a “Service”? A Service is a reusable component. A Service changes business data from one state to another. A Service is the only way how data is accessed. If you can describe a component in WSDL, it is a Service. 

صفحه 10:
10 Information Technology is Not SOA Information Management Information Systems Systems Design | را اتسنیا 00 ینت Computing & Communications 

صفحه 11:
Current Infrastructure Costs are Excessive (¢ Millions, 1.T. Costs) Pol OF 96 Pond nee ‏سر مین‎ 90% 800,02 صمصدت (1) جد( ‎Sak dog 9‏ ی ۱ 5551 9۹6 96,9۶ سرا 996 50,696 صصص (1) 7)ناا” 990 90090 م1 6 م۳ ‎Ofer 5066© 09 Dordt OAD PY OP $90 qe 222 0 ‎ ‎11 ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ 

صفحه 12:
Contractors Will Build Separate Infrastructures ۳۷0 $30.7 $24.1 78.5% 12 FY06 $29.9 $22.6 75.6% FY05 $28.7 $21.1 73.5% without SOA $ Billions Overall DOD IT Spend Contracted DoD IT Spend % Contracted 

صفحه 13:
13 Why Getting SOA Will be Difficult * Managing for Projects: - Software: 1 - 4 years Hardware: 3 - 5 years; - Communications: 1 - 3 years; - Project Managers: 2 - 4 years; - Reliable funding: 1 - 4 years; - User turnover: 30%/year; - Security risks: 1 minute or less. * Managing for SOA: - Data: forever. - Infrastructure: 10+ years. 

صفحه 14:
Why Managing Business Systems is Difficult? 40 Million lines of code in Windows XP is unknowable. Testing application (3 Million lines) requires >10% tests. Probability correct data entry for a supply item is <65%. There are >100 formats that identify a person in DoD. Output / Office Worker: >30 e-messages /day. 14 

صفحه 15:
+—OPR1ETY TERE Looe vac تما ۲۵۵مصرمهه] eoenass Lane, ناته سس ‎TERE‏ 0ب Jeroen, Lava How to View Organizing for SOA Davate Oeelestere sel Mew ما وت ‎Tools‏ لس ‎Grapkte Pe tedous‏ سا بات و باس مساق لوگ ال سب 1 وس ا 000 Cone ® ‏مد‎ © 000 "Review Gore ® Crwettved Gove ® ‏ددا دكا اع‎ 0 ‏عت ع‎ ‏و‎ ‎‘Date Ovwegrorel wed Tovkn loteerated Qeterow Opdinrtire ate Gaw, Cherrd Orwpulton aed “Avlevrerowivalivae Aedintry Qader de, Oowraerctal OF tor ho ‏اک ام سس‎ Grey od ‏س0‎ ‎Conwy Berto 0000000 هيوست Once owt Barter Coon Barter 

صفحه 16:
سس عد ممم ‎SLORT 0‏ یج 036۳/۳6/۷۷ ‎hECTMOOLOGY‏ ‎peevemoo fe IDPLIOVDY ‎۳۳۹۹۵۵۰ BLOM MERD BTBBWITY & hEOCWMOOLOCY SOMPLEXITY ‎ ‎16 ‎SOA Must Reflect Timing ‏رمعي ,ملسا لسسع سلما له ‎Cryin Ton ord‏ لها ‎Spear Poe‏ ‏سه 6 سا0 سبي ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ ‎ 

صفحه 17:
17 SOA Must Reflect Conflicting Interests Missions 

صفحه 18:
DoD Concept How to Organize for SOA Programs ا له ل ل ل ie 0 Agencies ‏لك‎ Air Force ommand Business MissionWarFighting Missi@telligence Mission “ocus of this, t resentation لها 18 

صفحه 19:
Application Services 19 Organization of Infrastructure Services communication Services Computing Services Security Services Data Services 

صفحه 20:
Organization of Data Services Data Services [ | | Discovery a) ‘ollaboration Imteroperabilit} Semantic Services Services Services Services Services 20 

صفحه 21:
Data Interoperability Policies Data are an enterprise resource. Single-point entry of unique data. Enterprise certification of all data definitions. Data stewardship defines data custodians. Zero defects at point of entry. De-conflict data at source, not at higher levels. Data aggregations from sources data, not from reports. 21 

صفحه 22:
22 Frequency 9,451 228 158 128 88 20 5 2 1 3: 323 Example of Data Pollution Citizen? US Yes USA U.S.A. U.S. United States (US) Green Card Naturalized Applied 22? 

صفحه 23:
23 XML LegalXML IFX cXML ebXML HL7 V3.0 ACORD (AL3, (> ۳۳۷/۶۵2۵ SEMI- STRUCTURED XML HL7 HIPAA ASTM EDL-XI2 ‏ممع لمع‎ FIX Cargo IMP. MYR AFP Post Script DJDE What Data? UNSTRUCTURED Microsoft Word Microsoft Excel PowerPoint PDF Star Office Word Perfect ASCII reports HT™L ۴۵0 Undocumented Flat files RPG ANSI 

صفحه 24:
Data Concepts * Data Element Definition - Text associated with a unique data element within a data dictionary that describes the data element, give it a specific meaning and differentiates it from other data elements. Definition is precise, concise, non-circular, and unambiguous. (ISO/IEC 11179 Metadata Registry specification) * Data Element Registry - A label kept by a registration authority that describes a unique meaning and representation of data elements, including registration identifiers, definitions, names, value domains, syntax, ontology and metadata attributes. (iso 11179-1) 24 

صفحه 25:
Data and Services Deployment Principles Data, services and applications belong to the Enterprise. Information is a strategic asset. Data and applications cannot be coupled to each other. Interfaces must be independent of implementation. Data must be visible outside of the applications. Semantics and syntax is defined by a community of interest. Data must be understandable and trusted. 

صفحه 26:
۱ uthenticatio Services 26 ۱ Organization of Security Services Systems Assurance Security Services Services eel Protection Services [ Transfer Services 

صفحه 27:
Security Services = Information Assurance * Conduct Attack/Event Response * Ensure timely detection and appropriate response to attacks. * Manage measures required to minimize the network's vulnerability. * Secure Information Exchanges * Secure information exchanges that occur on the network with a level of protection that is matched to the risk of compromise. * Provide Authorization and Non-Repudiation Services * Identify and confirm a user's authorization to access the network. 27 

صفحه 28:
Financial janagementj 28 Organization of Computing Services Configuration Services Computing Services Control & Quality Resource Planning [ Computing Facilities 

صفحه 29:
29 Computing Services * Provide Adaptable Hosting Environments - Global facilities for hosting to the “edge”. - Virtual environments for data centers. ¢ Distributed Computing Infrastructure - Data storage, and shared spaces for information sharing. * Shared Computing Infrastructure Resources - Access shared resources regardless of access device. 

صفحه 30:
Organization of Communication Services 30 

صفحه 31:
Network Services Implementation * From point-to-point communications (push communications) to network-centric processes (pull communications). ۰ Data posted to shared space for retrieval. * Network controls assure data synchronization and access security. 31 

صفحه 32:
Network Control is the Key 

صفحه 33:
Communication Services ¢ Provide Information Transport - Transport information, data and services anywhere. - Ensures transport between end-user devices and servers. - Expand the infrastructure for on-demand capacity. 33 

صفحه 34:
Organization of Application Services Application Services ددا سس | پیت 34 

صفحه 35:
Application Services and Tools * Provide Common End User Interface Tools - Application generators, test suites, error identification, application components and standard utilities. * Common end-user Interface Tools. - E-mail, collaboration tools, information dashboards, Intranet portals, etc. 

صفحه 36:
Example of Development Tools * Business Process Execution Language, BPEL, is an executable modeling language. Through XML it enables code generation. Traditional Approach ___ BPEL Approach - Hard-coded decision logic - Externalized decision logic - Developed by IT - Modeled by business analysts - Maintained by IT - Maintained by policy managers - Managed by IT - Managed by IT - Dependent upon custom logs _- Automatic logs and process capture - Hard to modify and reuse - Easy to modify and reuse 36 

صفحه 37:
A Few Key SOA Protocols * Universal Description, Discovery, and Integration, UDDI. Defines the publication and discovery of web service implementations. * The Web Services Description Language, WSDL, is an XML- based language that defines Web Services. * SOAP is the Service Oriented Architecture Protocol. It is a key SOA in which a network node (the client) sends a request to another node (the server). * The Lightweight Directory Access Protocol, or LDAP is protocol for querying and modifying directory services. * Extract, Transform, and Load, ETL, is a process of moving data from a legacy system and loading it into a SOA application. 37 

صفحه 38:
SOA Interoperability Goals for the Department of Defense Interoperability of solutions across the DoD strategic goal. Rules for sharing of data and services across the enterprise. Enforcement of standards. All data, services, and applications shall be accessible, understandable, and trusted. Global Information Grid for sharing of information with Federal Departments, Department of Homeland Security, the Intelligence Community, state and local governments, allied, coalition, non-governmental organizations (NGOs), academic, research and business partners. 38 

صفحه 39:
Example of Customizable Web Services Funmua_calacfarce cam) ‏ها دی مها هم‎ (opexchange: Cheon = Serle 9 ‏ممممسي تمفسة‎ ‏لصم‎ 15[| > totam ter > am ouctes 0) feature Bemests, ۲ ‏هتسه‎ ۱ ‏یه ها‎ ms 6 So pas ‏مه ها‎ ‏مسق‎ sex سوه شوت زو 3 ‏یه‎ cama tre noe مسح سه م ‎estar Links‏ + Loninse dase User * Louings eT usar 0 سک 

صفحه 40:
Why SOA Saves Code Provides a standard way of interacting with shared software. Enables software to become building blocks for reuse. Shifts focus to application assembly rather than design. Creates new applications out of existing components. Integrates with applications in other enterprises. 40 

صفحه 41:
Preservation of Assets is the Purpose of SOA Data & hat the Customer ystems Integration Trains to Apply; 4) Communications Infrastructure Architecture Applications Usage ‎Lowry - tere‏ اساسا بسحا ‎Ovexnmdy Dover Ovvet‏ سوه ‎(Oa Coterprise Pucetzra) — (Oveower Pooch (Bu Baterprise (Pucrtira)‏ :و00 خاو 00090> ‎>PO% oP Oost Crass)‏ ‎<OO% vo Cost ‎41 

صفحه 42:
42 Impacts of Information Technologies Information drives economic “arms race”. Obsolete assets will be discarded. Collaboration favors global consolidation. I.T. becomes an economic weapon. 

صفحه 43:
A Historical Perspective $1,000,0@0 2 2 ‏سوه م21 سس و‎ 3 00,۵ 3 1 5000 Bo Power ‏م0 ذم امم د‎ = 2 Saar 5 ۳ $a Bo Power = ban Ouxershy £ 50 3 z 3 $d] Bo Power = Perry Omrped 8 ‏ع‎ 0 160۵:۵۵6۵ 6/۵۵۵ ۵۵ doo ao ‏اس‎ - Years 43 

What is a Service Oriented Architecture? Prof. Paul A. Strassmann George Mason University, November 19, 2007 1 Problems Addressed by a Service Oriented Architecture 2 Purpose of Architecture: To Manage Interdependencies Suppliers Manufacturing Management Dealers Customer Logistics Logistics Engineeering Parts Financing Parts Financial Engineeering Financial Financing Warranties Logistics Repair Insurance Taxes Outsourcing Sourcing Marketing Maintenance Maintenance 3 Directions of System Architecture 1960 - 1980 1990 - 2000 •Organization Focus •Mainframe Centric •Internal Use •Unique Data •Process Focus •Client Server •Partial Connectivity •EDI File Transfer 2010 - 2050 •Distributed Functions •Data Centric •Universal Interoperability •Real-time Connectivity 4 Data Interoperability Expands as Response Time Shrinks 5 Interoperability Does not Scale 6 What is a Service Oriented Architecture (SOA)? • A method of design, deployment, and management of both applications and the software infrastructure where: – All software is organized into business services that are network accessible and executable. – Service interfaces are based on public standards for interoperability. 7 Key Characteristics of SOA • Quality of service, security and performance are specified. • Software infrastructure is responsible for managing. • Services are cataloged and discoverable. • Data are cataloged and discoverable. • Protocols use only industry standards. 8 What is a “Service”? • A Service is a reusable component. • A Service changes business data from one state to another. • A Service is the only way how data is accessed. • If you can describe a component in WSDL, it is a Service. 9 Information Technology is Not SOA Business Mission Information Management SOA Information Systems Systems Design Computing & Communications Informati on Technolo gy 10 Current Infrastructure Costs are Excessive ($ Millions, I.T. Costs) Function SOA Total 07 Spending % of Total Spending Warfighter Missions $10,876 36% IT Infrastructure $14,185 47% Logistics $2,377 8% HR Management $1,834 6% Finance & Administration $1,036 3% $185 1% $30,492 100% Other Total DoD FY 07 11 Contractors Will Build Separate Infrastructures without SOA 12 Why Getting SOA Will be Difficult • Managing for Projects: – Software: 1 - 4 years – Hardware: 3 - 5 years; – Communications: 1 - 3 years; – Project Managers: 2 - 4 years; – Reliable funding: 1 - 4 years; – User turnover: 30%/year; – Security risks: 1 minute or less. • Managing for SOA: – Data: forever. – Infrastructure: 10+ years. 13 Why Managing Business Systems is Difficult? • 40 Million lines of code in Windows XP is unknowable. • Testing application (3 Million lines) requires >1015 tests. • Probability correct data entry for a supply item is <65%. • There are >100 formats that identify a person in DoD. • Output / Office Worker: >30 e-messages /day. 14 How to View Organizing for SOA PERSONAL LEVEL Pri va t e Ap p l i ca t i o ns an d Fi l es Pri vacy an d In d i v i d u al Securi t y Barri er Ap p l i cat i on s Securi t y Barri er Grap h i c InfoW i n d ow, Perso nal To o l s, In q u iry Lan guages Cust om i zed Ap pl i ca t i o ns, Pro t o t yp i n g To o l s, Local App l i ca t i o ns and Fi l es Ap p l i ca t i o ns Devel o pmen t & M ai n t enance VARIETY HERE LOCAL LEVEL APPLICATION LEVEL Busi ness Securi t y Barri er Service A Process Securi t y Barri er Service B OSD Fu nc t i o nal Process A Fu nc t i onal Process B Fu nc t i onal Process C Func t i onal Process D Corp ora t e Po l i cy, Corp ora t e St an dards, Reference M o del s, Da t a M anagemen t and To o l s, In t egra t ed Syst ems Co nfi gura t i o n Da t a Base, Shared Com p u t i n g an d Tel ecomm un i ca t i o ns In d ustry St an dards, Commerci al Off- t he-Shelf Pro duc t s an d Servi ces BUSINESS LEVEL PROCESS LEVEL ENTERPRISE LEVEL STABILITY HERE GLOBAL LEVEL 15 SOA Must Reflect Timing Private Applications and Files PERSONAL Graphic InfoWindow, Personal Tools, Inquiry Languages Customized Applications, Prototyping Tools, Local Applications and Files Applications Development & Maintenance Business A Business B Infrastructure Support SHORT TERM ADAPTABILITY & TECHNOLOGY APPLICATION SIMPLICITY LOCAL BUSINESS Functional Process A Functional Process B Functional Process C Functional Process D Corporate Policy, Corporate Standards, Reference Models, Data Management and Tools, Integrated Systems Configuration Data Base, Shared Computing and Telecommunications, Security and Survivability Industry Standards, Commercial Off-the-Shelf Products and Services LONG TERM STABILITY & ENTERPRISETECHNOLOGY COMPLEXITY PROCESS GLOBAL 16 SOA Must Reflect Conflicting Interests Personal Local Organizations Missions Enterprise 17 DoD Concept How to Organize for SOA Programs Army, Navy Air Force Agencies Combatant Commands Business MissionWarFighting Mission Intelligence Mission Focus of this Presentation Enterprise Information Environment 18 Organization of Infrastructure Services Infrastructure Services (Enterprise Information) Data Services Security Services Computing Communication Application Services Services Services 19 Organization of Data Services Data Services Discovery Services Management Collaboration Interoperability Services Services Services Semantic Services 20 Data Interoperability Policies • • • • • • • Data are an enterprise resource. Single-point entry of unique data. Enterprise certification of all data definitions. Data stewardship defines data custodians. Zero defects at point of entry. De-conflict data at source, not at higher levels. Data aggregations from sources data, not from reports. 21 Example of Data Pollution Citizen? Frequency US 9,451 Yes 228 USA 158 U.S.A. 128 U.S. 88 United States 20 (US) 5 Green Card 2 Naturalized 1 Applied 1 ??? 323 22 What Data? 23 Data Concepts • Data Element Definition – Text associated with a unique data element within a data dictionary that describes the data element, give it a specific meaning and differentiates it from other data elements. Definition is precise, concise, non-circular, and unambiguous. (ISO/IEC 11179 Metadata Registry specification) • Data Element Registry – A label kept by a registration authority that describes a unique meaning and representation of data elements, including registration identifiers, definitions, names, value domains, syntax, ontology and metadata attributes. (ISO 11179-1). 24 Data and Services Deployment Principles • Data, services and applications belong to the Enterprise. • Information is a strategic asset. • Data and applications cannot be coupled to each other. • Interfaces must be independent of implementation. • Data must be visible outside of the applications. • Semantics and syntax is defined by a community of interest. • Data must be understandable and trusted. 25 Organization of Security Services Security Services Transfer Services Protection Services Certification Services Systems Assurance Authentication Services 26 Security Services = Information Assurance • Conduct Attack/Event Response • Ensure timely detection and appropriate response to attacks. • Manage measures required to minimize the network’s vulnerability. • Secure Information Exchanges • Secure information exchanges that occur on the network with a level of protection that is matched to the risk of compromise. • Provide Authorization and Non-Repudiation Services • Identify and confirm a user's authorization to access the network. 27 Organization of Computing Services Computing Services Computing Facilities Resource Planning Control & Quality Configuration Services Financial Management 28 Computing Services • Provide Adaptable Hosting Environments – Global facilities for hosting to the “edge”. – Virtual environments for data centers. • Distributed Computing Infrastructure – Data storage, and shared spaces for information sharing. • Shared Computing Infrastructure Resources – Access shared resources regardless of access device. 29 Organization of Communication Services Spectrum Interoperability Management Services Communication Services Connectivity Arrangements Continuity of Services Resource Management 30 Network Services Implementation • From point-to-point communications (push communications) to network-centric processes (pull communications). • Data posted to shared space for retrieval. • Network controls assure data synchronization and access security. 31 Network Control is the Key 32 Communication Services • Provide Information Transport – Transport information, data and services anywhere. – Ensures transport between end-user devices and servers. – Expand the infrastructure for on-demand capacity. 33 Organization of Application Services Application Services Component Repository Code Binding Services Maintenance Management Portals Experimental Services 34 Application Services and Tools • Provide Common End User Interface Tools – Application generators, test suites, error identification, application components and standard utilities. • Common end-user Interface Tools. – E-mail, collaboration tools, information dashboards, Intranet portals, etc. 35 Example of Development Tools • Business Process Execution Language, BPEL, is an executable modeling language. Through XML it enables code generation. Traditional Approach BPEL Approach - Hard-coded decision logic - Developed by IT - Maintained by IT - Managed by IT - Dependent upon custom logs capture - Hard to modify and reuse - Externalized decision logic - Modeled by business analysts - Maintained by policy managers - Managed by IT - Automatic logs and process - Easy to modify and reuse 36 A Few Key SOA Protocols • Universal Description, Discovery, and Integration, UDDI. Defines the publication and discovery of web service implementations. • The Web Services Description Language, WSDL, is an XMLbased language that defines Web Services. • SOAP is the Service Oriented Architecture Protocol. It is a key SOA in which a network node (the client) sends a request to another node (the server). • The Lightweight Directory Access Protocol, or LDAP is protocol for querying and modifying directory services. • Extract, Transform, and Load, ETL, is a process of moving data from a legacy system and loading it into a SOA application. 37 SOA Interoperability Goals for the Department of Defense • Interoperability of solutions across the DoD strategic goal. • Rules for sharing of data and services across the enterprise. • Enforcement of standards. • All data, services, and applications shall be accessible, understandable, and trusted. • Global Information Grid for sharing of information with Federal Departments, Department of Homeland Security, the Intelligence Community, state and local governments, allied, coalition, non-governmental organizations (NGOs), academic, research and business partners. 38 Example of Customizable Web Services (www.salesforce.com) 39 Why SOA Saves Code • Provides a standard way of interacting with shared software. • Enables software to become building blocks for reuse. • Shifts focus to application assembly rather than design. • Creates new applications out of existing components. • Integrates with applications in other enterprises. 40 Preservation of Assets is the Purpose of SOA What the Customer Trains to Apply; Applications Usage Short-term Asset (An Enterprise Function) >70% of Cost Open Systems, Equipment, Software, Communications Obsolescent Commodity Asset (Outsource According to Architecture) <20% of Cost Data & Systems Integration; Communications Infrastructure Architecture Long - term Asset (An Enterprise Function) <10% of Cost 41 Impacts of Information Technologies • • • • Information drives economic “arms race”. Obsolete assets will be discarded. Collaboration favors global consolidation. I.T. becomes an economic weapon. 42 A Historical Perspective $1,000,000 B Power = Information Superiority $100,000 B $10,000 Power = Control of Capital $1,000 B $100 Power = Land Ownership $10 $1 B Power = Territory Occupied $0 100,000 10,000 1,000 Timeline - Years 100 10 43