Object Oriented Software Engineering   View all facts   Glossary   Help
subject > use case > extension
Next use casegeneralization^3    Upuse case    Previous use casespecialization   

extension
subjectfact 
extensionhas definition A use case that makes optional interactions explicit or handles exceptional cases2001-08-30 14:55:33.0
has purpose to make optional interactions explicit or to handle exceptional cases, therefore allowing the description of the basic use case to remain simple2001-08-30 14:55:33.0
is a subtopic of 7.3 - Developing Use Case Models of Systems2001-08-30 14:55:34.0
is related to the use case it extends2001-08-30 14:55:34.0
is a kind of use case2001-08-30 14:55:34.0
lists all the steps from the beginning of the use case to the end, including the handling of the unusual situation2001-08-30 14:55:34.0
use caseassists an architect with the first draft of the architectural model2001-08-30 14:58:12.0
can be used to plan the development process2001-08-30 14:58:12.0
can be used to structure user manuals2001-08-30 14:58:12.0
can form the basis for the definition of test cases2001-08-30 14:58:12.0
can serve as as part of the contract between the customers and the developer2001-08-30 14:58:12.0
describes the user's interaction with the system2001-08-30 14:58:12.0
does not describe the computations the system performs2001-08-30 14:58:12.0
give an architect an idea about which components will be needed and how they will interact2001-08-30 14:58:12.0
has a use case name2001-08-30 14:58:12.0
has actors the actors or actor who can perform this use case (optional)2001-08-30 14:58:12.0
has goals zero or more goals2001-08-30 14:58:12.0
has postconditions zero or more postconditions2001-08-30 14:58:12.0
has preconditions zero or more preconditions which describe the state of the system before the use case occurs2001-08-30 14:58:12.0
has related use cases zero or more use cases that may be generalizations, specializations, extensions or inclusions of this one2001-08-30 14:58:12.0
has steps each step of the use case using a two column format, with the left column showing the actions taken by the actor, and the right column showing the system responses2001-08-30 14:58:12.0
has summary2001-08-30 14:58:12.0
includes only actions in which the actor interacts with the computer2001-08-30 14:58:12.0
is used to develop requirements2001-08-30 14:58:12.0
is used to validate requirements2001-08-30 14:58:12.0
may have high political or commercial value2001-08-30 14:58:12.0
may have one or more preconditions2001-08-30 14:58:12.0
may represent a high risk because for some reason their implementation is problematic.2001-08-30 14:58:12.0
must be validated using requirements validation methods2001-08-30 14:58:12.0
normally includes only actions in which the actor interacts with the system2001-08-30 14:58:12.0
should be independent of any particular user interface design2001-08-30 14:58:12.0

Next use casegeneralization^3    Upuse case    Previous use casespecialization