Architecturing Component Based Systems with XML Technologies and Standards

Size: px

Start display at page:

Download "Architecturing Component Based Systems with XML Technologies and Standards"

Clinton Smith
8 years ago
Views:

1 Architecturing Component Based Systems with XML Technologies and Standards XML Finland 2002 Jens Jakob Andersen, Agenda What is architecture Current approaches Emerging trends A new vision Wrap up

2 What is architecture Architecture. Originates in greek. Assisting buildmaster in getting full value for the money In ancient Greece, the notion was: Creates a harmonic structure for the house What is IT architecture IT Architecture. Ensure a harmonic IT structure, that is balanced between now and here demands as well as future demands. Harmonic defined as a platform that is good for all participants; Business, Software development, IT operations, Helpdesk and Architectural department Harmonic defined as a platform that is in tune, in the meaning that it can be played by the director of business, and respond in tune.

architecture IT Architecture. Ensure a harmonic IT structure, that is balanced between now and here demands as well as future demands.

3 How is harmony achieved? Build an adaptible infrastructure. (Systemzones, HW-, SW-, network-, data-level). Must be loosely coupled in order to be adaptible. Architecture consist of overall plan, and several subdomains: Technical, information, application and process Document, enforce and maintain it. Key point is adaptible! Adaptible = Able to facilitate change in business time space Changes needed done in Biz-time? Changes that I ve endured: We need a web-shop We need the salesforce online, so they allways have the latest price&product information available anywhere Support WAP phones now!!! Outphase expensive old Unix servers, but keep the applications running Create a unified customer profile for CRM (across many customerdatastores) I want the same color green, as in the new logo

Adaptible = Able to facilitate change in business time space Changes needed done in Biz-time?

4 Without plan? Without maintenance?

5 Different layers Several levels of architecture - Landscape where to place agricultural zones, city zones, nature zones - Cityscape where to place industrial zones, business zones, office zones, housing zones - Building architecture layout of the rooms, expression of the building etc. - Technical architecture where to place wiring, pipes etc. A harmonic architecture? Time has learned us some basic rules: Expect the unexpected Keep data separate from application layer Mainframe lesson Keep presentation separate from logic layer www lesson

the building etc. - Technical architecture where to place wiring, pipes etc. A harmonic architecture?

6 Architectural model Documentation & descriptions Users Applications Interfaces Applications Functional s Data Development platforn Runtime platform Complexity graph Software complexity Units Software engineers available Deliveries Time

Development platforn Runtime platform Complexity graph

7 Solution - 1 Deliveries Units Software engineers available Software complexity Time How - 1? Reusable components Costs 150% to 250% more to develop Solutions build on reusable components cost only 20% to build Components are today build to a certain programming platform. Components can only be connected and reused on that platform Component librarian and component resuse analyst are key to reuse Components can be data as well as functions

build Components are today build to a certain programming platform.

8 How - 2? Loosely coupled reusable components. With Web services and Semantic web concepts, we have now in hand the initial buidling blocks for building reusable components (web-services), abstracted datamodels (ontologies) and we have the first few elements of the building blocks to weave this into applications flow languages and models Emerging trends -functions Web services flow languages Standards for orchestrating the flow between web-services Evolving area follow it closely WSFL, Xlang, DAML-S, BPEL4WS and more

(web-services), abstracted datamodels (ontologies) and we have the first few elements of the building blocks to weave this into

9 Emerging trends - data XML, XML Schema, RDF, RDF Schema. Standards that gives us the foundation to model data in both syntactical and semantic ways System architecture model in RDF[-S] Comp/Server/IBM/p690 Application/Enduser/CRM Is a Is a MOF 2.5 Installed at Uses Apollo MOF DB Installed at Apollo Is a Comp/Server/Sun/E10000

semantic ways System architecture model in RDF[-S] Comp/Server/IBM/p690

10 Application architecture model in RDF[-S] MOF Uses Uses Uses Order Invoice Customer Can do Can do Can do Search Create Update Read Read Write Read Write Order Invoice Tight logic connections service provider layer service provider layer Service fullfilment layer Service fullfilment layer Data wrapper connector Data wrapper connector Data wrapper Data Data wrapper Data Data wrapper Data

service provider layer service provider layer Service fullfilment layer Service fullfilment

11 Service directory and discovery support Service configuration and management Service fullfilm ent Loosely coupled logic service provider layer Service AI engine Service definition data DB wrapper connector DB wrapper Data DB wrapper Data Virtual GUI

service provider layer Service AI engine Service definition

12 Virtual applications Virtual function libraries (WS + functional ontologies) Virtual data concepts (Datamodelling via ontologies) Virtual GUI with: - End user customization - Navigation of concepts - Interaction with concepts via virtual functions Enables us to build not just A2A integrations, but also applications on top of Semantic Web Future 2006? Virtual application deliveries Functional deliveries Units Software engineers available Software complexity Time

virtual functions Enables us to build not just A2A integrations, but also applications on top of Semantic Web Future

13 Creativity is exploring new areas

Vertical Integration of Enterprise Industrial Systems Utilizing Web Services

Vertical Integration of Enterprise Industrial Systems Utilizing Web Services A.P. Kalogeras 1, J. Gialelis 2, C. Alexakos 1, M. Georgoudakis 2, and S. Koubias 2 1 Industrial Systems Institute, Building