Use Case
A use case is a description of a particular use of the system by an actor or user. It is used widely in developing tests at system or acceptable level. A use case is a software and system engineering term that describes how a user uses a system to accomplish a particular goal. A use case acts as a software modeling technique that defines the features to be implemented and the resolution of any errors that may be encountered.
Use Case Testing
Use Case Testing is a technique that helps identify test cases that cover the entire system, on a transaction by transaction basis from start to the finishing point. Use cases are a sequence of steps that describe the interactions between the actor and the system. Use cases are defined in terms of the actor, not the system, describing what the actor does and what the actor sees rather than what inputs the system expects and what the system’s outputs.
Business Analyst and Project Manager will write use cases.
Use case
Use cases define interactions between external actors and the system to attain particular goals.
There are three basic elements that make up a use case
Use cases are modeled using unified modeling language and are represented by ovals containing the names of the use case. Actors are represented using lines with the name of the actor written below the line. To represent an actor's participation in a system, a line is drawn between the actor and the use case. Boxes around the use case represent the system boundary.
Characteristics associated with use cases are
● Organizing functional requirements.
● Modeling the goals of system user interactions.
● Recording scenarios from trigger events to ultimate goals.
● Describing the basic course of actions and exceptional flow of events.
● Permitting a user to access the functionality of another event.
Use Case Testing
Use Case Testing is a technique that helps identify test cases that cover the entire system, on a transaction by transaction basis from start to the finishing point. Use cases are a sequence of steps that describe the interactions between the actor and the system. Use cases are defined in terms of the actor, not the system, describing what the actor does and what the actor sees rather than what inputs the system expects and what the system’s outputs.
Business Analyst and Project Manager will write use cases.
Use case
Use cases define interactions between external actors and the system to attain particular goals.
There are three basic elements that make up a use case
- Actors are the type of users that interact with the system.
- System Use cases capture functional requirements that specify the intended behavior of the system.
- Goals Use cases are typically initiated by a user to fulfill goals describing the activities and variants involved in attaining the goal.
Use cases are modeled using unified modeling language and are represented by ovals containing the names of the use case. Actors are represented using lines with the name of the actor written below the line. To represent an actor's participation in a system, a line is drawn between the actor and the use case. Boxes around the use case represent the system boundary.
Characteristics associated with use cases are
● Organizing functional requirements.
● Modeling the goals of system user interactions.
● Recording scenarios from trigger events to ultimate goals.
● Describing the basic course of actions and exceptional flow of events.
● Permitting a user to access the functionality of another event.
Comments
Post a Comment