A Brif Overview of the Unified Modeling Language.pptVIP

下载本文档

1
0
约1.2万字
约 32页
2017-01-24 发布于河南
举报
版权申诉

A Brif Overview of the Unified Modeling Language.ppt

1、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

A Brief Overview of the Unified Modeling Language Bran SelicObjecTime Limited bran@ Overview Introduction The Object Paradigm Modeling with the UML Summary What is the UML? Inside the Standard The Object Paradigm A synergistic combination of various proven techniques including: encapsulation inheritance polymorphism/genericity Salient characteristic: a software system is rendered as a structure of collaborating parts the object paradigm is inherently structural Structure The individual parts of a system and their run-time topological relationships Fundamental structural relationship types: Objects Conceptual Objects Classes and Instances Design-time specifications for one or more distinct objects with a common form (structure and behavior) Object Behavior Programming Model Object “Engines” Passive objects: depend on external motive power (e.g., “main” program thread) Inheritance and Polymorphism Why Build Models? To understand the problem better To communicate with stakeholders To find errors or omissions To plan out the design To generate code UML Model Views Requirements (use case diagrams) Static structure (class diagrams) kinds of objects and their relationships Dynamic behavior (state machines) possible life histories of an object Interactive behavior (activity, sequence, and collaboration diagrams) flow of control among objects to achieve system-level behavior Physical implementation structures (component and deployment diagrams) software modules and deployment on physical nodes Object Instance Diagram State Machine Diagram State Machine Behavior Active Objects in the UML Concurrent incoming events are queued and handled one-at-a-time regardless of priority run-to-completion (RTC) execution model RTC and Concurrency Eliminates need to write complex and error-prone synchronization code if all passive objects encapsulated by an active object, only a single thread can pass through each passive object RTC Semantics State-Based Actions Hierarchical States and T