Business/Domain Model, Process, Analyst, etc

Taken from: http://iconprocess.com

The Business Object Model is a class diagram describing the key business entities and workers (roles) in the business processes being analyzed.

Domain Model
A domain model captures the most important Artifact: Business Entity abstractions (modeled as UML classes) within the context of the domain. A domain model does not include any business worker definitions. For example, an insurance company's domain model may include classes and relationships for policy, insured, and claim.

The Role: Business Process Analyst is responsible for Activity: Maintain Business Rules.
The Business Process Analyst needs to be familiar with techniques for organizational design, process improvement, technology assimilation, organizational change, and process modeling. This role must identify opportunities for improving business processes, organizational design, and corporate culture.

The Role: Business Designer performs the Activity: Find Business Workers and Entities, focusing only on the entities.

* The Role: Business Process Analyst and Role: Business Designer use it to capture information about key abstractions in the business, and possibly to describe the business processes in detail.
* The Role: Software Designer uses the model as input to developing analysis and design models, including use case realizations.
* The Role: Requirements Analyst and Role: Information Architect use it as input to the common vocabulary used when defining requirements and developing wireframes, respectively.
* All other roles may use this information to understand the project's key concepts.