Search results
Results from the WOW.Com Content Network
In software and systems engineering, a use case is a potential scenario in which a system receives an external request (such as user input) and responds to it.
Use case analysis is a technique used to identify the requirements of a system (normally associated with software/process design) and the information used to both define processes used and classes (which are a collection of actors and processes) which will be used both in the use case diagram and the overall use case in the development or redesign of a software system or program.
A use case diagram [1] is a graphical depiction of a user's possible interactions with a system. A use case diagram shows various use cases and different types of users the system has and will often be accompanied by other types of diagrams as well. The use cases are represented by either circles or ellipses. The actors are often shown as stick ...
Sequence diagrams are sometimes called event diagrams or event scenarios. For a particular scenario of a use case, the diagrams show the events that external actors generate, their order, and possible inter-system events. [2] The diagram emphasizes events that cross the system boundary from actors to systems.
CRC cards are frequently employed during the design phase of system and software development to transition use-case descriptions into class diagrams, allowing a smoother transition with a greater overview and permitting developers to implement solutions with low binding and high cohesion. CRC cards are usually created from index cards.
Process steps for a happy path are also used in the context of a use case. In contrast to the happy path, process steps for alternate flow and exception flow may also be documented. [3] Happy path test is a well-defined test case using known input, which executes without exception and produces an expected output. [4]
A use case survey is a list of names and perhaps brief descriptions of use cases associated with a system, component, or other logical or physical entity. This artifact is short and inexpensive to produce, and possibly advantageous over similar software development tools , depending on the needs of the project and analyst.
Use case points (UCP or UCPs) is a software estimation technique used to forecast the software size for software development projects. UCP is used when the Unified Modeling Language (UML) and Rational Unified Process (RUP) methodologies are being used for the software design and development.