UML/rose learning notes Series 5: usage-process description

Usage is a description of the domain process;

Usage is a descriptive document used to describe the sequence of events when a participant (an external active person) completes a process using the system;

Usage is the process of using the system;

Condition recognition

The first method used to identify usage is based on the participant's method:

1) identifying participants related to the system or organization;

2) identifies each participant in the execution process they initiate or participate in;

The second method used to identify usage is event-based:

1) identifies external events that must be responded by the system;

2) Associate events with participants and usage;

Usage and domain process

Describe a process, such as a business process.

The process describes the sequence of events, actions, and transaction processing from beginning to end. The sequence of these events or actions produces some useful conditions.

Meaningful results of participants or organizations.

Usage, system functions, and trackability

All the system functions identified in the Requirement Specification descriptions in the previous phase should be allocated to use cases;

In addition, it can also be used to check whether all system functions are allocated to various use cases through cross-reference of case descriptions;

This provides us with an important clue for mutual tracing between products. At the end of the system implementation and testing stage, all system functions and usage can be tracked;