1. This Presentation Courtesy of the
International SOA Symposium
October 7-8, 2008 Amsterdam Arena
www.soasymposium.com
info@soasymposium.com
Founding Sponsors
Platinum Sponsors
Gold Sponsors Silver Sponsors
Service Identification
Techniques
Track: SOA Modeling & BPM
Art Ligthart
Jan-Willem Hubbers
Linda Terlouw
2
1

2. About the workshop organizers
• Art Ligthart (art.ligthart@ordina.nl)
1988 – 1994: MSc in Business Administration
1994 – 2008: Solution Architect/Partner
• Jan-Willem Hubbers (jan.willem.hubbers@ordina.nl)
1988 – 1993: MSc in Computer Science
1994 – 1998: PhD in Computer Science
1998 – 2008: Solution Architect
• Linda Terlouw (linda.terlouw@ordina.nl)
1998 – 2003: MSc in Computer Science/
Business Information Technology
2003 – 2005: Consultant
2005 – 2008: Solution Architect
2005 – 2008: PhD Researcher
Goal and agenda
The goal of this workshop is to gain practical
experience with service identification techniques.
Agenda:
• 13:00 – 13:10: Introduction to Service Identification
• 13:10 – 13:35: Do-it-Yourselves Case Study
• 13:35 – 13:44: Feedback on Case Study
• 13:44 – 13:45: “Service Identifier of the Year” Prize Announcement
2

3. Method 5: starting from current systems
Main idea:
• existing legacy applications as starting point
Pros:
• pragmatic and quick
• can be used in a context where little process or function models are available
Cons:
• Law of Conservation of Challenges
• possible duplicate services due to duplications in
Get Client Bank Account
Put Client on Blacklist
application landscape
Get Client Address
Arrange Payment
Get Client Data
Process Order
App A App B App C
Method 5: starting from current systems
• Step 1. Analyse:
• User interfaces
• Data model
• Menus
• System manual: functions
• Transactions
• Application interfaces
• Batches
• Output: Reports, …
• Step 2. List functionalities
• Step 3. Cluster functionalities
• Step 4. Determine candidate services
• Step 5. Feasibility study
• Step 6. Document services
3

4. Method 1: process decomposition
Main idea:
• The business process is subdivided into sub-processes or decomposed into granular
activities and tasks. The lowest level tasks can consist of small, cohesive "logical units of
work" that are supported by the functionality offered by distinct services.
Pros:
• resulting services have a guaranteed fit with an organization's functional needs
• very intuitive (use it for proof-of-concepts and pilot projects)
Cons:
• may result in a (too large) gap between services and existing application landscape
• services can be tailored too specifically to the tasks and activities of one business process
(resulting in services that may not be reusable)
? ? ?
App A App B App C
Method 1: process decomposition
• Step 1. Analyse process design
• Phases
• (sub)Processes
• Activities
• Tasks
• Step 2. Detail (if necessary)
• Ensure that each Task is a Logical Unit of Work
• Step 3. Determine candidate services
• Each Task is a candidate service
• Step 4. Feasibility study
• Remove duplicates
• Step 5. Document services
4

5. And now you have to do some work!
• The CEO of the insurance company Protector
is fed up with the “never ending discussions of architects” and decided to organize
a pressure cooking workshop.
• During this workshop you are expected to identify services. Though time is limited, it would
severely disappoint the CEO of Protector if you would return without results!
Do-it-Yourselves Case Study (1/4)
• Please read the assignment carefully
• You have 2 minutes for reading it!!
1:00
1:01
1:02
1:03
1:04
1:05
1:06
1:07
1:08
1:09
1:10
1:12
1:13
1:14
1:15
1:16
1:17
1:18
1:19
1:20
1:21
1:22
1:23
1:24
1:25
1:26
1:27
1:28
1:29
1:30
1:31
1:32
1:33
1:34
1:35
1:36
1:37
1:38
1:39
1:40
1:41
1:42
1:43
1:44
1:45
1:46
1:47
1:48
1:49
1:50
1:51
1:52
1:53
1:54
1:55
1:56
1:57
1:58
1:59
2:00
0:01
0:02
0:03
0:04
0:05
0:06
0:07
0:08
0:09
0:10
0:12
0:13
0:14
0:15
0:16
0:17
0:18
0:19
0:20
0:21
0:22
0:23
0:24
0:25
0:26
0:27
0:28
0:29
0:30
0:31
0:32
0:33
0:34
0:35
0:36
0:37
0:38
0:39
0:40
0:41
0:42
0:43
0:44
0:45
0:46
0:47
0:48
0:49
0:50
0:51
0:52
0:53
0:54
0:55
0:56
0:57
0:58
0:59
1:11
0:11
End
5

6. Do-it-Yourselves Case Study (2/4)
• Please make assignment A: Identifying Services from
Existing Systems
• You have 8 minutes!!
Do-it-Yourselves Case Study (1/4)
8 minutes have passed!
Do-it-Yourselves Case Study (3/4)
• Please make assignment B: Identifying Services from
Business Processes
• You have 13 minutes!!
Do-it-Yourselves Case Study (1/4)
13 minutes have passed!
6

7. Do-it-Yourselves Case Study (4/4)
• Which other methods for service identification would you
consider?
• You have 2 minutes for giving your opinion!!
1:00
1:01
1:02
1:03
1:04
1:05
1:06
1:07
1:08
1:09
1:10
1:12
1:13
1:14
1:15
1:16
1:17
1:18
1:19
1:20
1:21
1:22
1:23
1:24
1:25
1:26
1:27
1:28
1:29
1:30
1:31
1:32
1:33
1:34
1:35
1:36
1:37
1:38
1:39
1:40
1:41
1:42
1:43
1:44
1:45
1:46
1:47
1:48
1:49
1:50
1:51
1:52
1:53
1:54
1:55
1:56
1:57
1:58
1:59
2:00
0:01
0:02
0:03
0:04
0:05
0:06
0:07
0:08
0:09
0:10
0:12
0:13
0:14
0:15
0:16
0:17
0:18
0:19
0:20
0:21
0:22
0:23
0:24
0:25
0:26
0:27
0:28
0:29
0:30
0:31
0:32
0:33
0:34
0:35
0:36
0:37
0:38
0:39
0:40
0:41
0:42
0:43
0:44
0:45
0:46
0:47
0:48
0:49
0:50
0:51
0:52
0:53
0:54
0:55
0:56
0:57
0:58
0:59
1:11
0:11
End
Do-it-Yourselves Case Study (1/4)
Feedback
7

8. “Service Identifier of the Year” Prize Announcement
Backup slides
8

9. Services?!?
• A service is a task offered by a service provider to (potential)
service consumers that conforms to the following properties:
o accessible through an interface;
o described by a service specification;
o implementation is hidden to service consumers;
o autonomous;
o stateless.
• Service identification is about finding the right services!
Possible pitfalls: Perfect Non-Existent Services
Spaghetti Services
Services in Name Only
Babel Services And Never Shall They Meet Services
9