Sisu

1. Web teenustel ja tarkvara agentidel põhinev infosüsteemide arendusEnn Õunapuuenn@cc.ttu.eeLühikursus

2. Sisu • Probleemi püstitus • Web teenus • Teenuse agent • Tegevusprotsesside modelleerimine • Teenustele põhinev arhitektuur • Teenustel põhinev analüüs ja disain • Äristandardid: ebXML • Reisistandardid: Opentravel.org • Haridusstandardid: IMS, SCORM • Lähema aja uurimisteemad • Küsimused

3. Probleemi püstitus Ettekandes esitan web teenustel ja tarkvara agentidel põhinevat infosüsteemide arendamise metodoloogiat ja arhitektuuri Süsteemide arendamise üheks kitsaskohaks on see, et programmikomponentide korduvkasutus on küll laialt deklareeritud, kuid väheselt kasutatud Lahendus probleemile oleks üldaksepteeritud standardite kasutuselevõtt

4. Paradigm Shift • Traditional Approach • ETL • EAI • Data warehouse • B2B + electronic commerce • New Holistic Approach • Service Oriented Architecture • Business-centric • Leverage XML

5. Infotöötluse (R)evolutsioon • täna: • –informatsioon • –teadmised • –otsused • homme: • –elektroonne globaalne töökoht • –vahendusagendid informatsiooni kogumise ja otsustused teeb inimene automaatne informatsiooni kogumine, otsustus

6. Web teenus • Tarkvara teenused on rakenduse loogika diskreetsed ühikud, millel on määratletud teadetel põhinevad juurdepääsud ja mis on kasutatavad hajutatud võrgus

7. Teenuse kasutamine

8. Web teenuse baasstandardid • SOAP • WSDL • UDDI

9. SOAP

10. WSDL dokumendi struktuur ·                     Abstract Definitions • TypesMachine- and language-independent type definitions. MessagesContains function parameters (inputs separate from outputs) or document descriptions. PortTypesRefers to message definitions in Messages section to describe function signatures (operation name, input parameters, output pameters). Concrete Descriptions • BindingsSpecifies binding(s) of each operation in the PortTypes section. Services Specifies port address(es) of each binding.

12. UDDI The Universal Description, Discovery and Integration (UDDI) on üks tähtsamaid ehitusplokke web teenustel põhinevatel rakendustel. UDDI loob platvormi, mis võimaldab kiiresti, lihtsalt ja dünaamiliselt leida web teenuseid Internetist.

13. Teenuste tüübid • Eristatakse alljärgnevaid teenuste tüüpe • Protsessi teenused - töövood • Oleku, olemi teenused • Tegevusteenused – protsessi tegevus • Infrastruktuuri teenused

14. Intelligent software agent (ISA) A software agent that uses Artificial Intelligence (AI) in the pursuit of the goals of its clients. • Artificial Intelligence is the imitation of human intelligence by mechanical means. • Delegacy for ISAs is far more absolute. ISAs have the capability to generate and implement novel rules of behavior which human beings may never have the opportunity or desire to review. • Competency as practiced by ISAs adds higher order functionality to the mix of capabilities. • Amenability in ISAs can include self-monitoring of achievement toward client goals combined with continuous, online learning to improve performance.

15. Teenuse agent Teenuse agent on teenus, mis aitab teil töötada teiste teenustega. Ta asub harilikult web teenuse kasutaja aadressruumis ja aitab teid nii teenuse väljakutsumisel, kui ka vastuste interpreteerimisel

16. Otsuseid toetav agent • Web teenuste kasutamise korral tekib meil pidevalt vajadus teha valikuid mitmete sarnaste teenuste vahel • Sellisel juhul on kasutatavad klassikalised otsustusmudelid • Lineaarne mitmekriteeriumiline mudel • Saaty meetod • Väljatõrjumise meetod (outranking) • Fuzzy loogika meetodid

17. Äriprotsesside modelleerimine

18. Petri võrgud

19. UML tegevusdiagramm

20. BPEL4WS Business Process Execution Language for Web Services (BPEL4WS) spetsifikatsioon määrab tegevusprotsesside kirjelduse web teenuste koordineerimiseks. Ta võimaldab luua komplekseid protsesse, mis võivad: • kutsuda välja Web teenuseid, • teostada andmete töötlust, • teostada tõrgete töötlust, • katkestada protsesse. Nimetatud tegevused võib teostada järjestikuliselt, paralleelselt või tingimuslikult.

