Use Cases

Printer-friendly version

Description:

A use case describes an objective that a primary actor wants to accomplish and the sequence of interactions between the primary actor and a system such that the primary actor's objective is successfully achieved. Use cases are not functional requirements and do not define internal system processes that would not be visible to the user in their interaction with the system. Use cases are about describing system behavior from the perspective of the user and as such can be considered user requirements.

Use cases shift the perspective of requirements development to discussing what users need to accomplish, in contrast to the traditional elicitation approach of asking users what they want the system to do.
See Alsohttp://tw.rpi.edu/web/UseCases

Projects:
ToolMatch LogoToolMatch (ToolMatch)
Description: or a given dataset, it is difficult to find the tools that can be used to work with the dataset. In many cases, the information that Tool A works with Dataset B is somewhere on the Web, but not in a readily identifiable or discoverable form. In other cases, particularly more generalized tools, the information does not exist at all, until somebody tries to use the tool on a given dataset. Thus, the simplest, most prevalent use case is for a user to search for the tools that can be used with a given dataset. A further refinement would be to specify what the tool can do with the dataset, e.g., read, visualize, map, analyze, reformat.
People:
Patrick West

Patrick West is a principal software engineer with the Tetherless World Constellation at Rensselaer Polytechnic Institute. His current projects are focused on the semantic expression of data science concepts and relationships in various domains, including solar, upper atmosphere, ocean science [...]