Chapter 3
Event
类图√ 活动图√ 用例(本章)
USE Case(用例)
- Overview
- Waiters on Call
- 怎么找use cases
- user goal
- event decomposition
- S.A.
- business process(chapter3)-events
- information(chapter4)-things
- 用例和用户目标 (定义、发现)Use Cases and User Goals
- 什么是用例?an activity that the system performs, usually in response to a request by a user
- 两种定义用例的技术:用户目标技术、事件分解技术。
- 用户目标技术8步骤 User Goal Technique: Specific Steps–8步骤
- 动名词短语
- Detail(第5章)
- 事件分解技术 Event Decomposition Technique
- 基本业务流程 EBP
- 事件 Event
- 事件类型 Types of Events
- 外部事件 External Events:an event that occurs outside the system, usually initiated by an external agent
- 临时事件 Temporal Events:an event that occurs as a result of reaching a point in time
- 状态事件 state event:
- an event that occurs when something happens inside the system that triggers some process
- reorder point is reached for inventory item(到达一个水平线的时候,重新下单)
- 外部事件清单 External Event Checklist
- 外部事件清单 External Event Checklist:
- External agent or actor wants something resulting in a transaction
- Customer buys a product
- External agent or actor wants some information
- Customer wants to know product details
- External data changed and needs to be updated
- Customer has new address and phone
- Management wants some information
- Sales manager wants update on production plans
- External agent or actor wants something resulting in a transaction
- 临时事件清单 Temporal Event Checklist
- Internal outputs needed at points in time
- Management reports (summary or exception)
- Operational reports (detailed transactions)
- Internal statements and documents (including payroll)
- External outputs needed at points of time
- Statements, status reports, bills, reminders
- Internal outputs needed at points in time
- 外部事件清单 External Event Checklist:
- 定义事件 Identifying Events
- 事件/前提条件和响应 Events versus Prior Conditions and Responses
- 事件序列:追踪事务处理的生命周期 The Sequence of Events: Tracing a Transaction’s Life Cycle
- 技术依赖和系统控制 Technology-Dependent Events and System Controls
- 系统控制是什么?
- 理想技术假设
- 理想技术假设是什么?
- 事件分解技术–7步骤
- 用例、参与者和符号 Use Cases and CRUD Technique(Create, Report, Update, and Delete增删改查)(信息工程方法)
- 参与者、自动化边界
- 用例图
- For Customer domain class(对于客户域类), verify that there are use cases that create, read/report, update, and delete (archive) the domain class
- CRUD Technique Steps
- RMO案例中的use cases
- 子系统(用例相关性)、架构
- 用例图(UC actor )
- 方向(单向、双向)(可能有个单向箭头)
- 子系统用例图,显示所有参与者
- 子系统用例图,显示所有顾客参与者
- 用例之间的关系(包含关系 <
> relationship) - UML有四种关系:关联、依赖、泛化、实现
作业:第三章课后题19题可不做,+问题与练习3+11
转载请注明来源,欢迎对文章中的引用来源进行考证,欢迎指出任何有错误或不够清晰的表达,可以邮件至 963614756@qq.com。