Solution Design and Evaluation
Core concepts
Solution design converts requirements into candidate options and selects the best fit. Candidates must understand how to develop alternatives, define evaluation criteria (cost, risk, feasibility, time to value, strategic fit, maintainability), and weight them for comparison. Know common evaluation methods: scoring matrices, cost-benefit analysis, SWOT, and proof-of-concept validation. Understand build-versus-buy-versus-reuse tradeoffs, total cost of ownership, and the role of non-functional requirements (performance, security, scalability, usability) in shaping design. Know the difference between a solution (the whole system of people, process, and technology) and a software component. Understand validation: does the solution meet the need and is it fit for purpose?
Traps
Questions often reward the answer that ties the solution back to the business need, not the most technically elegant option. Watch for choices that optimize a single criterion (lowest cost) while ignoring risk or lifecycle cost. Another trap confuses a prototype (learning tool, may be discarded) with a pilot (limited production release). Beware of "gold-plated" solutions that exceed requirements and add cost without value.
Worked rule of thumb
Use a weighted scoring matrix: list criteria, assign weights summing to 100%, score each option 1–5, multiply and sum. Run a sensitivity check: if small weight changes flip the winner, the decision is fragile and needs more evidence.
Example: Option A scores highest on cost but lowest on security; if security carries 30% weight, the matrix may reveal Option B as the better overall choice.