Artifact: Conceptual Domain Model

Captures the most important concepts in the domain the system is developed in as well as their relations.

Purpose

Allows the stakeholders involved in the development of the system to agree on the relevant concepts and their relation. It can also help define the scope of the solution developed.

Relationships

Parent Practices	Goal-driven Requirements Elicitation
Fulfilled Slots	[Technical Specification]
Roles	Responsible: Analyst	Modified By: Analyst Developer Product Owner Stakeholder
Tasks	Input To: Mitigate Uncertainty Factors Define System Limitations and Constraints Refine System Goals to Requirements Validate Requirements Create Test Cases Design the Solution Envision the Architecture Implement Solution Plan Project Refine the Architecture Assess Results Plan Iteration	Output From: Mitigate Uncertainty Factors Refine System Goals to Requirements

Description

Main Description

The Conceptual Domain Model is a structured specification of the relevant concepts of the system domain. It captures the relevant concepts and their relationship to each other, as well as the most important attributes of the concepts. It is often executed as a UML class diagram and can be an input to the tasks that define the architecture of the system.

The model does not usually contain any elements specific to multi-agent systems. These are added later on in the artefacts that pertain to the design of the architecture. Operations are also not part of the conceptual domain model.

This material is made available under the Creative Commons—Attribution-ShareAlike License v3.0.

Parts of this material is based on the Eclipse Process Framework Practice Library, distributed under the Eclipse Public License V1.0.