IC-Modeling with UML.ppt
《IC-Modeling with UML.ppt》由会员分享,可在线阅读,更多相关《IC-Modeling with UML.ppt(65页珍藏版)》请在三一文库上搜索。
1、1,Modeling with UML,2,Overview,What is modeling? What is UML? Use case diagrams Class diagrams Sequence diagrams Activity diagrams Summary,3,Systems, Models, and Views,A model is an abstraction describing system or a subset of a system A view depicts selected aspects of a model A notation is a set o
2、f graphical or textual rules for representing views Views and models of a single system may overlap each other,4,Systems, Models, and Views,Airplane,Flightsimulator,Scale Model,Blueprints,Electrical Wiring,5,Why Model Software?,Software is already an abstraction: why model software? Software is gett
3、ing larger, not smaller NT 5.0 40 million lines of code A single programmer cannot manage this amount of code in its entirety. Code is often not directly understandable by developers who did not participate in the development We need simpler representations for complex systems Modeling is a mean for
4、 dealing with complexity,6,Concepts & Phenomena,Phenomenon: An object in the world of a domain as you perceive it, for example: The lecture you are attending My black watch Concept: Describes the properties of phenomena that are common, for example: Lectures on software engineering Black watches A c
5、oncept is a 3-tuple: Its Name distinguishes it from other concepts. Its Purpose are the properties that determine if a phenomenon is a member of a concept. Its Members are the phenomena which are part of the concept.,7,A Concept Is a 3-tuple,Name Purpose Members,8,Concepts In Software,The type of a
6、variable represents all possible instances the variable can take. The relationship between type & instance is similar to that of concept & phenomenon. Abstract data type (ADT) Special type whose implementation is hidden from the rest of the system.,9,Class,A class is an abstraction in the context of
7、 object-oriented languages Like an abstract data type, a class encapsulates both state (variables) and behavior (methods) Unlike abstract data types, classes can be defined in terms of other classes using inheritance,10,Two Classes,Watch,time,date,CalculatorWatch,SetDate(d),calculatorState,11,Object
8、-Oriented Modeling,UML Package,12,Application & Solution Domain,Application Domain Requirements & analysis The environment in which the system is operating Solution Domain System design & object Design The available technologies to build the system,13,Unified Modeling Language,An emerging standard f
9、or modeling object-oriented software. Resulted from the convergence of notations from three leading object-oriented methods: OMT (James Rumbaugh) OOSE (Ivar Jacobson) Booch (Grady Booch),14,UML Diagrams,Use case diagrams Describe the functional behavior of the system as seen by the user. Class diagr
10、ams Describe the static structure of the system: Objects, Attributes, and Associations. Sequence diagrams Describe the dynamic behavior between actors and the system and between objects of the system. Statechart diagrams Describe the dynamic behavior of an individual object as a finite state machine
11、. Activity diagrams Model the dynamic behavior of a system, in particular the workflow, i.e. a flowchart.,15,Use Case Diagram,WatchUser,WatchRepairPerson,ReadTime,SetTime,ChangeBattery,Actor,Use case,Package,SimpleWatch,Use case diagrams represent the functionality of the system from users point of
12、view,16,Class Diagram,Battery load(),1,2,Time now(),PushButton state push() release(),1,1,1,1,1,2,blinkIdx blinkSeconds() blinkMinutes() blinkHours() stopBlinking() referesh(),LCDDisplay,SimpleWatch,Class,Association,Multiplicity,Attributes,Operations,Class diagrams represent the structure of the sy
13、stem,17,Sequence Diagram,Object,Message,Activation,Sequence diagrams represent the behavior as interactions,18,button1&2Pressed,Statechart Diagram,State,Initial state,Final state,Transition,Event,19,Other UML Notations,Implementation diagrams Component diagrams Deployment diagrams Introduced in lect
14、ure on System Design Object Constraint Language (OCL) Introduced in lecture on Object Design,20,UML Core Conventions,Rectangles are classes or instances Ovals are functions or use cases Instances are denoted with an underlined names myWatch:SimpleWatch Joe:Firefighter,21,UML Core Conventions,Types a
15、re denoted with nonunderlined names SimpleWatch Firefighter Diagrams are graphs Nodes are entities Arcs are relationships between entities,22,Use Case Diagram,Used during requirements elicitation to represent external behavior Actors represent roles, that is, a type of user of the system Use cases r
16、epresent a sequence of interaction for a type of functionality The use case model is the set of all use cases. It is a complete description of the functionality of the system & its environment,23,A Use Case Diagram,24,Actor,An actor models an external entity which communicates with the system: User
17、External system Physical environment An actor has a unique name and an optional description. Examples: Passenger: A person in the train GPS satellite: Provides the system with GPS coordinates,25,An Actor,26,Use Case,A use case represents a class of functionality provided by the system as an event fl
18、ow. A use case consists of: Unique name Participating actors Entry conditions Flow of events Exit conditions Special requirements,27,A Use Case,28,Use Case Example,Name: Purchase Ticket Participating actor: Passenger Entry condition: Passenger standing in front of ticket distributor. Passenger has s
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- IC-Modeling with UML IC Modeling
链接地址:https://www.31doc.com/p-3028379.html