Problem Recognition (OCR A Level Computer Science)

Problem Recognition

What is Problem Recognition?

• Problem recognition is determining if there is a problem that needs to be solved

• For example, if customers of an online shop complain that a checkout process is slow then problem recognition can be used to determine that there is a problem to be solved and what the problem actually is

• In this example, the core problems might relate to how many steps exist in the process or the poor organisation of information on the page

• Both of these problems are possible to solve through a software solution

• Code can be rewritten so that the number of steps is reduced and the information can be arranged in a simpler way

• But not all problems should or can be solved with software

Example 1: Slow response time in a GP surgery booking system

The big problem

• Slow response time: The primary issue is the slow response time in the online appointment booking system, leading to user frustration and abandoned bookings

Sub problems

1. Peak hour bottlenecks: The system experiences a significant peak-hour slowdown, indicating potential scalability issues

2. Delayed confirmation: Patients must wait several minutes for a confirmation screen to appear, which could point to inefficient processing of booking requests

3. User experience: Frustrated users may lose faith in the system or the GP surgery, possibly affecting its reputation

4. Abandoned bookings: The slow system is causing patients to abandon their appointments, meaning they are not seeking help with their health

Example 2: Low employee morale and high turnover rates in a sales team

The big problem

• Low employee morale and high turnover: The core issue is the high employee turnover rate and declining morale, which affects both team performance and the company's reputation

Sub problems

1. Unrealistic sales targets: Employees feel that the sales goals set by management are too challenging to achieve, causing stress

2. Lack of support: There is a feeling among team members that they lack the necessary support and resources to perform well

3. Poor work-life balance: Long working hours and high stress levels contribute to an imbalanced work-life equation

4. Team cohesion: The frequent departures disrupt team cohesion, affecting collaborative efforts and reducing overall productivity

• In this case, problems like low morale, unrealistic targets, and lack of emotional support are largely cultural and psychological issues and can't be directly solved with software

• Some software solutions may exist to help, such as project management, or somewhere to record and analyse why employees are leaving

• But the big problem requires human-centric solutions like revised management practices, team-building exercises, and counselling services