Architector Data Concept Modeller

A data concept model diagram is an invaluable aid for a definition team, and is an extremely useful communication tool, both within the data community and even to a wider business audience. Architector allows definition specialists to create compelling and meaningful concept models directly from definitions. The specialist does not need to understand model theory to visualize their concept definitions. Instead, once they have grasped some basic keywords and definition rules-of-thumb, Architector does the hard work of producing the consistent model diagrams.

Semantic Parser

Architector automatically parses every definition and most semantic relationships between terms are established directly from the term definitions. Architector then draws the corresponding concept model directly from the parsed definitions. This approach has major benefits:

  • The concept models are always an accurate representation of term definitions.
  • Concept models do not need to be manually drawn, and do not need to be re-drawn when a definition changes.
  • The automatic visualization of definitions provides a powerful feedback to the definition team, and helps to establish a common understanding.

Concept Visualisation

Architector can automatically visualize the semantic relationships between concepts. For example, here is a definition of a verb in the glossary:

Component Glossary Def

The parser has recognised three noun-type terms, underlined in green. And also one verb-type association, in blue italics, between two of the terms. In the Structure diagram (concept model) this is displayed as:

Component Glossary Concept

Definition experts and modellers may well argue that this representation is not correct. It may be better to define a noun: Assessment of Risk for a Customer, and to record this in the Customer Risk Assessment. If we agree then all that needs to be done is to change the appropriate definitions, and the model will be automatically updated.

Sectioning the Model

Once a business glossary extends over more than a hundred or so terms the concept model can get too large to take in all at once. So the glossary is divided into vocabularies, ontologies, domains and sections, and the model filtered to display only concepts from one or more divisions. Views of the model can be saved and made either private or public.
A ‘focal concept’ can be selected and the model then displays only concepts related to the focal concept. In addition, a model ‘depth’ can be defined, so that only concepts related by a defined degree of association are displayed.

External Vocabularies

External vocabularies can be loaded into Architector, and linked to the internal vocabulary to create a wider set of business terms. For example, the Financial Institutions Business Ontology (FIBO) can be loaded into Architector from the published Web Ontology Language (OWL) files. Here is a section of FIBO from Architector:

Architector Component - FIBO

Note that when definitions are loaded in from an OWL file, associations are set up based on the semantics inherent in the OWL statements.

Concept Model Features

Architector uses a combination of parsing and explicit associations to understand and automatically draw:

  • Concepts (nouns)
  • Associations (verbs)
  • Data properties
  • Nominalised associations
  • Concept instances
  • Roles
  • Categorisations and Taxonomies
  • Generalisations and specialisations
  • Compositions

Contact us today to request a copy of our Concept Modelling User Guide, or to request a live demo.

Start aligning your data definitioins and concept models today!

Case studies:

Due to the nature of work we undertake, and the types of clients we typically help, we do not post details of case studies online. Please contact us for more details.