New Features of UML2.0 UML2 UML2.0. Koichiro Ochimizu, JAIST UML Structured Classifier. Design View (Internal structure diagram)

Transcription

1 UML2UML2.0 James Rumbaugh, Ivar Jacobson, Grady Booch, The Unified Modeling Language Reference Manual, Second Edition, Addison-Wesley, Koichiro Ochimizu Japan Advanced Institute of Science and technologies School of Information Science New Features of UML2.0 Sequence Diagram constructs and notation based largely on the ITUInternational Telecommunication UnionMessage Sequence Chart standard, adapted to make It more objectoriented Decoupling of activity modeling concepts from state machines and use of notation popular in the business modeling community. Contextual modeling constructs for the internal composition of classes and collaborations. Theses constructs permit both loose and strict encapsulation and wiring of internal structures from smaller parts. Repositioning of components as design constructs and artifacts as physical entities that are deployed Structured Control constructs in a Sequence Diagram sd ticketing loop kioskkiosk box of office request(count, performance) show availability (seat-list) select(seat) Credit card service: Credit Card Service lifeline activity Activity (Activity Diagram) propose show initial node produce? decision activity final node schedule show fork demand payment (cost) insert card (card number) publicize show buy scripts and music hire artists build sets design lighting make costumes charge (card number, cost) alt print tickets ( performance,seats ) authorized rehearse completion transition reject eject card unauthorized perform dress rehearsal join An activity shows the flow of control among the computational activities involved in performing a calculation or a workflow. Activities are shown on activity diagrams Structured Classifier Design (Internal structure diagram) name: Type selltickets connector seller: TicketSeller name:type part A structured classifier is a classifier with internal structure. It contains a set of parts connected by connectors. An part has a type and a multiplicity within its container. An connector is a contextual relationship between two parts in a structured classifier. Structured classifiers may be tightly encapsulated by forcing all interactions between external environment and the internal parts to pass through s. A is an interaction point with well-defined interface. Messages received by a are automatically forwarded to the part. Each has a set of provides interfaces and s that define its external interactions. guide: PerformanceGuide db:performancedb [] Each has a set of provides interfaces and s that define its external interactions. A specifies the services that a to the may request. A specifies the services that a from the may require from the external environment. UML2.0

2 Design (component diagram) A component diagram is a kind of structured classifier, so its Internal structure may be defined on an internal structure diagram. A component diagram shows the components in a system that is, the software units from which the application is constructed. A small circle attached to a component or a class is a - a coherent set of services made available by a component or class. A small semicircle attached to a component or a class is a a statement that the component or class needs to obtain services from an element that provides them. Component Definition delegation connector component :CreditCardChargers use supplier client :TicketSeller component definition IndividualSales : Tickets : ManagerInterface : KioskInterface : ClerkInterface provides interface customeraccess clerkaccess Component Diagram (is a kind of structured classifier) compatible interface CreditCardCharges charge charge TicketSeller individualsales on IndividualSales Tickets customeraccess clerkacsess ManagerInterface individualsales component definition s of UML.5 Component Deployment Use-Case Logical Concurrency KioskInterface customeraccess ClerkInterface clerkaccess H.E. Eriksson and M. Penker, UML Toolkit John Wiley & Sons, Inc. UML2.0 s Major Area, Diagram Main Concepts structural static viewclass diagram design viewinternal structure (connector, interface, part,, provided interface, role, ), collaboration diagram (connector, collaboration use, role), component diagram (component,,,, realization,, subsystem) use case viewusecase diagram dynamic state machine viewstate machine diagram activity viewactivity diagram interaction viewsequence diagram, communication diagram physical deployment viewdeployment diagram model ment model ment viewpackage diagram profilepackage diagram Other Modifications UML2.0 2

3 Kiosk Use Case ( Use case diagram) buy tickets <<include>> relationship make charges survey sales subject buy subscription <<include>> use case actor Clerk Credit card Service Supervisor visibility optional named compartment Class Content <<stereotypename>> Cname +attrname:cname = expression #attrname:cname -attrname: Cname[] +opname(p:c, q:c2): C3 <<constructor>> opname(v:cname = value) Responsibility text description <<stereotypename>> tagname = value stereotype application tagged value stereotype icon stereotype name class name (italics for abstract) public attribute with initial value protected attribute private attribute with multiplicity many public concrete operation with return type stereotype on subsequent operations abstract operation with default value compartment name compartment list element generalization Static ( class diagram) phone: String add (name, phone) owner association d Reservation date:date attribute Subscription Series series:integer Individual Reservation 0.. constraint {xor} 0.. static operation rolenames (association end names) multiplicity Show show Active Class Cname Attr: Atype Op(par:Type):Rtype 3..6 Ticket available: Boolean sell(c:) exchange qualifier seat:string 0.. operations performance.. Performance date: Date time:tod Relationship Aname association generalization Design (collaboration diagram) A collaboration is a contextual relationship among a set of objects that work together to fullfill some purpose. It contains a collection of roles contextual slots within a generic pattern that can be played by, or bound to, individual objects. realization TheatreSales <<kind>> kiosk: Kiosk[] :BoxOffice terminal: SalesTerminal[] UML2.0 3

4 Interaction The interaction view describes sequence of exchanges among the parts of a system. An interaction is based on a structured classifier or a collaboration. A role is a slot that may be filled by objects in a particular us of an interaction. Interaction view shows the flow of control across many objects and is displayed in two diagrams focused on different aspects: sequence diagrams and communication diagrams. The communication diagram is called a collaboration diagram in UML.5. sd ticketing Interaction ( Sequence Diagram ) kioskkiosk box of office request(count, performance) loop show availability (seat-list) select(seat) alt demand payment (cost) insert card (card number) print tickets ( performance,seats ) reject eject card charge (card number, cost) authorized unauthorized Credit card service: Credit Card Service lifeline Interaction ( communication diagram) State Machine (state machine diagram) kiosk role bound to active objects : request(count, performance) 4: offer(seat-list) link 5: buy(seats) 8: comfirm(seats, cost) connector bound to transitive links ticketseller 3: seat-list:=lock(count) 6: claim(seats) 7:unlock(seat-list) 2: db := finddb( performance) guide: DBCluster db db: PerformanceDB[] guide subscribe/assign() timed out/unlock() initial state state accept/buy() Available select/lock() reject/unlock() Locked Sold transition exchange(other)/assign();reset(other) performanceguide connector bound to persistent links trigger event event parameter effect node Deployment ( deployment diagram descriptor level ) TicketServer CreditCardCharges.jar TicketSeller.jar actor Manager ManagerInterface.jar communication association artifact Deployment (deployment diagram instance level) node instance Main St. kiosk: Kiosk node name node type communication link headquarters: TicketServer Kiosk Interface.c ClerkInterface.c SalesTerminal River St. box office: SalesTerminal Telesales office: SalesTerminal <<manifest>> <<manifest>> KioskInterface ClerkInterface Valley Mail kiosk: Kiosk Clerk UML2.0 4

5 Model Management ( package diagram) Model Management ( Profile) Planning package package Publicity Scheduling The profile mechanism permits limited changes to UML without modifying the underlying metamodel. UML includes three main extensibility constructs: constraints, stereotypes, and tagged Records Operations Ticket Sales Ticket Records Show <<database>> {names for one season must be unique} stereotype application constraint stereotype icon Purchasing Accounting Payroll <<database>> Scheduling <<authorship>> author = Frank Martin Due = Dec.3,2009 tagged values UML2.0 5