UML other structural. diagrams. (Implementation Diagrams UML 1.5) Università di Padova. Facoltà di Scienze MM.FF.NN. Informatica - anno

Transcription

1 Università di Padova Facoltà di Scienze MM.FF.NN Informatica - anno Corso di Ingegneria del Software - B UML other structural diagrams (Implementation Diagrams UML 1.5) v 2.3 Renato Conte - UML: diagrammi di implementazione - 1 / 37 -

2 UML 2.0 Diagram UML 2.0 Structure Diagram Behavior Diagram Activity Diagram Object Class Diagram Use Case Diagram Diagram Composite Structure Diagram Interaction Diagram Package Diagram Sequence Diagram Component Deployment Diagram Diagram State Machine Diagram Interaction Overview Diagram Communication Diagram Timing Diagram Renato Conte - UML: diagrammi di implementazione - 2 / 37 -

3 Workflows, Models and Diagrams Use Case Diagrams Requirements Use Case Model Analysis Analysis Model Component Diagrams Design Model Deployment Diagrams Design Deployment Model Implementation Test Implem. Model Test Model Class Diagrams Object Diagrams Composite Structure Diagrams Sequence Diagrams Collaboration Diagrams Communication Diagrams Statechart Diagrams Activity Diagrams Renato Conte - UML: diagrammi di implementazione - 3 / 37 -

4 Implementation diagrams There are two types of implementation diagrams, both concerned with the physical details of system organization Component diagrams which show the relationships between software artifacts. Deployment diagrams (trad.it. diagrammi di messa in opera ) which show the relationships between hardware and software artifacts. Renato Conte - UML: diagrammi di implementazione - 4 / 37 -

5 Component is a physical and replaceable part of a system that conforms to and provides the realization of a set of interfaces. User guide Renato Conte - UML: diagrammi di implementazione - 5 / 37 -

6 Component «component» Type UML 1.5 Type UML 2.x «component» Name: Type Name: Type Renato Conte - UML: diagrammi di implementazione - 6 / 37 -

7 Components and classes ( rarely drawn ) fraudagent.dll Fraud Agent Fraud Policy Pattern Search Renato Conte - UML: diagrammi di implementazione - 7 / 37 -

8 Components and interfaces image.java (UML 2.x and 1.5) component.java ImageObserver «interface» ImageObserver image.java abort:int{final static} error:int{final static} component.java imageupdate():boolean Renato Conte - UML: diagrammi di implementazione - 8 / 37 -

9 Components and interfaces (UML 2.0) required interface OrderEntry OrderableItem «component» «component» :Order Order OrderEntry OrderableItem provided interface OrderableItem «component» Product OrderableItem «component» :Product Renato Conte - UML: diagrammi di implementazione - 9 / 37 -

10 component model: university system Renato Conte - UML: diagrammi di implementazione - 10 / 37 -

11 component model for a university system As you can see UML 2 uses this symbol as a visual stereotype within the rectangle to indicate that the rectangle represents a component although the textual stereotype of component is also acceptable (as you see with the Schedule component). Both diagrams model dependencies, either between components or between components and interfaces. You can also see that both diagrams use the lollipop symbol to indicate an implemented interface although the UML 2 version introduces the socket symbol to indicate a required interface. As far as I m concerned the socket symbol is effectively a visual stereotype applied to a dependency, the equivalent textual stereotype is shown on the dependency between the Persistence component and the JDBC interface. Renato Conte - UML: diagrammi di implementazione - 11 / 37 -

12 Components and code signal.h signal.h signal.h {version = 3.5} {version = 4.0} {version = 4.1} «parent» «parent» signal.cpp interp.cpp {version = 4.1} Modeling source code irq.h device.cpp Renato Conte - UML: diagrammi di implementazione - 12 / 37 -

13 Component A component is a physical unit of implementation with welldefined interfaces that is intended to be used as a replaceable part of a system. Well designed components do not depend directly on other components, but rather on interfaces that components support. - The UML Reference Manual component spell-check Dictionary synonyms interfaces Renato Conte - UML: diagrammi di implementazione - 13 / 37 -

14 Component diagram Component diagrams are one of the two kinds of diagrams found in modeling the physical aspects of an object-oriented system. They show the organization and dependencies between a set of components. Use component diagrams to model the static implementation view of a system. This involves modeling the physical things that reside on a node, such as executables, libraries, tables, files, and documents. - The UML User Guide Renato Conte - UML: diagrammi di implementazione - 14 / 37 -

15 Component diagram (captures the physical structure of the implementation) (UML 1.5) Renato Conte - UML: diagrammi di implementazione - 15 / 37 -

16 Component Diagram (UML 1.5) stereotyped component <<database>> Account Transactions Update interface usage dependency component ATM-GUI realization dependency Renato Conte - UML: diagrammi di implementazione - 16 / 37 -

17 component diagram Captures the physical structure of the implementation Built as part of architectural specification Purpose Organize source code Construct an executable release Specify a physical database Developed by architects and programmers Renato Conte - UML: diagrammi di implementazione - 17 / 37 -

