Decomposing such a structure or
breaking it down into smaller logical units may harm the relationship that is already in place.
Architectural best practices recommend avoiding excessive decomposition operations on
services and exercising analysis judgment when it comes to separating these logical entities.
Unnecessary partitioning activities may yield very fine-grained services that offer a negligible
Insurance Application
Processing
Service
Small-Business Insurance Service
Underwriting Service
Credit
Verification
Service
Questionnaire
Service
Portfolio/Atomic/Business
Legacy/Composite/Business
Legacy/Composite/Business.Small_business_division
Abstraction/Atomic/Business
Data
Transformer
Service
Data Aggregator
Service
Legacy/Atomic/Technical
Abstraction/Atomic/Technical
Legacy/Composite/Technical
Data Support Service
Solution
Legacy/Atomic/Business
EXHIBIT 7.11 FIRST PHASE DECOMPOSITION SOLUTION
Unification Analysis 143
Data
Transformation
Service
Data
Aggregation
Service
Data
Cleansing
Service
Data
Management
Service
Legacy/Composite.Circular/Technical
Atomic
Atomic
Composite
Data
Validation
Service
Atomic
Solution
EXHIBIT 7.12 DECOMPOSITION ON CIRCULAR STRUCTURE FORMATION
Decomposition Operation Benefits Service Analysis Best Practices
Promotes assets reusability Identify early reusability opportunities
Breaks down large services and service
clusters into more manageable entities
Facilitates the division of business from
technological implementations
Helps with partitioning tactical and
strategic assets, and isolating core business
from utility executables
Assists with separation of organizational
concerns
Separates lines of business functionalities
Avoid tight coupling solutions
EXHIBIT 7.
Pages:
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267