Question 1
4 marks
Mobile hardware constraints and API architecture in Computer Aided Dispatch
- Resource management
- System fundamentals
(a)
2 marks
- Identify two mobile device hardware resources that can constrain user experience during emergency reporting:
- 1) Battery power capacity: Continuous execution of GPS radios, screen backlights, and high-frequency cellular transmissions rapidly drains mobile batteries, threatening complete device shutdown during ongoing field crises.
- 2) Primary RAM and processor speed: Limited device memory and modest CPU processing power restrict the client's ability to render complex interactive vector maps or process local image compression before upload.
Mentor tip
Identify physical client-side hardware resources (battery life, RAM, CPU processing power, screen real estate, or GPS chip receiver) rather than backend server resources.
(b)
2 marks
- Outline why an Application Programming Interface (API) is essential when interfacing mobile apps with CAD backends:
- 1) Abstraction and interface standardization: The API establishes a formalized contract defining endpoints, data formats, and parameter types, allowing mobile app developers to request CAD services without needing visibility into internal backend database schemas or server code.
- 2) Security enforcement and backward compatibility: The API gateway authenticates incoming mobile requests via cryptographic tokens, enforces rate limiting, and shields internal server binaries from direct public exposure while maintaining backward compatibility across evolving app versions.
Mentor tip
Explain abstraction (separating frontend client requests from backend logic) and centralized authentication/security checks.

