Computer Science

• 1.1.1: What is meant by "context" when planning a new system? The environment in which the system will operate

  including user needs business requirements constraints and objectives.
• 1.1.2: Why is change management needed? It ensures a structured approach to transitioning systems or processes

  minimizing disruptions and securing stakeholder acceptance.
• 1.1.3: What compatibility issues can arise with legacy systems or business mergers? Conflicting data formats

  hardware/software incompatibilities different operating systems and integration challenges.
• 1.1.4: Compare on-premises implementation vs. hosting systems remotely (e.g.

  cloud). On-premises: full control higher setup/maintenance costs. Cloud/remote: lower upfront costs easier scaling but reliant on internet and third-party providers.
• 1.1.5: What are alternative installation processes? Direct (big bang)

  parallel (run old and new simultaneously) pilot (test in a small area first) phased (gradual rollout).
• 1.1.6: What problems may arise during data migration? Data loss

  corruption incompatible file formats incomplete transfers and potential downtime or system conflicts.
• 1.1.7: What are some types of testing? Alpha

  beta white-box black-box user acceptance integration and system testing.
• 1.1.8: Why is user documentation important? It helps users understand and operate the system effectively

  reducing errors and support costs.
• 1.1.9: What are methods of providing user documentation? Printed manuals

  online help FAQs embedded tutorials video guides and interactive help systems.
• 1.1.10: What are methods of delivering user training? Self-instruction (tutorials/manuals)

  formal classes (in-person or virtual) on-the-job training and online courses.
• 1.1.11: What are possible causes of data loss? Hardware failure

  software bugs human error cyberattacks (malware/ransomware) power outages and natural disasters.
• 1.1.12: What are the consequences of data loss in a given situation? Loss of productivity

  financial losses reputational damage legal liabilities and disruption of critical operations.
• 1.1.13: How can data loss be prevented? Regular backups (onsite/offsite)

  RAID systems cloud storage UPS (uninterruptible power supply) and robust security practices.
• 1.1.14: What are strategies for managing releases and updates? Version control

  continuous integration patch management incremental releases and rollback plans for failed updates.
• 1.2.1: Define hardware

  software peripheral network and human resources. - Hardware: Physical components (CPU memory etc.)- Software: Programs/instructions- Peripheral: External devices (printer mouse etc.)- Network: Linked systems sharing resources- Human resources: People who develop maintain and use the system
• 1.2.2: What roles can a computer take in a networked world? Client

  server peer or a hybrid role (e.g. peer-to-peer networks where each node can act as both client and server).
• 1.2.3: What are social and ethical issues in a networked world? Privacy

  security intellectual property rights digital divide and the impact of technology on employment and social interactions.
• 4.1.1: How do you identify the procedure to solve a problem? Break the problem into steps

  define inputs/outputs and outline the logical sequence of actions (an algorithm).
• 4.1.2: Why does the order of activities matter in a procedure? Incorrect sequencing can produce wrong results or cause system failures; the correct order ensures the desired outcome.
• 4.1.3: What is the role of sub-procedures in problem solving? They break down complex tasks into smaller

  reusable modules improving clarity maintenance and reusability.
• 4.1.4: When is decision-making required in a problem? Whenever there is a need to choose among multiple paths based on conditions or user inputs (e.g.

  if/else statements).
• 4.1.5: How do you identify decisions for a solution? Look for points where the process can branch or requires different actions depending on a condition or user input.
• 4.1.6: What is the condition in a decision? A Boolean expression or logical statement that evaluates to true or false


  dictating which path is taken.
• 4.1.7: How are decisions and conditions related? Conditions determine the outcome of decisions; decisions are the branching points that depend on the condition's true/false result.
• 4.1.8: How do you deduce logical rules for real-world situations? Identify all possible conditions

  apply logical reasoning (AND OR NOT) and form rules that map to outcomes or actions.
• 4.1.9: What are inputs and outputs in a solution? Inputs are data/resources needed to start or run a process; outputs are the results or products generated by that process.
• 4.1.10: What is pre-planning in problem-solving? Identifying tasks

  constraints required resources and potential issues before starting the main development or solution process.
• D.1.1: What is the general nature of an object in OOP? An entity combining data (attributes) and behaviors (methods) into a single

  self-contained unit.
• D.1.2: What is the difference between a class and an object? A class is the blueprint or template; an object is an instance of that class with specific attribute values.
• D.1.3: What is a UML diagram (in OOP context)? A visual representation of classes

  attributes methods and relationships (e.g. class diagrams) used to model object-oriented designs.
• D.1.4: How do you interpret UML diagrams? Read class names

  attributes methods and the relationships (association inheritance etc.) to understand system structure.
• D.1.5: What is decomposition in OOP design? Splitting a system into smaller

  related objects or classes each responsible for a specific part of the overall functionality.
• D.1.6: What are possible relationships between objects? Association (uses)

  aggregation (has-a) composition (part-of) and inheritance (is-a).
• D.1.7: Why reduce dependencies between objects? To create loosely coupled systems that are easier to maintain

  extend and test with minimal ripple effects when changes occur.
• D.1.8: How do you construct related objects for a given problem? Identify classes

  define their attributes and methods and establish relationships (association aggregation composition or inheritance).
• D.1.9: Why do we need different data types? To ensure correct data representation

  efficient memory usage and proper operations (e.g. integer vs. float vs. string).
• D.1.10: How are parameters passed in methods (OOP context)? They are given as inputs (arguments) to a method’s signature

  allowing data to be sent into or out of the method’s scope for processing.