This is arguably the most critical DBLC phase: making sure that the final product meets user and system requirements. The second phase focuses on the design of the database model that will support company operations and objectives. Boundaries are also imposed by existing hardware and software. The proposed system is also subject to limits known as boundaries, which are external to the system. Will the database design encompass the entire organization, one or more departments within the organization, or one or more functions of a single department? Knowing the scope helps in defining the required data structures, the type and number of entities, the physical size of the database, and so on.
The system’s scope defines the extent of the design according to operational requirements. The designer must recognize the existence of two sets of limits: scope and boundaries.
Will the system share the data with other systems or users?.Will the system interface with other existing or future systems in the company?.What is the proposed system’s initial objective?.
In any case, the database designer must begin to address the following questions: Company end users are often unable to describe precisely the larger scope of company operations or to identify the real problems encountered during company operations.Ī proposed database system must be designed to help solve at least the major problems identified during the problem discovery process. The process of defining problems might initially appear to be unstructured. The designer has both formal and informal sources of information.