Entity abstraction pattern
Part of this reusable logic pertains to the business entities,[3] that usually remains the same when compared to the rules and processing steps that may change in the future.
Apart from the reusability problem, in order to address the change in the behavior of a business entity, updating the entrenched entity related logic across multiple business processes requires extra efforts and makes the maintenance of such services a complex task.
This requires a top–down service-oriented analysis and design[6] service delivery process.
[5] The application of this design pattern requires adopting top-down service-oriented analysis and design service delivery process[6] which may not be suitable for organizations that have limited resources, both in terms of time and man-power.
Another important aspect is that once the entity-specific logic has been abstracted away in entity services, the dependency on such entity services increases as they become the sole point of contact for utilization functionality that is of interest to multiple business processes.
An ERD showing the relationships between different business entities and their attributes.
Entity specific logic is identified from the above ERD and abstracted away in relevant functional contexts that constitute the entity services.