Tag: ja-done

A UML use case diagram is the primary form of system/software requirements for a new software program under developed. Use cases specify the expected behavior (what) of a system, and not the exact method of making it happen (how). A complete set of use cases specifies all the different ways to use the system and therefore defines all behavior required of the system bounding the scope of the system.

A use case is a written description of how a user performs a task on your system. It outlines the behavior of the system from the user’s perspective when responding to a request. Each use case is represented as a sequence of simple steps, starting with the user’s goal and ending when the goal is achieved.

Use Case 2.0 is a scalable and agile approach that uses use cases to capturing requirements and driving the incremental development of a system to fulfill them. It helps you understand how the system will be used and leading you through the development of an appropriate system to support the users.

A use case diagram models different types of users interact with the system to solve a problem. As such, it describes the goals of the users, the interactions between the users and the system, and the required behavior of the system in satisfying these goals. Use cases define interactions between external actors and the system to attain particular goals. A use case diagram contains four main components