1、1. What are the three generic phases of software engineering? 什么是软件工程的三个通用阶段?(1) Definition phase 定义阶段(2) Development phase 发展阶段(3) Support phase 支持阶段2. Describe the phases of the prototyping model for software development.描述原型模型的软件开发的阶段Developer and customer meet and define the overall objectives f
2、or the software , identify requirements. 开发人员和客户会面并定义软件的总体目标 ,确定需求。The quick design sign leads to the construction of a prototype. 快速设计符号导致原型的建设。A prototype evaluated by the customer and used to refine the requirements. 原型评估客户和用于改进需求。Iteration occurs and the prototype is tuned to satisfy the custome
3、rs needs. 迭代发生和原型是调优,以满足客户的需求。3. Why are evolutionary models considered by many to be the best approach to software development?为什么进化模型被许多人认为是软件开发的最佳方法？Because time lines for the development of modern software are getting shorter and shorter, customers are becoming more diverse, and changes to requi
4、rements are becoming even more common (before delivery), we need a way to provide incremental or evolutionary delivery. The evolutionary process accommodates uncertainty better than most process models, allows the delivery of partial solutions in an orderly and planned manner, and most importantly,
5、reflects what really happens when complex systems are built.由于时间线的发展，现代软件变得越来越短，客户变得更加多样化，和变化的要求变得更加常见（交付之前），我们需要一种方式提供增量或进化交付。进化过程容纳不确定性，比大多数过程模型，允许交付的部分解决方案，在一个有序的和有计划的方式，最重要的是，反映了什么是真正发生时，复杂的系统。4. What are the five phases of software requirements analysis?什么是软件需求分析的五个阶段?Problem recognition 问题识别Ev
6、aluation and synthesis 评价和合成Modeling 建模Specification 规格Review 审查5. Describe the facilitated application specification technique (FAST).描述促进应用规范技术（快速）A meeting is conducted at a neutral site 在一个中立的地点开会Rules for preparation and participation are established 制定准备和参与的规则An agenda is suggested that is for
7、mal enough to cover all important points but informal enough to encourage the free flow of ideas 建议一项议程是正式的，足以涵盖所有重要的观点，但不足以鼓励自由流动的思想A “facilitator” controls the meeting 一个“ 促进”控制会议A “definition mechanism” is used 使用“定义机制”6. What are three primary objectives of the analysis model?什么是三个主要目标的分析模型?to d
8、escribe what the customer requires 来描述客户的要求to establish a basis for the creation of a software design 建立软件设计创作的基础to define a set of requirements that can be validated once the software is built 定义一组一旦建立了该软件，则可以进行验证的要求7. What are the data modeling elements represented in the entity relationship diagr
9、am (ERD)?代表的实体关系图 (ERD) 中的数据建模元素有哪些?Data objects - any entity producing or consuming information数据对象-任何实体生产或消费信息Attributes - data characteristics associated with a data object instance属性-与一个数据对象实例相关联的数据特性Relationships - indicate manner in which data objects are connected关系的表示的方式中，数据连接对象8. List the e
10、lements of the analysis model and explain the role of each element? 列出的分析模型的元素，并解释每个元素的作用？Data dictionary - contains descriptions of all data objects produced or consumed by the software 数据字典包含所有数据对象的产生或消耗的软件描述Entity relationship diagram (ERD) - depicts data object relationships 实体关系图（ERD）-描述数据对象之间的
11、关系Data flow diagram (DFD) - provides an indication of how data are transformed as they move through the system and the functions that transform the data flow 数据流图（DFD ）-提供了一个指示数据如何转化为他们移动通过系统和函数变换的数据流State transition diagram (STD) - indicates system responses to external events状态转换图（STD）-表示系统对外部事件的响
12、应9. List the four design models required for a complete specification of a design and explain how each is created.列出四个设计模型所需的完整规范设计和解释每一个构件是如何创建的。solution:解决方案:Data design - created by transforming the ERD and data dictionary into data structures required for software implementation.数据设计由改变 ERD 和数据字
13、典数据结构所需的软件实现。Architecture design - derived from the system specification and the subsystem interactions defined in the DFD.建筑设计来自中定义的系统规范和子系统交互过程。Interface design - derived from the DFD and CFD by focusing on how the software elements (humans and systems) interact.界面设计来自过程和 CFD 通过专注于软件元素(人类和系统)是如何交互
14、的。Component-level design - structural elements defined in the PSPEC, CSPEC, and STD are transformed into procedural descriptions of the software components 组件级设计,结构元素中定义 PSPEC,CSPEC,STD 被转化为程序的软件组件的描述10. Success criteria 成功标准1) Deliver the software to the customer at the agreed time.在约定的时间内将软件交付给客户。
15、2) Keep overall costs within budget.在预算内保持整体的成本。3) Deliver software that meets the customers expectations.提供符合客户期望的软件。4) Maintain a happy and well-functioning development team.保持一个快乐、运作良好的发展团队。11. Maintenance problems 与维护有关的问题1)Staff problems 人员问题 Limited understanding 理解的局限性 Management priorities 管
16、理的优先级 Morale 士气2)Technical problems 技术问题 Artifacts and paradigms 工件和范例 Testing difficulties 测试困难12. Types of maintenance 维修类型1) Maintenance to repair software faults 维修软件故障Changing a system to correct deficiencies in the way meets its requirements.改变一个系统，以纠正缺陷的方式符合其要求。2) Maintenance to adapt softwar
17、e to a different operating environment维护，以适应不同的操作环境Changing a system so that it operates in a different environment (computer, OS, etc.) from its initial implementation.改变一个系统，使它在不同的环境（计算机，操作系统等）从它最初的执行。3) Maintenance to add to or modify the systems functionality维护或修改系统的功能Modifying the system to sat
18、isfy new requirements.修改系统以满足新的需求。13. Factors affecting maintenance effort 影响维护成果的因素Application type 应用类型System novelty 系统新奇度Turnover and maintenance staff ability 人员翻新和维护人员能力System life span 系统生命期Dependence on a changing environment 对变化的环境的依赖Hardware characteristics 硬件特性Design quality 设计质量Code qual
19、ity 代码质量Documentation quality 文档质量Testing quality 测试质量14. Software management distinctions 软件管理的区别1) The product is intangible.该产品是无形的Software cannot be seen or touched. Software project managers cannot see progress by simply looking at the artifact that is being constructed. 软件不能被看见或触摸。软件项目经理不能看到进展
20、，只是看正在构建的神器2) Many software projects are one-off projects.许多软件项目都是一次性项目Large software projects are usually different in some ways from previous projects. Even managers who have lots of previous experience may find it difficult to anticipate problems. 大型软件项目通常在某些方面与以往的项目不同。即使有很多以前经历的管理者也会发现很难预测问题3) S
21、oftware processes are variable and organization specific.软件过程是可变的和组织的We still cannot reliably predict when a particular software process is likely to lead to development problems.当一个特定的软件过程可能导致开发问题时，我们仍然无法可靠地预测15. The risk management process 风险管理过程1) Risk identification 风险识别Identify project, product
22、 and business risks;确定项目，产品和商业风险2) Risk analysis 风险分析Assess the likelihood and consequences of these risks;评估这些风险的可能性和后果3) Risk planning 风险规划Draw up plans to avoid or minimize the effects of the risk;制定计划，以避免或减少风险的影响4) Risk monitoring 风险监测Monitor the risks throughout the project;监控整个项目的风险16. Group o
23、rganization 集团组织1) The way that a group is organized affects the decisions that are made by that group, the ways that information is exchanged and the interactions between the development group and external project stakeholders. 一组有组织的方式影响到该组的决策，信息交换的方式和发展集团和外部项目利益相关者之间的相互作用。2) Small software engine
24、ering groups are usually organized informally without a rigid structure.小型软件工程组通常是没有严格的结构组织起来的。3) For large projects, there may be a hierarchical structure where different groups are responsible for different sub-projects.对于大型项目，有可能是一个层次结构，不同的小组负责不同的子项目。4) Agile development is always based around an informal group on the principle that formal structure inhibits information exchange敏捷开发是一个非正式群体的原则，正式结构抑制信息交流
