Content deleted Content added
m caps |
refer to conceptual model |
||
Line 2:
A [[mental model]] captures ideas in a [[problem ___domain]], while a '''conceptual model''' represents 'concepts' (entities) and relationships between them.
A conceptual model in the field of [[computer science]] is a special case of a general [[conceptual model]]. To distinguish from other types of models, it is also known as a [[___domain model]]. Conceptual modeling should not be confused with other modeling disciplines such as [[data modelling]], [[logical modelling]] and physical modelling. The conceptual model is explicitly chosen to be independent of design or implementation concerns, for example, concurrency or data storage.
The aim of a conceptual model is to express the meaning of terms and concepts used by ___domain experts to discuss the problem, and to find the correct relationships between different concepts. The conceptual model attempts to clarify the meaning of various, usually ambiguous terms, and ensure that problems with different interpretations of the terms and concepts cannot occur. Such differing interpretations could easily cause confusion amongst stakeholders, especially those responsible for designing and implementing a solution, where the conceptual model provides a key artifact of business understanding and clarity. Once the ___domain concepts have been modeled, the model becomes a [[stability (software engineering)|stable]] basis for subsequent development of applications in the ___domain. The concepts of the conceptual model can be mapped into physical design or implementation constructs using either manual or [[Model-driven development|automated code generation approaches]]. The realization of conceptual models of many domains can be combined to a coherent platform.
| |||