13. （二）ICONIX过程方法
需求 设计 实现ICONIX Process is a use
case–driven analysis and
design methodology. Its
main focus is on how to get
reliably from use cases to
code in as few steps as
possible.
分析
45. 业务建模示例：业务用例+用例描述
• Basic Flow for Prepare Tender
– This business use case begins when the End User Department requires additional automation to improve operations. The goal is to
finalize a tender document that can be issued to candidate vendors.
– 1. Designation of End User Manager. The procurement department designates an End-User Manager for the entire acquisition process.
– 2. Prepare System Specifications. The End-User Manager prepares and submits specifications to the IT department.
– 3. Prepare Tender Document. The IT department reviews submitted specifications and prepares a tender document, augmenting the
submitted specifications with contractual requirements.
– 4. Approval of Tender Document. The End-User Manager reviews and approves the tender document. The use case then terminates.
• Alternate Flows
– 1. System Specifications Invalid. In Step 3, if the IT department finds the system specifications are too vague or unfeasible, the End-User
Manager needs to rework the specifications. The business use case then either resumes at Step 2 or terminates if the End-User Manager
does not wish to continue.
– 2. System Already Exists. In Step 3, if the IT department finds that the desired system is very similar to an existing system in another
department, then the IT department refers the End-User Manager to that department. If the End-User Manager wishes to proceed with
acquiring the "new" system, he or she must put the differentiating features in the system specifications, resubmit the specifications, and
continue at Step 2. The business use case terminates if the End-User Manager does not wish to continue.
– 3. Tender Document Discrepancies. In Step 4, if the End-User Manager notices discrepancies in the Tender Document, it is rejected, and
the IT department must rework it. The business use case continues at Step 3.
class Business Use Cases
«business actor»
End User Manager
Prepare Tender
Select Vendor
«business actor»
Vendor Manager
46. 业务建模示例：业务实现建模 – 时序图
sd Interaction
«business actor»
End User Manager IT Project Manager Enterprise
Architect
Legal Officer
Supplement Tender with Legal Terms()
Review Tender Document()
Prepare System Specification()
Prepare Tender Document()
Review and Supplement System Specification()
• 关注工作流程
• 重点在于区分职
责而非信息流
典型错误：
47. 业务建模示例：业务实现建模 – 时序图(续)
• 业务实现优化
– 引入自动化业务
工人（信息系统）
后的时序图变化
– 物流改成信息流
– 信息流改善
– 封装领域逻辑
sd Interaction2
«business actor»
End User Manager IT Project Manager Enterprise
Architect
Legal Officer Tender
Management
System
Contract
Management
System
Review and Supplement System Specification()
Prepare System Specification()
Supplement Tender with Legal Terms()
Prepare Tender Document()
Review Tender Document()
Search Contracts()
54. 系统需求示例：用户需求建模-系统用例图
• 区分系统需求与
系统需求实现的
区别
• 建模的用例粒度
控制到“系统对
用户提供的价
值”，即用户需
求层次，不需要
过细。
uc Prepare Tender Document
TenderSystem
End User Manager
Enterprise Architect
IT Project Manager
Legal Officer
Contract System
Prepare System
Specification
Rev iew Tender
Document
Supplement Tender
with Legal Terms
Prepare Tender
Document
Rev iew and
Supplement System
Specifications
55. 系统需求示例：用例描述
• Basic Flow
– This use case begins when the End-User Manager wants to review a tender document after being
notified by the IT Project Manager that the document has been completed.
– 1. List Tender Documents. The system retrieves and displays a summary list of Tender Documents for
the End-User Department, showing their status.
– 2. Open Tender Document. The End-User Manager selects a Tender Document. The system retrieves
and displays it.
– 3. Review Tender Document. The End-User Manager reviews the system specifications and legal
terms.
– 4. Tender Document Acceptable. If the End-User Manager accepts the contents, she or he approves
the document. The system notes the decision, and the IT department can now open the tender for
bidding. The use case terminates.
• Alternate Flows
– 1. Legal Terms Unacceptable. If in Step 3 of the Basic Flow the End-User Manager finds the Legal
Terms unacceptable, the reasons for rejecting them is noted. The system notifies both the IT Project
Manager and the Legal Officer of the rejection. The use case terminates.
– 2. System Specifications Unacceptable. If in Step 3 of the Basic Flow the End-User Manager finds the
System pecifications unacceptable, the reasons for rejecting it are noted. The system notifies both
the IT Project Manager and the Enterprise Architect of the rejection. The use case terminates.
Review Tender Document用例描述：
77. 敏捷需求方法：产品规划-版本计划
• 用户故事地图
(User Story
mapping)
– 决定构建优先级
– 鼓励迭代开发
– 确定项目范围
– 制定版本计划
– 排序和梳理
Backlog
– 可视化项目进度
User Activities
(Backbone)
User Tasks
(Walking Skeleton)
User Stories
http://www.slideshare.net/SteveRogalsky/user-story-mapping-in-practice
78. 敏捷需求方法：产品规划-版本计划(续)
• 从影响地图(Impact mapping)到用户故事地图(User Story Mapping)
– 每一个版本都应当有明确的商业意图，形成合力
– 通过KPI指标对结果进行监控，评测产品版本
Our Job is NOT to develop
software, our job is to
change the world.
- Jeff Patton
http://www.slideshare.net/chassa/2014-0618srdimpact-mapsstorymapsen
82. 敏捷需求方法：版本计划-MVP(续2)
• 确定MVP
– 客户调查
– 确定功能的四
象限
• 值得注意的是，
随着时间推移，
曾经属于加分
项的功能需求
可能慢慢变为
用户的基本需
求
– 壁垒
Delighters
• Things
customers are
excited about
Basic features
• Things
customers need
• “Must Be”
Performance Indifferent
• More is better • Not needed
93. 系统分解-分层结构
pkg Component Model
Infrastructure(Frameworks)
Presentation Infra
Infrastructure(Common Utilities)
Application Assembly
Business Domain
Application Infra
Domain Model Infra
Persistence Infra
Cross Cutting
Domain Model
Domain Repository Impl
Application
Query Model
Distributed Interface
Presentation
Distributed Infra
Web Clients (UI Views, Controllers, etc)
Web-Services DTOs
Application Services Components(Workflow, etc)
DomainServicesDomain
Objects
(Entities,
VOs)
RepositoryContracts
Result View Objects
Queries
Data Integration
Security(Authentication,
Authorization &Auditing)
Monitoring
(Warning&Alarm,
Functional&Performance)
diagnosable(Exception,
Log&Trace)
Integration Services
(UI/Service/Data
Integartion, extendable)
注：包层次结构的依赖关系
• 按照组件的可重用性进行分层
94. 系统分解-分区结构
Sales
Product
SKU
Name
Price
Quantity Ordered
…
Inventory Service (SAP)
Product
SKU
QOH
Location Code
…
Pricing Service
Product
SKU
Unit Price
Promotional Price
…
Inventory
Pricing
Sales
Customers
New
SKU
Event
New
SKU
Event
New
SKU
Event
Order
Accepted
Event
MessageBus
Who
coordinates the
sales process?
Online Ordering System
Web Shop
(Composite UI)
• 按照业务领域/服务职责进行分区
