|Impact of not having||
As in the business analysis model case, the business design model describes how the business works
internally to perform business functions, so the model is essential when considering changes to the business processes
or the organization (structure, roles and responsibilities) - you will be unable to reason about such changes without
UML Representation: Model, stereotyped as <<business design>>.
The business design model may have the following properties, similar to the
Business Analysis Model:
Introduction: A textual description that serves as a brief introduction to the model.
Business Systems: Components in the model, representing a hierarchy*.
Business Workers: The Business Worker classes in the model, owned by the Business Systems.
Business Entities: The Business Entity classes in the model, owned by the Business Systems.
Business Events: The Business Event classes in the model, owned by the Business Systems.
Business Rules: The Business Rules captured in the model. These are not the Business Rules that
are captured in document form in a separate artifact.
Relationships: The relationships in the model, owned by the Business Systems.
Business Use-Case Realizations: The Business Use-Case Realizations in the model, owned by the
Business Context Collaboration: The external realization of the interactions between the business
and the business actors, showing the services provided by the top-level Business System (that is, the
business itself), the interfaces for these services, the connections to the business actors, and the Business
Entities input and output.
Diagrams: The diagrams in the model, owned by the Business Systems.
*Note that the business itself is the top-level component (Business System), and may directly encapsulate business
workers, business entities etc.
For a more detailed description of different flavors of Business Design Model see Artifact: Business Analysis Model.