Academic Performance and Student Wellbeing

PRL1013 Problem Solving in Computing - LU2: Analyzing the Problem

• Course title: PRL1013 PROBLEM SOLVING IN COMPUTING
• Learning unit: LU2: Analyzing the Problem
• Instructors: Michelle Anak George, Eaqerzilla Phang, Dr Sinarwati Binti Mohamad Suhaili

Agenda

• Understand Your Problem
• Breaking Problem down to Small Parts
• Define problem domain
• Measuring end goals

Learning Outcomes

• Understand the importance of problem analysis and how it helps in creating effective solutions in computing.
• Identify and clearly define problems, knowing the difference between symptoms and the real issues.
• Break down big problems into smaller, manageable parts using easy-to-follow steps.
• Use problem-solving tools (e.g., 5 Whys, root cause analysis) to analyze issues.
• Consider different perspectives to ensure the solutions are comprehensive and relevant.

Flowchart for Problem Analysis Process

• 1) Importance & Objectives of Problem Analysis: Understanding the critical skill and objectives in problem analysis.
• 2) Understanding the Problem: Understanding the problem core elements, its causes, and potential impacts.
• 3) Identifying the Core Problem: Identifying the actual problem from its symptoms.
• 4) Contextual Analysis: Understanding the context in which the problem exists.
• 5) Tools for Understanding Problems: Utilizing analytical tools to systematically analyze the problem. (e.g. 5 Whys, Root Cause Analysis, Fishbone Diagram, Stakeholder Mapping)
• 6) Gathering Information: Gathering all relevant information, data, context and stakeholder perspectives.
• 7) Stakeholder Analysis & Mapping: Analyze stakeholders and their influence/interest.
• 8) Crafting the Problem Statement: Crafting a clear and concise problem statement.

Steps to Identifying the Core Problem

• Identify Symptoms
• Gather Information
• Analyze Context
• Focus on Core Problem
• Identify Root Causes

Example of Core Problem Identification

• Case Study: A real-world example demonstrating how proper core problem identification leads to more effective solutions.
• Outcome Improvement: Reinforces the importance of accurate problem identification for better results

Understanding the Core Problem: A Simple Example

• Scenario: A company's sales are dropping.
• Initial Guess: Poor marketing.
• Finding the Real Problem: Gather data (customer feedback, sales data, pricing, customer service quality), analyze the data, realize the core problem, and arrive at a solution.

4) Contextual Analysis

• Problem Environment: Understanding the context where the problem exists is vital to ensure a solution fits the circumstances.
• Solution Relevance: Solutions developed should be relevant to the problem's specific context.

Tools for Understanding Problems

• Analytical Tools: Using various tools (e.g., 5 Whys, root cause analysis, fishbone diagrams) to systematically analyze and understand a problem.
• Problem Clarity: Breaking down the problem into its core components to provide clarity and structure when addressing the issue.

6) Gathering Information

• Data Collection: Gathering comprehensive and accurate data related to the problem forms the basis for future analysis and decision-making.
• Inform Decisions: The collected data is crucial for making informed decisions ensuring solutions are well-founded in the collected data.

7) Stakeholder Analysis: Concept Visualization

• Identify Needs: Understanding stakeholder needs.
• Gather Views: Collecting opinions from stakeholders.
• Stakeholder Mapping: Visual representation of stakeholder influence and interest.
• Focus Efforts: Prioritizing efforts based on stakeholder impact.

7) Stakeholder Analysis

• Identify Needs: Understanding needs and perspectives of all stakeholders involved is essential for a holistic problem understanding.
• Incorporate Views: By incorporating stakeholder perspectives, analysis becomes more robust and solutions meet the needs of all involved parties.

Problem Statement

• Crafting Statements: A well-crafted problem statement defines the problem clearly, concisely, and specifically, guiding further analysis and solution development.
• Guiding Solutions: The statement should be detailed enough to guide the solution process, but flexible to adapt to new insights.

Example of a Good Problem Statement

• Real-World Example: Demonstrating how a well-defined problem statement guides the problem-solving process.
• Clarity and Specificity: The importance of concise and clear communication of the problem.

Case Study Example: Understanding Your Problem

