J2EE Design Pattern : Business Tier Patterns : Business Object Design Pattern
|Business Object Design Pattern?|
Business object have a conceptual domain model with business logic and relationship.
- You have a conceptual domain model with business logic and relationship.
- When there is little or no business logic in a business operation, applications will typically let clients directly access business data in the data store
You have a conceptual domain model with business logic and relationship.
- Use Business Objects to separate business data and logic using an object model.
- Business Objects encapsulate and manage business data, behavior and persistence. Business Objects help separate persistence logic from business logic. Business Objects maintain the core business data, and implement the behavior that is common to the entire application or domain.
Participants and Collaborations
The Client represents a client of the BusinessObject. The Client is typically a Session Façade, a helper object, or an Application Service that needs to access the BusinessObject.
ParentBO is the top-level BusinessObject that represents the parent object in the composite BusinessObject model. The parent object encapsulates dependent objects and implements its own intrinsic business logic and business rules.
These are dependent BusinessObjects that are managed by the ParentBO. Dependent BusinessObjects are tightly coupled to their parents and rely on their parents for their lifecycle management. Dependent objects do not exist without their parent objects. Each dependent object implements its own intrinsic business logic and rules to fulfill its responsibilities.
- POJO Business Object Strategy
- Composite Entity Business Object Strategy
|Example for Business Object|