MEG0015 Data Modeling
Content
Guidelines
Data modeling is the analysis of data objects that are used in a business process and the identification of the relationships among these data objects. Data modeling is a first step in the development of new MISMO XML standards. Several differing approaches or methodologies for data modeling exist. The data model visually describes how all the data items are related to each other. The data modeling effort helps to identify the data structures that are used in common by many mortgage processes and helps form linkages between the structures. The model simultaneously helps identify the structures that have common data. It also becomes the basis for organizing the XML Document Type Definition (DTD) or XML schema that will be used in the future.
At a minimum, a simple approach to creating a data model that allows for the graphic representation of each individual data item, with a descriptive name, and an expression of relationships between each of these data items with words is required. From such a total picture, a set of context areas within the business process shall be identified and defined. More sophisticated modeling techniques such as Unified Modeling Language (UML) may also be used.
Version .01
12/27/2006
| Release History |
| Date |
Release |
Comments |
| 12/27/2006 |
.01 |
Initial Version |
| 12/15/2008 |
.01 |
Updated contents of Disclaimer tab. |
| Changes Since Last Version |
| See above |
| Known Issues |
| Additional Review Required |
| Contacts |
| Name |
Organization |
Contact Details |
| <ENTER NAME> |
MISMO |
<ENTER CONTACT DETAILS> |
| Metadata |
| Element |
Description |
| Title |
MEG0015 Data Modeline |
| Identifier |
<SHOULD HAVE LINK FOR PUBLIC> |
| Subject |
MISMO Process MEG0015 Data Modeling |
| Description |
Describe process of data modeling |
| Type |
MISMO Process |
| Source |
<ENTER SOURCE HERE> |
| Relation |
|
| Coverage |
<ENTER COVERAGE HERE> |
| Creator |
<ENTER CREATOR HERE> |
| Publisher |
MISMO |
| Contributor |
Applies equally well to Version 2.x and 3.x |
| Rights |
Copyright of MISMO. All rights reserved. |
| Date Created |
12/27/2006 1:00:00 PM |
| Date Modifiend |
|
| Format |
Text |
| Language |
En |
References
Purpose
1. Introduction
1.1 Context
1.2 Purpose
1.3 Scope
1.4 Audience
1.5 Terminology
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119
. See «add reference to MISMO glossary for terminology used in this MEG».
1.6 Document Status
The information supplied in this document reflects the MISMO interoperability principles at the time of writing. It is a living document, which will be updated as required to reflect the evolving nature of XML technologies and service requirements identified by MISO constituency. Comments on this document should be sent to the MISMO designated contact identified in the document preface.
2. Rationale for this MEG
Comments
None.
Disclaimer
Disclaimer. MISMO® accepts no liability for the accuracy, adequacy, or completeness of the information contained in this MISMO Engineering Guideline (MEG).
Circulation. Material in this MEG may be reproduced free of charge without obtaining explicit permission from MISMO, provided that the source is acknowledged, the document title given, and the material used in context.
Copyright 2008 MISMO. All material in this MEG is the property of MISMO. All rights reserved.