In the complex world of Enterprise Architecture, the Technology Layer serves as the physical foundation upon which all software and business functions rest. It provides the most basic support capabilities, including computing, storage, and network communication infrastructure services. This tutorial will guide you through the concepts illustrated in the provided architecture diagram, demonstrating how to model these relationships effectively using Visual Paradigm and the ArchiMate standard.

Understanding the Core Components

The diagram presents a classic scenario where software applications (like CICS and DBMS) run on physical hardware, connected via a network to store data. Let’s break down the specific elements and their roles:

• Mainframe: This is a physical Node. In ArchiMate, a Node represents physical hardware or software resources. It is the container for our software components.
• CICS & DBMS: These are instances of System Software. CICS (Customer Information Control System) is a transaction processing monitor, and DBMS (Database Management System) manages data. They are deployed onto the Mainframe Node.
• NAS File Server: Another Node acting as storage, distinct from the mainframe’s internal storage.
• LAN: This represents a Communication Network. It facilitates the data flow between the Mainframe and the File Server.
• Data Files: An Artifact. In ArchiMate, an Artifact is a piece of information, such as a file, document, or data structure, that resides on a node.

Decoding the Relationships

The power of ArchiMate lies in the relationships connecting these elements. The diagram highlights several critical associations:

1. Deployment and Access

Observe the solid line connecting the Mainframe to the LAN. This is an Association. It indicates that the Mainframe is connected to the LAN, enabling communication. Similarly, the NAS File Server is associated with the LAN, showing how it connects to the network infrastructure.

2. Realization and Services

The diagram illustrates the abstraction of physical resources into services:

• Database Service: This is an interface provided by the system. The dashed arrow pointing from the Mainframe to the Database Service is labeled Realization. This means the Mainframe (specifically the software running on it) realizes or implements the Database Service.
• File Access Service: Similarly, the NAS File Server realizes the File Access Service, allowing users to access files over the network.

3. Artifact Storage

Notice the relationship between the NAS File Server and the Data Files. The dashed line labeled Artifact signifies that the Data Files are physically stored on the NAS File Server. This distinguishes the physical storage medium (Node) from the logical information it holds (Artifact).

Modeling in Visual Paradigm

To recreate this architecture in Visual Paradigm, you would typically drag and drop elements from the ArchiMate palette onto the canvas. Here is a logical breakdown of the steps you would take:

1. Create Nodes: Drag a Node onto the diagram and label it “Mainframe”. Duplicate this to create the “NAS File Server”.
2. Add System Software: Drag a System Software element and place it inside the Mainframe node.
3. Define Services: Create a Service element for “Database Service”. Use a dashed line to connect the Mainframe to this service, selecting the Realization relationship.
4. Connect the Network: Add a Communication Network element (LAN). Connect the Mainframe and NAS File Server to it using Association lines.
5. Add Artifacts: Finally, add an Artifact element for “Data Files” and connect it to the NAS File Server using the Artifact relationship.

Conclusion

By understanding these fundamental building blocks—Nodes, System Software, Services, and Artifacts—you can effectively model the physical infrastructure of your enterprise. This clear separation of concerns allows architects to analyze how changes in the physical layer (like upgrading a server) impact the services delivered to the business.