軟件工程復(fù)習(xí)資料_英文

1、Lecture 1 An Introduction to Software Engineering1 what does software engineering concern?1) Software engineering is concerned with theories, methods and tools for professional software development.2) Software engineering is concerned with cost-effective software development.2 What is software?Softw

2、are includes: computer programs data structures documents 3 What is the two types of software productsGeneric software(通用軟件) and custom software（定制軟件） 4 The three key elements of a successful software project are:on time, within budget, satisfies the users needs5 Generic activities in all software p

3、rocesses are:Specification（描述）, Development（開(kāi)發(fā)）, Validation（有效性驗(yàn)證）, Evolution（進(jìn)化）6 The attributes of good software include:Maintainability（可維護(hù)性）, Dependability（可依賴性）, Efficiency（有效性）, Acceptability（可接受性）Lecture 2 Software Processes 1 What is a software process model A software process model is an ab

4、stract representation of a software process. It presents a description of a process from some particular perspective.2 Draw the graphic presentation of Waterfall model and describe its character.1） 這種模型把軟件過(guò)程劃分成幾個(gè)順序的階段。階段間具有依賴性，前一個(gè)階段結(jié)束，后一個(gè)階段才能開(kāi)始；2） 這種模型很難對(duì)用戶變更做出調(diào)整，只適用于需求非常清楚和需求變更被嚴(yán)格限制的情況下。3 Describe

5、the basic principle of evolutionary development and its two types進(jìn)化式開(kāi)發(fā)的基本思想是先開(kāi)發(fā)一個(gè)原型給用戶使用，通過(guò)用戶反饋意見(jiàn)來(lái)不斷修改系統(tǒng)直到最后成熟，所以又被稱作快速原型開(kāi)發(fā)方法。它不主張將描述、開(kāi)發(fā)和有效性驗(yàn)證等活動(dòng)分開(kāi)進(jìn)行，而是讓這些活動(dòng)迭代執(zhí)行，同時(shí)讓這些活動(dòng)能得到快速的反饋信息。進(jìn)化式開(kāi)發(fā)有兩種基本類型：探索式開(kāi)發(fā)和拋棄式原型法。4 Draw the graphic presentation of incremental delivery and describe its character在這種開(kāi)發(fā)方式中，系統(tǒng)不

6、是作為一個(gè)整體交付，而是被分解成若干個(gè)增量，每個(gè)增量交付系統(tǒng)的部分功能。用戶的需求按優(yōu)先級(jí)排隊(duì)，優(yōu)先級(jí)最高的需求被放入最早交付的增量中。這樣，優(yōu)先級(jí)最高的系統(tǒng)功能就得到最多的測(cè)試，系統(tǒng)的可靠性較高。5 Describe the characters of Spiral development.（對(duì)照模型去理解）1) Process is represented as a spiral rather than as a sequence of activities with backtracking.2) Each loop in the spiral represents a phase in

7、 the process. 3) No fixed phases such as specification or design - loops in the spiral are chosen depending on what is required.4) Risks are explicitly assessed and resolved throughout the process.Lecture 3 Requirements Engineering1 Draw the graphic presentation of requirement engineering process.2

8、Describe the difference of functional requirements, non- functional requirements, Domain requirements.Functional requirements describe the services that the system should provide and how the system should react to particular inputs and how the system should behave in particular situations.Non-functi

9、onal requirements describe the constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc.Domain requirements come from the application domain of the system and that reflect characteristics of that domain.3 Descri

10、be the difference between user requirements and system requirements.1) User requirements should describe functional and non-functional requirements in such a way that they are understandable by system users who dont have detailed technical knowledge.User requirements are defined using natural langua

11、ge, tables and diagrams as these can be understood by all users.2) System requirements are more detailed specifications of system functions, services and constraints than user requirements.They are intended to be a basis for designing the system.They may be incorporated into the system contract.Syst

