Capture business concepts in a way that machines can process — and humans can understand.
Discover how conceptual reference models can be the foundation for an actionable enterprise and systems architecture.
Well-defined business-centric concepts provide the basis for integrating, federating, mapping between, and sharing information among different systems and communities. Capturing these concepts — in conceptual reference models — helps solve the interoperability crisis many organizations experience, even when different constituents’ vocabulary or “schema” seem unrelated.
Cutter Consortium Senior Consultant Cory Casanave makes a case for conceptual reference models as a foundation for an actionable enterprise and systems architecture during the Achieve an Enterprise Integration Strategy with Conceptual Reference Models webinar.
Enterprise information, services, and processes are the glue between organizations, people, and systems. Yet, many enterprises have no way to understand their systems as a whole; how they interact to deliver business value and their interdependencies. Enterprise and systems architectures provide visibility to and a strategy for the system of systems that supports the enterprise. Key architectural assets include information, services, processes, and rules models — but much of this crucial business and system of systems knowledge is locked-up in technology artifacts specific to a particular application.
At the foundation of an architected approach to systems is the need to understand business terms and concepts independently from the technologies and systems that implement them. Business concepts are captured in a “conceptual reference model” that defines business concepts in a way machines can process, and humans can understand. Such models can then be made part of services, process and rules models for a unified but agile enterprise strategy. Conceptual reference models can be the “glue” between systems, integrating and federating information.
Discover how to design the terms and concepts in conceptual reference models so that they represent the “stuff of the business,” not the stuff of IT, and make sense to business stakeholders.
More on Conceptual Reference Models