Object Oriented Software Engineering   View all facts   Glossary   Help
subject > representation > model > exploratory domain model
Next modelsignature    Upmodel    Previous modeluse case model   

exploratory domain model
subjectfact 
exploratory domain modelcontains elements that represent things in the domain2001-08-30 14:55:33.0
does not contain elements that do not represent things in the domain, but are needed to build a complete system2001-08-30 14:55:33.0
has part informal class diagram2001-08-30 14:55:33.0
helps in understanding the domain2001-08-30 14:55:33.0
is a subtopic of 5.8 - The Process Of Developing Class Diagrams2001-08-30 14:55:33.0
is not usually concerned with operations and polymorphism, nor with modelling principles such as avoiding multiple inheritance.2001-08-30 14:55:33.0
is a kind of model2001-08-30 14:55:33.0
may model things that will not be implemented2001-08-30 14:55:33.0
modelbecomes the core of documentation describing the system2001-08-30 14:56:36.0
is crucial in software development2001-08-30 14:56:36.0
is used to describe a software system2001-08-30 14:56:36.0
is used to validate a software system2001-08-30 14:56:36.0
see also model^22001-08-30 14:56:36.0
should be understandable by clients and users so they can participate in the development process as much as possible2001-08-30 14:56:36.0
should be properly reviewed2001-08-30 14:56:36.0
should provide abstraction so that not all details are visible at once2001-08-30 14:56:36.0
should provide insights about the system when software engineers analyze it2001-08-30 14:56:36.0
should use a standard notation such as UML so that everybody who looks at it will interpret it the same way2001-08-30 14:56:36.0

Next modelsignature    Upmodel    Previous modeluse case model