12、em requirements may be defined or illustrated using system models.4 Describe the process activities of requirements elicitation.Requirements elicitation process is an iterated process.1) Requirements discovery（需求發(fā)現(xiàn)）Interacting with stakeholders to discover their requirements. Domain requirements are

13、 also discovered at this stage.2) Requirements classification and organization（需求的分類與組織）Groups related requirements and organises them into coherent clusters.3) Prioritisation and negotiation（優(yōu)先排序和沖突解決）Prioritising requirements and resolving requirements conflicts.4) Requirements documentation（需求文檔化

14、）Requirements are documented and input into the next round of the spiral.5 what are viewpoints and what are the types of viewpointsnViewpoints are a way of structuring the requirements to represent the perspectives of different stakeholders. Stakeholders may be classified under different viewpoints.

15、There are three types:1) Interactor viewpointsPeople or other systems that interact directly with the system. In an ATM, the customers and the account database are interactor VPs.2) Indirect viewpointsStakeholders who do not use the system themselves but who influence the requirements. In an ATM, ma

16、nagement and security staff are indirect viewpoints.3) Domain viewpointsDomain characteristics and constraints that influence the requirements. In an ATM, an example would be standards for inter-bank communications. 5 Write down at least four principles of delaminated DFD. 頂層數(shù)據(jù)流圖上的數(shù)據(jù)流必須封閉在外部實(shí)體之間。 數(shù)據(jù)

17、應(yīng)通過(guò)加工流動(dòng)，避免從一個(gè)數(shù)據(jù)存儲(chǔ)直接流向另一個(gè)數(shù)據(jù)存儲(chǔ)。 每個(gè)加工至少有一個(gè)輸入數(shù)據(jù)流和一個(gè)輸出數(shù)據(jù)流，且輸入與輸出數(shù)據(jù)流要平衡。有輸入，無(wú)使用及輸出為“黑洞”，無(wú)輸入和產(chǎn)生而有輸出為“奇跡”。 在數(shù)據(jù)流圖中，需按層給加工框編號(hào)。編號(hào)表明該加工處在哪一層，以及上下層的父圖與子圖的對(duì)應(yīng)關(guān)系。 規(guī)定任何一個(gè)數(shù)據(jù)流子圖必須與它上一層的一個(gè)加工對(duì)應(yīng)，兩者的輸入數(shù)據(jù)流和輸出數(shù)據(jù)流必須一致。此即父圖與子圖的平衡。 圖上每個(gè)元素都必須有名字。數(shù)據(jù)流和數(shù)據(jù)文件的名字應(yīng)當(dāng)是“名詞”或“名詞性短語(yǔ)”，表明流動(dòng)的數(shù)據(jù)是什么。加工的名字應(yīng)當(dāng)是“動(dòng)詞賓語(yǔ)”，表明做什么事情。6 According to the dec

18、ision table, draw the decision tree.7 What are the attributes of a good SRS(System Requirements Specification)?1） 完整性：需求描述包含了所有的用戶要求，不應(yīng)該遺漏要求和必需的信息；2） 一致性：需求描述不能存在沖突；3） 可檢驗(yàn)性：功能與性能指標(biāo)應(yīng)該能夠量化衡量；4） 可理解性：需求描述方式要容易理解，沒(méi)有歧義；5） 可跟蹤性：要明確標(biāo)識(shí)需求與其原始材料的關(guān)系，能夠回溯道源頭；6） 可變更性：需求要易于修改，有良好的組織，如目錄、索引。Lecture 4 Software Desi

19、gn1 Describe the two scale parameter of Independency and explain why we need fine independency.模塊獨(dú)立性可用兩個(gè)定量準(zhǔn)則來(lái)度量：耦合（coupling）和內(nèi)聚（cohesion）。耦合性是對(duì)軟件程序結(jié)構(gòu)中各個(gè)模塊之間相互關(guān)聯(lián)程度的一種度量。內(nèi)聚性是信息隱藏和局部化概念的自然擴(kuò)展，它標(biāo)志一個(gè)模塊內(nèi)部各成分彼此結(jié)合的緊密程度。 模塊的內(nèi)聚性越強(qiáng)，耦合性越弱，獨(dú)立性越強(qiáng)。獨(dú)立性好的模塊對(duì)其它的模塊依賴性小，修改時(shí)對(duì)其它模塊的影響小，易于修改和擴(kuò)充，因此有良好的可維護(hù)性。2 What is the task

