1. Extends use case extension relationship
2. Include use case inclusion relationship
3. How to draw the Use Case view
3. Draw the Use Case view according to the business requirements
Fourth, the organizational structure of Use Case in the actual project
I. Overview
Use cases attempt to describe the relationship between roles and systems in use cases, describe the functional requirements of the system, the interactions between roles and systems, and the reactions of the system.
Members have the ability to browse product categories, generate product information based on keywords, and select products to add to the shopping cart.
2. Terminology Explanation
1. Extends use case extension relationship
Extension relationships are generally used to describe the extension of one element to another behavior. An extension in a Use Case indicates that one UC may extend the functionality of another UC . Extensions in Use Cases usually imply an optional flow.
2. Include use case inclusion relationship
The package line relationship represents the behavior of the source element package line target element, and the package line relationship in UC is the behavior function of one UC package line in another UC. Using the package-line relationship can prevent the definition of common function modules in multiple UCs at the same time, some like delegation
3. Actor _ _
Users in the system are divided into multiple roles according to the system, and each role will interact with the system. A user can have one or more roles.
If the roles used in the system are subdivided, they can be divided into main roles and auxiliary roles
For example: in the e-commerce website, the main roles are suppliers, front-end members, system administrators, etc.; auxiliary roles are Email Sender , logistics system, cash flow system, etc.
3. How to draw the Use Case view
Note: The design tool is EA ( Enterprise Architect 7.0 )
Suppose the current functional requirements are:
A. Suppliers need to fill in the Form form to submit products
B. Suppliers submit products by importing CSV files
C. Commodity developers need to review the products submitted by suppliers
1. New construction
【File 】-> 【New Project 】-> Fill in the project name: Example.eap
2. CreateUse Case View
Right-click the newly created Project above -> select [ New View ] -> a dialog box pops up, select [ Use Cse ] as shown below
Click [ OK ], under the Model project, a new Package will be created .
Right-click on Package [Commodity submission and listing] -> select [ Add ] -> select [ Add Diagram ], as shown in the following figure
The following dialog box will pop up: select【UML Behavioral】->Use Case, click【OK】
In this way, an empty Use Case is newly created. Next we need to add content to the empty Use Case.
3、根据业务需求画Use Case视图
Note：从左侧的ToolBox工具栏中
选择一些Use Case的元素，直接拖曳左边的Element，到右边的工作区，就可以把Element放到咱们的Use Case试图中。
A、拖曳两个Actor 元素到工作区，分别命名为“供应商”“商品开发人员”
B、拖曳三个Use Case元素到工作区，分别命名为“商品提报”“CSV档导入商品” “商品审核”
如下图所示：
C、通过关联关系 链接角色与系统功能，如下图：
至此，商品提报场景的Use Case图已经画完。一个Use Case视图会对应一个或者多个Use Case用例。
关于什么是Use Case 请参照《需求阶段如何书写Use Case》
四、Use Case 在实际项目中的组织结构
这是一个使用UC描述的系统需求功能目录图，每一个UC描述了Actor使用使系统时，与系统的交互行为。
五、总结
用例试图描概括了用例中角色和系统之间的关系，描述了系统功能需求，角色和系统的交互以及系统的反应。是客户和开发人员全貌理解项目需求功能比较好的一个方式，也是后续功能迭代的依据和方向。
版权
作者：灵动生活
出处：http://www.cnblogs.com/ywqu
如果你认为此文章有用，请点击底端的【推荐】让其他人也了解此文章，
你也可以加我的新浪微博,以便实时了解我的动态:http://weibo.com/ywqu
WOWO英语(英语培训学校)：http://www.wowomandarin.cn 上海电子商务解决方案:http://www.hello36.com
上海闪酷系列解决方案：
电子商务解决方案 移动电商APP软件 培训学校管理系统 购物分享社区系统 移动开发解决方案 在线问卷调查系统
本文版权归作者和博客园共有，欢迎转载，但未经作者同意必须保留此段声明，且在文章页面明显位置给出原文连接，否则保留追究法律责任的权利。