CodeIEB
Theory Notes/🖥️ Topic 1: System Technologies/12.1.4
12.1.4Grade 12

Recommending a Hardware Solution

This subtopic is pure application — given a described user and their needs, you must motivate a complete, justified hardware recommendation, including for mobile/portable scenarios.

A strong hardware recommendation answer follows this structure for every component:

  • State the component/specification you recommend.
  • Justify it by linking directly back to a specific need mentioned in the scenario (not a generic 'this makes it faster').

Example

Scenario: 'A graphic designer needs a new computer for photo editing and wants to work from client sites occasionally.' Recommendation: A laptop (not desktop) — because the scenario specifically requires portability for client visits. Recommend a high-resolution display and a dedicated/discrete graphics card — because photo editing is visually and processor-intensive and benefits from accurate colour and GPU acceleration. Recommend an SSD — because large image files need to load and save quickly, and reliability matters for professional client work.

For a computer-based solution to a broader business/user problem, motivate the full system (not just hardware) in terms of what the specified user actually needs to accomplish — considering budget, scale, and expected growth, not only raw performance.

Mobile technologies and their constraints — a mobile device recommendation must explicitly weigh trade-offs that don't apply to a desktop:

ConstraintTrade-off to discuss
Battery lifeMore powerful components generally drain the battery faster; there's a balance between performance and how long the device lasts between charges
SizeSmaller devices are more portable but have less room for cooling, bigger batteries, or high-end components
Computing powerMobile chips are generally less powerful than desktop equivalents to manage heat and power draw
Power consumptionRelated to 11.2.6 (network/connectivity considerations) — always-on connectivity (Wi-Fi, mobile data, GPS) further drains battery life

💡 Exam Tip

Never recommend a component in isolation. Every recommendation must be tied back to a phrase or need explicitly stated in the scenario — markers award marks for the justification, not just the correct component name.