20、 of architectural design?It is to identify the sub-systems making up a system and to build the framework for sub-system control and communication.3 Describe the basic character of repository model.Shared data is held in a central database or repository and may be accessed by all sub-systems4 Describ

21、e the basic composing of Client-server model.Set of stand-alone servers which provide specific services such as printing, data management, etc.Set of clients which call on these services.Network which allows clients to access servers.5 Describe the characters of Abstract machine (layered) model1) Th

22、is model organises the system into a set of layers (or abstract machines) each of which provide a set of services.2) It supports the incremental development of sub-systems in different layers. When a layer interface changes, only the adjacent layer is affected.6 Describe two types of control model.C

23、entralised control: One sub-system has overall responsibility for control and starts and stops other sub-systems.Event-based control: Each sub-system can respond to externally generated events from other sub-systems or the systems environment.7 Describe three types of software reuse.Application syst

24、em reuseThe whole of an application system may be reused either by incorporating it without change into other systems (COTS reuse) or by developing application families.Component reuseComponents of an application from sub-systems to single objects may be reused.Object and function reuseSoftware comp

25、onents that implement a single well-defined object or function may be reused.8 What is framework?框架是一種高于對(duì)象層次的大粒度抽象的復(fù)用成分Framework is a sub-system design made up of a collection of abstract and concrete classes and the interfaces between them9 Draw and describe the graphic presentation of MVC framewor

26、k .這個(gè)框架有三個(gè)基本組件：控制器、模型和視圖1） 控制器：代表應(yīng)用程序的邏輯部分，它定義了一個(gè)用戶如何和程序進(jìn)行交互并且定義了用戶行為是如何映射到模型；2） 模型：負(fù)責(zé)對(duì)數(shù)據(jù)模型和所有用來(lái)確定應(yīng)用程序狀態(tài)的信息進(jìn)行管理；3） 視圖：從不同的角度對(duì)存儲(chǔ)在模型中的數(shù)據(jù)進(jìn)行展示。10 Draw the graphic presentation of user interface design process.11 The principles of user interface design are:用戶熟悉、一致性、意外最小化。12 Error messages should be polit

27、e, concise, consistent and constructive.13 ExerciseLecture 5 Object-oriented Analysis and Design1 Compared with traditional structural developing methods，what are advantages of object-oriented methods？n符合人類自然思維方式，易于理解、描述和實(shí)現(xiàn)。n對(duì)需求變化有較好的適應(yīng)性：封裝機(jī)制和消息傳遞機(jī)制將需求變化影響限制在對(duì)象內(nèi)部。n支持軟件復(fù)用：封裝性有助于實(shí)現(xiàn)復(fù)用；繼承、實(shí)例化實(shí)現(xiàn)了對(duì)象復(fù)用；類庫(kù)提

28、供了大量公共代碼。n可維護(hù)性好：封裝性和消息傳遞造成低耦合，錯(cuò)誤定位和修改容易；繼承與多態(tài)使得功能的擴(kuò)展更加容易。n開(kāi)發(fā)過(guò)程銜接緊密：在軟件生命周期各階段可以使用同樣的模型描述。2 Describe the ultimately purpose of UMLUML是一種標(biāo)準(zhǔn)的圖形化建模語(yǔ)言，為不同領(lǐng)域的人們提供一種統(tǒng)一的交流標(biāo)準(zhǔn)，這種標(biāo)準(zhǔn)使得系統(tǒng)構(gòu)造者能夠用標(biāo)準(zhǔn)的、易于理解的方式建立能表達(dá)出他們想象力的系統(tǒng)藍(lán)圖，并使客戶、分析員、設(shè)計(jì)人員、程序員和系統(tǒng)其它涉及者能夠相互理解和達(dá)成一致，從而能夠有效地共享和交流設(shè)計(jì)結(jié)果。3 Exercise（要求熟悉UML各種模型）Lecture 6 Softw

