systems of electronic commerce tjtse56 2011

Systems of electronic commercetjtse56 2011

Jukka HeikkiläProfessor, Information Systems (eBusiness)

Vice Dean, Faculty of Information TechnologyJyväskylä University

e-mail: jups@jyu.fi tel: +358 50 581 8361

1

2

Long transaction (Software AG, 1999)

2

3

Networked components in practice

If everything was CORBA-compliant

– How to combine narratives and relevant states and transitions, when

– systems are distributed? – systems are asynchronous?– systems are independent?

3

4

Interapplication (Integration) Spaghetti (Ovaska, 2003)

4

Solution by

Integrating more?

Documenting better?

Standardising platforms?

Standardising interfaces?

Developing new systems?

...

5

MDA (Oya, 2002)

6

MDA (c.f. Oya, 2002)

7

An example (Oya, 2002)

8

An example (Oya, 2002)

9

An example (Oya, 2002)

10

An example (Oya, 2002)

11

MDA (Oya, 2002)

12

MDA (Oya, 2002)

13

MDA (Oya, 2002)

14

MDA (Oya, 2002)

15

MDA (Oya, 2002)

16

MDA (van der Krogt,

2008)

Actually, there is a third/fourth level of

abstraction, i.e., CIM, Computation Independent Model

(intended for business analysts)

So, we are backwhere we started,

QED :-)

PSM Bridge PSM Bridge

Code BridgeCode Bridge

17

5

What is MDA? (1/2) (Kim, 2008)

> Next level of abstraction; model-based development

18

Agile Development & Pragmatic MDA Using OptimalJ | © 2006 by Prashanth Shidlaghatta & Mike Sawicki19

User Interface

Business/Problem Domain

Persistence

DBDB DB

Legacy/Ext. Systems

Separation of Concerns

§ Employ architectural best practices

§ Formalize and store business logic

§ Architect for the future

§ Keep Technology at arm’s length

19

Agile Development & Pragmatic MDA Using OptimalJ | © 2006 by Prashanth Shidlaghatta & Mike Sawicki20

Construction ConsistencyManaging Dual Architectures

Application Arch.

Features

Technical Arch.

SOA, Distr.,

Web App

Working App!

Construction GuidelinesPatterns,

Conventions

ConsistentVariable

20

Agile Development & Pragmatic MDA Using OptimalJ | © 2006 by Prashanth Shidlaghatta & Mike Sawicki21

Agile Development

§ Shrink waterfall cycle into small iterations§ Ensure working application§ Demonstrate feature progress§ Make it simpler to embrace change§ Improve communication

between business and IT§ Deliver business value

faster and continuously

21

Agile Development & Pragmatic MDA Using OptimalJ | © 2006 by Prashanth Shidlaghatta & Mike Sawicki22

Agile

Agile Development

#3

MDA – Bringing the Success Factors Together

User Interface

Business/Problem Domain

Persistence

DBDB DB

Legacy/Ext. Systems

Separation of Concerns

#1#2

Application Arch. Technical Arch.

Working App!

Dual Architecture

Construction Guidelines

MDA

22

6

What is MDA? (2/2) (Kim, 2008)

> The Idea

* IIOP (Internet Inter-ORB Protocol) makes it possible for distributed programs written in different programming languages to communicate over the Internet.

23

!"#$%"$&'($)"*(+'$,-*$.,%%(/-'$%"$0&1+*$

,-$,22+13,%1"-4

5 6/,-'7"/8,%1"-'$,/($(''(-%1,+$1-$%9($):;$*(<(+"28(-%$2/"3(''

= 6/,-'7"/8,%1"-'$!"#$""%&'()"*+&,-*$!"#$""%&'()"*+&,%)&-()"

!"#$%&'"(#)*'$+

,#))-"$%

!"#$%&'"(#)*'$+!"#$%$&$'%

!"#$%&'"(#)*'$+('')

!"#$%&'"(#)*'$+!"#$%$&$'%

!"#$%&'"(#)*'$+('')

5 6/,-'7"/8,%1"-'$,/($,+#,>'$(?(3&%(*$0>$%""+'

= 6/,-'7"/8,%1"-$:(71-1%1"-'

5 ):;$1-$./,3%13(

= @%,-*,/*'$0,'(*

= A(2"'1%"/>$0,'(*$B)CDE

= 6/,-'7"/8,%1"-$.,%%(/-'

!"#$%&'()*+,-,*+,*$

.&+,"

!"#$%&'(/-,01%10.&+,"

2&+,.&+,"

Mappings and transformations between models should be modelled too(Eeles & Williams, 2007)

24

The role of MetamodelsEeles & Williams (2007)

•UML = Universal Modelling Language

•MOF = Meta Object Facility is an extensible model driven integration framework for defining, manipulating and integrating metadata and data in a platform independent manner. MOF-based standards are in use for integrating tools, applications and data.

•XML = eXtensible Markup Language

•XMI = XML Metadata Interchange

•CWM = Common Warehouse Metamodel

25

MDA in practice (Wallin, 2006)

26

Defining AssetsEeles & Williams (2007)

AssetClassification

Descriptors: Name/Value pairs

ContextDomain, Development, Test,

Deployment, and so on…

UsageUsage Instructions & ActivitiesFilling Variability Points

Related Assets

Association, Aggregation,

Dependency, Parent

Solution

Artifacts

Requirements

Models, Code, Tests

…Documents

Asset Overview

Name Desc Version State Profile

27

IBM Software Group | Rational software

25

Volvo IT – JNX Framework

Design Model

Domain Model

Implementation Model

Requirements

synchronize

Platform-specific Model

Platform-independent ModelModel

templates

Patterns

Patternstransform

extend

Patternsintegrate

validate

Code & TestBusiness

logic

RAS

Repository

Service

Reusable asset

(.ras file)

Reusable asset

(.ras file)

Reusable asset

(.ras file)

Reusable asset

(.ras file)

An Example: Eeles & Williams (2007)

28

7

MDA in Practice (Kim, 2008)

> Reduced cost and complexity of application development.

• Model-oriented implementation.

> Improved application quality and validation at model level.

• Constraint based, generated test cases.

> Reuse of business models

> Platform independence

> Rapid inclusion of emerging technologies

• Take a business model (off the shelf).

• Take a implementation model (off the shelf).

• Describe links between them.

• Generate the system.

> Available modelling products

• ArcStyler, iUML, OptimalJ, ...

29

30

Service orientation(IBM, c.f. Poutanen, 2006)

Existing Resources

Service Modeling

Services

Business Process

Components

QoS, Security, M

anagement &

Monitoring (Infrastructure Service)

Process Choreography

Simple and Composite Services

Enterprise Components

Package

Custom ApplicationCustom

Application

Package

ServiceC

onsumer

ServiceProvider

Integration Architecture

30

31

Patterns revisited

31

32

CBM ∪ SOA ⇒ SOMA(Service Oriented Modeling and Architecture IBM, 2006)

32

summary: SOMF 2.0 (BeLL, 2008;

33

Summary of How-to: IBM (2006)

34