modelling class t16: conceptual modelling – architecture image from

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

Upload: annabelle-cooper

Post on 02-Jan-2016

219 views

Category:

Documents


2 download

TRANSCRIPT

ModellingClass T16: Conceptual Modelling – Architecture

Image from http://viz.cwrl.utexas.edu/taxonomy/term/52

Modelação 2

ProgramT01-T02 – Module 1 - Introduction to Systems ModelingT03-T06 – Module 2 - Conceptual Modeling – DomainT07-T11 – Module 3 - Conceptual Modeling – BehaviorT12-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 – MethodologiesT22-T23 – Module 7 - Ontology: Advanced

T24-T25 - Conceptual Modeling – Global Revisions; Exercises, …

System’s Structure and Architecture

System’s Structure and Architecture

UML-

Package Diagrams

5Modelação

Packages…A generic mechanism to group modeling elements

Modelação 6

Packages…

Modelação 7

Packages…

Modelação 8

UML-

Components Diagrams

9Modelação

Components Diagram (UML)

Modelação 10

• 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.

Components Diagram (UML)

Modelação 11

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.0Schema Dependencies (http://docs.oasis-open.org/ubl/prd-UBL-2.0/)

Interfaces in Components

Modelação 12

“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…

• …

Components Diagram (UML)

Modelação 13

• 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.

Components can contain other components…

Modelação 14

wordsmith.dll

wordsmith.dll

Speller.obj

Thesaurus.obj

Speller.obj

Thesaurus.obj

Elements in a Components Diagram

Modelação 15

UML-

Deployment Diagrams

16Modelação

• 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 17Retirado do “Help” do Enterprise Architect

Deployment Diagram

• A hardware node

• A software application

• A specification (document)

• A software component

Modelação 18Retirado do “Help” do Enterprise Architect

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 19Retirado do “Help” do Enterprise Architect

Deployment Diagram (Example)

Deployment Diagram (Example)

Modelação 20

Nodes with components…

NodesA node is a physical resource (computational node, a person, …)

Modelação 21

Nodes and Instances of Nodes

Modelação 22

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 23

Nodes and Components (example)

Modelação 24

Nodes and Components (example)

Modelação 25

Nodes and Components (example)

Modelação 26

Cardinality…

Instances of Nodes and Components (example)

Modelação 27

“connection”: physical connections between nodes…

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