第一篇：软件工程总结2
As early as when I chose the software professional , I always think of software engineering is nothing but the code to knock.knock from the process of code to realize the meaning and use all the code in software engineering.I have always been a hard knock code to learn software development when haven't learned.After learning of software engineering ,I feel I've learning method is wrong.I used to only focus on the code, rather than on theoretical knowledge as well as programming ideas ,and the program's structure.My knowledge of software engineering point of this course summary as below : ● Software: Software is able to complete the intended function and performance of the executable computer program and the procedures required for the normal execution of data, coupled with the program's operation and use of documents.● Software features:(1)software is a logical entity, rather than specific physical entity, so it has the abstract.(2)software is the people's intelligence activities, the knowledge and technology transform into a product of information.(3)After software transform into the product, its production simply copy different from the hardware manufacturer.(4)the maintenance process more complex than hardware, and even lead to new errors.● Software crisis: refers to the process of software development and maintenance of a range of serious problems encountered.Cause of a software crisis:(1)The sharp increase in software maintenance costs, a direct threat to the expansion of computer applications.(2)software production technology progress is slow.● Software Engineering: a guiding engineering disciplines of development and maintenance of computer software.● Software life cycle: from definition to a software development, use and maintain, until finally
being abandoned, to undergo a long period of time, usually the software through this long period of time known as the life cycle.Software life cycle can be divided into the following stages: Problem Definition;Feasibility study;Demand Analysis;Overall(summary)design;Detailed design;Coding and unit testing;Integrated Test;Software Maintenance.● ● software process models: software development model is the whole process of software Waterfall model is that the life cycle model, proposed by the BMBoehm , it is the basis for development, software development activities and structural framework of the relationship between them.software engineering model.Its core idea is to simplify the problem by process, implementation and design of functional separation, to facilitate division of labor.The use of structured analysis and design methods, the logical and physical implementation to achieve separation.Waterfall model emphasizes the role of the document and asked each stage must be carefully verified.● ● ● ● Rapid prototyping model: to achieve the customer or a future user interaction with the system.Phased development: increments and iterations(repeated increments).Spiral model: the combination of the waterfall model and rapid prototyping models.It Agile methods: Agile development is a people-centered, iterative, incremental development emphasized the neglect of other risk analysis models, especially for large complex systems.methodology.In agile development, software project build was cut into several subprojects, each subproject results are tested, with the integration and operation characteristics.In other words, it is to a large project into multiple interrelated, but small projects can be run independently, and were completed.In this process, the software has been in a usable condition.● Feasibility study: compression simplified systems analysis and design process, that is to say a
higher level in a more abstract approach to the design process.Not solve the problem, but the problem is solvable and determine whether it is worthwhile solution.● ● System flow chart is a traditional tools of depicting the physical system.It is expressed in the Structured method of analysis using data flow diagrams and data dictionary to describe.Its core data flow between the various components in the system, rather than the data processing control process.idea is simple decomposition of the problem, said the physical and logical separation of data and logic of the system abstraction.Summarize, structural analysis is stream-oriented top-down stepwise refinement, a needs analysis.● Data flow diagram(DFD): describe the flow of information and data move from input to output in the process of change experienced.● Data Dictionary(DD)effect: the software provides a definition of each data entry in order to maintain the consistency of the data in the system.● ER diagram have three core constructs: 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.● The tasks of requirements analysis: requirements analysis work to be done in-depth description of software functionality and performance, to determine the limits of software design and software interface with other system elements in detail ,to define the validity of the other software requirements.In general, the needs analysis phase of the mission and work: 1 , to determine the complex requirements of the system.(1)functional requirements(2)performance requirements(3)operational requirements(4)possible future expansion requirements(5)reliability and availability requirements(6), error handling and security requirements(7)Interface Requirements(8)Design constraint, etc.2, the data analysis system requirements(1)to build conceptual models:(2)image depicts the data structure and standardized data structure 3, the logical model derived 4, to amend the plan: the revaluation cost, schedule, etc.5, the prototype system to verify the correctness and the system meets the requirements.● requirements analysis principles:(1)must be able to express and understand the problem of data fields and function fields;(2)by top-down, layer by layer decomposition of the problem;(3)to given the system's logical and physical views.● ● Requirements definition: A complete listing of everything the customer wants to Requirements specification: Restates the requirements as a specification of how the proposed achieve ,describing the entities in the environment where the system will be installed.system shall behave.● Software design task: to produce the software requirements analysis phase into a description of methods of representation with the appropriate software design documentation.No matter what kind of software design, software design generally includes data design, architecture design, interface design and process design and so on.● Structured design methods: a stream-oriented design methods, the central task is to use the DFD diagram shows the system model into a software architecture model to determine the software architecture and interfaces.● Data stream type: Data flow-oriented design methods to map the flow of information into a software architecture, information flow type determines the mapping method.Information flow has the following two types: transformation flow and transaction flow.● Structured analysis methods: Module: It is a entity with clearly defined input, output and physical characteristics of the program.All input modules are essential to achieve the function, all outputs are generated action.Modular: the program is divided into several modules, each module has a sub-function, these modules lumped together to form a whole, can complete the assigned functions, to achieve the requirements of the problem.Modular design: the large-scale software in accordance with the principles laid divided into a smaller , relatively independent but interrelated modules.Decomposition and module independence, is the modular design of the important guiding ideology.Abstract: that is, characteristics of the nature of things out not to consider them in detail.Information Hiding: The information contained in the module does not allow other modules do not need to call information.Module independence: the software system software requirements for each module involves only the specific sub-functions, while the rest of the system and software modules interface is simple.Cohesion : mark a module with all elements of the close of each other.Coupling : a software architecture is the interconnection between various modules within the measure of the degree.Depth: that software architecture to control the number of layers, it can often mark a system roughly the size and complexity.Width: within the structure of the software module on the same level of maximum total.Fanout: a module direct control(call)number of modules, fan-out is too large means that the module is too complex, fan-out is too small(for example, is always 1)is not good.Fan: the number of higher level modules that directly call it, the greater the share of the fan module, the more the higher number of modules, which is good.● We can measure coupling along a range of dependence
● The basic principles of software design: Modular;abstract;information hiding;module independence.● ● The basic software design experience: Module independence, low coupling, high cohesion, The difference between testing and debugging: Test is to find errors in the program and program public module.execution process.Debugging by locating and correcting errors, eliminate software failures, to ensure reliable operation of the program.● ● Types of tests: According to test whether the actual application environment to points, there are Test methods: Black box testing method, according to the program's functionality to design test static analysis and dynamic testing.cases;White-box testing method, according to the internal structure of the program under test design test cases.The usual practice is to use black box method the basic design of the test program, and then add some white-box method program.● Software testing test case design is a central element.Test a program to use multiple test cases, and each test case should include a set of test data and a corresponding expected test results.● Black box testing method in the three common techniques: equivalence division method, boundary value analysis, error guessing(guessing)method.● ● operation ● Software Reliability: It is a program, in accordance with the provisions of the specification the probability of a successful run in a given time interval.● ● Software Maintenance: Software operation phase of the software product modifications is The type of software maintenance: improving maintenance;adaptive maintenance;maintained.commissioning maintenance;preventive maintenance.● Software maintainability: measure of the ease of software maintenance of a software attribute.Qualitative said, depends on the maintainability of software the following properties: intelligibility, modifiability and testability.● Software configuration: Software life cycle, its various forms, various versions of the documentation and procedures in general.● Software Re-engineering: reverse engineering, restructuring and other technology, a full understanding of the original software, based on the decomposition, synthesis, and re-building software to improve software understandability, maintainability, reusability.● UML class diagram of Figure 9 include: class diagram;object graph;use case diagram;sequence diagram;collaboration diagram;state diagram;activity diagram;component diagram;deployment diagram.● Using UML for modeling the demand: that we can use cases(use case)needs to proceed as a good starting point for modeling.Use cases are organized according to the system using the system.To use cases as a starting point for requirements modeling, allows us to focus attention on customers.Use case diagram is to show a set of use cases, the relationship between the participants and their plans.Use case diagram includes the following three aspects.1.Participants.2.Use cases.3.Dependence, generalization and association.● diagram.Activity Diagram: these will be described in the UML activity flow graph is called an activity
White-box testing method: logic coverage test and path testing method.Test steps: 1.Unit testing 2.Integration Testing 3.Validity of test 4.System Testing 5.Parallel
● ● ● State Diagram: to model the dynamic aspects of the system.From the UML design point of view, the type of class usually can be divided into three types: The relationship between classes(analysis): entity class, the boundary type and the control class.Relationships is the link between things.(1)dependency(2)generalization(3)implementation(4)associated.● Component diagrams and deployment diagrams relations: Component diagrams used to describe the composition of software systems, but did not describe the system in hardware-related composition.Deployment plans used to describe the physical topology of the system hardware and software running on this structure.● Forward process and reverse engineering: Forward process is to achieve positive language mapping and the process model into code.Reverse engineering is the mapping from a specific implementation language and the code to model the process.Personally think, the course of Software Engineering is a a necessary science courses for people who do software development.By learning this course, programmers will focus on software development, theoretical knowledge, and to do project development ideas.After learning of the course you will not write a program to blindly apply the code, but to clarify the structure of the program and ideas.When the program from the start, when to stop.What needs to be added in the middle of the function, to improve the software.In fact, software engineering is not difficult to learn and easy.If Software Engineering linked to daily life, then, is the day you should do first, what to do after.Understand what to do first, what to do after the after the write process is not so difficult, more complex programs can be divided into several large pieces.After you sort out the idea of the program step by step solution can be one of the problems, and ultimately software.If you do not learn software engineering process to clarify the idea , then do a large project development, so much code, not a very good structure, it will eventually lead to procedural confusion, mistakes, even more aware of the code will do nothing of the elements.All in all, as a programmer to learn software engineering course is necessary, if not to learn software engineering, you will not do the project development, it is impossible to develop a complete software out.
第二篇：软件工程总结
软件工程课程总结
摘要：
计算机是20世纪最重大的科学技巧成就之一，使当代社会的经济、军事、科研、教育、服务等方面在概念和技巧上发生了性的变化，对人类社会的进步已经并还将产生极为深刻的影响。目前，计算机是世界各发达国度剧烈竞争的科学技巧领域之一。
电子计算机早期功效主要是计算，后来已远远超越单纯计算的功效，还可模拟、思维、进行自适应反馈处理等等，把它叫做“电脑”更为合实际。由于电子计算机功效的飞跃性发展，应用于生产和生活的各个方面，直接和显著地提高了生产、工作和生活的效率、节奏和水平，在软科学研究和应用中它也起着关键作用，因此它已被公认是现代技巧的神经中枢，是未来信息社会的心脏和录魂。计算机学科分为四个领域，分别是计算机科学，计算机工程，软件工程和信息系统。
正文：
软件工程是研究和应用如何以系统性的、规范化的、可定量的过程化方法去开发和维护软件，以及如何把经过时间考验而证明正确的管理技术和当前能够得到的最好的技术方法结合起来的学科。包括项目管理，分析，设计，程序的编写，测试和质量控制。它涉及到程序设计语言、数据库、软件开发工具、系统开发平台、标准、设计模式等方面。
学了《软件工程》这门课程和一些有关资料后，感觉一些东西都曾经接触过，但在实际工作中有些理论要完全遵循可能还有些障碍，软件工程只是提供了理论上的一些结论，但对项目的具体可操作性的规范的制定方面却做的很少，《软件工程》发展了几十年，光是开发模型就达到了10多种，对不同的项目采用合适的开发模式，有些项目在不同的开发阶段可能还要转换开发模式，把它们灵活的应用到实际中还是很困难的。
软件技术是信息技术产业的核心之一，软件技术的发展是与信息技术产业的发展互相促进的。当今世界，信息技术正处于新一轮重大技术突破的前夜。预计今后 20~30 年是信息科学技术的变革突破期，可能导致 21 世纪下半叶一场新的信息技术革命。近年来，从 IT 界到一些国家首脑，都高度关注以物联网为标志的新一轮信息技术的发展态势，认为这是继 20 世纪 80 年代 PC 机、90 年代互联网、移动通信网之后，将引发 IT 业突破性发展的第三次 IT 产业化浪潮。每一次重大的技术变革都会引起企业间、产业间甚至国家间竞争格局的重大变化，也促进了软件技术与软件产业的重大变革与发展。
近年来，信息技术、软件技术、软件系统与软件产业的发展备受关注，已有不少论述、分析与判断。近10 年内网络技术经历宽带化、移动化和三网融合将走向基于 Ipv6 的下一代互联网，2010 年 1 月，国家 863 计划信息技术领域办公室和国家 863 计划信息技术领域专家组，在上海举办“信息-物理融合系统 CPS发展战略论坛”，提出“信息-物理融合系统 CPS 是一个综合计算、网络和物理环境的多维复杂系统，是信息和物理世界的深度的融合交互，可实现大型工程系统的实时感知、动态控制和信息服务，使系统更加可靠、高效与实时协同，使得人类物理现实和虚拟逻辑逐步融合，具有重要而广泛的应用前景。业界关于软件工程的代表性观点创立与使用健全的工程原则，以便经济地获得可靠且高效率的软件。应用系统化，遵从原则，可被计量的方法来发展、操作及维护软件；也就是把工程应用到软件上。与开发、管理及更新软件产品有关的理论、方法及工具。一种知识或学科，目标是生产品质良好、准时交货、符合预算，满足用户所需的软件。实际应用科学知识在设计、建构电脑程序，与相伴而来所产生的文件，以及后续的操作和维护上。
6使用与系统化生产和维护软件产品有关之技术与管理的知识，使软件开发与修改可在有限的时间与费用下进行。
7建造由工程师团队所开发之大型软件系统有关的知识学科。对软件分析、设计、实施及维护的一种系统化方法。系统化地应用工具和技术于开发以计算机为主的应用。
10软件工程是关于设计和开发优质软件。
《软件工程》是一门综合性和实践性很强的核心课程，它属于是一门交叉学科，包含有：软件开发技术（软件开发方法学、软件开发过程、软件工具和软件工程环境）、软件工程管理（软件管理学、软件经济学、软件心理学）。主要内容包括软件工程概述、可行性分析、需求分析、概要设计、详细设计、面向对象分析与设计、编码、软件测试、项目计划与管理。
本课程是面向准备从事软件开发的毕业生而开设的一门专业课程。针对计算机教学中软件工程这一薄弱环结，结合目前软件开发商对人才的要求，对计算机专业的毕业生进行软件工程强化培训，目的是使毕业生能够了解和掌握软件工程的基本理论和方法，并在实际软件开发中运用这些方法。
我理解，软件工程是按照工程学的管理方式，有组织、有计划的，在一定的质量基础、时间限度和成本范围内，实现功能明确的软件系统。而且，软件工程在企业范围内运行，一定需要企业资源的支持，要与企业的经营、决策、管理体系联系在一起，才能够被踏踏实实的落实下来。
软件工程项目是一个需要一步一步的计算，分析思考而来的，需要不断思考，研究不断进步，软件业作为一个服务业，要想得到发展，首先必须形成一个对软件服务有迫切需要的市场。其次，这个市场中的消费者必须具备足够的购买力。软件的消费群体简单一点，可以分为个体消费和企业消费。中国的企业群体，数量庞大，但是质量不高。上规模的企业极少。国内目前能够形成比较大规模的独立市场的，肯定是小规模的软件系统。
随着信息化时代的到来其地位越来越受到人们的重视，软件工程从一个学科，或是某一个研究方向来说，人员仅仅是过程，方法的执行者，所以人员素质往往被忽略，软件工程是一门实践性很强的学科，所以在实际的软件研究过程中，人员的素质占有很重要的地位。要有出色的软件问世，研发人员的素质至关重要！
作为软件工程的学习者应该不断创新，不断尝试、实践，不断研究和学习，中国的软件工程技术依旧滞后于国外一些软件工程技术，作为新一代的学习者应该担当起振兴起中国软件事业，使中国科技得到高速发展！
现在已经是信息化时代，信息化潮流不断涌现，想要掌握主动权就是掌握信息化的发展方向，这就需要我们不断学习，时间，研究，学习国外的先进技术，转变自己的技术，然后融合，创新。
软件技术不是一成不变的，是随着社会的进步的不断进步，不需要不断的创新，不断的改善的，需要我们不断的学习，不断的研究，不断进步。
第三篇：软件工程总结
1.Software is a product and can be manufactured using the same technologies used for other engineering artifacts Answer: b 2.WebApps are a mixture of print publishing and software development, making their development outside the realm of software engineering practice.Answer: b 3.Software engineering umbrella activities are only applied during the initial phases of software development projects.Answer: b 4.Planning ahead for software reuse reduces the cost and increases the value of the systems into which they are incorporated.Answer: a 5.The essence of software engineering practice might be described as understand the problem, plan a solution, carry out the plan, and examine the result for accuracy.Answer: a 6.In agile process models the only deliverable work product is the working program.Answer: b 7.A most software development projects are initiated to try to meet some business need.Answer: a 8.In general software only succeeds if its behavior is consistent with the objectives of its designers.Answer: b 9.Software processes can be constructed out of pre-existing software patterns to best meet the needs of a software project.Answer: a 10.Process technology tools allow software organizations to compress schedules by skipping unimportant activities.Answer: b 11.It is generally accepted that one cannot have weak software processes and create high quality end products.Answer: a 1.Requirements engineering is a generic process that does not vary from one software project to another.Answer: a 2.A stakeholder is anyone who will purchase the completed software system under development.Answer: b 3.It is relatively common for different customers to propose conflicting requirements, each arguing that his or her version is the right one.Answer: a 4.Developers and customers create use-cases to help the software team understand how different classes of end-users will use functions.Answer: a 5.Use-case actors are always people, never system devices.Answer: b 6.Analysis patterns facilitate the transformation of the analysis model into a design model by suggesting reliable solutions to common problems.Answer: a 7.In win-win negotiation, the customer’s needs are met even though the developer’s need may not be.Answer: b 8.In requirements validation the requirements model is reviewed to ensure its technical feasibility.Answer: b
1.Object-oriented domain analysis is concerned with the identification and specification of reusable capabilities within an application domain.Answer: a 2.In structured analysis models focus on the structure of the classes defined for a system along with their interactions.Answer: b 3.Creation and refinement of use cases if an important part of scenario-based modeling.Answer: a 4.It is important to consider alternative actor interactions when creating a preliminary use case.Answer: b 5.Brainstorming is one technique that may be used to derive a complete set of use case exceptions.Answer: a 6.In many cases there is no need to create a graphical representation of a usage scenario.Answer: a 7.One or more attributes of a data object must be defined as a key to allow the location of an instance of the data object.Answer: a 8.Attributes are chosen for an object by examining the problem statement and identifying the entities that appear to be related.Answer: b 9.An analysis package involves the categorization of analysis model elements into useful groupings.Answer: a 10.The data flow diagram must be augmented by min-spec that can serve as a guide the design of the software component that will implement the process.Answer: a 11.The UML sequence diagram show the order in which system events are processed.Answer: b 12.Analysis patterns are discovered, they are not explicitly created.Answer: a 13.It is not possible to justify the time required for WebApp requirements analysis.Answer: b 14.UML activity diagrams can be used to represent the user observable functionality delivered by the WebApp as well as the operations contained in each analysis class.Answer: a 15.Configuration analysis focuses on the architecture of the user’s web browsing environment.Answer: b 16.Content objects are extracted from use cases by examining the scenario description for direct or indirect content references.Answer: a 1.With thorough testing it is possible to remove all defects from a program prior to delivery to the customer.Answer: b 2.Program flow graphs are identical to program flowcharts.Answer: b 3.The cyclomatic complexity of a program can be computed directly from a PDL representation of an algorithm without drawing a program flow graph.Answer: a 4.Graph-based testing methods can only be used for object-oriented systems Answer: b 5.Equivalence testing divides the input domain into classes of data from which test cases can be derived to reduce the total number of test cases that must be developed.Answer: a 6.Boundary value analysis can only be used to do white-box testing.Answer: b 7.Orthogonal array testing enables the test designer to maximize the coverage of the test cases devised for relatively small input domains.Answer: a 8.Client/server architectures cannot be properly tested because network load is highly variable.Answer: b 1.The best representation of system architecture is an operational software prototype.Answer: b 2.The architectural representations can be an enabler for communication among project stakeholders.Answer: a 3.An architectural description is often documented using an architecture template.Answer: b 4.An architectural genre will often dictate the architectural approach that may used for the structure to be built.Answer: a 5.Before an architectural pattern can be chosen for use in a specific system it must have a code implementation to facilitate its reuse.Answer: b 6.Once selected, archetypes always need to be refined further as architectural design proceeds.Answer: a 7.Quantitative methods for assessing the quality of proposed architectural designs are readily available.Answer: b
Chapter 10 Self-Check Quiz
1.In the most general sense a component is a modular building block for computer software.a.True b.False
Answer: a(Section 10.1)
2.In the context of object-oriented software engineering a component contains
a.attributes and operations b.instances of each class c.roles for each actor(device or user)d.set of collaborating classes
Answer: d(Section 10.1.1)
3.In traditional software engineering modules must serve in which of the following roles?
a.Control component b.Infrastructure component c.Problem domain component d.All of the above
Answer: d(Section 10.1.2)
4.Software engineers always need to cerate components from scratch in order to meet customer expectations fully.a.True b.False
Answer: b(Section 10.1.3)
5.Which of the following is not one of the four principles used to guide component-level design?
a.Dependency Inversion Principle b.Interface Segregation Principle c.Open-Closed Principle d.Parsimonious Complexity Principle
Answer: d(Section 10.2.1)
6.The use of stereotypes can help identify the nature of components at the detailed design level.a.True b.False
Answer: a(Section 10.2.2)
7.Classes and components that exhibit functional, layer, or communicational cohesion are relatively easy to implement, test, and maintain.a.True b.False
Answer: a(Section 10.2.3)
8.Software coupling is a sign of poor architectural design and can always be avoided in every system.a.True b.False
Answer: b(Section 10.2.4)
9.WebApp content design at the component level focuses on content objects and the manner in which they interact.a.True b.False
Answer: b(Section 10.4.1)
10.A WebApp functional architecture describes the key functional components and how they interact with each other.a.True b.False
Answer: a(Section 10.4.2)
11.Which of these is a graphical notation for depicting procedural detail?
a.box diagram b.decision table c.ER diagram d.flowchart
Answer: d(Section 10.5.1)
12.A decision table should be used
a.to document all conditional statements b.to guide the development of the project management plan c.only when building an expert system d.when a complex set of conditions and actions appears in a component
Answer: d(Section 10.5.2)
13.A program design language(PDL)is often a
a.combination of programming constructs and narrative text b.legitimate programming language in its own right c.machine readable software development language d.useful way to represent software architecture
Answer: a(Section 10.5.3)
14.In component-based software engineering, the development team examines the requirements to see which are amenable to composition, rather than construction, before beginning detailed design tasks.a.True b.False
Answer: a(Section 10.6)
15.Which of the following is not one of the major activities of domain engineering?
a.analysis b.construction c.dissemination d.validation
Answer: d(Section 10.6.1)
16.Which of the following factors would not be considered during component qualification?
a.application programming interface(API)b.development and integration tools required c.exception handling d.testing equipment required
Answer: d(Section 10.6.2)
17.Which is the following is a technique used for component wrapping?
a.black-box wrapping b.clear-box wrapping c.gray-box wrapping d.white-box wrapping
Answer: b(Section 10.6.2)
18.Which of the following is not one of the issues that form a basis for design for reuse?
a.object-oriented programming b.program templates c.standard data d.standard interface protocols
Answer: a(Section 10.6.3)
19.In a reuse environment, library queries are often characterized using the ________ element of the 3C Model.a.concept b.content c.context d.all of the above
Answer: c(Section 10.6.4)
1.The importance of software design can be summarized in a single word a.b.c.d.Answer: d(Section 8.1)
2.Which of the following is not a characteristic common to all design methods?
a.configuration management b.functional component representation c.quality assessment guidelines d.refinement heuristics
Answer: a(Section 8.2.2)
3.Which of the following can be used to represent the architectural design of a piece of software?
a.Dynamic models b.Functional models c.Structural models d.All of the above
Answer: d(Section 8.3.2)
4.Design patterns are not applicable to the design of object-oriented software?
a.True b.False
Answer: b(Section 8.3.3)
5.Since modularity is an important design goal it is not possible to have too many modules in a proposed design.a.True b.False
Answer: b(Section 8.3.5)
6.Information hiding makes program maintenance easier by hiding data and procedure from unaffected parts of the program.accuracy complexity efficiency quality
a.True b.False
Answer: a(Section 8.3.6)
7.Cohesion is a qualitative indication of the degree to which a module
a.can be written more compactly.b.focuses on just one thing.c.is able to complete its function in a timely manner.d.is connected to other modules and the outside world.Answer: b(Section 8.3.7)
8.Coupling is a qualitative indication of the degree to which a module
a.can be written more compactly.b.focuses on just one thing.c.is able to complete its function in a timely manner.d.is connected to other modules and the outside world.Answer: d(Section 8.3.7)
9.When using structured design methodologies the process of stepwise refinement is unnecessary.a.True b.False
Answer: b(Section 8.3.8)
10.Software designs are refactored to allow the creation of software that is easier to integrate, easier to test, and easier to maintain.a.True b.False
Answer: a(Section 8.3.10)
11.Which of the following is not one of the five design class types
a.Business domain classes b.Entity classes c.Process classes d.User interface classes
Answer: b(Section 8.3.13)
12.Which design model elements are used to depict a model of information represented from the user’s view?
a.Architectural design elements b.Component-level design elements c.Data design elements d.Interface design elements
Answer: c(Section 8.4.1)
13.Which design is equivalent to the floor plan of a house?
a.Architectural design b.Component-level design c.Data design d.Interface design
Answer: a(Section 8.4.2)
14.Which design model is equivalent to the detailed drawings of the access points and external utilities for a house?
a.Architectural design b.Component-level design c.Data design d.Interface design
Answer: d(Section 8.4.3)
15.Which design model is equivalent to a set of detailed drawings for each room in a house?
a.Architectural design b.Component-level design c.Data design d.Interface design
Answer: b(Section 8.4.4)
16.The deployment design elements specify the build order for the software components.a.True b.False
Answer: b(Section 8.4.5)
第四篇：软件工程总结
第一章软件与软件工程的概念
软件的概念：软件是计算机系统中与硬件相互依存的另一部分，软件包括程序，数据，及其相关文档的完整集合。程序是按事先设计的功能和性能要求执行的指令序列。数据是使程序能够正确地处理信息的数据结构。文档是与程序开发，维护和使用有关的图文资料。
程序的最小单位是函数及子程序，程序与数据是分离的，在面向对象程序设计时代，程序的最小单位是类，在类中封装了相关的数据及指令代码。
软件的特性，判断正误：1.软件是无形的、不可见的逻辑实体，因此，软件是无法描述的。（错）
2、软件的开发特性是指软件需要大量手工劳动，难以自动化生产。（对）
3、有缺陷的软件就是废品。（错）
4、软件的生产指的是软件的复制。（错）
5、由于软件的开发充满人的个性特点，因此管理并不决定软件开发的成败（错）。
6、软件的开发环境往往就是软件的运行环境，或者与其兼容。（对）
7、合格的软件产品不需要维护，软件需要维护说明其质量不合格。（错）
8、软件可以不断改进，因此软件不需要废弃。（错）
软件的分类：1，系统软件：能与计算机硬件紧密配合在一起，使计算机系统各个部件，相关的软件和数据协调，高效的工作的软件。2，应用软件，是在系统软件的支持下，在特定区域内开发，为特定目的服务的一类软件。3，支撑软件，也叫工具软件，是协助用户开发软件的工具性软件。4，可复用软件，最初实现的典型的可复用软件是各种标准函数库，通常是由计算机厂商提供的系统软件的一部分。
IEEE给出的定义：软件工程是开发，运行，维护和修复软件的系统方法。软件的定义：计算机程序，方法，规则，相关的文档资料一集在计算机上运行时所必需的数据。
软件危机的典型表现
1、成本太高，预算不准
2、超过预计时间
3、软件质量标准不明确
4、生产率低
5、缺乏文档资料，难以维护。原因：1，缺乏软件开发的经验和有关软件开发数据的积累，使得开发工作的计划很难制定。2.软件人员与用户的交流存在障碍，除了知识背景的差异，缺少合适的交流方法及需求描述工具。3，软件开发过程不规范，缺少方法和规范的指导。4，随着软件规模的增大，其复杂性往往会呈指数级升高。5，缺少有效的软件评测手段，提交用户的软件质量差。
软件危机发生的主要原因有：
1、遇到了无法解决的高难度技术问题（不是）
2、无法招聘到足够的编程高手（不是）
3、软件人员与用户互相不理解（是）
4、计划和管理不科学、落实不力（是）
5、软件质量标准不明确（是）
软件的质量特性包括（选择）问题1：
1、功能性
2、可靠性
3、使用性
4、经济性（不包括）
软件的质量特性包括（选择）问题2：
1、效率
2、可维护性
3、可移植性
4、经济性（不包括）
软件工程的目标是运用先进的软件开发技术和管理方法来提高软件的质量和生产率，也就是要以较短的周期，较低的成本生产出高质量的软件产品，并最终实现软件的工业化生产。软件生存期：软件的孕育，诞生，成长，成熟，衰亡的生存过程。软件生存期由软件定义，软件开发和运行维护三个时期组成，每个时期又可划分为若干个阶段。
2、软件定义时期的任务主要任务是解决“做什么”的问题，确定工程的总目标和可行性；实现工程目标的策略及系统功能；估计需要的资源和成本；制订工程进度表。通常又分为3个阶段：问题定义，可行性研究，需求分析。
3、软件开发时期的任务和包含阶段主要任务是解决“如何做”的问题，设计和实现定义的软件。由概要设计、详细设计、编码和测试4个阶段组成。
4、软件运行维护时期的主要任务是使软件持久地满足用户的需要，通常有4类维护活动：改正性维护；适应性维护；完善性维护；预防性维护。开发过程中的典型文档：软件需求规格说明书。项目计划。软件测试计划。软件设计说明书。用户手册。软件工程各个阶段的基本任务
1、问题定义与可行性研究：解决什么问题？能否解决问题？是否值得做？”
2、需求分析：做什么
3、软件设计：如何实现
4、程序编码和单元测试：实现设计
5、集成和系统测试：组装连接测试、功能验证测试
6、软件运行和维护：修改 第二章软件工程方法与工具
软件工具：是指能支持软件生存周期中某一阶段（如系统定义，需求分析，设计，编码，测试，维护等）的需要而使用的软件工具。
需求分析工具
1、结构化图形工具箱。通过数据流程图DFD进行功能分析。包括DFD图形工具，实体-关系图(E-R)图形工具，Jackson图形工具，Warnier图形工具，Visio综合工具，2、面向对象工具，Rational Rose，PowerDesigner，Visio 设计工具（1)概要设计工具：设计目标软件的体系结构、控制结构和数据结构。软件的体系结构通常用模块结构图来描述。模块的数据结构通常用实体-关系图来描述。Visio。Rational Rose 详细设计工具。设计模块的算法和内部实现细节。详细设计描述方法有输入-处理-输出(IPO)图。问题分析图(PAD)。盒图(NS图)。流程图(FC)。程序设计语言(PDL)。结构化语言。判定表。判定树
第三章软件需求获取与结构化分析方法 需求获取的主要任务是与用户沟通，了解系统或产品的目标是什么，客户或用户想要实现什么，系统和产品如何满足业务的要求，最终系统或产品如何用于日常工作。获取并理解用户的需求是软件工程师所面对的最困难的任务之一。
需求分析的困难体现：系统的目标或范围问题；需求不准确性问题；需求的易变问题
需求获取的任务：发现和分析问题，并分析问题的原因，结果关系。与用户进行各种方式的交流，并使用调查研究方法收集信息。按照三个成分即数据，过程和接口观察问题的不同侧面。将获取的需求文档化，形式有用例，决策表，决策树等。需求获取的原则：深入浅出，以流程为主线。
获取具体的需求的途径1，与用户交流。2，现有产品或竞争产品的描述文档。3，系统需求规格说明。4，当前系统的问题报告和改进要求。5，市场调查和用户问卷调查。6，观察用户如何工作。
关于需求获取问题的认识辨析：
1、没有与用户交流就不可能获取系统需求。（不能获取准确、全面的系统需求）
2、没有经过与用户交流而获取的需求都是不真实的需求。（一些需求从用户以外的途径获取）
3、系统开发必须独立完成，参考类似系统及技术文档属于抄袭行为，应予避免。（系统开发包含研究行为，应了解对手产品，取长补短）
4、系统开发包含改进当前系统的缺陷和不足。（对）
5、需求调查时，用户所说的需求未必是真实、准确的需求，因此需求分析需要依赖用户，但是不能过分迷信用户。（对，需求描述是困难的）
6、观察用户如何工作也是一种需求调查行为。（对）
软件需求分析阶段的任务：需求获取，需求分析，需求定义，需求验证。完整性，正确性，合理性，可行性，充分性。
结构化分析方法：是一种建模技术。核心是数据字典。
功能模型用数据流图（DFD)来描述使用实体—关系图（ER图）建立数据模型。使用状态转换图（简称状态图）建立系统行为模型。数据字典。加工规格说明。需求建模的依据是需求描述
数据建模，ER图，需要认真看。
第四章结构化设计方法
结构化设计方法是在模块化，自顶向下逐步细化及结构化程序设计技术基础上发展起来的，结构化设计方法可分为两类：一类是根据系统的数据流进行设计，称为面向数据流的设计，或称过程驱动设计，另一类是根据系统的数据结构进行设计，称为面向数据结构的设计，或称数据驱动的设计。
软件的体系结构设计，模块化设计都是分而治之策略的具体表现。模块化是将整体软件划分为独立命名且可独立访问的模块，不同的模块通常具有不用的功能或指责，每个模块可独立开发，测试，最后组装成完整的软件。模块是构成软件的基本构件。模块并不是越小越好，当模块数目增加时，每个模块的规模将减小，开发单个模块的成本确实减少了，但是随着模块数目增加，模块之间关系的复杂程度也会增加，设计模块间接口所需要的工作量也将增加。
模块的独立性是指软件系统中每个模块只涉及软件要求的具体的子功能，而与软件系统中其他模块的接口是简单的，若一个模块只具有单一的功能且与其他模块没有太多的联系，那么称此模块有独立性。
自顶向下，逐步细化：抽象是指忽视一个主题中与当前目标无关的方面，以便更充分地注意与当前目标有关的方面，当我们进行软件设计时，设计开始时应尽量提高软件的抽象层次，按抽象级别从高到低进行软件设计，将软件的体系结构按自顶向下方式，对各个层次的过程细节和数据细节逐层细化，直到用程序设计语言的语句能够实现为止，从而最后确定整个系统的体系结构，这就是自顶向下逐步细化过程。
复用是指同一事物不做修改或稍加修改就可以多次重复使用，将服用的思想用于软件开发，称为软件复用。1是尽量使用已有的构件。2是如果确实需要创建新的构件，则在设计时应该考虑将来的可重复使用性。软件设计的阶段与任务：从工程管理的角度，可以将软件设计分为概要设计阶段和详细设计阶段。从技术的角度，传统的结构化方法将软件设计划分为体系结构设计、数据设计、接口设计和过程设计4部分；概要设计包括体系结构设计、数据设计、接口设计。详细设计即过程设计，对结构表示进行细化，得到软件详细的数据结构和算法。
软件设计各项设计工作的依据：体系结构设计，定义软件模块及其之间的关系，依赖于数据流图。数据设计，依赖于ER图。接口设计，依赖于顶层数据流图。过程设计：依赖于加工规格说明、状态图
基于数据流方法的设计过程：1.复查并精化数据流图。2.确定数据流图中数据流的类型，典型的数据流类型有变换型数据流和事务型数据流。3.导出初始的软件结构图。4.逐级分解。5.精化软件结构。6.导出接口描述和全局数据结构。
软件模块结构的改进方法：1，模块功能的完善化。2，消除重复功能，改善软件结构。3，模块的作用范围应在控制范围之内。4，尽可能减少高扇出结构，随着深度增大扇入。5，避免或减少使用病态连接。6，模块的大小要适中。接口设计的依据是数据流图中的自动化系统边界。
自顶向下，逐步细化的设计过程主要包括两个方面：一是将复杂问题的解法分析和细化成由若干个模块组成的层次结构，二是将每个模块的功能逐步分解细化为一系列的处理。第五章编码
编码容易出现的风格不足
1、变量或函数名字缺乏具体含义
2、变量或函数名字与其用途不符
3、变量或函数未加上必要的注释
4、函数未说明其功能、参数的意义
5、引用的符号未加以解释和说明
6、对循环等重要的程序语句未注释
7、对用到的重要库函数没有解释说明
8、对结构体等复杂数据结构的组成成分没有解释说明
9、缺乏必要的提示语句 第六章软件测试方法
软件测试是在软件投入生产性运行之前，对软件需求分析，设计规格说明和编码的最终复审，是软件质量控制的关键步骤。软件测试是为了发现错误而执行程序的过程。
第五篇：软件工程总结
一、软件工程概述
1．软件特点
软件：计算机程序（人们为了实现特定的功能而编制的一组指令集），软件文档，以及计算机程序运行时所需要的数据。
软件是计算机系统中的逻辑成分，具有无形性，可复用性。
2．软件分类（1）按功能划分：系统软件、支撑软件、应用软件。（2）按工作方式划分：实时处理软件、分时处理软件、交互式软件、批处理软件。（3）按规模划分：微型软件、小型软件、中型软件、大型软件。（4）按服务对象划分：通用软件、定制软件。3．软件发展阶段（1）程序设计时代（20世纪50年代）。（2）程序系统时代（20世纪60年代）。（3）软件工程时代（20世纪70年代起）。4．软件危机
（1）危机现象：软件开发成本与进度估计不准确，软件产品与用户要求不一致，软件产品质量可靠性差，软件文档不完整不一致，软件产品可维护性差，软件生产率低。
（2）危机原因：科学的工程化思想组织和指导，完善的质量保证体系，软件文档的不重视，软件的不可见性，系统规模庞大，生产工程化程度低，对用户需求关心不 够，对维护不够重视，开发工具自动化程度低。5．软件工程
软件工程：运用现代科学技术知识来设计并构造计算机程序及为开发、运行和维护这些程序所必须的相关文件资料。软件工程是一门关于软件开发与维护的工程学科，它涉及软件生产的各个方面，能够为经济、高效地开发高质量的软件产品提供最有效的支持。
软件工程的目标：控制成本，满足需求，提高质量，提高可靠性，是产品易于维护，移植，升级和使用，控制开发周期。
（1）工程方法：结构化方法、JSD方法、面向对象方法。（2）软件工具：具有自动化特征的软件开发集成支撑环境。（3）工程过程：在软件工具支持下的一系列工程活动，基本活动是软件定义、软件开发、软件验证、软件维护。（4）工程管理：项目规划，项目资源调配，软件产品控制。（5）工程原则：分阶段生命周期计划，阶段评审制度，严格的产品控制，采用先进的技术，成果能清楚地审查，开发队伍精练，不断改进工程实践。（6）工程目标：开发成本较低，软件功能能满足用户需求，软件性能较好，软件可靠性高，软件易于使用、维护与移植，能按时完成开发任务并及时交付使用。（7）工程文化：包括工程价值、工程思想和工程行为三个方面的内容。
二、软件工程过程模型 1．软件生命周期 如同任何事物都有一个发生、发展、成熟直至衰亡的全过程一样，软件系统或软件产品也有一个定义、开发、运行维护直至被淘汰这样的全过程，我们把软件将要经历的这个全过程称为软件的生命周期。它包含：软件定义、软件开发、软件运行维护三个时期，并可以细分为可行性研究、项目计划、需求分析、概要设计、详细设计、编码实现与单元测试、系统 2 集成测试、系统确认验证、系统运行与维护等几个阶段。
软件定义期 软件定义是软件项目的早期阶段，主要由软件系统分析人员和用户合作，针对有待开发的软件系统进行分析、规划和规格描述，确定软件是什么，为今后的软件开发做准备。这个时期往往需要分阶段地进行以下几项工作。1．软件任务立项 软件项目往往开始于任务立项，并需要以“软件任务立项报告”的形式针对项目的名称、性质、目标、意义和规模等作出回答，以此获得对准备着手开发的软件系统的最高层描述。2．项目可行性分析 在软件任务立项报告被批准以后，接着需要进行项目可行性分析。可行性分析是针对准备进行的软件项目进行的可行性风险评估。因此，需要对准备开发的软件系统提出高层模型，并根据高层模型的特征，从技术可行性、经济可行性和操作可行性这三个方面，以“可行性研究报告”的形式，对项目作出是否值得往下进行的回答，由此决定项 目是否继续进行下去。3．制定项目计划 在确定项目可以进行以后，接着需要针对项目的开展，从人员、组织、进度、资金、设备等多个方面进行合理的规划，并以“项目开发计划书”的形式提交书面报告。4．软件需求分析 软件需求分析是软件规格描述的具体化与细节化，是软件定义时期需要达到的目标。需求分析要求以用户需求为基本依据，从功能、性能、数据、操作等多个方面，对软件系统给出完整、准确、具体的描述，用于确定软件规格。其结果将以“软件需求规格说明书”的形式提交。在软件项目进行过程中，需求分析是从软件定义到软件开发的最关键步骤，其结论不仅是今后软件开发的基本依据，同时也是今后用户对软件产品进行验收的基本依据。软件开发期 在对软件规格完成定义以后，接着可以按照“软件需求规格说明书”的要求对软件实施开发，并由此制作出软件产品。这个时期需要分阶段地完成以下几项工作。1．软件概要设计 概要设计是针对软件系统的结构设计，用于从总体上对软件的构造、接口、全局数据结构和数据环境等给出设计说明，并以“概要设计说明书”的形式提交书面报告，其结果将成为详细设计与系统集成的基本依据。模块是概要设计时构造软件的基本元素，因此，概要设计中软件也就主要体现在模块的构成与模块接口这两个方面上。结构化设计中的函数、过程，面向对象设计中的类、对象，它们都是模块。概要设计时并不需要说明模块的内部细节，但是需要进行全部的有关它们构造的定义，包括功能特征、数据特征和接口等。在进行概要设计时，模块的独立性是一个有关质量的重要技术性指标，可以使用模块的内聚、耦合这两个定性参数对模块独立性进行度量。2．软件详细设计 设计工作的第二步是详细设计，它以概要设计为依据，用于确定软件结构中每个模块的内部细节，为编写程序提供最直接的依据。详细设计需要从实现每个模块功能的程序算法和模块内部的局部数据结构等细节内容 3 上给出设计说明，并以“详细设计说明书”的形式提交书面报告。3．编码和单元测试 编码是对软件的实现，一般由程序员完成，并以获得源程序基本模块为目标。编码必须按照“详细设计说明书”的要求逐个模块地实现。在基于软件工程的软件开发过程中，编码往往只是一项语言转译工作，即把详细设计中的算法描述语言转译成某种适当的高级程序设计语言或汇编语言。为了方便程序调试，针对基本模块的单元测试也往往和编码结合在一起进行。单元测试也以“详细设计说明书”为依据，用于检验每个基本模块在功能、算法与数据结构上是否符合设计要求。4．系统集成测试 所谓系统集成也就是根据概要设计中的软件结构，把经过测试的模块，按照某种选定的集成策略，例如渐增集成策略，将系统组装起来。在组装过程中，需要对整个系统进行集成测试，以确保系统在技术上符合设计要求，在应用上满足需求规格要求。5．系统确认验证 在完成对系统的集成之后，接着还要对系统进行确认验证。系统确认验证需要以用户为主体，以需求规格说明书中对软件的定义为依据，由此对软件的各项规格进行逐项地确认，以确保已经完成的软件系统与需求规格的一致性。为了方便用户在系统确认期间能够积极参入，也为了系统在以后的运行过程中能够被用户正确使用，这个时期往往还需要以一定的方式对用户进行必要的培训。在完成对软件的验收之后，软件系统可以交付用户使用，并需要以“项目开发总结报告”的书面形式对项目进行总结。
软件运行与维护期 软件系统的运行是一个比较长久的过程，跟软件开发机构有关的主要任务是对系统进行经常性的有效维护。软件的维护过程，也就是修正软件错误，完善软件功能，由此使软件不断进化升级的过程，以使系统更加持久地满足用户的需要。因此，对软件的维护也可以看成为对软件的再一次开发。在这个时期，对软件的维护主要涉及三个方面的任务，即改正性维护、适应性维护和完善性维护。2．瀑布模型 瀑布模型诞生于20世纪70年代，是最经典的并获得最广泛应用的软件过程模型。瀑布模型中的“瀑布”是对这个模型的形象表达，即山顶倾泻下来的水，自顶向下、逐层细化。（1）特点：线性化模型、阶段具有里程碑特征、基于文档的驱动、阶段评审机制。（2）作用：为软件项目按规程管理提供了便利，为其他过程模型的推出提供了一个良好的 拓展平台。（3）局限性：主要适合于需求明确且无大的需求变更的软件开发，但不适合分析初期需求 模糊的项目。3．原型模型（1）快速原型方法：是原型模型在软件分析、设计阶段的应用，用来解决用户对软件系统在需求上的模糊认识，或用来试探某种设计是否能够获得预期结果。（2）原型进化模型：针对有待开发的软件系统，先开发一个原型给用户使用，然后根据用 户的使用意见，对原型不断修改，使它逐步接近，并最终到达开发目标。
点击咨询 