需求分析A卷復(fù)習(xí)點(diǎn)

1、精選優(yōu)質(zhì)文檔-傾情為你奉上精選優(yōu)質(zhì)文檔-傾情為你奉上專心-專注-專業(yè)專心-專注-專業(yè)精選優(yōu)質(zhì)文檔-傾情為你奉上專心-專注-專業(yè)（Choice）functional requirements and Nonfunctional requirement 功能性需求和非功能性需求team member role 團(tuán)隊(duì)成員的角色project success criteria 項(xiàng)目成功標(biāo)準(zhǔn)coupling, cohesion 耦合,凝聚力actor 男演員；行動(dòng)者；作用物The architecture style 體系結(jié)構(gòu)風(fēng)格Entity Objects，Control Object ，Bounda

2、ry Object 實(shí)體對(duì)象,控制對(duì)象,邊界對(duì)象use case naming rule 用例的命名規(guī)則Requirements analysis System Design Object Design Implementation（What should we do in each step?）需求分析系統(tǒng)設(shè)計(jì)對(duì)象設(shè)計(jì)實(shí)現(xiàn)(在每一步我們應(yīng)該做什么?)Functional modelObject modelDynamic model 功能模型 對(duì)象模型 動(dòng)態(tài)模型Use case diagramSequence diagramClass diagramState machine diagram用

3、例圖 序列圖 類圖 狀態(tài)機(jī)圖RelationshipCardinalityMultiplicityOverridePolymorphism Encapsulation 關(guān)系 基數(shù) 多樣性 覆蓋 多態(tài)性 封裝Inheritance Aggregation Generalization Composition Association Usability Reliability 產(chǎn)業(yè) 聚集 泛化 組成協(xié)會(huì) 可用性 可靠性 Performance Maintainability Verifiability 性能 可維護(hù)性 可驗(yàn)證性(These terms you should know their g

4、eneral meaning)(這些詞匯你應(yīng)該知道他們的一般含義)（Q&A）Model A model is an abstract representation of a system that enables us to answer questions about the system. Models are useful when dealing with systems that are too large, too small, too complicated, or too expensive to experience firsthand. Models also allow

5、us to visualize and understand systems that either no longer exist or that are only claimed to exist.一個(gè)模型是一個(gè)抽象的表示一個(gè)系統(tǒng),使我們能夠回答關(guān)于系統(tǒng)的問題。模型是有用的在處理系統(tǒng),太大,太小,太復(fù)雜或太貴的第一手經(jīng)驗(yàn)。模型還允許我們想象和理解系統(tǒng)不再存在或者只是聲稱存在。Abstract Class 抽象類When an inheritance relationship serves only to model shared attributes and operations, tha

6、t is, if the generalization is not meant to be instantiated, the resulting class is called an abstract class.當(dāng)一個(gè)只會(huì)繼承關(guān)系模型共享的屬性和操作,也就是說,如果概括不是為了被實(shí)例化,生成的類叫做抽象類。Nonfunctional requirements 非功能性需求Nonfunctional requirements describe aspects of the system that are not directly related to the functional beha

7、vior of the system. Nonfunctional requirements include a broad variety of requirements that apply to many different aspects of the system, from usability to performance.系統(tǒng)的非功能需求描述方面沒有系統(tǒng)的功能行為直接相關(guān)。非功能需求包括一個(gè)廣泛的各種各樣的需求,適用于系統(tǒng)的許多不同的方面,從可用性性能。Greenfield engineering 新建工程the development starts from scratchno

8、 prior system existsso the requirements are extracted from the users and the client. A greenfield engineering project is triggered by a user need or the creation of a new market 發(fā)展從scratch-no前系統(tǒng)存在的需求提取用戶和客戶端。新建工程項(xiàng)目是由一個(gè)用戶需要或創(chuàng)建一個(gè)新的市場Sequence diagram 序列圖A sequence diagram ties use cases with objects. I

