Systems development: who should select the solution technique that a computing system will implement, balancing feasibility, requirements, and organizational constraints?

Introduction / Context:
Choosing a solution technique—algorithmic approach, optimization method, or processing strategy—requires aligning business requirements with technical feasibility. The role responsible must understand both the domain and the technological landscape, while coordinating with specialists and users.

Given Data / Assumptions:

• The selection must reflect requirements, constraints, and performance goals.
• Stakeholders include users, programmers, and possibly OR experts.
• We seek the role that integrates perspectives and owns the design choice.

Concept / Approach:
System analysts are trained to translate requirements into specifications, evaluate alternatives, consider cost–benefit and risk, and select techniques that programmers will implement. They may consult OR experts for models and users for needs, but the analyst synthesizes these inputs into the system's chosen approach.

Step-by-Step Solution:

Verification / Alternative check:
Standard SDLC artifacts (functional specs, solution design) are authored or owned by analysts or solution architects, confirming this choice.

Why Other Options Are Wrong:

• OR expert: Provides modeling expertise but not overall system selection in general SDLC.
• Programmer: Implements the chosen technique; selection is upstream.
• User: Provides requirements and validation, not the technical selection.
• None: Incorrect because analysts are correct.

Common Pitfalls:
Confusing technical design authority (analyst/architect) with implementation (programmer) or domain input (user).

Final Answer:
system analysts