REQUIREMENTS ENGINEERING 需求工程
Requirements engineering encompasses seven distinct tasks: inception, elicitation,elaboration, negotiation, specification, validation, and management
Inception 启动
At project inception, you establish a basic understanding of the problem,the people who want a solution, the nature of the solution that is desired, and the effectiveness of preliminary communication and collaboration between the other stakeholders and the software team
在项目启动时，您对问题、需要解决方案的人员、所需解决方案的性质以及其他利益相关者和软件团队之间初步沟通和协作的有效性建立了基本的了解
Elicitation 启发
Establish business goals.Once the goals have been captured, a prioritization mechanism should be established,and a design rationale for a potential architecture (that meets stakeholder goals
建立业务目标,一旦确定了目标，就应该建立优先级机制，以及潜在架构的设计原理（满足利益相关者的目标)
Elaboration 细化
The information obtained from the customer during inception and elicitation is expanded and refined during elaboration. This task focuses on developing a refined requirements model
在初始和启发过程中从客户获得的信息在细化过程中得到扩展和细化。这项任务的重点是开发一个精细的需求模型
Negotiation 谈判
You have to reconcile these conflicts through a process of negotiation. Customers, users, and other stakeholders are asked to rank requirements and then discuss conflicts in priority.
你必须通过谈判的过程来调和这些冲突。要求客户、用户和其他利益相关者对需求进行排序，然后按优先级讨论冲突
Specification 规范
a written document, a set of graphical models, a formal mathematical model,a collection of usage scenarios, a prototype, or any combination of these.
一份书面文档、一组图形模型、一个正式的数学模型、一组使用场景、一个原型或这些的任意组合
Validation 验证
a consequence of requirements engineering are assessed for quality during a validation step。technical review
对需求工程产生的工作产品进行质量评估，技术审核
Requirements management 需求管理
help the project team identify,control, and track requirements and changes to requirements at any time as the project proceeds
帮助项目团队在项目进行过程中随时识别、控制和跟踪需求以及需求变更
ESTABLISHING THE GROUNDWORK(Inception) 建立基础（启动）
- Identifying Stakeholders 识别利益相关者
- Recognizing Multiple Viewpoints 认识多种观点
- Working toward Collaboration 努力协作
- Asking the First Questions 提出第一个问题
- Nonfunctional Requirements（a quality attribute, a performance attribute, a security attribute） 非功能性需求（质量属性、性能属性、安全属性）
- Traceability（documented links between software engineering work products） 可追溯性（工作产品（例如，需求和测试用例）之间记录的链接）
ELICITING REQUIREMENTS(elicitation) 获取需求（获取）
- Collaborative Requirements Gathering 协作需求收集
- Quality Function Deployment（“concentrates on maximizing customer satisfaction from the software engineering process”） 质量功能展开（专注于最大限度地提高软件工程过程中的客户满意度）
- Usage Scenarios(Developing a Preliminary User Scenario(use case diagram)) 使用场景（开发初步用户场景（用例图））
- Elicitation Work Products(requirement specification) 获取工作产品（需求规范）
DEVELOPING USE CASES(how to develop use case diagram) 开发用例（如何开发用例图）
BUILDING THE ANALYSIS MODEL(elaboration) 构建分析模型（详细阐述）
Elements of the Analysis Model 分析模型的元素
- Scenario-based elements: use case diagram
基于场景的元素：用例图 - function elements: activity diagram(function model, depicts the business logic for each
功能元件:活动图（功能模型，描述每个用例的业务逻辑）。 - Class-based elements（information or data elements）: class diagram(information model)
基于类的元素（信息或数据元素）：类图（信息模型） - Behavioral elements: state diagram and sequence diagram
行为元素：状态图和序列图