山东大学软件工程课件Chapter04.pptVIP

Why are requirements important? --See Sidebar 4.1 on Page 142. 4.1 The Requirements Process 4.1.1. Requirement 需求的定义 A proposed software system has a purpose, usually expressed in terms of goals or desired behavior. A Requirement: is an expression of desired behavior. Requirements: Are specific descriptions of functions or characteristics that address the general purpose of the system. 4.1.2. The requirements process Step 1: Elicition 需求引导 Step 2: Analysis 分析和建模 Step 3: Specification 形成文档 Step 4: Validation 验证和确认 4.2 Requirements Elicitation 1. Requirements elicitation is critical/difficult. Requirements are ill-formed and ill-understood by everyone. Customers know their business ,but cannot always describe their business problems to outsiders. Developers know about computer solutions, but not always about how possible solutions will affect the customers’ business activities. People have different meanings for the same words. 2. Stakeholders: 利益相关者 Clients who are the ones paying for the software development; 委托人 Customers who buy the software; 顾客 Users who will use the software; 用户 Domain experts who are familiar with the software to be developed; 领域专家 Market researchers; 市场调查人员 Lawyers or auditors; 律师/审计员 Software engineers or other technology experts. 技术专家 4. The goal of the Requirements process 目的 Requirements are elicited at the beginning of development, and the goal is to determine the nature of the customer’s problem Problem and understanding is mostly easily stated in terms of the customer’s business Requirements should be focused on the customer and the problem, not on the solution or implementation A discussion of any solution is premature until the problem is clearly defined 4.3 Types of Requirements 1. Functional requirement and Nonfunctional requirement See Table 4.2. (1) Functional requirement 功能性需求 做什么功能需求 (2) Quality/Nonfunctional Requirement 质量/非功能性需求 做得怎样质量需求 (3) Design Constraint 设计约束 (4) Process Constraint 过程约束 2. Making Require