Support and Security Content 1

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/31

encourage image

There's no tags or description

Looks like no tags are added yet.

32 Terms

1
New cards

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.

2
New cards

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.


3
New cards

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.

4
New cards

Components of Computational Thinking

  • Decomposition: Breaking down a problem or system into smaller, more manageable parts.\n- Pattern Recognition: Identifying similarities, trends, and recurring traits within and between problems.\n- Abstraction: Removing unnecessary details and focusing strictly on essential information.\n- Algorithmic Design: Creating a sequence of step-by-step instructions to solve a problem.
5
New cards

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.

6
New cards

Purpose of Decomposition

To reduce complexity by dividing a system or fault into smaller parts so each can be evaluated, tested, or resolved independently.

7
New cards

Tasks of Decomposition

  • Identify the main features of a problem.\n- Characterise each identified feature.\n- Break problems down into smaller, more manageable parts.\n- Break solutions down into smaller, more manageable parts.
8
New cards

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.

9
New cards

Methods to Represent Decomposition

  • Block diagrams: Box-and-line diagrams showing main structural components and connections.\n- Information flow diagrams: Visual maps showing how data moves between parts of a system.\n- Flowcharts: Diagrams mapping process steps, logic choices, and execution direction.\n- Written descriptions: Text-based breakdowns outlining structural modules sequentially.
10
New cards

Using Methods to Represent Decomposition

Applying block diagrams, flowcharts, or text descriptions to structure system architecture or troubleshooting steps.

11
New cards

Purpose of Pattern Recognition

To find trends and leverage past experience or established solutions to resolve current issues quickly.

12
New cards

Using Pattern Recognition for Problem Solving

  • Find and interpret trends/similarities: Spotting that system slowdowns occur at specific daily times.\n- Find common features with existing solutions: Identifying that malware behavior matches a known threat signature.\n- Make predictions and assumptions: Anticipating that a hardware failure in a core switch will disconnect connected subnets.
13
New cards

Purpose of Abstraction

To hide internal complexity and filter out noise, leaving only what is required to model and solve the issue.

14
New cards

Tasks of Abstraction

  • Identify information that is needed.\n- Filter out unnecessary details.\n- Hide details of internal workings.
15
New cards

Requirements When Using Abstraction

  • What inputs are needed: Data required to start execution.\n- Expected outputs and outcomes: The generated result or final system state.\n- Things that will vary: Dynamic parameters (variables, session IDs).\n- Things that will remain constant: Static parameters (default ports, maximum retries).\n- Key actions the solution must perform: Essential operational steps.\n- Repeated processes the solution will perform: Loops and recursive operations.
16
New cards

Using Abstraction in Problem Solving

Designing system models or user interfaces by focusing purely on inputs, outputs, and key logic while hiding backend processing.

17
New cards

Interrelationships & Suitability in Digital Support & Security

  • Interrelationships: Decomposition breaks down the fault -> Abstraction isolates key parameters -> Pattern Recognition maps symptoms to known issues -> Algorithmic Design constructs the repair steps.\n- Suitability: Select components based on problem complexity; simple network faults require rapid pattern matching, while complex infrastructure projects require full decomposition and abstraction.
18
New cards

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.

19
New cards

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).

20
New cards

Benefits & Drawbacks of Flowcharts

Benefits: Visual layout makes decision paths and branches clear.\nDrawbacks: Can become cluttered and unreadable for large algorithms.

21
New cards

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.

22
New cards

Actions to Control Ordering of Steps in Algorithms

  • Sequence: Executing steps strictly one after another in order.\n- Selection: Choosing between alternate paths based on a condition (IF/ELSE).\n- Iteration: Repeating a set of instructions until a condition is met (WHILE, FOR, REPEAT).
23
New cards

Algorithmic Operations (1.2.6 to 1.2.10)

  • Determine purpose & how it works: Trace algorithm steps to identify functional intent.\n- Determine output: Dry-run algorithms using test inputs to determine expected output.\n- Identify errors: Detect syntax, logic, or runtime errors (e.g., infinite loops, incorrect relational operators).\n- Correct errors: Modify conditional checks, boundary values, or sequence order.\n- Design algorithms: Construct end-to-end logic using sequence, selection, and iteration.
24
New cards

Problem-Solving Approaches

  • Top-down: High-level overview first, breaking down systematically into lower-level details.\n- Bottom-up: Solving low-level components first, combining them to build the overall system.\n- Modularisation: Dividing a system into independent, self-contained functional modules.
25
New cards

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.

26
New cards

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.

27
New cards

Approaches & Actions in Root Cause Analysis

  • Five whys: Iteratively asking "Why?" (typically five times) to drill down from symptom to root cause.\n- Failure mode and effects analysis (FMEA): Proactive analysis evaluating failure points, severity, probability, and detection methods.\n- Event tree analysis (ETA): Logical diagram mapping potential outcomes following an initial event.\nActions after using RCA:\n- Log: Record all findings, actions, and evidence in the tracking system.\n- Close: Formally close the ticket once the permanent resolution is validated.\n- Escalate: Forward to a manager, domain specialist, or third-party vendor if out of scope.
28
New cards

High-Level Problem-Solving Process

  1. Define the problem\n2. Gather information\n3. Analyse the information\n4. Make a plan of action\n5. Implement a solution\n6. Review the solution
29
New cards

Definition of a Digital Incident

A single unplanned event that disrupts service operations and negatively impacts service quality.

30
New cards

Definition of a Digital Problem

The underlying, unknown cause of one or more incidents.

31
New cards

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.

32
New cards

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.