Developing the Logical Model
Go Up to Using ER/Studio Data Architect
A logical model is developed before the physical model. It addresses the business and functional requirements of systems development. The logical design allows you to determine the organization of the data that you need to store in a database before you create the database; it serves as a blueprint.
To design the most effective data model possible, you should focus on the logical design before developing the physical design. Both the logical and physical design processes are complex so it is best to separate rather than to mix the two. A sound logical design should streamline the physical design process by clearly defining data structures and the relationships between them.
A data model can be extremely useful for other things besides creating databases, though that is generally its primary purpose. In systems development, the goal is to create an effective database application that can support some or all of your enterprise. However, a data model of your business can help you define operational aspects of your business that you might otherwise overlook. Also, a well-defined data model that accurately represents your business can be helpful in orienting employees to goals and operations. The data model can also serve as an invaluable communications tool for both internal and external constituents.
For more information, see the following topics:
- Logical Design Concepts
- Creating and Editing Entities and Tables
- Creating and Editing Keys
- Creating and Editing Business Data Objects
- Associate Similar Objects Using User-Defined Mappings
- Working with Relationships
- Working with Universal Mappings
- Validating the Model
- Creating and Editing Database Users
- Creating and Editing Database Roles
- Creating and Editing SQL Procedures
- Customizing Datatype Mappings