I never sat down and learned all the contexts under Unified Modeling Language (UML) classes. This is why I built the Technology Business Meta Model Schematic View which is a “Keep It Simple Stupid” approach. It still applies the principals of UML while simplifying the options for relations of objects. I know that when building proper ULM diagrams, we must define Generalization, Association, Multiplicity, Aggregation, and Properties. Do we really need to know all those details on how to visual represent them? Microsoft Visio 2013 Diagram of a Meta Model schematic. Metamodel View for Infrastructure.

1. BusinessTechnology and Information
Datacenter
Server
Network DeviceClient Device
Network
Location
Software
Product Version
IT Standard
Logical
Application
Logical
Technology
Business
Capability
Database / Data
Store
uses
Hosted inHosted in
Hosted in
uses
Hosted in
realizes
realizes
realizes
uses
uses
uses
Uses & realizes
Software
Product
realizes
uses
uses
uses
Composed of