Difficulty: Easy
Correct Answer: Implementation planning
Explanation:
Introduction / Context:
Implementation in the systems development life cycle (SDLC) is the set of activities that moves a tested solution into real use. The very first action must create clarity about scope, tasks, responsibilities, and risk handling so that every downstream activity stays coordinated and controlled.
Given Data / Assumptions:
Concept / Approach:
Implementation planning defines what to do, who will do it, when, and how to manage cutover, training, data conversion, communications, facilities, procurement, and contingency plans. Without a plan, later steps become ad hoc and risky.
Step-by-Step Solution:
1) Identify implementation objectives (reliability, minimal downtime, user readiness).2) Break down tasks: training, file conversion, environment prep, rollout sequencing.3) Assign roles, responsibilities, and dates.4) Define change management, communication, help desk, and fallback strategy.5) Approve the plan and communicate it to stakeholders.
Verification / Alternative check:
If one attempted to start with hardware selection or announcements, those actions would lack context and sequencing. A validated plan must logically precede procurement, facility prep, and public communications.
Why Other Options Are Wrong:
Select the computer: procurement is a later execution detail governed by the plan.Announce the implementation project: communications timing and content are part of the plan.Prepare physical facilities: facility work is scheduled by the plan.None of the above: incorrect because Implementation planning is correct.
Common Pitfalls:
Jumping into procurement or training without an integrated plan, ignoring rollback provisions, or failing to assign owners leads to delays and scope creep.
Final Answer:
Implementation planning
Discussion & Comments