18 Component Diagram (UML 1.5) Register.exe Billing.exe Billing System People.dll User Course.dll Course Student Course Professor Course Offering Renato Conte - UML: diagrammi di implementazione - 18 / 37 -

19 Component Diagram (UML 2.0 with port) Port Port Renato Conte - UML: diagrammi di implementazione - 19 / 37 -

20 Component stereotypes «executable» Specifies a component that may be executed on a node «library» Specifies a static or dynamic object library «table» Specifies a component that represents a database table «file» Specifies a component that represents a document containing source code or data «document» Specifies a component that represents a document Renato Conte - UML: diagrammi di implementazione - 20 / 37 -

21 Deployment Diagram (trad.it. diagrammi di messa in opera ) Shows the configuration of run-time processing elements and the software components, processes and objects that live on them Deployment diagrams may be used to show which components may run on which nodes Renato Conte - UML: diagrammi di implementazione - 21 / 37 -

22 Deployment Diagram Application Data Main Database Server Image data NY Office London Office Renato Conte - UML: diagrammi di implementazione - 22 / 37 -

23 <<workstation>> Web server administrator Internet connection <<Web Browser>> Netscape <<protocol>> HTTP <<workstation> > Application client <<protocol>> <<Web server>> HTTP Tomcat <<Web browser>> <<server> Application Server > <<Servlet library>> <<session>> Web Application CGI MS IE <<session>> JDBC OS connection <<Database>> <<DBMS server>> <<session>> Oracle SQL App Database LAN connection <<protocol>> TCP <<workstation>> Database administrator <<DBMS client>> SQL Plus Renato Conte - UML: diagrammi di implementazione - 23 / 37 -

24 Deployment Diagram with components (instances) (UML 1.5) :Client <<browser>> :OpenSourceBrowser videostoreserver :AppServer <<Container>> VideoStoreApplication <<Session>> ShoppingSession <<Entity>> Catalog <<Entity>> ShoppingCart :DBServer <<database>> DB :VideoStore Renato Conte - UML: diagrammi di implementazione - 24 / 37 -

25 Deployment Diagrams Deployment diagrams are one of the two kinds of diagrams found in modeling the physical aspects of an object-oriented system. They show the configuration of run-time processing nodes and the components that live on them. - The UML User Guide Renato Conte - UML: diagrammi di implementazione - 25 / 37 -

26 Components in a deployment diagram Components represent runtime manifestations of code units. Components that do not exist as run-time entities do not appear on these diagrams; they should be shown on component diagrams. A deployment diagram shows instances whereas a component diagram shows the definition of component types themselves. Renato Conte - UML: diagrammi di implementazione - 26 / 37 -

27 Deployment Diagram Renato Conte - UML: diagrammi di implementazione - 27 / 37 -

28 Deployment Diagram Captures the topology of a system s hardware Built as part of architectural specification Purpose: Specify the distribution of components Identify performance bottlenecks Developed by architects, networking engineers, and system engineers Renato Conte - UML: diagrammi di implementazione - 28 / 37 -

29 Nodes A node is a physical element that exists at runtime and represents a computational resource, generally having at least some memory and, often, processing capability. data_server Renato Conte - UML: diagrammi di implementazione - 29 / 37 -

30 Connecting nodes t:terminal Deploys «ethernet» user.exe s:server Deploys dbadmin.exe c:console Deploys «RS-232» admin.exe Renato Conte - UML: diagrammi di implementazione - 30 / 37 -

31 Stereotyped nodes t:terminal Deploys user.exe «ethernet» «RS-232» s:server c:console Renato Conte - UML: diagrammi di implementazione - 31 / 37 -

32 Deployment Diagram with Stereotyped Renato Conte - UML: diagrammi di implementazione - 32 / 37 -

33 Nodes with components (UML 1.5) Components participate in the execution of a system; nodes execute components. AdminServer:HostMachine «database» meetings :Scheduler Reservations Joe smachine:pc { Client } :Planner Deployment diagram of a client-server system Renato Conte - UML: diagrammi di implementazione - 33 / 37 -

34 Deployment Diagram Client / server servers clients console 2..* «processor» caching server Deploys http.exe rting.ex e 4..* «processor» server Deploys dbadmin.ex e tktmstr.exe logexec.exe Renato Conte - UML: diagrammi di implementazione - 34 / 37 -

35 Deployment Diagram :console Note: country servers are reachable to one another via the company s private network :console :regional server :console :Inter net :regional server :country server :regional server :logging server Renato Conte - UML: diagrammi di implementazione - 35 / 37 -

36 Bibliography Grady Booch, James Rumbaugh, Ivar Jacobson. The Unified Modeling Language User Guide, Addison Wesley, (1999). Grady Booch, James Rumbaugh, Ivar Jacobson The Unified Modeling Language Reference Manual, Addison Wesley, (1999). Ivar Jacobson, Grady Booch, James Rumbaugh The Unified Software Development Process, Addison Wesley, (1999). Renato Conte - UML: diagrammi di implementazione - 36 / 37 -

37 Web references OMG UML - Unified Modeling Language: Superstructure version formal/ UML: tool, demo, doc UML: Tutorial e link Renato Conte - UML: diagrammi di implementazione - 37 / 37 -