最后整理面向对象复习提纲.

1、0 bject-Oriented Systems Analysis and Desi一. The Object-Oriented Systems Development Environment （面向对象系统开发环境 ）oriented '?:rientid adj.定 向的；导向的；以为方向的1. systems development cycle （SDC）（系统开发周期）P2 （一定考）1）Project management and planning （项目管理与计划）2）System analysis （系统分析）3）System design （系统设计）4）Systems

2、 implementation （实施）and operation（系统的实施以及运行 ）Fiyur 1.1 The Systems eveioprrbent CyelflSystemSystemsDnignftolad ManagenieiTf and PlanningSysitemsImpJernentaliQn and Op?测恤2. Characteristics of Systems （系统特性）P5 （不考）Components （成员，组件（也称为子系统）Interrelationships （相互关系） Boundary （边界）rpose（目的） erfaces （接口）In

3、puts （输入）Output （输出）Constraints （约束）3. Important System Concepts （重要的系统概念）P6 （了解）1）Decomposition -break ing dow n a system into smaller con stitue nts （分解把一个系统分成更小的成分）2）Modularity -the result of decomposition; parts of a system （模块分解结果；系统的部分）3）Coupling -extent of dependencies between subsystems （耦合子

4、系统间的依赖程度）4）Cohesion -extent to which a subsystem performs a single function（类聚一个子系统执行一个简单功能的范围）4. types of in formation systems （信息系统的类型）P12 （中文含义）TPS -Transaction （事务） Processing （处理） System （事物处理系统） ，goal is to improve transaction processing by increasing speed, enhancing （提高）productivity, improvi

5、ng efficiency and accuracyMIS - Management Information System （管理信息系统），goal is to provide the information that helps managers intheir jobsDSS - Decision Support System （决策支持系统），goal is to support decision-making with unstructured andun predictable problemsFigure 1.7Depictions d1cd IjrifhftTlMiunSyst

6、er： TPS, MISrDSS5. Evolution of System Development Methodologies（系统开发方法的变革）P16 （比较重要，考）1）SDLC - Systems Development Life Cycle （系统开发生命周期）2）SAD - Structured Analysis and Design - Use of Data Flow Diagrams （结构化分析和设计方法一注重流程图）3）Data-Oriented Methodology - Use of Entity Relation Diagrams （面向数据方法 一使用 ER 图

7、）4）Object-Oriented Methodology - Use of Unified Modeling Language （UML） Diagrams（面向对象方法使用UML语言图表）5）Agile（adi.敏捷的）Methodologies - Adaptive, people-oriented approach （敏捷方法）6. Key Differe nces Between Structured and Object-Orie nted An alysis and Desig n（结构化与面向对象分析与设计的区别） P22必考（填空，简答）CharacteristicsStr

8、ucturedObject-Orie ntedMethodology （方法论）SDLCIterative/ In creme ntal （增量, 迭代）Focus （焦点）Process （过程）Objects （对象）Risk （风险）HighLowReuse （重用）LowHighMaturity （成熟）Mature and widespread （成熟 和广泛使用）Emerging （新兴的）Suitable for （使用领域）Well-defi nedprojects withstable user requireme nts（具有稳定需求很好定义项 目）Risky large

9、projects with cha nging user requireme nts（风险大，具有不断改变的项 目）二. Introduction to Object Orientation （面向对象介绍）P32 （名词解释，注意范化）1. Concepts（概念）of Object-Oriented （面向对象的概念）1）Object - An entity（实体）that encapsulates data and behavioK对象-将数据和行为压缩 （压缩）的一个实 体）2）Class - A category of objects that share the same attr

10、ibutes, operati ons, relati on ships, and sema ntics （类一 分享相同属性、操作、关系、语义的对象的分类）3）attribute - A named property of a class that describes a range of values that instances of the attribute might hold （属性-描述一系列价值）4）operation - A behavior of an object5）Encapsulation - The characteristic of object-orie nt

