Object Oriented Software Engineering   View all facts   Glossary   Help
subject > representation > model > use case model
Next modelexploratory domain model    Upmodel    Previous modelsystem model   

use case model
subjectfact 
use case modelconsists of a set of use cases, and an optional description or diagram indicating how they are related2001-08-30 14:58:13.0
has part description or diagram indicating how use cases are related2001-08-30 14:58:13.0
has part use case2001-08-30 14:58:13.0
is a subtopic of 7.3 - Developing Use Case Models of Systems2001-08-30 14:58:13.0
is a kind of model2001-08-30 14:58:13.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
will contain classes from the original system if the system is an extension to an existing system2001-08-30 14:56:36.0
will contain many classes from the framework if the system is being built using a framework2001-08-30 14:56:36.0

Next modelexploratory domain model    Upmodel    Previous modelsystem model