Skip to content

Information Modeling Summary

This lesson summarizes the key concepts of information modeling as applied in the STEP and AP 210 context.

What is Information Modeling?

Information modeling is the process of defining the structure, relationships, and constraints of data in a domain. An information model is a formal specification that:

  • Defines the types of objects that exist in the domain

  • Specifies their attributes and relationships

  • Enforces constraints to ensure data validity

  • Provides a shared vocabulary for communication

The EXPRESS Modeling Approach

EXPRESS follows an entity-attribute approach to information modeling:

  • Each real-world concept maps to an entity

  • Properties of concepts map to attributes

  • Relationships between concepts use references (entity-valued attributes)

  • Constraints enforce business rules using WHERE rules and global rules

  • Complex types are built using enumerations, selects, and aggregations

Abstract vs. Concrete Models

In the STEP framework, there are two levels of modeling:

  • Application Reference Model (ARM) - An abstract model of the application domain, using domain-specific terminology

  • Application Interpreted Model (AIM/MIM) - A concrete model mapped to the STEP integrated resources, using generic resource constructs

AP 210 defines both. The ARM describes electronic design concepts; the MIM maps them to STEP resource entities for data exchange.

Mapping Tables

The connection between ARM and AIM is documented in mapping tables that specify:

  • Which ARM entity maps to which AIM entity

  • How ARM attributes map to AIM attributes

  • Any constraints needed to specialize the generic AIM entities for the AP 210 domain

Model Quality

A good information model should be:

  • Complete - Covers all required concepts in the domain

  • Unambiguous - Each concept has a single, clear interpretation

  • Consistent - No contradictions between definitions

  • Minimal - No redundant definitions

  • Extensible - Can be extended for future requirements