Getting Started with InfoSphere Data Architect

More documents

Recommendations

Info

66 Getting started with InfoSphere Data Architect • Prime word: A word that represents the business concept about which data is being collected. Prime words are nouns that describe the subject area of the data. For example: LOAN, EMPLOYEE • Class word: A word that identifies a distinct category or classification of data. For example: RATE, NAME • Modifier: A word that further qualifies or distinguishes the prime and class words. It helps make the object name clear and unique, and it can help restrict the meaning of the class and prime words. For example: NEXT, FIRST You can use IBM InfoSphere Data Architect to help you define these semantic rules or naming standards. You will learn more about how to specify some of these options for future data modeling projects in Section 3.4, Working with naming standards. To enforce the naming conventions that are specified in a glossary model, the glossary model must be referenced by the project that contains the models to be analyzed. To reference an existing glossary model in a project, perform the following steps: Note: You do not need to perform these steps, since you are creating a glossary model that the project will reference in an upcoming section. This step is only necessary if you did not add the glossary model to the project when you created it, or if you imported a glossary model from another product. 1. Select the data design project in the Data Project Explorer. The properties for the data design project display in the Properties view. 2. Open the Naming Standard tab, then click the Add button. The File Selection window opens. 3. Expand the data design project, and then select the glossary model from the list of files, as shown in Figure 3.13.
Chapter 3 – Logical Data Modeling 67 Figure 3.13 – Selecting a glossary model The glossary model is referenced by the data design project. 3.3.1 Best practices for naming standards and glossary models Here are some best practices you can keep in mind when designing your naming standards: • Choose the singular form of the word for entity names. • Do not use numbers for the first character of an entity name. • Choose short, unambiguous names, and try to use no more than one or two words. When creating glossary models, consider the following best practices: • Create a separate enterprise standard project that contains any glossary or domain model that should be shared throughout the organization. You will learn more about domain models in Chapter 4.
Page 3 and 4:
G E T T I N G S T A R T E D W I T H
Page 5 and 6:
5 Notices This information was deve
Page 7:
7 Trademarks IBM, the IBM logo, and
Page 10 and 11:
10 Getting started with InfoSphere
Page 12 and 13:
Page 14 and 15:
Page 17 and 18: 17 About the Authors Erin Wilson is
Page 19 and 20: 19 Contributors The following peopl
Page 21: PART I - OVERVIEW AND SETUP 21
Page 24 and 25: 24 Getting started with InfoSphere
Page 43 and 44: Chapter 2 - Data Modeling Overview
Page 45 and 46: Chapter 2 - Data Modeling Overview
Page 47: PART II - MODELING YOUR DATA 47
Page 107 and 108: Chapter 6 - Generating Reports, Imp
Page 117 and 118:
Chapter 6 - Generating Reports, Imp
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Let's import the data model into th
Page 127:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 143 and 144:
Chapter 8 - Model Mapping and Disco
Page 145 and 146:
8.1.2 Further managing naming stand
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157:
Page 160 and 161:
Page 162 and 163:
Page 165 and 166:
Chapter 10 - The Data Management Li
Page 167 and 168:
Page 169:
Page 172 and 173:
http://publib.boulder.ibm.com/infoc
Page 174:
Getting started with InfoSphere Dat
show all

Getting Started with InfoSphere Data Architect

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?