Which phases of the system development life cycle are associated with both in-house development and systems that are purchased from an outside vendor?

• A. Phases involving the production of several alternative conceptual systems that satisfy system requirements
• B. Phases involving a system being physically constructed
• C. Phases involving needs analysis and system specification
• D. Phases involving selecting a programming language

Answer: (C)

The main idea being tested is that the start of any system project—figuring out what is needed and documenting those requirements—applies whether you’re building the system in-house or buying it from a vendor. Needs analysis is about identifying business problems, user needs, data, processes, controls, and performance goals. System specification then translates those needs into precise, testable requirements that define what the system must do and how it must behave.

This pair of activities is essential before deciding how to implement. If you’re developing in-house, the specification guides design, development, and testing. If you’re purchasing off-the-shelf, the specification serves as the yardstick for evaluating vendor proposals, performing fit-gap analyses, and determining what customization or configuration is needed to meet the requirements. Other phases, like exploring multiple conceptual designs or choosing a programming language, are more tied to how you implement them and to decisions made after the needs and requirements are known, so they aren’t as universally applicable to both build and buy paths as the needs analysis and system specification are.