29、are Implementation and Validation1 Each program component involves at least three major aspects: control structures, algorithms, and data structures.2 Describe the difference between verification and validation.l Verification: "Are we building the product right”.The software should conform to i

30、ts specification.l Validation: "Are we building the right product”.The software should do what the user really requires3 The two methods in V & V process are :Software inspection is concerned with analysis of the static system representation to discover problems (static verification)Softwar

31、e testing is concerned with exercising and observing product behaviour. The system is executed with test data and its operational behaviour is observed. (dynamic verification)4 Draw the graphic presentation of software testing process.5 The two phases of system testing are integration testing and re

32、lease testing 6 In integration testing , to simplify error localisation, systems should be增量集成.7 Describe the base composing of test case and the base principle of equivalence partition testing.測(cè)試用例的基本構(gòu)成可以包括：設(shè)計(jì)的輸入、期望的輸出、測(cè)試環(huán)境和測(cè)試對(duì)象的描述。等價(jià)劃分測(cè)試是測(cè)試用例設(shè)計(jì)的一種方法。設(shè)計(jì)測(cè)試用例時(shí)，可以按特征把數(shù)據(jù)輸入域化分成若干等價(jià)類，等價(jià)類中的每個(gè)數(shù)據(jù)應(yīng)該以同樣的方式得到處

33、理，因此對(duì)于揭露程序中的錯(cuò)誤是等效的。這樣，就可以選取少量有代表性的輸入數(shù)據(jù)作為測(cè)試數(shù)據(jù)，以期用較小的代價(jià)暴露較多的程序錯(cuò)誤。8 Describe the difference between black-box testing and white-box testing.黑盒測(cè)試又叫做功能測(cè)試，測(cè)試者只關(guān)心系統(tǒng)的功能而不關(guān)心軟件的實(shí)現(xiàn)。也就是說(shuō)測(cè)試者不必了解有關(guān)系統(tǒng)的任何細(xì)節(jié)，只把系統(tǒng)看成是一個(gè)能夠處理輸入，產(chǎn)生輸出的“黑盒子”，僅從功能的角度設(shè)計(jì)測(cè)試用例。白盒測(cè)試又叫做結(jié)構(gòu)測(cè)試，是一種根據(jù)軟件的結(jié)構(gòu)知識(shí)導(dǎo)出測(cè)試用例的設(shè)計(jì)方法。測(cè)試者把被測(cè)試組件看成是一個(gè)打開(kāi)的“白盒子”，組件的內(nèi)部結(jié)構(gòu)對(duì)測(cè)

34、試者是透明的，通過(guò)對(duì)所用算法結(jié)構(gòu)的分析設(shè)計(jì)測(cè)試用例。9 Describe the basic principle of basis path testing and calculate the number of basis paths in the figure.12345678在程序控制流圖的基礎(chǔ)上，分析控制結(jié)構(gòu)的環(huán)路復(fù)雜度,并用這個(gè)復(fù)雜度為指南定義執(zhí)行路徑的基本集合，從而導(dǎo)出基本可執(zhí)行路徑集合，設(shè)計(jì)出測(cè)試用例并保證每個(gè)可執(zhí)行語(yǔ)句至少執(zhí)行一次，而且每個(gè)條件在執(zhí)行時(shí)都將分別取真、假兩種值。1) 計(jì)算環(huán)路復(fù)雜度V(G)V(G)=簡(jiǎn)單判定的數(shù)目+1 或 封閉區(qū)域的數(shù)目+1=42) 導(dǎo)出獨(dú)立路徑的數(shù)目由于V(G)=4，所以共有4條路徑Lecture 7 Software Project Management1 Describe the process of project planning Establish the project constraints Make initial assessments of the project parameters Define project milestones and deliverableswhile project has not been completed or cancelled