Object Oriented Software Engineering View all facts Glossary Help |
subject > representation > model > use case model |
use case model | ||||
subject | fact |
use case model | consists of a set of use cases, and an optional description or diagram indicating how they are related | |
has part description or diagram indicating how use cases are related | ||
has part use case | ||
is a subtopic of 7.3 - Developing Use Case Models of Systems | ||
is a kind of model | ||
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 | ||
will contain classes from the original system if the system is an extension to an existing system | ||
will contain many classes from the framework if the system is being built using a framework |
Next model: exploratory domain model Up: model Previous model: system model