11、ati on in which data and behavior are bun dled into aclass and hidden from the outside world （圭寸装-面向对象的数据和行为被塞进一个类，隐藏起来的特征）6）Generalization ,d?en?r?lai'zei?i 般化 -A relati on ship betwee n a more gen eral （or pare nt） class and a more specific （or child） class （一个一般的事物（父类）和一个特定的事物（子类）的一种关系）7）Inhe

12、ritance in'herit ?ns纟继承-The mechanism by which the more specific spi'sifik class in agen eralizati on relati on ship in cludes the attributes and operatio ns of the more gen eral class（子类包括父类的属性和操作的一般关系的原理）8）Polymorphism - The ability for differe nt classes of objects to resp ond to ide ntic

13、al messages in differe nt ways （多态性-不同类关于对象用不同方法解决相同问题的能力）9）Association - A relati on ship or link betwee n in sta nces of （or objects） of classes 关联 -类中实例或对 象之间的关系或连接2. UMLUML - Unified Modeling Language （ UML 的图表 11 个）（定考，简答，有哪些图）1）用例图： Use-case diagram 'dai?gr?m -shows use cases, actors, and

14、relati on ships describ ing user interactions with system （以用例、角色和关系来描述系统用户之间的相互作用）2）顺序图、时序图 Sequence'si:kw ?ns diagram -shows interactions,int ?r'?k ?n of objects via 'vai ? message-passing in time-ordered manner （显示通过有序时间方式的传递信息的对象之间的关系）3）通讯图 Communication diagram -similar to sequence

15、diagram, but without the time-ordering （和顺序 图相似，但是没有时间顺序）4）类图 Class diagram -shows set of classes and relationships （generalizations and associations） 显 示类和关系（）的集合5）对象图 Object diagram -shows specific instances of a class diagram （特殊的类图的例子）6）活动图 Activity diagram -shows flow of activities, or wokflow

16、of objects7）状态图 State diagram - shows transitioningtr?n'si ?n of an object from state to state inresponse to events （展示活动的流程图或对象状态图一对象为响应某个事件从一个状态变成另一个状态的过程）8）合成结构图 Composite'k?mp?zit structure diagram -shows how a component whole is made up of its parts （显示如何通过每个部分构成一个完整的组件）9）包图 Package dia

17、gram -shows logical grouping of analysis or design elements （显示分析与设计原理 的逻辑组）10）组件图 Component diagram -shows software components or modules and their relationships （显 示软件部件或模块和他们之间的关系）11）部 署 图 Deployment diagram - shows configuration of runtime processing nodes and their components （显示处理节点的结构和他们的组件）三

18、. Managing the Object-Oriented Information Systems Project （管理面向对象信息系统项目）P62 （了解）1. Project Phases （阶段）项目管理的四个阶段（一）Project Initiation i,ni?i'ei?n （项目初始化） - First phase of project management, involves assessment of project scope, size, and complexity k?m'pleksiti and establishmenti'st?bli

19、 ?m?nt of project procedurespr?'si:d?（ 项目管理的第一个阶段包括评估方案的范围、尺寸、复杂性和项目规程的确立）A . The Project Workbook - An online or hardcopy repository ri'p?zit?ri of all project correspondenceri'p?zit?ri 通信；一致；相当 , inputs, outputs, deliverables di'liv ?r?bl, procedures, and standards项目工作手册 一一个在线的或者所有

20、项目通信，输入，输出，产出，规程，和标准的知识库B. The Project Charter 't? at?- A short, high-level document prepared for internal and external stakeholders toformally 'f?:m?li announce the establishment of the project and to briefly describe its objectives, key assumptions?'s?mp?n假定，设想，and stakeholders项目章程一一个短

21、的，高水平为内部和外部利益相关者去正式的宣布这项目的确定和简短地描述他的对象，关键设想和利益相关者而准备的文档。（二）Project Planning - Second phase of project management, focusing on defining clear, discrete activities and the work needed to complete each activity within a single project （ 项目计划） 一项目管理的第二个阶段，主 要集中在做清新定义，独立部件的活动区和工作需要在一个简单的项目中完成的行为a）BPP - T

