Analyze the domain model and update it if necessary
You will usually use a conceptual (domain) data model for this step. Focus on ensuring that appropriate
relationships are reflected in the model. In particular, aggregational and compositional relationships are
important, because their presence guides the determination of groups of data elements that have a strong affinity with
each other.
If this examination identifies the need for additional aggregations and compositions, ensure that they are added to the
model.
If you (as the SOA Architect) need clarification on aspects of the data model, enlist the support of the Data
Architect. If any changes need to be made to the model, make the Data Architect aware of these. If you are
dealing with an Enterprise resource, it is likely that role will be responsible for making the changes.
|
Identify domain elements with strong affinities
It is likely that groups of domain elements will be identified that are frequently, if not always, accessed
together. These are our affinity groups -- also known as domain type encapsulation clusters. |
Map an information management service to each individual domain type
Provide the create, read, update, and delete (CRUD) operations for each domain type in a type-specific candidate service.
|
Map an information management service to each affinity group
These are used to provide access to portions of the domain model that commonly are manipulated and accessed
together. |
Update candidate service portfolio and service hierarchy
Add the new candidate services to the candidate service portfolio. Position them within the candidate service
hierarchy. |
|