What is a Use Case
The writing of the use case description document is the embodiment of the system analyst's deep understanding of the user's needs. It is an important basis for the later sequence diagram and actual development. It can also be used as a basis for project estimation and to measure developer productivity according to UC complexity and development cycle. Therefore , the writing standard of UC is very important, and I will share with you some experience in work, such as writing format, writing content and matters needing attention.
Outline diagram:
1. Preliminary preparation
Ø Have a very deep and complete understanding of the user's problems
Ø Ensure that all user problems can be solved
ØRealize the needs of users to the business model
Ø Provide instructions and framework for the subsequent design and development process
Ø Generate UI interface according to requirements
2. Content of Use Case
First use case name: usually the name of the module or the name of the function point in the module.
Secondly, the document change record ( Revision History ), the details are as follows:
1. Brief Description _
Describe the role of the use case in the system. For example, who is the user of this use case and what the user needs to do.
2. Preconditions _ _
Describe the conditions that must be met before the use case is executed. For example, before use case B is executed, A must be executed first , then the precondition of use case is to execute A.
3. Post Codition _
Condition after this use case is executed
4 , the main process ( Basic Flows )
The basic flow of the user's operation of the use case is the main reference for the later sequence diagram
5. Alternative Flows _
In the process of operating the main process, some branch processes that appear are the main reference for the later sequence diagram.
6. Special Requirement _
Describe some subtle function points, such as user authentication rules, order number generation rules, whether SSL encryption is required, etc.
7. User Interface _
The UI made by the artist according to the needs , and the description of the fields in the UI .
8. Additional Information ( Addition Information )
A description of some business logic, you can put the system logic attempt ( Logic View ) here
3. Summary
在阅读UC的过程中主要遇到以下问题“基本流程和选择性流程描述的不够清楚或者不够详细”的问题，主要是因为系统分析人员对需求理解的不够透彻，分析的不够彻底。
版权
作者：灵动生活
出处：http://www.cnblogs.com/ywqu
如果你认为此文章有用，请点击底端的【推荐】让其他人也了解此文章，
你也可以加我的新浪微博,以便实时了解我的动态:http://weibo.com/ywqu
WOWO英语(英语培训学校)：http://www.wowomandarin.cn 上海电子商务解决方案:http://www.hello36.com
上海闪酷系列解决方案：
电子商务解决方案 移动电商APP软件 培训学校管理系统 购物分享社区系统 移动开发解决方案 在线问卷调查系统
本文版权归作者和博客园共有，欢迎转载，但未经作者同意必须保留此段声明，且在文章页面明显位置给出原文连接，否则保留追究法律责任的权利。