Content deleted Content added
Jgilmore911 (talk | contribs) →Literature: Added a further resource (Halpin) which provides significant information on this subject. |
Removed reference to https://en.wikipedia.org/w/index.php?title=Physical_modelling&redirect=no as it is now redirecting to https://en.wikipedia.org/wiki/Physical_modelling_synthesis which gas no relation to physical modelling in IT. |
||
Line 1:
{{nofootnotes|date=March 2015}}
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 also known as a [[___domain model]]. Conceptual modeling should not be confused with other modeling disciplines such as [[data modelling]], [[logical modelling]] and
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.
| |||