Chapter 11 操作契约
Chapter 11 操作契约
我们在哪儿 em Domain Sequence Operation Transition Modeling Diagrams Contracts to Design Architecture
我们在哪儿
Modeling date quantity Vision Use-Case Model ♀、< arnves names Require-i Use Case Diagre Use Case Text ments the doma the post- events attributes conditions/ associations at underg make Supplementary Post-conditions ( id, quantity) Operation Contracts System Sequence Diagrams requirements that Design Mode must be satisfied Product catalog Design
Operation: enterItem(…) Post-conditions: - . . . Operation Contracts Sale date . . . Sales LineItem quantity 1 1..* . . . . . . Domain Model Use-Case Model Design Model : Register enterItem (itemID, quantity) : ProductCatalog spec = getProductSpec( itemID ) addLineItem( spec, quantity ) : Sale Requirements Business Modeling Design Sample UP Artifact Relationships : System enterItem (id, quantity) Use Case Text System Sequence Diagrams make NewSale() system events Cashier Process Sale : Cashier use case names system operations Use Case Diagram Vision Supplementary Specification Glossary starting events to design for, and more detailed requirements that must be satisfied by the software Process Sale 1. Customer arrives ... 2. ... 3. Cashier enters item identifier. the domain objects, attributes, and associations that undergo changes requirements that must be satisfied by the software ideas for the postconditions
目标 口确定系统操作 口为系统操作创建契约
目标 确定系统操作 为系统操作创建契约
为什么需要操作契约 口用例和SSD是用来描述系统行为的主要方式,在 大多数情况下足以满足需求。 口有时需要对系统行为进行更为详细和精确的描述 口操作契约用于描述领域模型里对象的详细变化, 作为系统操作的结果
为什么需要操作契约 用例和SSD是用来描述系统行为的主要方式，在 大多数情况下足以满足需求。 有时需要对系统行为进行更为详细和精确的描述 操作契约用于描述领域模型里对象的详细变化， 作为系统操作的结果