2014软件工程各章节重要知识点(按考试大纲总结)

1、2014软件工程各章节重点知识点（按考试大纲总结）第1章 ：软件工程的范畴THE SCOPE OF SOFTWARE ENGINEERING1掌握软件工程、软件危机、生命周期的概念 1%Software engineering is a discipline学科 aim is the production生产 of software.fault-free;delivered on time ;within budget;satisfies the clients needs;be easy to modify when the needs changeSoftware crisis:the q

2、uality of software was unacceptably low,deadlines and budgets were not being met.Life-cycle model:The steps to follow遵循 when building构建 software,A theoretical description理论描述 of what should be done.Life cycle:The actual steps实际步骤 performed执行 on a specific具体 product.2掌握维护的3种分类并能够结合具体例子进行判断 1%Postdeli

3、very maintenance:Corrective纠错性 maintenance;Perfective完善性 maintenance;Adaptive适应性 maintenanceCorrective纠错性 maintenance:removal去除 of residual faults残留错误 ;leaving the specifications规格说明文档 unchangedPerfective完善性 maintenance:additional functionality额外功能;decreased response time减少响应时间Adaptive适应性 maintenanc

4、e:changes made in response to changes in the environment3掌握为什么没有计划、文档和测试阶段 1%Why There Is No Planning Phase计划阶段, Testing Phase测试阶段 or Documentation Phase文档阶段?Planning, continual持续的 testing and documentation activities活动 are carried out执行 throughout贯穿于 the life cycle.There is no separate独立的 planning,

5、 testing or documentation phase.This testing is the responsibility职责 of Every software professional专业人员, and The software quality assurance group软件质量保证小组(SQA group) Documentation Must Always be Current:Key individuals may leave before the documentation is complete.We cannot perform a phase without h

6、aving the documentation of the previous phase.We cannot test without documentation.We cannot maintain without documentation.4掌握软件工程的传统生命周期模型（瀑布模型）的阶段划分和各阶段的主要任务1%Classical(Waterfall瀑布) Life-Cycle Model 1. Requirements phaseExplore研究 the concept概念;Elicit提取 the clients requirements客户需求2. Analysis (spe

7、cification) phaseAnalyze分析 the clients requirements;Draw up制定 the specification document规格说明文档(specifications);Draw up the software project management plan软件项目管理计划(SPMP);“What the product is supposed期望 to do”3. Design phaseArchitectural design结构设计, followed by;Detailed design详细设计;“How the product do

8、es it”4. Implementation phaseCoding编码;Unit testing单元测试;Integration集成;Acceptance testing验收测试5. Postdelivery maintenanceCorrective纠错性 maintenance;Perfective完善性 maintenance;Adaptive适应性 maintenance6. Retirement5掌握传统的维护观念与现代的维护观念之间的区别1%Classical maintenance is Development-then-maintenance model开发-维护 模型Th

9、is is a temporal时间性 definition,Classification归类 as development or maintenance depends on取决于 when an activity is performed.Modern Maintenance is nowadays defined as:The process过程 that occurs when a software artifact软件制品 is modified被修改 because of a problem or because of a need for improvement改善 or ada

10、ptation适应.Maintenance occurs whenever software is modified修改.Regardless of不管 whether this takes place before or after installation of the software product.Modern maintenance is corrective, perfective, or adaptive maintenance performed at any time.第2章 ：软件生命周期模型SOFTWARE LIFE-CYCLE MODELS1 掌握编码-修补模型、瀑布

11、模型、快速原型开发模型、开源模型、敏捷过程模型、同步-稳定模型、螺旋模型等这些模型的模型图（如果有图的话）以及优缺点和适用场合，并能绘制。5-10%Code-and-Fix Model代码-修复模型 1.without requirements or specifications or design2.may work well on short programming exercises较短的编程练习 (100 or 200 lines)3.the easiest way to develop software and by far目前 the worst wayWaterfall Mode

12、l1. with feedback loops2. documentation driven文档驱动no phase is complete until the documentation for that phase has been completed;The waterfall model, depending on依赖于 specifications, can lead to导致 the products that do not meet the clients needs.Rapid Prototyping Model快速原型1. linear development2. rapid

13、3. meet the clients needOpen-Source Life-Cycle Modelpostdelivery maintenance life-cycle model Two informal非形式的 phasesCore group核心小组 Peripheral group外围小组Open-source software is generally maintained by unpaid volunteers志愿者Users may submit defect reports缺陷报告, both failure reports and fault reportsAn in

14、itial working version is produced when using The rapid-prototyping model;The code-and-fix model; and The open-source life-cycle modelThen:Rapid-prototyping model:The initial version is discarded丢弃Code-and-fix model and open-source life-cycle model:The initial version becomes the target product目标产品Ag

15、ile Processes敏捷过程stories特性;pair programming成对编程;Extreme programming极限编程:XP is one of a number of new paradigms collectively referred to as统称为 agile processes.A principle原则 of XP is to minimize最小化 the number of features.One way of achieving this is to use timeboxing时光盒技术Another common feature of agil

