Skip to content
Definition
When designing a solution to a problem, it is crucial to think ahead about the inputs (data provided to the system) and outputs (results produced by the system) required for the program to function correctly.

Understanding Inputs and Outputs

Key Point
CategoryWhat it meansKey design checks
InputsData provided to the system for processingData type, format/order, validation rules
OutputsResults produced after processingClarity, destination (screen/file/device), usefulness
Worked Example
Worked Example: ATM System
InputsPurpose
transactionTypeDeposit / balance check / withdrawal selection
cardDetailsIdentify account via card reader
pinAuthenticate user
amountAmount to deposit or withdraw
OutputsPurpose
displayBalanceShow account balance on screen
dispenseCashProvide physical cash
printReceiptProvide transaction record
audioFeedbackAccessibility and confirmation prompts
Why this matters: planning inputs/outputs early prevents security gaps (e.g., no PIN validation) and usability gaps (e.g., no clear confirmation output).