1/31
Looks like no tags are added yet.
Definition & Purpose of Computational Thinking
Definition: A structured problem-solving approach that formulates a problem and expresses its solution in a way that a computer (or human) can effectively carry out.\nPurpose: Enables systematic analysis of problems to represent them as systems, processes, relationships, or organizations of data.
When to Use Computational Thinking
When dealing with complex, non-obvious, or multi-faceted digital issues.\n- When designing automated systems, security protocols, network structures, or repeatable processes.\n- When organizing and analyzing large structures or relationships of data.
Benefits & Drawbacks of Computational Thinking
Benefits:\n- Creates scalable, reusable, and repeatable solutions.\n- Reduces human error by establishing strict logical pathways.\n- Enables automation of manual tasks.\nDrawbacks:\n- High initial setup time and cognitive effort.\n- Risks over-engineering or over-complicating minor, simple tasks.\n- Solutions can be rigid if underlying parameters change unexpectedly.
Components of Computational Thinking
Benefits & Drawbacks of Computational Thinking Components
Decomposition:\n- Benefit: Makes large tasks manageable; allows parallel execution across team members.\n- Drawback: Focuses heavily on isolated parts, potentially missing system-level integration issues.\nPattern Recognition:\n- Benefit: Speeds up diagnosis by enabling the reuse of known solutions.\n- Drawback: Misleading if new problems mimic known symptoms but stem from different causes.\nAbstraction:\n- Benefit: Simplifies complex models and reduces cognitive overload.\n- Drawback: Omitting too much detail can obscure root technical causes.\nAlgorithmic Design:\n- Benefit: Delivers precise, reliable, and automatable results.\n- Drawback: Can be complex and difficult to account for all edge cases.
Purpose of Decomposition
To reduce complexity by dividing a system or fault into smaller parts so each can be evaluated, tested, or resolved independently.
Tasks of Decomposition
Using Decomposition for Problem Solving
Example: Troubleshooting a server network failure by isolating into 4 sub-tasks: Physical Cabling -> Network Interface Card (NIC) -> IP Configuration -> Firewall Rules.
Methods to Represent Decomposition
Using Methods to Represent Decomposition
Applying block diagrams, flowcharts, or text descriptions to structure system architecture or troubleshooting steps.
Purpose of Pattern Recognition
To find trends and leverage past experience or established solutions to resolve current issues quickly.
Using Pattern Recognition for Problem Solving
Purpose of Abstraction
To hide internal complexity and filter out noise, leaving only what is required to model and solve the issue.
Tasks of Abstraction
Requirements When Using Abstraction
Using Abstraction in Problem Solving
Designing system models or user interfaces by focusing purely on inputs, outputs, and key logic while hiding backend processing.
Interrelationships & Suitability in Digital Support & Security
Definition, Characteristics & Purpose of Algorithms
Definition: A set of ordered, unambiguous instructions designed to perform a specific task.\nCharacteristics: Finite (must end), unambiguous, correct, clear inputs/outputs.\nPurpose: Ensures tasks are performed consistently, accurately, and can be automated by digital systems.
Methods to Express Algorithms
Flowcharts:\n- Terminators: Start/End points.\n- Processes: Single action steps.\n- Sub-processes: Pre-defined sub-routines.\n- Decisions: Branching logical tests (True/False or Yes/No).\n- Inputs/Outputs: Data entry or displayed results.\n- Arrows: Flow of execution.\n- Labels: Text clarifying logic paths (e.g., "Yes", "No").\nWritten descriptions using hierarchical markers: Numbered/bulleted text showing step sequences (e.g., 1.0, 1.1, 1.1.1).
Benefits & Drawbacks of Flowcharts
Benefits: Visual layout makes decision paths and branches clear.\nDrawbacks: Can become cluttered and unreadable for large algorithms.
Benefits & Drawbacks of Written Descriptions
Benefits: Easy to create in standard documentation formats without drawing software.\nDrawbacks: Complex nested logic and loops can become difficult to follow in pure text.
Actions to Control Ordering of Steps in Algorithms
Algorithmic Operations (1.2.6 to 1.2.10)
Problem-Solving Approaches
Benefits & Drawbacks of Problem-Solving Approaches
Top-down:\n- Benefit: Clear high-level visibility; focuses on ultimate objectives.\n- Drawback: May miss critical low-level hardware or driver constraints.\nBottom-up:\n- Benefit: Ensures core components work before building higher structures.\n- Drawback: Integration issues may appear late in development.\nModularisation:\n- Benefit: Facilitates parallel development and easy replacement of modules.\n- Drawback: Interfaces between modules must be meticulously managed.
Purpose of Root Cause Analysis (RCA)
To identify the underlying, primary cause of a fault to ensure a permanent solution is applied rather than just treating symptoms.
Approaches & Actions in Root Cause Analysis
High-Level Problem-Solving Process
Definition of a Digital Incident
A single unplanned event that disrupts service operations and negatively impacts service quality.
Definition of a Digital Problem
The underlying, unknown cause of one or more incidents.
Process of Incident Management
Detection:\n- Report: Log incoming user/monitoring reports.\n- Record: Document incident details in the service desk tool.\n- Prioritise: Assign priority based on impact and urgency.\nResponse:\n- Identify owner: Assign to an individual or team.\n- Resolve and restore: Apply a workaround or fix to restore service operations.\n- Record resolution: Document actual resolution steps taken.\nIntelligence:\n- Record lessons: Document findings and update knowledge base.\n- Identify cause: Pass to Problem Management for root cause investigation.\n- Share lessons: Disseminate findings to support teams.
Interrelationships & Judgements on Strategy Suitability
Match problem-solving approaches to scenario requirements:\n- Critical outages: Incident management lifecycle (Detection -> Restore quickly with workaround).\n- Recurring faults: Transition from Incident to Problem Management -> Execute Root Cause Analysis (5 Whys / FMEA).\n- Complex software/infrastructure bugs: Apply Modularisation and Top-Down / Bottom-Up approaches.