16、e processes is stand-up meetings站立会议Stand-up meetings and timeboxing techniques are instances实例 of two basic principles原则 that underlie应用 all agile methods敏捷方法:ommunication沟通;satisfying the clients needs as quickly as possible尽可能快地1. Agile processes have had some successes with small-scale小型 softwar

17、e development 2. Agile processes are good when requirements are vague模糊不清 or changing Synchronize-and Stabilize Model同步-稳定模型Microsofts life-cycle modelAt the end of the day synchronize同步 (test and debug调试)At the end of the build构件 stabilize稳定化 (freeze冻结 the build)Spiral Model螺旋模型a rapid-prototyping

18、model with each phase preceded by之前带有 risk analysis风险分析Strengths优点risk-driven风险驱动Weaknesses缺点For large-scale大型 and internal内部 software only Summary：第3章：软件过程SOFTWARE PROCESS1掌握每个工作流（包括需求流、分析流、设计流、实现流、测试流）的目标 2%The Requirements WorkflowAim: to determine what the client needs,not what the client wantsT

19、he Analysis WorkflowAim: analyze分析 and refine提取 the requirementsPS:Why not do this during the requirements workflow?The artifacts of the requirements workflow be comprehensible能被理解 by the client and be expressed in a natural language用自然语言描述;All natural languages are imprecise不精确Two separate workflow

20、s are needed:the language of the client(natural language);complete enough for the designers(UML)The Design WorkflowAim: to refine细化 the analysis workflow until the material材料 is in a form that can be implemented by the programmers PS:Many nonfunctional requirements need to be finalized at this time,

21、 including choice of programming language,reuse issues,portability issues.The Implementation WorkflowAim: to implement the target目标 software product in the selected implementation languageThe Test WorkflowAim: to find defect（mistake过错, fault差错, failure故障）PS:The test workflow is the responsibility of

22、 Every developer and maintainer, and The quality assurance groupTraceability可追踪性 of artifacts is an important requirement for successful testingThe analysis artifacts should be checked by means of a review评审:walkthrough走查;inspections审查kinds of running test cases测试用例:unit单元 testing;integration集成 test

23、ing;product产品 testing;acceptance验收 testingThe COTS software is released for testing by prospective clients潜在客户:alpha release (版)beta release (版): the correct release2掌握需求流的每个步骤（了解应用领域、建立业务模型、找出限制条件），了解主要限制条件（包括最终期限、可靠性、成本），掌握以下观点：开发者能够给予客户的应该是客户需要的而不是客户想要的 1%Requirements Workflow Tasks:(1) gain an u

24、nderstanding of the application domain应用领域:That is, the specific business environment in which the software product is to operate(2) build a business model业务模型:Use UML to describe the clients business processes(3) determine the clients constraints限制条件:deadline期限;portability可移植性;reliability可靠性;respon

25、se time响应时间;cost成本:The client will rarely inform告知 the developer how much money is available,A bidding procedure招标程序 is used instead.Developer should do what the client needs,not what the client wants3掌握设计流的两个步骤：结构设计和详细设计的设计内容2%Classical Design传统范型的设计:architectural design结构设计decompose分解 the product

26、into modulesdetailed design详细设计design each module:data structures数据结构;algorithms算法4掌握统一过程的四个阶段以及每个阶段的目标 1%The Phases of the Unified Process:inception phase开始阶段 Aim: to determine whether the proposed software product is economically viable经济上可行elaboration phase细化阶段 Aim: to refine细化 the initial requir

27、ementsconstruction phase构建阶段 Aim: to produce the first operational-quality version可工作版本 of the software producttransition phase转换阶段 Aim: to ensure that the clients requirements have indeed been met5. 掌握规格说明文档中可能出现的问题（包括模糊、不完备和矛盾），掌握软件项目管理计划的组成部分（包括可交付的东西、里程碑和预算）1%Specification document规格说明文档It const

28、itutes构成 a contract合同;It must not have imprecise phrases like:optimal最优;98% complete;if 0=num=30, green light is lit被点亮; if 30num OLD1.2.3. write OLD to NEWTRAN OLD1.2.3. write OLD to NEWTRAN OLD1. write TRAN to NEW 2.3. errorThird Refinement第三次求精The third refinement is wrong.“Modify Jones” followed

29、 by “Delete Jones” is incorrectly handled.Solution:Level-1 lookahead一级前瞻Processing a TRAN only after the next TRAN has been analyzed分析.PS:Introduce level-1 lookahead, and draw up a 3*3 table.2掌握软件度量的两种分类（即产品度量和过程度量）以及度量时用到的具体指标（例如：代码行、每千行代码检测出的错误数、平均故障间隔时间等等），掌握五种基本度量（即规模、成本、持续时间、工作量、质量）1%Software M

