The primary goal of logical data modeling is to meet the needs of your users’ reporting requirements. Developing such a model involves the following:
|•||Identification of user requirements|
|•||Design of solutions|
|•||Evaluation of those solutions|
Logical data modeling is a reiterative process, where additional questions and concerns arise with each draft of the logical data model.
Your user community can consist of people with vastly different requirements. For example, company executives are typically interested in overall trends and may want reports showing data aggregated across the company and over a long period of time. Lower-level managers are typically more interested in data about their particular areas of responsibility. These managers may want reports about their specific region or store over short-and long-terms.
When creating the logical data model, you must consider all the potential users and how to accommodate their varied requirements. In some cases, lack of data in the source systems can limit user requirements. Sometimes, to satisfy user requirements, you can derive additional data not found in the source systems, as explained in Existing source systems.
User requirements are an important part of the initial project design process. However, additional user requirements can be encountered after deploying a project as users encounter areas for enhancement. In some cases, new user requirements can require you to modify the logical data model to better support the type of analysis and the retrieval of data that users demand.