9、t shows how the behavior of a use case (orscenario) is distributed among its participating objects. Sequence diagrams are usually not asgood a medium for communication with the user as use cases are, since sequence diagramsrequire more background about the notation. 一個(gè)序列圖用例與對(duì)象的關(guān)系。它顯示了一個(gè)用例的行為(或場景)分布在

10、其參與的 對(duì)象。序列圖通常不像良好的交際工具與用戶用例,因?yàn)樾蛄袌D需要更多的關(guān)于符號(hào)的背景。What is the difference between a scenario and a use case? When do you use each construct?1)什么是場景和用例的區(qū)別?當(dāng)你使用每個(gè)構(gòu)造嗎?Ans: A scenario is an actual sequence of interactions (i.e., an instance) describing one specific situation; a use case is a general sequence

11、 of interactions (i.e., a class) describing all possible scenarios associated with a situation. Scenarios are used as examples and for clarifying details with the client. Use cases are used as complete descriptions to specify a user task or a set of related system features.答:實(shí)際情況是一個(gè)序列的交互(即。、一個(gè)實(shí)例)描述一

12、個(gè)特定的情況,一個(gè)用例是一個(gè)通用的交互序列(即。描述所有可能的場景,一個(gè)類)相關(guān)情況。場景是用作澄清例子和細(xì)節(jié)與客戶。用例作為完整的描述來指定一個(gè)用戶任務(wù)或一組相關(guān)的系統(tǒng)特性。What the difference between Generalization and Specialization?2)一般化與特殊化的區(qū)別是什么?Ans: Generalization is the modeling activity that identifies abstract concepts from lower-levelones. Specialization is the activity th

13、at identifies more specific concepts from a high-level one. 答:泛化是識(shí)別的建?；顒?dòng)從低級(jí)別的抽象概念 的人。專業(yè)化的活動(dòng)從一個(gè)高層確定更具體的概念。What the difference between functional requirements and nonfunctional requirements?3)功能性需求和非功能性需求之間有什么區(qū)別?Ans: A functional requirement is a specification of a function that the system must suppor

14、t, whereas a nonfunctional requirement is a constraint on the operation of the system that is not related directly to a function of the system.答:功能需求是一個(gè)函數(shù)的一種規(guī)范,系統(tǒng)必須支持,而非功能需求是一個(gè)約束的操作系統(tǒng),并不直接相關(guān)的系統(tǒng)的一個(gè)函數(shù)。 About 4-Layer Architectural Style, please list the four layers and function of each layer.層建筑風(fēng)格,請(qǐng)列出四

15、層,每一層的功能。Ans：4-Layer-architectural styles (4-Tier Architectures) are usually used for the development of electronic commerce sites. The layers areThe Web Browser, providing the user interfaceA Web Server, serving static HTML requestsAn Application Server, providing session management (for example th

16、e contents of an electronic shopping cart) and processing of dynamic HTML requestsA back end Database, that manages and provides access to the persistent dataIn current 4-tier architectures, this is usually a relational Database management system (RDBMS).答:4-Layer-architectural風(fēng)格(4-Tier架構(gòu))通常用于電子商務(wù)站點(diǎn)

17、的發(fā)展. 層是1。Web瀏覽器,提供用戶界面2。一個(gè)Web服務(wù)器,提供靜態(tài)HTML請(qǐng)求3。一個(gè)應(yīng)用程序服務(wù)器,提供會(huì)話管理的內(nèi)容(例如一個(gè)電子購物車)和動(dòng)態(tài)HTML處理請(qǐng)求4。一個(gè)后端數(shù)據(jù)庫,管理和提供訪問持久數(shù)據(jù)在當(dāng)前4-tier架構(gòu),這通常是一個(gè)關(guān)系數(shù)據(jù)庫管理系統(tǒng)(RDBMS)。What the four techniques to elicit requirements?四大技術(shù)引出需求什么?Ans：Questionnaires: Asking the end user a list of pre-selected questionsTask Analysis: Observing end users in their operational