MISMO Reference Model

1
MISMO Reference Model

• Dave Krause, Dave Hollander, Greg Alvord
• PRIA Winter Conference 2007
• Washington, DC
• March 1, 2007

2
The Vision

• One Model to rule them all, One Model to find
  them, One Model to bring them all, and in the
  darkness bind them .
• ( Sorry JRRT)

3
Motivation for a reference model

• Interoperability across work group boundaries
• Change management
• Cost of standards development

4
Use cases for V3

• Identify security needs of data points
• Multilingual text
• Multi national currency
• Unified structure for Multi-service request
• Unified structure for eClosing

5
Organization of the RM

• Abstract Layer Organized for easier management
  of the standards
• Concrete Layer Models of the transactions
• Deliverables XSD Schemas, Documentation, HTML
  pages, XSLT transforms

6
Implementation of the RM

• Contivo Builder
• Influenced Organization of Models
• Free for use by the WGs

7
Vocabularies

• Vocabulary-driven is a scaleable approach
• Team Aware
• Infrastructure Aware
• XML Aware

Vocabulary
8
XML Aware

• XML Aware means being able to represent all the
  complexity of XML syntax and structure
• Non-XML model limitations restrict interaction
  with other XML based services and standards
• All of the detail of the XML types and document
  structures

9
XML Aware Simplify XML Schema

• Today developers
• Waste effort managing and flattening namespace
  and file structures
• Waste time understanding new schemas because of
  syntax
• Sacrifice compatibility by hand generation and
  testing specific tools
• With Builder
• Packages make namespaces and chameleons easy
• Namespace and file structure easily navigated and
  managed
• Testing simplified by consistently use of XML
  features

10
Infrastructure Aware

• Infrastructure aware means capturing all the
  technical requirements, types and structures used
  in system or service interfaces
• Concrete model defines how data is represented
• Builder uses a concrete model to define the
  vocabularys physical structures

11
Infrastructure Aware Concrete Model

• Constraints
• Cardinality
• Attributes
• Simple data types
• Default values
• Components
• Composition (sequence, choice, all)
• Construction (complex type, group)
• Global elements
• Namespaces

12
Infrastructure Aware Reuse

• Today Reuse is Limited
• by syntax and style
• Files, namespaces, chameleons
• Use of globals and references
• Change xs to xsd
• complicating service and application development
• Starting over is the norm
• With Builder reuse is encouraged
• Schema import and export fixes syntax and style
  differences
• Reuse definitions bydrag-n-copy and drag-n-drop
• Reuse reduces data complexity which accelerates
  development

13
Team Aware

• Team aware means the entire business team can
  collaborate and share design requirements and
  definitions.
• Conceptual domain defines why data is related
• Builder uses a semantic model to define the
  vocabularys conceptual domain

14
Team Aware Dictionary

• Dictionary lists terms in the vocabulary
• Terms define business concept or object
• Properties
• Name
• Comments
• Qualifiers
• Aliases
• Status
• Role
• Operations
• Create
• Modify
• Search
• Examine

15
Team Aware Semantic Model

• Role of the semantic model
• Find and capture the meaning of terms
• Ease navigation through large vocabularies
• Encourage reuse
• Provide implementation templates
• Provide Where Used information
• Semantic Elements
• Terms
• Semantic Components

16
Team Aware From Confusion to Clarity

• Today meaning is obscured
• Semantics obscured by substantial and stylistic
  complexity
• Which details are important?
• Details that why and how are intermixed
• Mixed levels of abstraction
• With Builder
• Dictionary describes concepts
• Components describe business objects
• Separate semantic from structural relationships

17
Team Aware Contivo Manager

• Contivo Manager provides a controlled place for
  vocabularies and related files.

18
Contivo Manager - Features

• Search
• Ability to quickly find any document,
• Specialized search for vocabulary terms and
  components
• File Storage
• Flexible File Types
• Cross-organization span increases need for
  flexibility in supporting all types of files.
• Access Control
• Versioning of all files
• XML Aware
• XML-aware storage of integration and SOA system
  metadata
• XML specific search

19
Summary

• Builder is more than a schema tool
• Supports collaboration between technical
  developers and business analysts
• Supports collections of schemas with a single
  vocabulary model
• Provides vocabulary-wide search and navigation.
• Contivo vocabularies are shared and controlled
  files
• Large size allows for single master
• Vocabulary files can used together
• Control and governance is file based
• Namespaces managed at package level, not per term

20
Tour of the MISMO Vocabulary
21
Team-aware Finding the Right Component

• Show me
• The "Liability Type data point
• anything with "Lifetime Cap in the name
• all terms with "Dwelling Unit" in the definitions
• all terms with of deprecate in the definitions
• Condominium as enumerated value

22
Enumerations

• Enumerations have
• Types
• Literals
• Comments
• Add MoneyMarket to ACH Account type
• Add comment to MoneyMarket literal
• Find all enumeration literals with descriptions

23
Reconciliation

• This process examines all implementations and
  develops a reconciled reference model.
• Examples
• Property
• Borrower

24
Closing Slide

• Dave Krause, MBA/MISMO, 202-557-2772
• DKrause_at_mortgagebankers.org
• Dave Hollander, Contivo, [phone]
• DHollander_at_Contivo.com
• Greg Alvord, Optimal Blue, 972-781-0200
• galvord_at_optimalblue.com