没有合适的资源?快使用搜索试试~ 我知道了~
软件工程参考答案(中文注释).doc
0 下载量 99 浏览量
2023-07-04
15:20:03
上传
评论
收藏 1.99MB DOC 举报
温馨提示
试读
28页
软件工程参考答案(中文注释).doc
资源推荐
资源详情
资源评论
.
整理 doc
软件工程(外文教材)复习
一、 Fill in the blanks(X blanks, 1 point/blank, total
XX points)
(一) Chapter 1
1. Today, software takes on a dual role. It is a product, and the same time, the
vehicle for delivering a product. 1。今天,软件具有双重作用。这是一个产品,同
时,交付产品的车辆。
2. Software delivers(提供) the most important product of our time----information.
3. software doesn't wear out, but it does deteriorate 软件没有磨损,但它恶化
4. Software engineering is a layered technology. Any engineering approach must rest
on an organizational commitment to quality 软件工程是一个分层的技术。任何工程方
法必须依赖于一个组织对质量的承诺。
5. software engineering encompasses(包括) a process, method for managing and
engineering software, and tools. 5。软件工程过程,用于管理和软件工程方法和工
具。
6. Umbrella activities occur throughout the software process and focus primarily
on project management, tracking, and control. 6。伞活动发生在整个软件过程和主要
集中在项目管理,跟踪,控制。
(二) Chapter 2
7. A process was defined as a collection of work activities, actions and tasks that
are performed when some work product is to be created. 定义为一个集合的工作是一个
过程,活动和任务执行时的一些工作产品被创建。
8. There are four different process flow: Linear process flow, iterative process
flow, evolutionary process flow, parallel process flow 有四种不同的工艺流程:
线性流程,迭代流程,进化过程流,并行流程
9. Three types of process pattern are: stage pattern, task pattern, phase pattern 三
种过程模式:阶段模式,任务模式,相模式
10. Prescriptive process models were originally proposed to bring order to the chaos
of software development.规定的过程模型最初提出的软件开发的混乱带来秩序。
.
整理 doc
11. Prescriptive process models have been applied for many years in an effort to
bring order and structure to software development. 11。规定的过程模型已经被应用
在努力使软件开发秩序和结构多年。
12. The Unified Process is a "use case driven, architecture-centric, iterative and
increment" software process designed as a framework for UML methods and tools.
统一的过程是一个“用例驱动,以体系结构为中心,迭代和增量”设计为 UML 的方法和
工具的框架,软件过程
13. The incremental model combines elements of linear and parallel process flows.增量
模型相结合的线性和平行的流程元素。
14. When an incremental model is used, the first increment is often a core product.
当一个增量模型时,第一个增量往往是核心产品
15. When your customer has a legitimate need, but is clueless about the details,
develop a prototype as a first step. 当你的客户有一个合法的需要,但对细节一无所
知,开发了一个原型作为第一步
16. The spiral model is an evolutionary software process model that couples the
iterative nature of prototyping with the controlled and systematic aspects of
the waterfall model. 螺旋模型是一种进化的软件过程模型,对原型的迭代性质与控制
和瀑布模型系统方面
17. The spiral development model is a risk-driven process model generator.. The 螺旋
发展模型是风险驱动的过程模型的发电机。
(三) chapter 3
18. An agile process reduces the cost of change because software is released in
increments. 一个敏捷过程中减少变化的成本,因为软件发布增量。
19. Beck defines a set of five values that establish a foundation for all work
performed as part of XP ---- communication, simplicity, feedback, courage, and
respect. 贝克定义了一组五个值,所有的工作为 XP ----沟通,简单,反馈,勇气,
和尊重。
20. Refactoring improves the internal structure of a design without changing its
external functionality or behavior. 重构,
21. 提高了设计的内部结构而不改变其外部的功能或行为
22. XP acceptance tests are derived from user stories. XP 的验收测试,来自用户故
事
(四) chapter 4
23. Requirements engineering builds a bridge to design and construction 需求工程
的桥梁设计与施工
24. Requirements engineering encompasses seven distinct tasks: inception,
elicitation, elaboration, negotiation, specification, validation, and
management. 需求工程包括七个不同的任务:起始,启发,制定,协商,规范,验证,
和管理
.
整理 doc
25. Quality function deployment identifies three types of requirements: normal
requirements, expected requirements, exciting requirement. 质量功能展开确定了
三种类型的要求:正常的要求,要求,令人兴奋的要求
26. The intent of the analysis model is to provide a description of the required
informational, functional, and behavioral domains for a computer-based system.
分析模型的目的是提供所需信息的描述,功能,和一个基于计算机的系统行为域
(五) chapter 5
27. The requirement model - actually a set of models - is the first technical
representation of a system. 需求模型是一组模型-是第一个技术系统的表示
28. The requirements modeling action results in one or more of the following types
of models: Scenario-based models, data models, class-oriented models,
flow-oriented models, behavioral models. 在以下一个或多个类型的模型作用的结果,
建模的要求:基于场景的模型,数据模型,面向类的模型,流量导向模型,行为模型
29. The analysis model and requirements specification provide a means for assessing
quality once the software is built. 分析模型和要求规范一旦建立软件质量评估提
供了一种手段
30. An association defines a relationship between classes. Multiplicity defines how
many of one class are related to how many of another class. 一个关联定义类之
间的关系。多重定义多少一级与另一个类的多少
(六) chapter 6
31. The DFD takes an input-process-output view of a system. DFD 需要一个系统的输入输出过
程观
(七) chapter 7
32. The importance of software design can be stated with a single word-- quality.
软件设计的重要性,可以说一个字——质量
33. Independence is assessed using two qualitative criteria: cohesion and coupling.
Cohesion is an indication of the relative functional strength of a module.
Coupling is an indication of the relative independence among modules. 使用两
个独立的评估的质量标准是:衔接和耦合。凝聚力是一种指示功能模块的相对强度。耦
合是一个相对独立的模块,在显示
34. Functional independence is achieved by developing modules with "single-minded"
function and an "aversion" to excessive interaction with other modules. 功能
独立性是通过发展与“专一”功能和“厌恶”与其他模块的相互作用模块实现过
35. The design model has four major elements: data, architecture, components, and
interface. 设计模式有四大要素:数据,体系结构,成分,和接口
36. At the architectural level, data design focuses on files or databases; at the
component level, data design considers the data structures that are required
to implement local data objects. 在建筑设计,数据以文件或数据库;在组件级别的
数据认为,设计要求实现本地数据对象的数据结构
.
整理 doc
37. There are three parts to the interface design element: the use interface,
interfaces to system external to the application, and interfaces to components
within the application. 有三个部分:界面设计元素的使用界面,对应用程序的外部
系统的接口,而接口组件内的应用
38. Deployment-level design elements indicate how software functionality and
subsystems will be allocated within the physical computing environment that will
support the software. 部署水平设计元素说明软件的功能和子系统将在物理计算环境
配置,将支持软件
(八) chapter 8
(九) chapter 9
39. List three types of cohesion within the context of component-level design for
OO system: Functional, layer, communicational, 。表三种衔接在组件级设计中面
向对象的系统:功能,层,通信
40. List three types of cohesion within the context of component-level design for
OO system: Content coupling, common coupling, control coupling. 表三种衔接在
组件级设计中面向对象的系统:内容耦合,公共耦合,控制耦合
41. Three constructs in structured programming are: sequence, condition, and
repetition. 三结构在结构化程序设计:序列,条件,和重复
(十) chapter 10
42. Three golden rules for GUI design are: place the user in control, reduce the
user's memory load, make the interface consistent. 控制用户的活动,减少用户
的记忆负担,使界面保持一致
43. The user interface design process encompasses four distinct framework
activities: (1)interface analysis and modeling, (2) interface design, (3)
interface construction, (4)interface validation. 用户界面设计过程包括四个不同
的框架活动:(1)界面的分析和建模,(2)界面设计(3)界面结构,(4)接口的验证
44. Four different models come into play when a user interface is to be analyzed
and designed. These models are: user model, design model, the user's mental model
implementation model. 四种模式进入游戏时,用户界面是被分析和设计。这些模型是:
设计模型,用户模型,用户的心理模型的实现模型
45. As the design of a user interface evolves, four common design issues almost
always surface: system response time, user help facilities, error information
handling, and command labeling. 系统响应时间、用户帮助设施,错误信息处理和命
令标记
46. System response time has two important characteristics: length and variability 系
统的响应时间有两个重要的特征:长度和变异性
(十一) chapter 11
.
整理 doc
47. McCall's quality factors focus on three important aspects of a software product:
product operation, product transition, product revision 麦考尔的质量的因素集
中在一个软件产品的三个重要方面:产品操作,产品过渡,产品修改
(十二) chapter 12
48. FTR is the abbreviation of Formal technical review. FTR 是正式的技术审查的缩
写
(十三) chapter 14
49. V&V, Verification: Are we build the product right? Validation: Are we build the
right product? V&V,验证:我们建立产品吗?验证:我们建立正确的产品?
50. Software testing strategy begins from small scale to large scale, undergoes four
different testing: unit testing, Integration testing, validation testing,
System testing. 软件测试的策略,从小型到大型,经历了四个不同的测试:单元测试,
集成测试,确认测试,系统测试
51. Because a component is not a stand-alone program, driver and/or stub software
must often be developed for each unit test. 因为一个组件是不是一个独立的程序,
驱动程序和/或存根软件必须经常被开发为每个单元测试
52. In the context of an integration test strategy, regression testing is the
reexecution of some subset of tests that have already been conducted to ensure
that changes have not propagated unintended side effects. 在一个集成测试策略
的背景下,回归测试是对已经进行,确保变化不会传播意想不到的副作用的一些子集的
重新执行测试
(十四) chapter 15
53. List three characteristics of software testability: Operability, observability,
Controllability 软件可测试性三个特点:可操作性 observability(可观测性),可控
性
54. There are two kinds of test case design methods for conventional software:
white-box testing and black-box testing. 传统的软件测试案例设计方法:白盒测试
和黑盒测试
(十五) chapter 16
55. There are two different strategies for integration testing of OO Systems:
Thread-based testing and use-based testing. 有面向对象的系统集成测试的两种不
同的策略:基于线程的测试和基于使用的测试
(十六) chapter 17
(十七) chapter 18
56. Effective software project management focuses on the four P's: People, Product,
process, project.有效软件项目管理的重点是四个 P:人,产品,工艺,工程
剩余27页未读,继续阅读
资源评论
yyyyyyhhh222
- 粉丝: 412
- 资源: 6万+
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功