Use-Case View)

I. Overview

Ii. Glossary

1. Extended relationship of Extends Use Cases

2. Include case inclusion relationship

3. Role)

Iii. How to draw the Use Case View

1. Create a project

2. Create a Use Case View

3. Use Case view based on business needs

Iv. Organizational Structure of Use Case in actual projects

 

V. Summary

 

I. Overview

The Use Case attempts to summarize the relationship between roles and systems in the use case, and describes the functional requirements of the system, the interaction between roles and systems, and the system response.

Members can browse product categories, send messages based on keywords, and select products to join the shopping cart.

Ii. Glossary 1. Extended relationship of Extends Use Cases

An extended relationship is generally used to describe an element extension for another behavior. The extension in Use Case indicates that a UC may be extended to another UC function. Expansion in Use Case usually implies a selective process.

2. Include case inclusion relationship

The package row relationship indicates the behavior of the target element of the Source Element package row. The inclusion relationship in UC is the behavior function of another UC row in UC. Using the package-line relationship can prevent defining common function modules in multiple UC instances at the same time, for example, entrusting a delegation

3. Role)

Users in the system are divided into multiple roles based on the system. Each role interacts with the system. A user can have one or more roles.

Roles used in the system can be divided into primary roles and secondary roles.

For example, e-commerce websites have major roles such as suppliers, front-end members, and system administrators. The secondary roles include Email Sender, logistics system, and golden stream system.

Iii. How to draw the Use Case View

Note:The design tool isEA(Enterprise effecect 7.0)

Assume that the current functional requirements are:

A. Suppliers must enter the Form to report products.

B. The supplier reports the product by importing the CSV document.

C. The product developer must review the product reported by the supplier

1. Create a project

[File]-> [New Project]-> enter the Project name: Example. eap

2. Create a Use Case View

Right-click the newly created Project and choose New View. In the displayed dialog box, select Use Cse, as shown in figure

　　

Click OK. In the Model project, a new Package is created.

Right-click Package, and choose "commodity report mounting"> "Add"> "Add digoal", as shown in

The following dialog box is displayed: Select UML Behavioral> Use Case and click OK]

In this way, an empty Use Case is created. Next, we need to add content to the empty Use Case.

3. Use Case view based on business needs

Note:Select some Use Case elements from the ToolBox toolbar on the left and drag the Element on the left to the workspace on the right to put the Element in our Use Case attempt.

A. Drag Two Actor elements to the workspace and name them "Suppliers" and "Product Developers" respectively"

B. Drag the three Use Case elements to the workspace and name them "commodity Report", "CSV File Import Commodity", and "commodity Review" respectively"

As shown in:

C. Link roles and system functions through associations, such:

 

So far, the Use Case diagram of the commodity reporting scenario has been completed. A Use Case view corresponds to one or more Use Case cases.

For more information about the Use Case, see 《How to Write Use Case in the demand stage"

 

Iv. Organizational Structure of Use Case in actual projects

This is a functional directory map of the system requirements described using UC. Each UC describes the interaction between Actor and the system when using the system.

V. Summary

The Use Case attempts to summarize the relationship between roles and systems in the use case, and describes the functional requirements of the system, the interaction between roles and systems, and the system response. It is a good way for customers and developers to fully understand the functions required by the project. It is also the basis and direction for subsequent functional iterations.