Knowing the benefits of using logical or conceptual data models, how should organizations use logical models to achieve optimal results? The most significant influence on properly using logical models is the "approach" and "attitude" towards modeling.
Approach refers to how you work with and create your model. Do you model a business or do you simply build a database? Are you considering the users' needs or the programmers' needs. Attitude is reflected by your objectives and how you use the model. Do you want to understand the business and design an application with a future, or do you want a database that you can justify right away?
For one organization, an optimal result is an implemented database that can most easily grow and adapt to meet the changing business needs. For another organization, an optimal result is an implemented database that delivers the best possible execution speed, no matter what the cost is in the future. For most organizations, the optimal result lies somewhere between these extremes.
A C-Thinker will use a model to document the business and its rules. C-Thinkers use words like "ENTITY", "ATTRIBUTE", and "RELATIONSHIP". Their model reflects the business and can be used by the users to verify, test, and alter the organization of data. When working, they are said to be using C-Think techniques.
An I-Thinker will use a model to document a database design that they have already planned. I-Thinkers use words like "FILE", "HEADER", "DETAIL", "FIELD", and "RECORD". Their model is implementation oriented and designed for programmers. When working, they are said to be using I-Think techniques.
Most developers begin as I-Thinkers. By understanding the nature and role of the C-Thinker, and by using C-Think techniques, they begin to see things differently. During the process of evolution, an I-Thinker will become a Dual C/I-Thinker. Eventually the C-Thinker role should grow and develop until it takes over and the Architect becomes a New World C-Thinker.
