Object Oriented Software Engineering View all facts Glossary Help |
subject > process > analysis > use case analysis |
use case analysis | ||||
subject | fact |
use case analysis | assists a software engineer to define the tasks that the user interface must help the user perform | |
can be used to determine responsibilities | ||
can be used to eliminate proposed functionality if the functionality does not support any use case | ||
can help define the scope of the system, i.e. what the system must do and does not have to do | ||
has definition The process of dividing up the functionality of the system into use cases, and determining the relationships among those use cases | ||
does not cover all aspects of software, such as an activity that is internal to a system | ||
has procedure | ||
has purpose to model the system from the point of view of how users or other systems interact with this system when trying to achieve their objectives | ||
helps developers model different user roles | ||
is an intuitive way to understand and organize what the system should do, since it is based on user tasks and expresses the tasks in natural language | ||
is similar to task analysis | ||
is useful for requirements analysis | ||
is a subtopic of 7.3 - Developing Use Case Models of Systems | ||
is a kind of analysis | ||
process | see also process^2 |