श्रेणी: Unified Modeling Language

In the area of software testing, “use case” and “test case” are the most critical and closely interrelated terms, but they are quite different. A use case tells us how a system will behave or perform a given task under given conditions. A test case contains the actual test data, the instruction set of the system, and the expected results of the interaction with the system.

Use case diagrams help stakeholders to understand the nature and scope of the business area or the system under development, thus, use case modeling is generally regarded as an excellent technique for capturing the functional requirements of a system. They can be served as the basis for the estimating, scheduling, and validating effort.

Activity Diagrams describe how activities are coordinated to provide a service which can be at different levels of abstraction. Typically, an event needs to be achieved by some operation, particularly where the operation is intended to achieve a number of different things that require coordination, or how the events in a single use case relate to one another, in particular, use cases where activities may overlap and require coordination. It is also suitable for modeling how a collection of use cases coordinate to create a workflow for an organization.

A deployment diagram is a diagram that shows the configuration of run time processing nodes and the components (hardware, software & middleware on hardware) that live on them that is used to model the static deployment view of a system (topology of the hardware).

A use case is a tool for identifying the business goals of a system. The identification of use cases helps define system scope, ensuring that the requirements to be found will all be aligned with the business values, needs and strategy.