A Modelbased Approach for Integrating Third Party Systems with Web Applications

1
A Model-based Approach for Integrating Third
Party Systems with Web Applications
Nathalie Moreno, Antonio vallecillo Universidad
de Málaga vergara,av _at_ lcc.uma.es
2
Agenda
3

• Web applications are moving from stand-alone
  systems to distributed applications
• They need to interoperate with third party
  systems, such as external Web services, portlets
  or legacy applications in order to properly
  exchange information and services with them
• Currently, integration of pre-developed systems
  is mostly achieved at implementation level (not
  at model level)
• Integration needs to be considered at all phases
  of the development process

4

• A proper integration approach requires
• the provision of mechanisms for making explicit
  provided and required interfaces of external
  systems, data, process, choreography or
  presentation models, etc.
• the identification of the main concerns involved
  in modeling Web applications that interact third
  party systems
• .using separate models (so portability,
  interoperability and reusability can be obtained
  through architectural separation of concerns)
• .in a platform-independent fashion

5
MDA is suitable for developing distributed
systems that are made up of components running on
different platforms/tiers. For example, there may
be web tier implemented on ASP.Net, but which
talks to a middle-tier using EJBs, with a
back-end being a Sybase RDBMS. MDA can generate
the software for the tiers, plus the code to
glue it all together.
Haywood, 2004
6
Agenda
7

• A framework specifically designed to integrate
  third party applications and legacy systems into
  Web systems by separating independent concerns
  into a set of views on the system, each one
  focusing on one particular viewpoint
• A viewpoint is an abstraction of a system
  focusing on one concern. Viewpoints are expressed
  using a selected set of concepts and structuring
  rules

8
ltltusegtgt
ltltusegtgt
ltltusegtgt
ltltusegtgt
ltltusegtgt
ltltusegtgt
9
(No Transcript)
10

• The development of a typical Web application with
  data, business process and hypertext involves the
  definition of at least three PIMs, each one for a
  viewpoint

11
(No Transcript)
12
Create class diagram (PIM) describing object
model
Marks
Mark PIM elements with stereotypes
Customize the marked PIM with annotations
Annotations
Specify the target platform
Mappings
Generate a PSM
Generate the Code
Mappings
13
Marks

14
Marks
Annotations

15

Marks
Annotations
Mappings
16
Agenda
17

18
(No Transcript)
19
PIM
Create class diagram (PIM) describing object model
Marks

Marked PIM
Annotations
Annotated PIM
Mappings
PSM
20
PIM
2.1
Mark PIM elements with stereotypes
Mark PIM elements with stereotypes
Marks

Marks
Marked PIM
Annotations
Annotated PIM
Mappings
PSM
21
PIM
2.1
Mark PIM elements with stereotypes
Mark PIM elements with stereotypes
Marks

Marked PIM
Annotations
Annotated PIM
Mappings
PSM
22
PIM
Apply transformation rules
Marks
2.2
Component
Package
P2C
Marked PIM
C2C
Class
Class
Association
Port
A2PC
Annotations
Interface
A2U
UsageDepend.
AssociationEnd
Annotated PIM
A2I
ImplementationDepend.
Mappings
Rule A2U from assoc_end UML!AssociationEnd
(assoc_end.stereotypes-gt includes(InternalSystem))
to port UML!Port Maps to .
PSM
23
PIM
The marked PIM
Marks

Marked PIM
2.3
Annotations
Annotated PIM
Mappings
PSM
24
PIM
Customize the marked PIM with annotations
Marks

Summary of the stereotypes used
Marked PIM
3.1
Annotations
Annotated PIM
Mappings
PSM
25
PIM
Customize the marked PIM with annotations
Marks

Marked PIM
3.1
Annotations
Annotated PIM
Mappings
PSM
26
PIM
Customize the marked PIM with annotations
Marks

Marked PIM
Annotations
Annotated PIM
3.2
Mappings
PSM
27
PIM
Specify the target platforms
Marks

Marked PIM
Annotations
Annotated PIM
Mappings
4.1
PSM
CORBA
WSDL
JAVA
28
PIM
Apply the transformation rules
Marks

Marked PIM
Annotations
Annotated PIM
Mappings
4.2
PSM
29
PIM
Generate de PSM
Marks

Marked PIM
Annotations
Annotated PIM
Mappings
PSM
5
30
(No Transcript)
31
Step 3.1
Conceptual model

Conceptual Model
32
Step 4.1
Navigation model
Navigation Model

33
Step 5
Presentation model
Presentation Model

34
Agenda
35

• Web Development methods should address in full
  the interactions with third party systems
• Model-driven Web Engineering proposals should
  able to incorporate these external applications
  into their models
• In this paper we have presented a model-based
  framework that covers the aspects that need to be
  considered for the high-level integration of Web
  applications with third party systems

36

• Make use of transformation languages for defining
  the model transformations, so they can be easily
  re-used and integrated with MDA tools
• Improve the description of the behavioural
  aspects (suggestions welcome)
• Study the (semi-automatic) derivation of adaptors
  in case incompatibilities are detected (at the
  PIM level)
• Cover the description of QoS information in the
  models, in order to be able to deal with these
  aspects

37
Thank You !