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

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 client’s needs;be easy to modify when the needs changeSoftware crisis:the quality 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%Postdelivery maintenance:Corrective纠错性 maintenance;Perfective完善性 maintenance;Adaptive 适应性 maintenanceCorrective纠错性maintenance:removal去除of residual faults残留错误;leaving the specifications规格说明文档 unchangedPerfective完善性 maintenance:additional functionality额外功能;decreased response time减少响应时间Adaptive适应性 maintenance: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, testing or documentation phase.This testing is the responsibility职责 ofEvery 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 having the documentation of the previous phase.We4掌握软件工程的传统生命周期模型（瀑布模型）的阶段划分和各阶段的主要任务1%Classical(Waterfall瀑布) Life-Cycle Model1. Requirements phaseExplore研究 the concept概念;Elicit提取 the client’s requirements客户需求2. Analysis (specification) phaseAnalyze分析 the client’s 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 does 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开发-维护模型This 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 adaptation适应.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 掌握编码-修补模型、瀑布模型、快速原型开发模型、开源模型、敏捷过程模型、同步-稳定模型、螺旋模型等这些模型的模型图（如果有图的话）以及优缺点和适用场合，并能绘制。

5-10%Code-and-Fix Model代码-修复模型1.without requirements or specifications or design3.the easiest way to develop software —— and by far目前 the worst wayWaterfall Model1. with feedback loops2. documentation driven文档驱动no phase is complete until thedocumentation for that phase hasbeen completed;The waterfall model, depending on依赖于 specifications, can leadto导致 the products that do notmeet the client’s needs.Rapid Prototyping Model快速原型1. linear development2. rapid3. meet the client’s needOpen-Source Life-Cycle Modelpostdelivery maintenance life-cycle model Two informal非形式的 phasesCore group核心小组Peripheral group外围小组Open-source software isgenerally maintained by unpaidvolunteers志愿者Users may submit defect reports缺陷报告, both failure reportsand fault reportsAn initial 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目标产品Agile 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 agile 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 client’s needs as quickly as possible尽可能快地1. Agile processes have had some successes with small-scale小型 software development2. Agile processes are good when requirements are vague模糊不清 or changingSynchronize-and Stabilize Model同步-稳定模型Microsoft’s 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 model with each phase preceded by之前带有 risk analysis风险分析Strengths优点risk-driven风险驱动Weaknesses缺点For large-scale大型and internal内部software onlySummary：第3章：软件过程SOFTWARE PROCESS1掌握每个工作流（包括需求流、分析流、设计流、实现流、测试流）的目标 2%The Requirements WorkflowAim: to determine what the client needs,not what the client wantsThe 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 workflows 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 programmersPS:Many nonfunctional requirements need to be finalized at this time, including choice of programming language,reuse issues,portability issues.The Implementation WorkflowAim: to implement the target目标 software product in the selected implementation language The Test WorkflowAim: to find defect（mistake过错, fault差错, failure故障）PS:The test workflow is the responsibility of 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集成 testing;product产品testing;acceptance验收 testingThe COTS software is released for testing by prospective clients潜在客户:alpha release (α版) beta release (β版): the correct α release终期限、可靠性、成本），掌握以下观点：开发者能够给予客户的应该是客户需要的而不是客户想要的 1% Requirements Workflow Tasks:(1) gain an understanding of the application domain应用领域:Thatis, the specific business environment in which the software product is to operate(2) build abusiness model业务模型:Use UML to describe the client’s business processes(3)determine the client’s constraints限制条件:deadline期限;portability可移植性;reliability可靠性;response time响应时间;cost成本:The client will rarely inform告知 the developer how muchmoney 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 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 economicallyviable经济上可行elaboration phase细化阶段 Aim: to refine细化 the initial requirementsconstruction phase构建阶段 Aim: to produce the first operational-quality version可工作版本 ofthe software producttransition phase转换阶段 Aim: to ensure that the client’s requirements have indeed been met5.掌握规格说明文档中可能出现的问题（包括模糊、不完备和矛盾），掌握软件项目管理计划的组成部分（包括可交付的东西、里程碑和预算）1%Specification document规格说明文档It constitutes构成 a contract合同;It must not have imprecise phrases like:optimal最优;98% complete;if 0<=num<=30, green light is lit被点亮; if 30<num<=45, yellow light is lit. The specifications must not have:contradictions矛盾;ambiguity模糊;incompleteness不完整Software Project Management Plan 软件项目管理计划Once the client has signed off签署 the specifications, we draw up the software project management6.掌握回归测试概念及方法。