![]() |
subject > representation > model |
![]() ![]() | ||||||||||||
model comparison table |
Subject | have part | omit | model | is a synonym of | is a subtopic of | consist of | develop during | help in | has part | has definition | concern with | contain |
---|---|---|---|---|---|---|---|---|---|---|---|---|
exploratory domain model | things that will not be implemented | 5.8 - The Process Of Developing Class Diagrams | understanding the domain | informal class diagram | operations and polymorphism, nor with modelling principles such as avoiding multiple inheritance. | elements that do not represent things in the domain, but are needed to build a complete system | ||||||
signature | 5.2 - Essentials of UML Class Diagrams | The format of an operation or message, including arguments and return value | many classes from the framework if the system is being built using a framework | |||||||||
system domain model | many classes that are needed to build a complete system; in fact it can contain less than half the classes of the system | things that will actually be implemented | domain model | 5.8 - The Process Of Developing Class Diagrams | requirements analysis, or the early stages of design | elements that do not represent things in the domain, but are needed to build a complete system | ||||||
system model | things that will actually be implemented | 5.8 - The Process Of Developing Class Diagrams | elements that represent things in the domain | |||||||||
use case model | description or diagram indicating how use cases are related | 7.3 - Developing Use Case Models of Systems | a set of use cases, and an optional description or diagram indicating how they are related | use case | many classes from the framework if the system is being built using a framework |
Next representation: name Up: representation Previous representation: language