Contents   Introduction   Concepts   User Help   Modeler Help   Browser Help
Administrator Help   Developer Help    Utility Help   Visio   Graphical Modeler

Tips on Building and Sharing a Domain Meta Model ("MetaSet")

1. Model the concepts using an object oriented class modeling technique, but limiting inheritance - This will give you the Types to set up in EVA Netmodeler
2. Define the relationships between the classes
3. Decide if some relationships need Info Nodes
4. Define the attributes of the classes
5. Choose data types for the attributes
6. Create or choose an existing EVA Netmodeler Domain to contain the types you will create. The domain is created simply as an instance of Archi Domain
7. Define types in EVA Netmodeler while logged on with Administrator privileges. Ensure your types are associated with the right domain when you create them. It is also a good idea to document your types as you define them. The documentation should provide a concise definition of the concept that each represents and a few examples of the things that could be instances.
8. Test the new types
9. Grant security access to users/groups who should be able to work with these types
1. If you need new users/groups, see if they are similar to ones you already have - cloning and modifying is much easier than setting up from scratch
2. Try to come up with clean cohesive groupings, which can be combined to yield the unique permutations you need for actual groups/people e.g. combine Business Architect with Program Manager for an individual who performs both roles (he can be a member of both groups)
3. Override or extend the group inherited rights at the individual user level where necessary e.g. All "Manager" groups will have access to a common set of Business Architecture information, but only the Finance Manager will additionally have access to Budget items
10. Define an export package for the MetaSet listing all included types
11. When exporting a MetaSet, include:
1. Meta Data for all types
2. Images and support files e.g. templates (these will be output to the designated directory during the export process)
3. Instances for:
1. Security profiles for typical users
2. Any required system settings
3. Any standard category schemes e.g. Deliverable Types etc.
4. Any required lookups for standard values