1 / 28

Modelling

Modelling. Class T16: Conceptual Modelling – Architecture. Image from http://viz.cwrl.utexas.edu/taxonomy/term/52. Program. T01-T02 – Module 1 - Introduction to Systems Modeling T03-T06 – Module 2 - Conceptual Modeling – Domain T07-T11 – Module 3 - Conceptual Modeling – Behavior

oded
Download Presentation

Modelling

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Modelling Class T16: Conceptual Modelling – Architecture Image from http://viz.cwrl.utexas.edu/taxonomy/term/52

  2. Program T01-T02 – Module 1 - Introduction to Systems Modeling T03-T06 – Module 2 - Conceptual Modeling – Domain T07-T11 – Module 3 - Conceptual Modeling – Behavior T12-T15 – Module 4 - Ontology T16 – Module 5 – Conceptual Modeling – Architecture (UML) T17 – … support for the project… T18 – Module 5 – Conceptual Modeling – Architecture (UML; SysML) T19 – …overview… T20-T21 – Module 6 - Conceptual Modeling – Methodologies T22-T23 – Module 7 - Ontology: Advanced T24-T25 - Conceptual Modeling – Global Revisions; Exercises, … Modelação

  3. System’s Structure and Architecture

  4. System’s Structure and Architecture

  5. UML-Package Diagrams Modelação

  6. Packages… A generic mechanism to group modeling elements Modelação

  7. Packages… Modelação

  8. Packages… Modelação

  9. UML-Components Diagrams Modelação

  10. Components Diagram (UML) • A Component Diagram illustrates the pieces of software, embedded controllers and such that make up a system, and their organization and dependencies. • A Component Diagram has a higher level of abstraction than a Class diagram; usually a component is implemented by one or more Classes (or Objects) at runtime. They are building blocks, built up so that eventually a component can encompass a large portion of a system. Modelação

  11. Components Diagram (UML) • The dependencies among software systems’ components can be expressed in components diagrams: • Source code • Binary code • Executable code • Business processes… • Documents… • … • Example: UBL - Universal Business Language 2.0 • Schema Dependencies (http://docs.oasis-open.org/ubl/prd-UBL-2.0/) Modelação

  12. Interfaces in Components • “Interfaces” are important to support replacement and re-usage... • A component initially designed for one specific system can be reused in another system… • A component can be replaced by other component… • … Modelação

  13. Components Diagram (UML) • Assembly connectors link the provided interfaces supplied by Product and Customer to the required interfaces specified by Order. • A Dependency relationship maps a customer's associated account details to the required interface Payment, indicated by Order. Modelação

  14. Components can contain other components… wordsmith.dll Speller.obj Thesaurus.obj  Speller.obj wordsmith.dll Thesaurus.obj Modelação

  15. Elements in a Components Diagram Modelação

  16. UML-Deployment Diagrams Modelação

  17. Deployment Diagram • A Deployment diagram shows how and where the system is to be deployed; that is, its execution architecture. • Hardware devices, processors and software execution environments (system Artifacts) are reflected as Nodes, and the internal construction can be depicted by embedding or nesting Nodes. • As Artifacts are allocated to Nodes to model the system's deployment, the allocation is guided by the use of deployment specifications. Modelação Retirado do “Help” do Enterprise Architect

  18. Deployment Diagram (example) • A hardware node • A software application • A specification (document) • A software component Modelação Retirado do “Help” do Enterprise Architect

  19. Deployment Diagram (Example) • Two Nodes have a TCP/IP communication path indicated. • Deployment relationships indicate the deployment of Artifacts. Furthermore, a deployment spec defines the process of deployment for the networkScanner Artifact. • The Manifestation relationships reveal the physical implementation of components ReposCustomer and ReposInternalRecords. Modelação Retirado do “Help” do Enterprise Architect

  20. Deployment Diagram (Example) Nodes with components… Modelação

  21. Nodes A node is a physical resource (computational node, a person, …) Modelação

  22. Nodes and Instances of Nodes Modelação

  23. Nodes and Components • Both can be part of generalizations, dependencies or associations… • Both can have instances… • But • Components are things that take part in the execution of a system • While • Nodes are things that execute components • Components represent groups of logical elements • While • Nodes represent the physical deployment of components Modelação

  24. Nodes and Components (example) Modelação

  25. Nodes and Components (example) Modelação

  26. Nodes and Components (example) Cardinality… Modelação

  27. Instances of Nodes and Components (example) “connection”: physical connections between nodes… Modelação

  28. Modelação Image from http://blog.miragestudio7.com/wp-content/uploads2/2007/07/speedbump_comic_when_architects_propose_model_funny.gif

More Related