Object Oriented Software Engineering View all facts Glossary Help |
subject > representation > model > exploratory domain model |
exploratory domain model | ||||
subject | fact |
exploratory domain model | contains elements that represent things in the domain | |
does not contain elements that do not represent things in the domain, but are needed to build a complete system | ||
has part informal class diagram | ||
helps in understanding the domain | ||
is a subtopic of 5.8 - The Process Of Developing Class Diagrams | ||
is not usually concerned with operations and polymorphism, nor with modelling principles such as avoiding multiple inheritance. | ||
is a kind of model | ||
may model things that will not be implemented | ||
model | becomes the core of documentation describing the system | |
is crucial in software development | ||
is used to describe a software system | ||
is used to validate a software system | ||
see also model^2 | ||
should be understandable by clients and users so they can participate in the development process as much as possible | ||
should be properly reviewed | ||
should provide abstraction so that not all details are visible at once | ||
should provide insights about the system when software engineers analyze it | ||
should use a standard notation such as UML so that everybody who looks at it will interpret it the same way |
Next model: signature Up: model Previous model: use case model