The Entity-Control-Boundary Pattern (ECB) is an architectural pattern where the class-design is use-case driven. It shares some similarity but should not to be confused with the Model-View-Controller Pattern.
The Entity-Control-Boundary Pattern (ECB) is an architectural pattern where the class-design is use-case driven. It is also related to robustness-analysis. It shares some similarity but should not to be confused with the Model-View-Controller Pattern.
This pattern distinguishes classes based on their responsibilities in use-cases:
Entities are classes representing information that matters to the users and the stakeholders, such as
Customer,Product,ShoppingCart.Boundaries are classes that represent the link between a use-case and system actors, such as user interfaces (for human actors), or gateways and proxies (for system actors).
Controls are classes responsible for a use-case. They orchestrate the realisation of a use-case and for this purpose coordinate related boundary- and entity- classes.
See also:
- Reference on Entity-Control-Boundary Pattern on Wikipedia
- Article on The Entity-Control-Boundary Pattern from San José State University
- Article on Robustness diagrams by Scott Ambler
