Header image
Oxford Architectural Design & Consulting
 
 
(EA)2 User's Guide
Infrastructure Architecture Diagram
This diagram type is used to model the infrastructural elements that support the applications. It uses the (EA)<sup>2</sup> Infrastructure Architecture Toolbox.
(EA)<sup>2</sup> Infrastructure Toolbox
 InfrastructureArchitectureToolbox
Infrastructure Architecture Toolbox
  • Package
  • IT Capability – this is a infrastructural capability that is provided to the applications. Examples include Persistence, Message Routing, Security, and Directory & Authentication Services.
  • Site – a physical location of the enteprise where its IT systems reside.
  • Network Region – a demarcated segment of the network, e.g. DMZ, intranet.
  • Vendor – a supplier of some infrastructural product or service.
(EA)<sup>2</sup> IT Software
  • IT App – an application that realizes IT Capabilities. A Business App may be standalone or be part of a Business System
  • Service – functionality that encapsulates data access or business functionality that is provided to software clients (Service Oriented Architecture).
(EA)<sup>2</sup> IT Hardware
  • Server Model – the configuration of a server that can be purchased from a server vendor. An instance of a Server Model, i.e. a Server, is modeled by creating an instance of a Server Model.
  • Server Frame Model – the configuration of a server that can be purchased from a server vendor. An instance of a Server Frame Model, i.e. a Server, is modeled by creating an instance of a Server Frame Model. Servers may be logically deployed on a Server Frame.
  • PC Model – the configuration of a PC that can be purchased from a PC vendor. An instance of a PC Model, i.e. a Server, is modeled by creating an instance of a PC Model.
  • Network Node Model – generic version of a Server Model to be used for nodes that are not considered Servers or Server Frames.
  • Firewall Model –
  • Router Model –
  • Switch Model –
  • Load Balancer Model –
  • CSU/DSU Model –
  • Device Model – the configuration of a device that can be purchased from a device vendor. An instance of a Device Model, i.e. a Device, is modeled by creating an instance of a Device Model.
  • Network Adapter – a device used by a computer to access the network. This is modeled as a port that is placed on the network node (Server, etc).
  • IP – a Network Adapter that uses the TCP/IP protocol.
  • Port – a TCP/IP port that an application or service "listens on"
(EA)<sup>2</sup> Infrastructure Configurables

These are user modeled classes that define the values that may be given to other model element's tagged values.

  • Device Type – examples: <<Device Type>> Harddrive, <<Device Type>> SAN, <<Device Type>>
  • Network Node Type – examples: <<Network Node Type>> Firewall, <<Network Node Type>> Switch
  • Network Type - <<Network Type>> Satellite, <<Network Type>>T1, <<Network Type>> Ethernet
  • Service Type – See (EA)<sup>2</sup> Application Architecture Toolbox
  • File Type – examples: <<File Type>> CSV, <<File Type>> Fixed Length.
  • Schedule –  used to create the types of schedules that may apply to business processes, activities, ETL Jobs, etc. Examples: <<Schedule>> Monthly, <<Schedule>> Daily, <<Schedule>> Intra-day
More Info
For more information on Infrastructure Architecture go to the Infrastructure Architecture Overview page.
 

All Rights Reserved.