Object Oriented Software Engineering View all facts Glossary Help |
| subject > representation > model > system domain model |
| system domain model (domain model) | ||||
| subject | fact | |||
| system domain model | is a synonym of domain model | ![]() |
| contains domain classes, associations and attributes | ![]() | |
| 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 | ![]() | |
| is a subtopic of 5.8 - The Process Of Developing Class Diagrams | ![]() | |
| is developed during requirements analysis, or the early stages of design | ![]() | |
| is a kind of model | ![]() | |
| omits many classes that are needed to build a complete system; in fact it can contain less than half the classes of the system | ![]() | |
| only models things that will actually 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: system model Up: model Previous model: signature