• Imagine...

  A virtual space where your project team members - enterprise and business architects, managers, systems analysts, and developers can view and discuss all aspects of a project?

  Now you can integrate Discussion Threads into your project framework so everyone can view, discuss, and address the interrogatories of "Who", "What", "Where", "When", "Why" and "How".

The Zachman Framework serves as a comprehensive logical structure for classifying and organizing the complex descriptive representations of an enterprise. It utilizes a matrix that intersects six fundamental interrogatives—what, how, where, who, when, and why—with different stakeholder perspectives, ranging from high-level planners to detailed implementers.

By mapping these dimensions, the model provides a standardized language for viewing a business through various lenses, such as data, process, and motivation. Ultimately, this schema functions as a blueprint for enterprise architecture,  ensuring that every technical detail aligns with the broader strategic goals of the organization.

Structured Perspectives (The Zachman Framework)

These blueprints also illustrate business perspectives through the Zachman Framework, which categorizes views based on the stakeholder's role in the enterprise:

• Planner (Scope): Focuses on a high-level "List of Things" important to the business (Contextual).
• Owner (Enterprise Model): Views entities as "Business Entities" and "Relationships" (Conceptual).
• Designer (System Model): Views the data as a "Logical Data Model" with "Data Entities" and "Relationships" (Logical).
• Builder (Technology Model): Sees the model as "Physical Data Models" involving tables, segments, and keys (Physical).

The Universal Model Framework offers a ready-made, component-based approach to data modeling. It uses reusable patterns and core “kernel” entities that apply to nearly every business, covering almost fifty key subject areas. This gives your teams a standard data structure to start from, so you can design faster and with more consistency instead of reinventing the wheel.

Alongside this, the Zachman Framework provides a structured matrix for viewing your organization from multiple angles—such as data, functions, and locations—across different stakeholder perspectives, from executive planners to technical implementers.

Together, these frameworks help you turn complex business requirements into integrated, interoperable information systems. The result is a shift away from building one-off solutions toward a model of logical reuse, better alignment to strategy, and greater efficiency across the enterprise. 

Let's look at an Example.

 In the Universal Model Framework, sales and manufacturing perspectives differ because they focus on distinct characteristics—specifically different attributes and associations—of the same underlying entity.

You might ask ... How do sales and manufacturing perspectives differ for a single entity?

While both departments may interact with the same data, such as a specific "PRODUCT" or "ASSET," their functional needs change how that entity is modeled:

• Sales Perspective: This view focuses on attributes and relationships relevant to revenue and customer interaction. It would likely emphasize data points such as customer contact information, contract management, market offerings, and pricing structures.
• Manufacturing Perspective: This view prioritizes the physical creation and storage of the item. It would focus on inventory control, facility locations, resource requirements, and production specifications.

Key Differences in Modeling using the Universal Model Framework

• Contextual Relationships: The framework uses the same "kernel" entity (the core object) for both, but the perspective defines the context through its relationships. For example, the same "PERSON" entity might be viewed as a "Customer" by Sales and a "Production Worker" by Manufacturing.
• Levels of Abstraction: Depending on the perspective, a modeler might use kernel extension to add specific details required by manufacturing (like machine tolerances) that are irrelevant to sales. Conversely, they might use kernel combination if a particular perspective finds the universal model's standard details too granular for their needs.
• Functional Use: In manufacturing, an entity like an "ASSET" is viewed as a resource available to perform a function. In a sales-adjacent view, that same asset might be classified as a business solution designed to meet a specific customer need.

How Perspectives Alter Model Views

• Different Attributes and Associations: An entity viewed from a sales perspective will have different attributes and associations than the same entity viewed from a manufacturing perspective. For example, sales may focus on customer contact and contract management, while manufacturing focuses on inventory and production capacity.
• Contextual Meaning: Perspectives help define the context of an object. For instance, while an organization might deal with "Employees," "Managers," and "Customers," the UMF abstracts these into a universal "PERSON" object class. The specific perspective (e.g., HR vs. Sales) defines the relationship and context that the "PERSON" holds within the "ORGANIZATION".
• Granularity of Detail: Depending on the business need, a perspective might require kernel extension—adding specific entities, attributes, or relationships to a universal component—or kernel combination, where multiple object classes are merged because a specific business view finds them too detailed.

Functional vs. Object Views

The Universal Model Framework facilitates these changing perspectives by offering two primary levels of views:

1. Object-View: Provides a "big picture" perspective showing how various object classes relate across the entire enterprise.
2. Object-Class-View: Focuses on a single "kernel" entity and its closely coupled properties, allowing a deep dive into a specific business subject area (like ASSET or PERSON).

Benefits of combining the two?

Business perspectives function as an additional frame of reference that determines the level of abstraction and the specific characteristics of an object class. Because different business functions interact with the same data in unique ways, a single entity can look very different depending on who is viewing it. Addressing this issue enables us to:

Gain an overarching view of project strategy and context.

See the relationship between your project strategy and project goals and objectives.

Track project business requirements across systems and applications.

Understand the business context before making decisions. 

See how Visible's new release of its Advantage platform, featuring Discussion Threads for team collaboration, enables your project team to view, discuss, and address all aspects of your project from its planning through implementation. All you need to do is fill in the form below and we will send you a free software license and instance of the Universal Model Framework for your industry.