Network computing hardware diagrams

Starting with the transformation to client-server systems from mainframes and later with the advent of e-Business and J2EE, large enterprises moved predominantly into a highly network-based distributed network computing environment, with firewalls and demilitarized zones. Currently, most applications have a web front-end, and looking at the deployment architecture of these applications, it is very common to find three distinct layers in the network landscape: a web presentation layer, a business logic or application layer, and a back-end data store layer. It is a common practice for applications to be deployed and hosted in a shared and common infrastructure environment. Therefore, it becomes highly critical to document the mapping between logical applications and the technology components (for example, servers) that support the application both in the development and production environments. The purpose of the network computing hardware diagram is to show the deployed logical view of logical application components in a distributed network computing environment.

network-computing-hardware-diagramThis diagram shows where application components are deployed, how the computers are networked, and so on

This diagram presents the hardware (servers, workstations) that are interconnected by a network, as well as the technical and application components that are deployed on this hardware.

Technical, architectural components such as web servers are added to the logical components identified in the application architecture.

server-deviceServer device: Represents a hardware platform, that can be connected to other devices, and on which application components are deployed.

workstationWorkstation: Workstations are connected via network links to the IS. Application components can be deployed there.

process-componentProcess application component: A process application component is responsible for a business process execution. It orchestrates the tasks of the process.

entity-componentEntity application component: An entity component is frequently derived from business entities, and is responsible for managing the access to the entity, and its integrity.

utility-componentUtility component: Represents an application component that is frequently reused, and most of the cases bought off the shelf.

interaction-application-componentInteraction application component: Represents the top level components that manage the interaction with elements outside the IS. In most cases, it is a GUI component, such as here a web interface.

DataBaseApplicationComponent32Database application component: This represents a repository. In pure SOA architecture, these elements should not appear. However, for legacy analysis or technology architecture, modeling repositories or repository deployment can be useful.

ApplicationApplication: This application component corresponds to legacy applications, off the shelf products, or can be an assembly of application components.

internal-actor-32Internal actor: An actor that belongs to the enterprise

associationAssociation between two classes: An association has a name, and for each extremity provides the role name and cardinalities (possible number of occurrences) of related elements.

Comments   

Nikita Green
+1 # Nikita Green 2014-01-30 14:38
The topic was short but very helpful thank you Nikita Green
Reply | Reply with quote | Quote
Danny
+2 # Danny 2014-02-19 16:07
Is there any free tool for making these diagrams?
Reply | Reply with quote | Quote
admin
-1 # admin 2014-02-19 16:23
Hi Danny,

You can use Modelio (http://www.modelio.org/downloads/download-modelio.html) with the Togaf Architect module (www.modeliosoft.com/en/modelio-store/modules/modeling-extensions/togaf-architect-open-source.html) and you can download a TOGAF modeling project example (http://www.togaf-modeling.org/downloads-menu/viewcategory/3-togaf-modeling-examples.html). Choose the right example for your Modelio version. Please note that the Modelio open source tool does not include the Requirements. You need the Modelio commercial edition to work with the requirements (Analyst feature) from Modeliosoft (http://www.modeliosoft.com).

Best regards
Reply | Reply with quote | Quote
sabdelrehim
0 # sabdelrehim 2016-08-19 13:21
Quoting admin:
Hi Danny,

You can use Modelio (http://www.modelio.org/downloads/download-modelio.html) with the Togaf Architect module (www.modeliosoft.com/en/modelio-store/modules/modeling-extensions/togaf-architect-open-source.html) and you can download a TOGAF modeling project example (http://www.togaf-modeling.org/downloads-menu/viewcategory/3-togaf-modeling-examples.html). Choose the right example for your Modelio version. Please note that the Modelio open source tool does not include the Requirements. You need the Modelio commercial edition to work with the requirements (Analyst feature) from Modeliosoft (http://www.modeliosoft.com).

Best regards


Hi,

Togaf Architecture Module in Modelio is a commercial one. Is there any free tool?

Thanks
Reply | Reply with quote | Quote
Fariba
0 # Fariba 2014-08-25 10:01
Hi,
Can I have an article or Reference about Togaf application in Healthcare? A full Model with Specified Layers.Please help me, I need it for my Thesis and I have a short time! :sad:
Thanks
Reply | Reply with quote | Quote
sabdelrehim
0 # sabdelrehim 2016-08-19 13:19
Hi,

Togaf Architecture Module in Modelio is a commercial one. Is there any free tool?

Thanks
Reply | Reply with quote | Quote
antonio
0 # antonio 2016-08-22 08:04
Hi,

You can use the Open Source version of Togaf Architect (http://store.modelio.org/92-togaf-architect-open-source.html) which is free but you will not have the requirements. In Modelio, the Requirements are a commercial feature.

Best regards
Reply | Reply with quote | Quote

Add comment


Security code
Refresh

Login

Sign in to use the forum and be informed of the latest news.

Latest comments