Join the Universal Model sourcing community and become a part of this global effort today

Click here if you are interested in becoming a member of the Forum to access the Visible Universal Model Framework.

The Visible Universal Model Framework is built based on the following three premises:

Premise #1:

That most businesses perform a common set of business functions, such as Marketing, Sales, Research, Production, and Purchasing.

Premise #2:

That each business function performs many of the same activities in the management of Contacts, Documents, Contracts, Inventory, Control, Budgeting, Accounting, Hiring, Training, etc.

Premise #3:

That many of the activities act on similar data, e.g. organizations, people, skills, products, services, facilities, locations, assets, liabilities, accounts, documents, etc.

Model as Components:

Although the concept of component-based application development has been around for many years, earlier tools were only suitable for enterprise modeling and did not provide a mechanism for building entire systems from built components or for defining re-useable business objects early in the life cycle. The Visible Universal Framework attempts to fulfill the ideal of total model reuse through familiar objects and patterns. The key to this approach is to consider a model as constructed of reusable components, i.e., object classes. Every model contains common object classes and by raising the level of abstraction, the Visible Universal Model Framework provides a common template about object classes and the relationships within the model. It is fully compatible with commercially available modeling software programs, database design tools and application development products, so the models can immediately be developed into applications.

Why Use a Universal Framework:

By enabling the reuse of the business objects across the various functions of the business system, the Visible Universal Model Framework provides the basic requirement statements, data entities, data relationships and business processes that are often overlooked during the system requirements gathering phase of major projects. These models can be used as complete business objects or selected components that can be assembled to build new systems, such as customer information systems, data warehouses, executive information systems, and decision support systems.