Consider the technical motivations first. The most common usage of the unification
process is for service typing conversion??”specifically, for transforming a composite service into
an atomic one by first merging all its internal sub-service processes. This approach is typically
applied to reduce internal design and architectural complexities and to align service granularities.
Furthermore, logic reorganization activities, software redesign and re-architecture efforts, and
underlying source code refectoring may require unification of services to eliminate unjustified
service decoupling conditions. Second, business imperatives and alterations to business strategies
and mission, modification to business requirements, changes to business priorities, reduction of
business functionality redundancy, and business consolidation efforts may justify the unification
of services to avoid functionality redundancy across organizations.
UNIFICATION PROCESS. The process of unifying atomic services is straightforward and fairly
simple. To merge two existing services, the action is typically to import one entity into the other
or unify both under a new service name. This activity should be planned with care and meticulously
applied to preserve the processes of the joining parties for tracking purposes. Conversely,
Individual
Account
Service
Retirement Account Service
SEP-IRA
Account
Service
Traditional
IRA
Account
Service
Legacy/Composite/Business
Atomic Atomic
Investment
Account
Service
Retirement
Account
Service
Abstraction.
Pages:
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269