Difficulty: Easy
Correct Answer: Program testing
Explanation:
Introduction / Context:
The Implementation phase moves a completed system into production. Typical activities include preparing data, training users, arranging facilities, executing cutover, and stabilizing operations. Testing is essential, but core program testing is generally completed earlier.
Given Data / Assumptions:
Concept / Approach:
Implementation emphasizes readiness and transition: converting files, educating users, setting up environments, and migrating. Program testing belongs to the build/test phases that validate correctness before roll-out.
Step-by-Step Solution:
1) Identify implementation tasks: training, conversion, facility preparation, communications.2) Identify development/testing tasks: unit/integration/system tests and defect fixes.3) Map each option to its predominant phase.4) Conclude which option does not belong to implementation.
Verification / Alternative check:
Project plans normally show code and test completion gates before deployment start. Acceptance activities may overlap, but routine program testing is a prerequisite, not an implementation step.
Why Other Options Are Wrong:
File conversion: clearly an implementation activity to populate production data.User training: a standard implementation activity to prepare stakeholders.All of the above: wrong because at least two are correct implementation tasks.None of the above: wrong because one activity does not belong.
Common Pitfalls:
Confusing acceptance testing with core program testing; acceptance belongs near rollout, whereas coding tests should finish beforehand.
Final Answer:
Program testing
Discussion & Comments