2. Deployment Diagrams Depicts a static view of the run-time configuration of Nodes

3. Why Deployment Diagrams? Explore issues involved with installing your system in production. Explore the dependencies that the system has with other systems that are in production environment Depict major deployment configuration of a business application Depict hardware/network structure of an organization.

4. UML Diagrams

5. Core Package - classifier

6. Deployment diagrams show the configuration of run-time processing elements and the software components, processes, and objects that execute on them. Node

7. Node is a physical Object (can be software/hardware) May represent processing resource, human resource. Node is represented as either type or instance. Node may contain other instances. node : node_type Associations are also shown in the diagram

8. High Level Deployment Diagram

9. Dependency Protocol Components Deployment Diagram

10. Concise Diagram Software

11. Another deployment diagram….

12. Node and components

13. Guidelines Indicate Software Components on Project-Specific Diagrams Focus on Nodes and communication association on Enterprise Level Diagrams. Name Nodes with description terms. Model only critical dependencies between components Apply consistent stereotypes to components,Nodes Apply visual stereotypes to Nodes Indicate communication protocols as stereotypes. Physical nodes should be labeled with the stereotype device

14. While Modeling Deployment Architecture.. Identify scope of the model Consider fundamental technical issues Identify distribution architecture –Fat/Thin client Identify Nodes and their connection Distribute software to the nodes.

15. Exercise Draw deployment diagram for your company’s web application