In systems implementation planning, when should database preparation begin relative to key prerequisites such as selecting the computer platform, organizing MIS staff, and readying physical facilities?

Introduction / Context:
In information systems implementation, database preparation is a critical activity that depends on foundational readiness. Attempting to design, configure, and load a database before key prerequisites are fulfilled leads to rework and risk. The question tests understanding of proper sequencing in implementation planning.

Given Data / Assumptions:

• The target computer hardware and platform must be known (operating system, storage layout, DBMS edition).
• Management information systems (MIS) staff must be available and organized to own and operate the database.
• Physical facilities (server room power, cooling, racks, network, security) must be ready.

Concept / Approach:
Sound implementation sequencing ensures environment readiness before data activities. Hardware choice affects DBMS features, storage configuration, and performance tuning. Staff capacity affects administration and backup routines. Facilities determine reliability and security. Only when these are confirmed should database preparation begin, minimizing change churn.

Step-by-Step Solution:

Verification / Alternative check:
If any prerequisite changes (for example, a different OS or storage), earlier DB work becomes invalid. Therefore the safe point to begin is after all prerequisites are stable.

Why Other Options Are Wrong:

Common Pitfalls:
Beginning schema work on a temporary server, skipping capacity planning, and overlooking backup infrastructure lead to delays and rollbacks.

Final Answer:
After all of the above prerequisites are in place.