21. Teenustel põhinev arhitektuur • Teenustel põhinev arhitektuuri korral rakendus on koostatud osadest, mida kutsutakse web teenusteks ja teenuse agentideks • Iga teenus kutsutakse välja standardsete teadetega • Operatsioonide semantika on lähedane ärifunktsioonidele

22. Simplification Through BCM Layers Implementation Layer Contract - Collaboration Partner Specific Constraints 4 Physical - Message & Presentation Tactical Legacy Extension Layer Publish 3 Frameworks & Standards Baseline Specification per CoI Business Layer Business Drivers: Model / Process / Constraints 2 Target Constructs & Patterns Strategic Conceptual Layer Business Goals 1 Concepts in Ontology Authoritative Sources

23. Service Oriented Architecture (SOA) User Interface - Presentation Apps Web Browser Email Client Telephone Wireless Front-End Common Services Web Services 1 Assurance DCR Registry Workflow Access SOA Enterprise Information Services Layer - EISL DCW DCD Exchange Common Exchange SOAP-based Envelope HTTP 2 Collaboration Gateway Business Applications and Functions Back-End Finance Account Project Mgmt HR Procure Backup for side: 25 Warehouse

24. Teenustel põhinev arhitektuur

25. WS-I.org • BEA Systems • IBM • Microsoft • Novell • Oracle • SAP • Sun Microsystems

26. Teenustel põhinev analüüs ja disain

27. Infosüsteemi elutsükkel • Veelange meetod • Spiraal meetod • Iteratiivne (RUP)

29. The Rational Unified Process captures many of modern software development's best practices in a form suitable for a wide range of projects and organizations: • Develop software iteratively. • Manage requirements. • Use component-based architectures. • Visually model software. • Continuously verify software quality. • Control changes to software.

30. The core process workflows are divided into six core “engineering” workflows: 1. Business modeling workflow 2. Requirements workflow 3. Analysis & Design workflow 4. Implementation workflow 5. Test workflow 6. Deployment workflow And three core “supporting” workflows: 1. Project Management workflow 2. Configuration and Change Management workflow 3. Environment workflow

38. The BOM is an organizational view of the Business Areas and Process Areas as defined by a domain taxonomy. BOM ·Business Area [Package] ·Process Area [Package] ·Process(es) [Use Cases] [Activity Diagrams] ·Categorization/ClassificationSchema Process Areas Business Operation Map Business Areas Business Operations Map Business Processes

41. ebXML business process specification schema Business process models describe interoperable business processes that allow business partners to collaborate. Business process models for e-business must be turned into software components that collaborate on behalf of the business partners. The goal of the ebXML Specification Schema is to provide the bridge between e-business process modeling and specification of e-business software components

42. UMM Metamodel and ebXML Business Process Specification Schema

43. Basic Semantics of a business collaboration

44. 1.      Business Collaborations A business collaboration is a set of Business Transactions between business partners. Each partner plays one or more roles in the collaboration. The ebXML Business Process Specification Schema supports two levels of business collaborations, Binary Collaborations and Multiparty Collaborations. Binary Collaborations are between two roles only.

45. A Business Transaction is the atomic unit of work in a trading arrangement between two business partners. A Business Transaction is conducted between two parties playing opposite roles in the transaction. The roles are always a requesting role and a responding role. Like a Binary Collaboration, a Business Transaction is a re-useable protocol between two roles. The way it is re-used is by referencing it from a Binary Collaboration through the use of a Business Transaction Activity as per above. In a Business Transaction Activity the roles of the Binary Collaboration are assigned to the execution of the Business Transaction. Unlike a Binary Collaboration, however, the Business Transaction is atomic, it cannot be decomposed into lower level Business Transactions.

46. 1.      Choreography The Business Transaction Choreography describes the ordering and transitions between business transactions or sub collaborations within a binary collaboration. In a UML tool this can be done using a UML activity diagram. The choreography is described in the ebXML Business Process Specification Schema using activity diagram concepts such as start state, completion state, activities, synchronizations, transitions between activities, and guards on the transitions.

47. Business Transaction A Business Transaction is the atomic unit of work in a trading arrangement between two business partners. A business transaction consists of a Requesting Business Activity, a Responding Business Activity, and one or two document flows between them. A Business Transaction may be additionally supported by one or more Business Signals that govern the use and meaning of acknowledgements and relatedmatters in the transaction.

49. The BOM is an organizational view of the Business Areas and Process Areas as defined by a domain taxonomy. BOM ·Business Area [Package] ·Process Area [Package] ·Process(es) [Use Cases] [Activity Diagrams] ·Categorization/ClassificationSchema Process Areas Business Operation Map Business Areas Business Operations Map Business Processes Analüüsi protsess

50. Süsteemi arhitektuur