22、he Baseline Project Plan 项目计划的基本原则（三）Project Execution ,eksi'kju: ?n （项目执行） - Third phase of project management, involving putting the planscreated in the previous 'pri:vj ?s phases into action, and monitoring actual progress against the BPP 包括让先 前阶段的计划去执行，监控保证真实的进展不违反项目设计的基本原则（四）Project Clo

23、sedown （项目结束）Final phase of the project management process, focusing on bringingthe project to an end 项目管理进程的最后一个阶段，结束项目2 Project Management Tools （项目管理工具）1）Critical path scheduling 关键路径安排2）Network diagrams 网络图3）Gantt diagrams 甘特图4）Work breakdown structures （WBS） 工作分解结构5）Software tools 软件工具四 . Selec

24、ting and Planning Projects （选择和计划项目 ）（了解）（也就是基本不考）1 Feasibility Assessment 可行性评价 P1021）Economic feasibility 经济可行性2）Technical feasibility 技术可行性3）Schedule feasibility 计划可行性4）Legal and contractual feasibility 法律和合同的可行性5）Political feasibility 政策可行性五. Determining Object-Oriented Systems Requirements （ 确定

25、面向对象系统需求 ）1 Traditional methods for determining requirements 需求决定的传统方法1）Interviews with individuals 个体访谈2）Observation of workers 工人的观察3）Business documents 商业文档2 Modern methods for determining requirements 需求决定的现代方法1）JAD - Joint Application Design 联合应用设计2）Prototyping 'pr?ut?taip 原型设计3）Agile Metho

26、dologies 敏捷的方法论六. Structuring Systems Requirements: Use Case Description and Diagrams （ 结构化系统需求： 用例描述和图 ）1. Use case diagram （P163）（看懂例图，大题）1）Use Case - A depictiondi'pik?n 描写 of a system 's behavior or functionality under various conditionsas the system responds to requests from users（ 用例 -

27、 一个在许多情况下为解决用户的请求的系统的行 为或功能的叙述） 名字解析2）Actor - An external entity that interacts with the system （参与者 - 一个外部与系统相互作用的实体）3）Boundary - The dividing line between the system and its environment （ 系统边界 - 系统与其环境的分界线）4）Connection - An associati on betwee n an actor and a use case （连接 -在用例和角色之间的关联）5）include R

28、elationship - An association between two use cases where one use case uses the functionalitycontained in the other（包含关系 -一个用例用到了另一个用例中包含的功能）6）extend Relationship - An association between two use cases where one adds new behaviors or actions to theother （扩展关系-通过添加新的行为和动作而扩展用例）2. Written Use Cases P17

29、21）Five suggested levelsa）White -as seen from clouds （白云）b）Kite - “ birc-eye view ” 风筝）c）Blue - sea-level view （ 海平面 ）d）Fish -below sea-level （鱼 ）e）Black -bottom of the sea 海的底部（ 深海 ）2) Format'f ?:m?t for Written Use Case 书写用例格式a) Titleb) Primary actorc) Stakeholders 风险承担者d) Precondition ,pri:k

30、?n'di?n 前提e) Minimal guarantee , g?r?n'ti:最低保障f) Success guaranteeg) Trigger'tri g?触发器h) Main success seenariosi'n a:ri?u主要的成功场景i) Extensions 扩展3 Examples of use case diagramFigure 6.3-6.7七 . Conceptual Data Modeling ( 概念数据模型 ) (一个题目 )1 ER data model - Entity 'ent?ti n. 实体 ；存在 re

31、lationship2. Coneeptual (概念)Data Model ElementsP192, P1911) Class2) Object - An instance of a class3) Attributes - Types of Attributes(Simple attributes, Multivalued attributes, Composite attributes), key(Primarykey, Candidate key)属性-属性类型(简单属性，多值属性，复合属性)，键(主键，候选键)4) Identifiers ai'dentifai ? 标识符

32、5) Relationship - Role, Degree( Un ary, Bin ary, Tern ary), Multiplicity( One-o one, One -o -many, Many -o many)角色，关系的度(程度 )(一元关系，二元关系，三元关系)，多样性()3 Types of Associations 关系的类型1) Association -no object is subordinate s?'b?:dineit to any other. 关联 在关系中没有对象从属于其他对象2) Aggregation -one class represent

