【正文】 2是如果確實需要創(chuàng)建新的構(gòu)件，則在設(shè)計時應(yīng)該考慮將來的可重復(fù)使用性。模塊的獨立性是指軟件系統(tǒng)中每個模塊只涉及軟件要求的具體的子功能，而與軟件系統(tǒng)中其他模塊的接口是簡單的，若一個模塊只具有單一的功能且與其他模塊沒有太多的聯(lián)系，那么稱此模塊有獨立性。軟件的體系結(jié)構(gòu)設(shè)計，模塊化設(shè)計都是分而治之策略的具體表現(xiàn)。數(shù)據(jù)字典。結(jié)構(gòu)化分析方法：是一種建模技術(shù)。（對）需求調(diào)查時，用戶所說的需求未必是真實、準(zhǔn)確的需求，因此需求分析需要依賴用戶，但是不能過分迷信用戶。關(guān)于需求獲取問題的認(rèn)識辨析：沒有與用戶交流就不可能獲取系統(tǒng)需求。3，系統(tǒng)需求規(guī)格說明。將獲取的需求文檔化，形式有用例，決策表，決策樹等。獲取并理解用戶的需求是軟件工程師所面對的最困難的任務(wù)之一。程序設(shè)計語言(PDL)。詳細(xì)設(shè)計描述方法有輸入處理輸出(IPO)圖。模塊的數(shù)據(jù)結(jié)構(gòu)通常用實體關(guān)系圖來描述。需求分析工具結(jié)構(gòu)化圖形工具箱。軟件測試計劃。由概要設(shè)計、詳細(xì)設(shè)計、編碼和測試4個階段組成。軟件生存期由軟件定義，軟件開發(fā)和運行維護(hù)三個時期組成，每個時期又可劃分為若干個階段。4，隨著軟件規(guī)模的增大，其復(fù)雜性往往會呈指數(shù)級升高。軟件危機的典型表現(xiàn)成本太高，預(yù)算不準(zhǔn)超過預(yù)計時間軟件質(zhì)量標(biāo)準(zhǔn)不明確生產(chǎn)率低缺乏文檔資料，難以維護(hù)。3，支撐軟件，也叫工具軟件，是協(xié)助用戶開發(fā)軟件的工具性軟件。（對）合格的軟件產(chǎn)品不需要維護(hù)，軟件需要維護(hù)說明其質(zhì)量不合格。（對）有缺陷的軟件就是廢品。文檔是與程序開發(fā)，維護(hù)和使用有關(guān)的圖文資料。軟件技術(shù)不是一成不變的，是隨著社會的進(jìn)步的不斷進(jìn)步，不需要不斷的創(chuàng)新，不斷的改善的，需要我們不斷的學(xué)習(xí)，不斷的研究，不斷進(jìn)步。上規(guī)模的企業(yè)極少。軟件工程項目是一個需要一步一步的計算，分析思考而來的，需要不斷思考，研究不斷進(jìn)步，軟件業(yè)作為一個服務(wù)業(yè)，要想得到發(fā)展，首先必須形成一個對軟件服務(wù)有迫切需要的市場。本課程是面向準(zhǔn)備從事軟件開發(fā)的畢業(yè)生而開設(shè)的一門專業(yè)課程。系統(tǒng)化地應(yīng)用工具和技術(shù)于開發(fā)以計算機為主的應(yīng)用。實際應(yīng)用科學(xué)知識在設(shè)計、建構(gòu)電腦程序，與相伴而來所產(chǎn)生的文件，以及后續(xù)的操作和維護(hù)上。業(yè)界關(guān)于軟件工程的代表性觀點創(chuàng)立與使用健全的工程原則，以便經(jīng)濟(jì)地獲得可靠且高效率的軟件。近年來，從 IT 界到一些國家首腦，都高度關(guān)注以物聯(lián)網(wǎng)為標(biāo)志的新一輪信息技術(shù)的發(fā)展態(tài)勢，認(rèn)為這是繼 20 世紀(jì) 80 年代 PC 機、90 年代互聯(lián)網(wǎng)、移動通信網(wǎng)之后，將引發(fā) IT 業(yè)突破性發(fā)展的第三次 IT 產(chǎn)業(yè)化浪潮。學(xué)了《軟件工程》這門課程和一些有關(guān)資料后，感覺一些東西都曾經(jīng)接觸過，但在實際工作中有些理論要完全遵循可能還有些障礙，軟件工程只是提供了理論上的一些結(jié)論，但對項目的具體可操作性的規(guī)范的制定方面卻做的很少，《軟件工程》發(fā)展了幾十年，光是開發(fā)模型就達(dá)到了10多種，對不同的項目采用合適的開發(fā)模式，有些項目在不同的開發(fā)階段可能還要轉(zhuǎn)換開發(fā)模式，把它們靈活的應(yīng)用到實際中還是很困難的。計算機學(xué)科分為四個領(lǐng)域，分別是計算機科學(xué)，計算機工程，軟件工程和信息系統(tǒng)。deployment diagram.● Using UML for modeling the demand: that we can use cases(use case)needs to proceed as a good starting point for cases are organized according to the system using the use cases as a starting point for requirements modeling, allows us to focus attention on case diagram is to show a set of use cases, the relationship between the participants and their case diagram includes the following three , generalization and association.● Diagram: these will be described in the UML activity flow graph is called an activityWhitebox testing method: logic coverage test and path testing steps: testing Testing of test Testing ● ● ● State Diagram: to model the dynamic aspects of the 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 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 position of software systems, but did not describe the system in hardwarerelated 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 engineering is the mapping from a specific implementation language and the code to model the think, the course of Software Engineering is a a necessary science courses for people who do software learning this course, programmers will focus on software development, theoretical knowledge, and to do project development learning of the course you will not write a program to blindly apply the code, but to clarify the structure of the program and the program from the start, when to needs to be added in the middle of the function, to improve the fact, software engineering is not difficult to learn and Software Engineering linked to daily life, then, is the day you should do first, what to do what to do first, what to do after the after the write process is not so difficult, more plex programs can be divided into several large you sort out the idea of the program step by step solution can be one of the problems, and ultimately 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 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 plete software out.第二篇：軟件工程總結(jié)軟件工程課程總結(jié)摘要：計算機是20世紀(jì)最重大的科學(xué)技巧成就之一，使當(dāng)代社會的經(jīng)濟(jì)、軍事、科研、教育、服務(wù)等方面在概念和技巧上發(fā)生了性的變化，對人類社會的進(jìn)步已經(jīng)并還將產(chǎn)生極為深刻的影響。collaboration diagram。preventive maintenance.● Software maintainability: measure of the ease of software maintenance of a software 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 Reengineering: reverse engineering, restructuring and other technology, a full understanding of the original software, based on the deposition, synthesis, and rebuilding software to improve software understandability, maintainability, reusability.● UML class diagram of Figure 9 include: class diagram。s functionality to design test static analysis and dynamic 。s logical and physical views.● ● Requirements definition: A plete 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 shall behave.● Software design task: to produce the software requirements analysis phase into a description of methods of representation with the appropriate software design 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 streamoriented 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 floworiented design methods to map the flow of information into a software architecture, information flow type determines the mapping flow has the following two t