Correct option is A
The
database design process generally begins with
requirements collection and analysis, where the required data, relationships, constraints and operations of the organization are identified.
Based on these requirements, a
conceptual schema is created, commonly using an Entity–Relationship (ER) model to represent entities, attributes and relationships independently of implementation details.
The conceptual design is then transformed through
data model mapping into a logical schema suitable for the selected database model, such as the relational model. Finally,
physical design determines how the logical schema will actually be stored and accessed, including storage structures and access paths.
Information Booster
1.
Requirements Collection and Analysis (C)
· This is the
starting point of database design.
· Requirements are collected from users, application specifications, business rules, and existing systems.
· It identifies required
data items, relationships, constraints, transactions and operations.
· The output is a clear specification of what the database must support.
2.
Conceptual Schema Creation (A)
· The requirements are represented at a
high level, independent of a particular DBMS.
· The
ER model is commonly used during this stage.
· It identifies entities, attributes, relationships, and relevant constraints.
· Example: In a university database, STUDENT, COURSE and ENROLLMENT can be modeled as conceptual components.
3.
Data Model Mapping (B)
· The conceptual schema is transformed into a schema using the
data model selected for implementation.
· In a relational database, entities and relationships are mapped into
relations (tables).
· Attributes become columns, while appropriate keys and integrity constraints are identified.
· This stage bridges the conceptual representation and the logical database structure.
4.
Physical Design (D)
· Physical design determines
how the database will be stored and accessed.
· Decisions may involve file organization, indexes, storage structures, partitioning and access paths.
· The objective is to achieve suitable
performance, storage efficiency and maintainability.
· Physical design is therefore dependent on the logical schema produced earlier.
Additional Knowledge
·
Option (b) is incorrect: It places
data model mapping before conceptual schema creation. The conceptual representation must first be developed from the collected requirements.
·
Option (c) is incorrect: It starts by creating the conceptual schema before understanding the system's requirements. Requirements analysis should precede conceptual modeling.
·
Option (d) is incorrect: Although it begins with conceptual schema creation, it incorrectly places
requirements collection after it.
·
Important distinction:
Conceptual design focuses on
what data and relationships are required, whereas
physical design focuses on
how that data will be stored and accessed efficiently.
·
Sequence to remember:
Requirements → Conceptual → Logical/Mapping → Physical.

