1. Luís Ferreira Pires Dick Quartel Remco Dijkman Marten van Sinderen
Methodological support for service-oriented design IPA spring days 2005
Luís Ferreira Pires
Dick Quartel
Remco Dijkman
Marten van Sinderen

2. Contents Context Motivation Design approach Basic conceptual model
ISDL
Conformance assessment and composition abstraction
Conclusions and future work
30 November 2018
IPA spring days 2005

3. Context
This work is performed in the scope of the Freeband A-Muse project
Project objectives
to develop knowledge, technology and tools to help master complexity, facilitate re-use and address Freeband characteristics in service design and provisioning
Freeband characteristics
mobility, context-awareness, attentiveness and personalization
30 November 2018
IPA spring days 2005

4. A-MUSE vision: semantic Freeband services
Sensor
Client app
Service/context mgr
3rd party
service providers
Semantic definitions
Defined in
terms of
Notify
Registries &
repositories
30 November 2018
IPA spring days 2005

5. A-MUSE vision: enabled by modelling utility
User/provider requirements
Design
Deployment
Usage
Service/context specification
Implementation/realization
Description
30 November 2018
IPA spring days 2005

6. A-MUSE research topics
User/provider requirements
Service/context specification
Implementation/realization
Description
Design
Deployment
Usage
Design process,
Design languages,
Platform-independent
modelling
Tools,
Case studies
Platform-dependent
Modelling,
Platform-specific
mappings
Description languages,
Ontology languages
30 November 2018
IPA spring days 2005

7. Motivation for service design
Business process models
‘direct’ relation
SOC technology
e.g., based on web-services
WSDL, SOAP, UDDI, BPEL, ..
30 November 2018
IPA spring days 2005

8. Motivation for service design
Indirect relation
complexity
different stakeholders
re-use of designs
multiple design steps
abstraction levels
Business process models
SOC technology
e.g., based on web-services
WSDL, SOAP, UDDI, BPEL, ..
30 November 2018
IPA spring days 2005

9. Design approach: principles
System [Webster’s]
a regularly interacting or
interdependent group of items
forming a unified whole
System
Environment
Service
interactions between system
and users (environment)
+ their relationships
(focus: behaviour aspect)
Service S
Service S1 S2 S3
external perspective
internal perspective
System service
external system behaviour
(interaction contributions
+ relationships)
Conformance
equivalence of
external behaviour
Service
S3.1
S3.2
S3.3
S3.4
30 November 2018
IPA spring days 2005

10. Design approach: milestones
Business process specification
model, analyse, redesign application context
abstract from distinction application / environment
Application service specification
separation application / environment
Application service design
de-/composition from/into sub-services
platform independent (abstract platform)
Application service implementation
mapping onto SOC-technology
30 November 2018
IPA spring days 2005

11. Design steps: milestones
System
Environment
Business process
specification 1
Service S
Application service
specification 2
Service S1 S2 S3 3
Application service
design
Service
S3.1
S3.2
S3.3
S3.4 4
Application service
implementation
30 November 2018
IPA spring days 2005

12. Basic conceptual model
Foundation for communication, modelling languages, design methods and techniques
Requirements
Broad-spectrum
business processes and applications
mapping onto SOC concepts
Limited number of concepts
Generic
multiple abstraction levels
support conformance assessment
30 November 2018
IPA spring days 2005

13. Basic conceptual model
Abstract interactions
Concrete interactions
supported by service
platforms
Application service
Business partner, application, ...
Application
design
Activity properties,
Messages
Business process,
Business role
Business task,
Application action
30 November 2018
IPA spring days 2005

14. Interaction System Design Language (ISDL)
Applications
(Application) services and protocols
Business processes dialect: Amber (Testbed Studio)
Underlying conceptual model  elementary and generic concepts
Expressive  causality relations
Supports conformance assessment
Precise (formal) semantics
30 November 2018
IPA spring days 2005

15. ISDL concepts causality target causality relation action interaction
(a  b)  c  d
action
interaction
data language
binding
contribution
behaviour structuring
- causality-oriented
- constraint-oriented
behaviour
target attributes
entity E
shorthand
30 November 2018
IPA spring days 2005

16. Business process specification
Case study context-aware “call-a-cab” application
30 November 2018
IPA spring days 2005

17. Application service specification
Delimitation of environment and application
30 November 2018
IPA spring days 2005

18. Application service design
30 November 2018
IPA spring days 2005

19. Composition correctness
Service S’
abstraction step
comparison step
(equivalent?)
Service S
design step
(refinement)
Service S1 S2 S3
30 November 2018
IPA spring days 2005

20. Abstraction rules Causality refinement
Integrate interactions into actions
Identify inserted actions and reference actions
Remove inserted actions (simplified)
indirect causality relations between reference actions via an inserted action must be replaced by an equivalent relation between the reference actions
the same for indirect relations between action attributes
Simplify relations
30 November 2018
IPA spring days 2005

21. Application service design
30 November 2018
IPA spring days 2005

22. Application design validation
Step 1 Integrate interactions into actions
Step 2 Identify inserted actions
30 November 2018
IPA spring days 2005

23. Application design validation
Step 3a Abstract from inserted action CABreq
30 November 2018
IPA spring days 2005

24. Application design validation
Step 3b Abstract from inserted action DRVind
30 November 2018
IPA spring days 2005

25. Application design validation
Step 3c Abstract from inserted action DRVrsp
30 November 2018
IPA spring days 2005

26. Application design validation
Step 3d Abstract from inserted action CABrsp
30 November 2018
IPA spring days 2005

27. Application design validation
Step 3e Abstract from inserted action Notify
30 November 2018
IPA spring days 2005

28. Application design validation
Step 4 Simplify relations
30 November 2018
IPA spring days 2005

29. Composition abstraction
comparison step
(equivalent?)
Service S
Service S’
design step
(refinement)
abstraction step
Service S1 S2 S3
Bottom-up usage
composition abstraction
 facilitates re-use
Top-down usage
conformance validated
by construction
30 November 2018
IPA spring days 2005

30. Conclusions
ISDL is suitable to support service-oriented design since it enables
the modelling of business process, service specifications and designs at distinct abstraction levels
assessing the conformance between models at successive abstraction levels
the abstraction of internal behaviour of service designs
30 November 2018
IPA spring days 2005

31. Future work ISDL profiles to support different stakeholders
Tool support
support available: editor, simulator
near future: abstractor/conformance validator, transformation to BPEL/WSDL, modelling profiles
Use of ontologies for (inter)action attribute semantics
Investigate/demonstrate added-value for Business and Application Integration tools
30 November 2018
IPA spring days 2005