• Scenario: Declining academic performance in a high school.
• Background: Teachers and students notice a decline in academic performance over several semesters.
• Step 1: Identifying the Problem
• Initial Observation: Academic performance across multiple subjects is dropping.
• Core Issue: Students' grades are declining, with an increase in classroom disruptions and disengagement.
• Step 2: Gathering Information
• Data Collection: School gathers data on student grades, attendance, behavior, and teacher feedback.
• Student Surveys: Surveys and interviews reveal students experience higher levels of stress and difficulty balancing their increased workload.
• Step 3: Contextual Analysis
• Recent Changes: New curriculum, more rigorous testing standards, and increased homework/extracurricular activities.
• Student Feedback: Students feel overwhelmed by the increased workload, and teachers report new teaching methods might not sync with learning styles.
• Step 4: Crafting your Problem Statement
• The high school has observed a decline in academic performance.
• Step 5: Identifying the Core Problem
• Root Cause Analysis: Based on data, the decline is attributed to the new curriculum and increased workload.
• Core Problem: Difficulty with the new curriculum and increased student stress lead to the issues observed.
• Outcome: Review and adjust the curriculum, provide additional support (tutoring/counseling), aligned with student needs and learning styles.

Breaking Problem to Small Parts

• Overview: Problem decomposition techniques like top-down and bottom-up approaches are discussed.

Why Decomposition Matters

• Why Decomposition Matters: Breaking down complex problems into smaller, more manageable components simplifies the process of problem-solving and aids in identifying root issues.
• Structured Approach: Decomposing the problem ensures each component is addressed effectively, leading to a comprehensive resolution.

Introduction to Problem Decomposition

• What is Decomposition?: Breaking down the problem into smaller, manageable parts.
• Advantages: Facilitates easier understanding and solving of complex problems, allowing focused attention on individual parts leading to more effective solutions.

Techniques for Problem Decomposition

• Top-Down Approach: Starting with the overall problem and progressively breaking it down into constituent parts.
• Bottom-Up Approach: Begins with smaller detailed components, subsequently integrating them into a complete solution.

Example of Top-Down Approach

• Goal: Plan a successful office birthday party.
• Break Down: Venue, food and drinks, entertainment.
• Detail Requirements: Specific tasks for each component.
• Execute: Implementing the planned tasks and activities

Example of Bottom-Up Approach

• Tasks and Details: Individual tasks, like decoration, food ordering, creating a playlist
• Combine Components: Assemble each task for a complete party plan.
• Assemble the Event: Comprehensive plan to ensure all elements are prepared cohesively.
• Review and Adjust: Review elements, and incorporate any changes to improve effectiveness further

Modularization

• Breaking into Modules: Dividing a problem into independent modules for easier development and testing.
• Benefits: Facilitates easy testing and maintenance through modular design.

Benefits of Modularization

• Easier Testing: Simplifies and expedites testing by enabling isolated module testing.
• Maintenance: Easier changes and modifications in modules without affecting the entire system.

Case Study on Decomposition: Simple Calculator

• Decompose the System: Dividing a calculator application into modules (UI, arithmetic operations, handling input, displaying results). Develop Modules: Designing each module focusing on tasks like input processing, performing calculations, and displaying results. Integrate Components: Combining the developed modules into a complete functioning application. Benefits: Simplifying development, enhances maintainability, and facilitates updates or extensions to specific operations.

Decomposition

• Definition: Breaking a complex system into smaller, manageable modules.
• Purpose: Simplification of development and enhanced maintainability.
• Example: A calculator app with modules for user interface, arithmetic, input handling, and display.
• Benefits: Facilitates easier development, testing, and updates for the application.

Modularization Versus Decomposition

• Decomposition: Breaks down complex problems into smaller entities for easier handling.
• Modularization: Arranges the constituent parts into distinct, reusable modules to improve system design and maintainability.

Case Study on Modularization: Simple Calculator

• Defines Arithmetic Modules: separating the calculator into modules of addition, subtraction, multiplication, and division.
• Develop Each Module: Implementing each operation as an independent function or module, optimizing for accuracy.
• Integrate Modules: Combining the various modules to allow the calculator to execute the chosen function.
• Simplify Maintenance: Allows for separate and convenient updates for specific parts.

Challenges in Problem Decomposition

• Common Issues: Potential difficulties in decomposing problems (identifying the correct level of detail, managing dependencies).
• Overcoming Challenges: Implementing strategies like iterative refinement, strong collaboration, and employing decomposition tools.

Tools for Decomposition

• Visualization Tools: Using tools like flowcharts, diagrams to visualize the steps or components to visualize linkages and relationships between them within the process.
• Application: Using these tools for efficient problem decomposition, improving understanding, and finding solutions to complex problems.

Practice Exercise on Decomposition

• Exercise: Decomposing the functionality of a library management system into smaller, manageable modules.
• Requirements: Defining the responsibilities of each module and demonstrating how they interact to form a cohesive system.

Conclusion

• Thank you

This quiz explores the core issues affecting academic performance within a school environment. It addresses methods of data collection, recent changes contributing to student overwhelm, and the impact of classroom disruptions on learning. Additionally, it investigates teachers' observations regarding student interactions and the school's response to performance declines.