30、etrics度量:Product metrics产品度量(size规模 of product;reliability可靠性 of product)Process metrics过程度量(efficiency效率 of fault detection during development)The Five Basic Metrics:(1) size规模(2) cost(3) duration持续时间(4) effort工作量(5) quality度量时的具体指标:lines of code (LOC)size; LOC per monthsize; defects错误数 per 1000 LO

31、Cquality；number of faults detectedquality；person-monthseffort；monthsduration；3掌握CASE工具的概念以及分类（即高端与低端，工具与工作平台与环境）1%Conception概念：computer-aided software engineering (CASE) tools 计算机辅助软件工程工具Taxonomy分类 of CASE：UpperCASE tool: 高端CASE工具(1)help developer during the earlier phase:requirement, analysis, desi

32、gn;(2)front-end前端 toolLowerCASE tool: 低端CASE工具(1)help developer during the latter phase:implement, postdelivery maintenance;(2)back-end后端 tooltool工具:a product that assists in just one aspectworkbench工作平台:a collection of tools that together support one or two activitiesenvironment环境:supports the comp

33、lete software process4掌握软件版本的两种分类（即修订版和变种版）以及这两种分类的区别 1%Software Versions:revisions修订版 and variations变种版1. revision修订版: a version to fix a fault in the artifact.Revision is written to replace its predecessor前任.We cannot throw away an incorrect version (the old version)2. variation变种版: is a version f

34、or a different operating systemhardware.Example: two variations of the printer driver打印机驱动 for supporting an ink-jet喷墨 printer and a laser激光 printerVariations are designed to coexist共存 in parallel平行.PS:name version technique:(1)multiple多个revision:sacknowledgeMessage/1;acknowledgeMessage/2(2) multipl

35、e variations:printerDriver(inkJet);printerDriver(laser)(3)multiple revisions of one variation:printerDriver(laser)/12;printerDriver(laser)/13;printerDriver(laser)/14第6章 ：测试TESTING1掌握质量的定义以及软件质量保证小组（即SQA小组）的责任 2%Software quality assurance group软件质量保证小组(SQA group)The role of SQA group:ensure the quali

36、ty of software process软件过程,thereby从而 ensure the quality of software product2掌握走查时小组成员的构成、走查清单的构成、走查的两个步骤、走查的两种方式以及这两种方式之间的区别 2%小组成员的构成:A walkthrough team consists of from 4 to 6 members;走查清单的构成:It includes representatives代表 of (1)The team responsible for负责 the current workflow and for the next workf

37、low(2)The SQA groupThe walkthrough team is chaired主持 by the SQA representative走查的两个步骤:The walkthrough is preceded by preparation准备 lists of items:(1)items not understood;(2)items that appear to be incorrect走查的两种方式Two types of conducting实施 a walkthrough:participant-driven参加者驱动:question-answer form;do

38、cument-driven文档驱动:read-question-answer form;3掌握审查时小组成员的构成、审查的五个步骤 2%审查小组成员构成:An inspection team has four members:moderator主持者;members of the teams performing the current workflow and the next workflow;a member of the SQA group;Special roles are played by the moderator,reader,recorder.五个步骤An inspecti

39、on has five formal steps:overview概要;preparation准备;inspection审查;rework修订;follow-up跟踪4掌握走查与审查之间的区别 2%区别Comparison比较 of inspections and walkthroughs:walkthrough走查:Two-step, informal process (1)preparation准备(2)analysis分析inspection审查:Five-step, formal process (1)overview概要(2)preparation准备(2)inspection审查(

40、4)rework修订(5)follow-up跟踪PS:Strengths优点 and Weaknesses缺点 of Reviews评审Strengths:Faults are detected earlierWeakness:may be less effective if the process is inadequate不充分5掌握需要测试的五个行为特性（即实用性、可靠性、健壮性、性能和正确性）的定义以及相关度量指标（如平均故障间隔时间、平均修复时间）1%correctness正确性:A product is correct if it satisfies its specificati

41、onsutility实用性:The extent程度 to which the product meets the users needs. Eg:ease of use;useful functions;cost effectivenessreliability可靠性:A measure of the frequency频率 and criticality严重性 of failure故障Eg:mean平均 time between failures;mean time to repairrobustness健壮性:A function函数 of The range of operating

42、conditions; The possibility of unacceptable results with valid有效 input; The effect of invalid inputperformance性能:The extent to which space and time constraints限制 are metEg:real-time software is characterized by hard real-time constraints;If data are lost because the system is too slow, there is no w

43、ay to recover those data;6掌握测试的两种分类 1%There are 2 basic types of testing:Execution-based基于执行的 testing执行测试:executing执行code;running test cases运行测试用例Non-execution-based基于非执行的 testing非执行测试:review评审:document review; code review第7章：从模块到对象FROM MODULES TO OBJECTS1掌握以下概念的定义：模块、模块内聚、模块耦合 1%Module模块:A lexically