33、s the whole, and the other represents the part, but it is a loose coupling. 聚合 (两个类通过整体 -部分关系绑定 )一个类代表整个，另一个代表部分，但是它是一种耦合3) Composition - an aggregation with a tight coupling. The whole and the part cannot exist without each other. 合成物 一个紧密结合的集合体，整体和部分不可分离4. Generalizations - A superclass/subclass r

34、elationship based on inheritancein'herit ?ns (遗传，继承 ) .一般化关系- 一个超类 /子类关系，它是基于继承概念的(必考)5 Examples of class diagram Figure 7.6-7.30八. Object-Relational Modeling ( 对象关系模型 ) (名词解析)1. Relational Data Model 关系型数据模型RDM - Relational Data Model data represented as a set of (一组) related tables or relation

35、s 以关系表或关系 的形式表示数据Relation - A named, two-dimensional table of data 二维数据表1) Rules of Normalization 规范化1st NF - all relations are in 1NF2nd NF - relations with no partial-key 'p a:?l 局部 functional dependencies3rd NF - relations with no transitive 'tr?nsitiv 传递 functional dependenciesHigher nor

36、mal forms - 4th, Boyce Codd, 5th - mainly theoretical, 0'rietik ?l理论上的，not needed for most OOSAD problems 2 Object Extensions to Relational Modeling 关系型数据模型的对象扩展1) ORDM - Object-relational Data Model 对象关系型数据模型 _名字解析Generalization 一般化Multivalued attributes 多值属性Aggregation 聚合（支持聚合的机制）Object identi

37、fiers 对象标识符Pointers 指针Behaviors 行为丰富的数据类型集合2） Translating Conceptual Data Model to Object-Relational Model （将概念数据模型转换成对象关系）Translate classes 转换类Translate relationships 转换关系Normalize object relations 使对象关系标准化Mergem ?:d? object relations 合并对象关系九. Analysis Classes （分析类 ） 掌握概念，不是重点1 Analysis Class：A cla

38、ss that represents initial data and behavior requirements, and whose software and hardware-oriented details have not been specifiedEntity class：Boundary class：Control class：2 Sequence Diagram - A diagram that shows the interaction between objects to perform critical pieces of use case behavior in a

39、time-ordered manner （顺序图 -展现对象之间交互去按时间顺序评论一系列用例行为的图）3 Communication Diagram - A diagram that shows the interactions between objects to perform critical pieces of the use case behavior （协作图 -展现对象之间交互去按时间顺序评论一系列用例行为的图（重点在于如何协 作而非顺序） ）4 Analysis Class Diagrams - Analysis classes are completed by includ

40、ing operations, which fulfill the responsibilities taken by the analysis class（分析类图-各个分析类及这些类之间的关系（分析类去执行职责的包含操作） ）5 Activity Diagram - A diagram that emphasizes the flow of control from activity to activity in an object （ 活动图- 强调对象中活动对活动的控制流）6 State Diagram - A diagram that captures the behavior of

41、 an object by specifying the sequence of states it goes through during its lifetime in response to events, together with the responses to those events （状态图 记录对象的 行为，他指出了对象在其生命周期内经历的状态序列，以及对这些事件如何响应）7 Business Rule- A directive that is intended to influence or guide business behavior in support of bu

42、siness policy formulated in response to an opportunity or threat（业务规则 -一种意图在于影响或指导业务行为的指标，它支持着形式化的，用于响应机遇或威胁的业务策略）1） Types of Business Rule P258（一）Constraints -restrictions, mainly in the form of permissible values, validation rules, and multiplicities 约束-限制条件，主要以许可值，确认规则，多样性的约束形式（二）Calculations ,k?

43、lkju:lei ?n - mathematical formulas or algorithms that produce some value 计算 - 数学公式或者生成值的算法（三）Value inferences -establishing the value of an attribute based on a test condition 值推理 - 基于测试 条件确定一个属性的值（四）Action enablers - deciding on an action based on a test condition 动作启动器 - 基于一个测试条件 决定一个动作（五）OCL - Object Constraint Language 对象约束