Information Model Creation Issues
When you insert an information model into the Repository, you have the following choices and decisions to make:
-
How much of the tool information will you store in the Repository database and how much will you store in other files?
-
For each class you define in your information model, what Automation server will create instances of that class?
-
Can you tune the database schema to improve performance?
-
Should you create a new information model or extend an existing one?
-
Should you assign object identifiers, or let the Repository do this for you?
-
How will your information model accommodate movement from one object to another?
The following sections discuss each of these: