MSF for CMMI Process Improvement项目体验: Work Items : Requirement （更新版）

从MSF的角度来看：

需求分类：

l         Customer Requirement：Scenario, quality of service

l         Product Requirement：Safety, security, functional, operational, and interface

体会：

微软把需求文档分为2种，客户需求和产品需求。

总体感觉采集客户需求的时候，文字格式化的工作不是非常严，比RUP的模版要简单得多，但是微软提出Storyboard Scenarios，这是图形化的需求表示，Storyboard Scenarios包含Generate Screenshots和Create Screen Flow Diagram。我使用的微软一些软件来看，微软自己应该也是按照这样的流程来做的，因为我在一些软件没有正式发布出来时候，看到很多Screenshots，那些Screenshots是使用VISIO之类的软件制作出来的。而且制作Screenshots好处也是显而易见的,用户可以有感性的认识，对需求采集很有帮助。Screen Flow Diagram是对流程的认识,有了这几步骤，用户的可视化的需求基本完整了，那些非可视的需求可以在quality of service重点说明。

对于产品需求来讲，重点是要指导限定设计。

 

涉及流程：

Envision阶段：

l         Product Manager：Capture Product Vision

 

Planning阶段：

l         Business Analyst：Create a Scenario

l         Solution Architect：Create a Quality of Service

l         Project Manager：Plan Project

l         Solution Architect：Create Solution Architecture

l         Business Analyst：Create Product Requirements

l         Project Manager：Plan an Iteration

 

Build阶段：

l         Solution Architect：Analysis

l         Developer：Implement a Development Task

l         Developer：Fix a Bug

l         Tester：Test a Customer Requirement

l         Tester：Verify a Product Requirement

体会：

       按部就班的跟着这些流程走，当然是可以走通的，但是问题的关键当然不是走形式，不是能走通就行，每个阶段，都有自己的目标和里程碑。Envision阶段目标是确定范围；Planning阶段是细化明确用户需求，确定本次迭代需要先做哪些。Build阶段就要分析、实现和验证需求。

从CMMI的角度来看：

CMMI包含若干PA（Process Area），每个PA包含若干Goal，每个Goal包含若干Practices,微软通过Work streams and Activities来实现这些Practices。具体清单：

 

CMMI 涉及到需求的PA有2个：

1.         Requirements Development（CMMI Process Area）

1)        Develop Customer Requirements(CMMI Goal)

u       Elicit Needs(CMMI Practices)

l         User Experience Architect：Develop Lifestyle Snapshot（Work streams and Activities）

l         Business Analyst：Brainstorm Scenarios

l         Business Analyst：Brainstorm Quality of Service Requirements

l         Tester：Conduct Exploratory Testing

u       Develop the Customer Requirements

l         Business Analyst：Brainstorm Scenarios

l         Business Analyst：Brainstorm Quality of Service Requirements

2)        Develop Product Requirements

u       Establish Product and Product-Component Requirements 

l         Solution Architect：Define Functional Requirements

l         Solution Architect：Define Security Requirements

l         Solution Architect：Define Safety Requirements

u       Allocate Product-Component Requirements 

l         Solution Architect：Allocate Product Component Requirements

u       Identify Interface Requirements

l         Solution Architect：Define Interface Requirements

3)        Analyze and Validate Requirements

u       Establish Operational Concepts and Scenarios

l         User Experience Architect：Develop Lifestyle Snapshot

l         Business Analyst：Write Quality of Service Requirements

l         Business Analyst：Write Scenarios

l         User Experience Architect：Storyboard Scenarios

l         Solution Architect：Define Operational Requirements

u       Establish a Definition of Required Functionality 

l         Solution Architect：Develop a Domain Model

l         Solution Architect：Define Functional Requirements 

l         Solution Architect：Define Interface Requirements 

l         Solution Architect：Define Security Requirements 

l         Solution Architect：Define Safety Requirements 

l         Solution Architect：Define Operational Requirements  

u       Analyze Requirements 

l         User Experience Architect：Develop a User Interface Flow Model

l         Solution Architect：Develop a Domain Model

u       Analyze Requirements to Achieve Balance 

l         Business Analyst：Prioritize Quality of Service Requirements

l         Business Analyst：Prioritize Scenarios

l         User Experience Architect：Develop a User Interface Flow Model

l         Solution Architect：Develop a Domain Model

l         Project Manager：Select Iteration Backlog

u       Validate Requirements With Comprehensive Methods

l         Solution Architect：Validate Quality of Service Requirements

l         User Experience Architect：Validate Scenarios

l         Subject Matter Expert：Validate Requirements

2.         Requirements Management

n         Manage Requirements

u       Obtain an Understanding of Requirements 

l         Business Analyst：Brainstorm Scenarios

l         Business Analyst：Brainstorm Quality of Service Requirements

u       Obtain Commitment to Requirements 

l         Project Manager：Obtain Iteration Commitments

l         Project Manager：Obtain Project Commitments

u       Manage Requirements Changes 

l         Business Analyst：Analyze Change Request

l         Release Manager：Track Change Requests

u       Maintain Bidirectional Traceability of Requirements 

u       Identify Inconsistencies Between Project Work and Requirements

l         Auditor：Identify Inconsistencies