newerLogo3

3.0 Solution Engineering

The engineered solution is founded on collections of highly engineered data models within the Metabase System.

  •   Data Element Models
  •   Concepts Data Model
  •   Database Logical Model
  •   Database Physical Model

Data Element Model. Data elements consist of a number of tables for storing data elements including the data elements encapsulating business environment of Concepts, Conceptual Value Domain, Data Element Concept and Data Element Classifications. Each data element is supplemented with Value Domains. Semantic and Data Use Modifiers and data that can be assigned to each data element concept and data element to modify the data element’s meaning and use. There is a one-to-many relationship between data element and attribute.

Concepts Data Model. Concept Data Models consist of number of Metabase System tables for storing subjects, entities, attributes, and inter-entity relationships. Relationships can interrelate entities within multiple subjects. Every entity attribute should map to its parent data element. Semantic and data use modifiers can be assigned to entity-attributes. There is a one-to-many relationship between attribute and column, and there is also the ability for an entity to be semantically deployed across many tables, and multiple entities to be deployed within one table.

Database Logical Model. Database Logical Models consist of number of Metabase System tables for storing the data structure components: schema, tables, columns, and inter-table relationships. Relationships are restricted to tables within a single schema. Every table column should map to its parent attribute. Semantic and data use modifiers can be assigned to every table column. There is a one-to-many relationship between column and DBMS column, and there is also the ability for one table to be employed across many DBMS tables, and multiple tables to be employed within one DBMS table.

Database Physical Model. Operational Database Models consist of number of Metabase System tables for storing: DBMS schema, DBMS tables, DBMS columns, and inter-table DBMS relationships. Relationships are restricted to DBMS tables within a single DBMS schema.

DBMS Relationships are restricted to DBMS tables within a single DBMS schema. Each Database Physical Model can address multiple Implemented Database Models. There is a backwards relationship from every DBMS column to its parent column. As stated above, there is also the ability for one DBMS table to be deployed from multiple tables, and multiple DBMS tables to be deployed from one table.

For Sales and Corporate: 1-301-249-1142 Whitemarsh@Wiscorp.com

Whitemarsh Information Systems Corporation

2008 Althea Lane Bowie, Maryland 20716 USA

Copyright 1981 - 2016, Whitemarsh Information Systems Corporation
Proprietary Data, All rights Reserved