软件工程重点总结.doc

.软件工程复习重点总结1. (P-2) Analysis: decompose a large problem into smaller, understandable pieces，(一个大问题分解成更小的、 可以理解部分)abstraction is the keySynthesis: build (compose) software from smaller building blocks, (生成撰写软件从较小的构造块) composition is challenging2 Software Engineering Solving Problems (continued)：(P-4) method： refers to a formal procedure（指的是一个正式的程序）tool：an instrument or automated system for accomplishing something in a better wayprocedure（过程）：a combination of tools and techniques to produce a product（工具和技术来生产一种产品的组合）paradigm（范例）：philosophy or approach for building a product3. (P-6)A fault: occurs when a human makes a mistake, called an error, in performing some software activities（在执行某些软件活动）; A failure: is a departure（偏差）from the systems required behaviour; Error can lead to fault；fault can lead to failure。4. participates in a project：(P-15) Customer: the company, organization, or person who pays for the software systemDeveloper: the company, organization, or person who is building the software systemUser: the person or people who will actually use the system5.Activities and objects(P-16) An activity is an event initiated by a trigger（活动是由一个触发器的事件） Objects or entities are the elements involved in the activities（Objects 或实体是要素参与活动的）6. Relationships and the system boundaries(P-17) A relationship defines the interaction among entities and activities（A 关系定义实体和活动的相互作用） System boundaries determine the origin of input and destinations of the output（边界确定输入的来源与目的地的输出）7.a system as a collection of things : (P-17)a set of entities(一组实体), a set of activities , a description of the relationships among entities and activities and a definition of the system.8.The development of software includes the following activities (P-24) Requirements analysis and definition System design Program design Writing the programs Unit testing Integration testing System testing System delivery Maintenance 9.developer roles(P-26) Analyst Designer Programmer Tester Trainer10. (P-45)A process: a series of steps involving activities, constrains, and resources that produce an intended output of some kind（一系列步骤涉及活动，受到了限制，及资源，产生一预期的输出）A process involves a set of tools and techniques11.(P-46) Software life cycle: Implementation ,delivery ,use, and maintenance（实施、发布、 使用及维修） When a process involves building a software, the process may be referred to as software life cycle Requirements analysis and definition System (architecture) design Program (detailed/procedural) design Writing programs (coding/implementation) Testing: unit, integration, system System delivery (deployment) Maintenance 12software process models：（P-48） Waterfall modelV modelPrototyping model(原型化)Operational specification modelTransformational model（转化）Phased development（阶段化开发）: increments and iterations（反复递增）Spiral model（螺旋模型）Agile methods（敏捷方法）13. Prototyping is useful for verification(确认) and validation（验证）（P-51）14.Elements of a process are viewed in terms of seven types（P-64） Activity Sequence Process model 过程模型 Resource Control Policy Organization15. Project schedule(P-83)Describes the software-development cycle for a particular project byenumerating the phases or stages of the project(枚举阶段或项目的阶段)breaking each phase into discrete tasks or activities to be completed(每个阶段分成离散任务或活动，以完成)Portrays(描绘) the interactions(相互影响) among the activities and estimates(估算) the times that each task or activity will take16. Activity and milestone(P-83) Activity: takes place over a period of timeMilestone: completion of an activity - a particular point in time17. Critical Path Method(CPM)(P-87) 见作业18. Key activities requiring personnel（P-95）requirements analysissystem designprogram designprogram implementation（实现，执行）testingtrainingmaintenance quality assurance（保证）19. risk（P119）is an unwanted event that has negative consequences(消极结果)20. Risk impact(影响): （P-120）the loss associated with the event与该事件关联的损失 Risk probability(概率): the likelihood that the event will occur事件发生的可能性Risk control(控制): the degree to which we can change the outcome我们可以更改结果的程度Quantify(量化) the effect of risks：Risk exposure = (risk probability) x (risk impact) 21. Risk management：（P-121） risk assessment（评估） risk control22.（P-143） A requirement： is an expression of desired behaviour是所需行为的表达式A requirement deals with ：objects or entities ，the states they can be in，and the functions that are performed to change states or object characteristics23. Process for Capturing Requirements（P-144） Elicitation（引入） Analysis SpecificationValidation（验证） /构成了software requirements specification (说明书)24. functional requirement （P-148） describes required behavior in terms of required activitie描述所需的活动所需的行为sQuality requirement or nonfunctional requirementdescribes some quality characteristic that the software must possess(拥有) Design constraint(约束): a design decision such as choice of platform or interface components设计的平台或界面组件如选择决策Process constraint:a restriction on the techniques or resources that can be used to build the system对技术或可用于构建系统的资源限制25. Prioritization might separate requirements into three categories（P-152）Essential(基本): absolutely must be met绝对需要满足的需求Desirable(合意): highly desirable but not necessary非常理想，但不必须的Optional(可选): possible but could be eliminated但可能被淘汰26. Requirements definition: （P-154）a complete listing of everything the customer wants to achieve完整列表的客户希望实现的一切Describing the entities in the environment where the system will be installed 描述在将安装在系统环境中的实体Requirements specification:restates （重申）the requirements as a specification of how the proposed（提出） system shall behave 27.ER diagram have three core constructs（P-158）ER 图表有三个核心构造An entity: depicted as a rectangle, represents a collection of real-world objects that have common properties and behaviors描述为一个的矩形表示一个实际的对象的集合 具有公共属性和行为A relationship: depicted as an edge between two entities, with diamond in the middle of the edge specifying（指定） the type of relationship描述为一个两个实体之间的边缘 An attribute: an annotation(注解) on an entity that describes data or properties associated with the entity描述数据或与该实体相关联的属性的实体上的注释 28.（P-172） A data-flow diagram (DFD) models functionality and the flow of data from one function to another数据流关系图 DFD 模型的功能和数据到另一个函数的流 A buble represents a process一个 buble 表示一个流程 An arrow represents data flow一个箭头表示数据流量 A data store: a formal repository(仓库) or database of information Rectangles represent actors: entities that provide input data or receive the output result矩形表示参与者： 实体提供输入的数据或接收输出结果29.(P-223)Design:is the creative process of transforming the problem into a solutionThe description of a solution is also known as design是创造过程的问题转化为解决方案的描述称为设计30. Design is a two-part interactive process (P224) Conceptual design (system design)(概念性设计) Technical design(技术性设计)31. (P228)Modules or components: 组件composite parts of designA system is modular when each activity of the system is performed by exactly one component活动的系统由一个组件执行 inputs and outputs of each component are well-defined all inputs to it are essential to its function输入其功能至关重要 all outputs are produced by one of its actions输出由其动作之一制作32. Architectural Styles and Strategies Three Design Levels:(P229) Architecture（系统结构）Code design Executable design（执行设计）33. Architectural Styles and Strategies Design Styles （P230）Pipes and filters(管道/过滤器)Object-oriented designImplicit invocation(隐式调用)Layering（分层设计）Repositories(数据仓库)Interpreters(解释器)Process control(过程控制)Client-server(客户/服务器)34. Component independence（P-248）Coupling(耦合度)Cohesion(内聚度)Highly coupled when there is a great deal of dependenciesLoosely coupled components have some dependency, but the interconnections among components are weak（大多数采用松散） Uncoupled components have no interconnections at all35.We can measure coupling along a range of dependence（P-249） Characteristics of Good Design Coupling: Types of Coupling Content(内容) couplingCommon (公共) couplingControl (控制) couplingStamp (标记) couplingData (数据) coupling36. Exceptions can be handled in one of three ways：（P255）异常处理 Retry(重试) Correct(更正) Report(报告)37.program component involves at least three major aspect:(P-340) Control structures ,algorithms,and data structure 38.making the code efficiency(效率) may have hidden costs(代价)(P-342) cost to write the code faster cost to test the code cost to understand the code cost to modify the code39.Software Faults and Failures types of Faults(P-367) 软件故障及故障的类型的故障Algorithmic fault算法Computation and precision fault 计算和精度Documentation faultStress or overload faultsCapacity or boundary faults 容量边界Timing or coordination faults(协调)Throughput(吞吐量) or Performance faultsRecovery fault 恢复故障Hardware and system software faultStandards and procedures fault 40.Testing Organization（P371.）Module testing, component testing, or unit testing(单元测试 ) Integration testing(集成测试)The next step is ensuring that the interfaces among the components are defined and handled properly. Performance testing(性能测试)Compares the system with the remainder of these software an hardware requirements.41.Testing steps（P-372） 42. Integration Testing集成测试（P-390）具体实例见作业Bottom-up(自底向上)Merging components to test the larger systemTop-down (自顶向下)Big-bang(大棒)Sandwich testing(多层结构测试)Modified top-down(改性自上而下)Modified sandwich (改性多层结构测试)43.Principles of