Pular para o conteúdo

Eduqas GCSE Computer Science

GCSE · EduqasComputer Science706 cartões

706 flashcards, criado pelo cookie, em 88 subbaralhos que seguem os temas do curso.

Estudar estes cartões

Selecionamos opções do mesmo curso que são muito usadas, e todas podem ser lidas sem uma conta.

Tudo sobre Computer Science

Procurando ajuda com Computer Science?

A Cookie Tutoring, nosso próprio serviço de aulas particulares, pode ter tutores de Computer Science. As aulas são ao vivo e individuais, e os primeiros 15 minutos com qualquer tutor são grátis.

Encontrar um tutor

Flashcards for Eduqas GCSE (9-1) Computer Science (C500QS), split into Component 1 Understanding Computer Science and Component 2 Computer Programming, then by topic in the specification's order. Delete or suspend any subdeck your course leaves out once the deck is yours.

Ao adicioná-lo, você terá sua própria cópia, com todos os subbaralhos. Cada cartão volta a aparecer pouco antes de você esquecê-lo, e cada resposta certa ou errada conta para o seu domínio do tema. Depois de adicioná-lo, você pode excluir ou suspender as partes que não está estudando.

O que há dentro (88 subbaralhos)

  • Component 1 Understanding Computer Science506 cartões
    • 1 Hardware67 cartões
      • 1.1 Central processing unit29 cartões
      • 1.2 Memory and storage28 cartões
      • 1.3 Additional hardware and embedded systems10 cartões
    • 2 Logical operations45 cartões
      • 2.1 Logical operators and truth tables20 cartões
      • 2.2 Boolean simplification25 cartões
    • 3 Networking and cybersecurity89 cartões
      • 3.1 Networks and topologies17 cartões
      • 3.2 Network hardware10 cartões
      • 3.3 Protocols and the OSI model25 cartões
      • 3.4 The internet, DNS and URLs7 cartões
      • 3.5 Routing8 cartões
      • 3.6 Cybersecurity threats13 cartões
      • 3.7 Protecting systems9 cartões
    • 4 Data representation and storage96 cartões
      • 4.1 Number systems and integers47 cartões
        • 4.1.1 Counting systems16 cartões
        • 4.1.2 Signed integers9 cartões
        • 4.1.3 Binary arithmetic13 cartões
        • 4.1.4 Data types9 cartões
      • 4.2 Characters, graphics and sound30 cartões
        • 4.2.1 Characters9 cartões
        • 4.2.2 Graphics12 cartões
        • 4.2.3 Sound9 cartões
      • 4.3 Storage units and compression19 cartões
        • 4.3.1 Storage units9 cartões
        • 4.3.2 Compression10 cartões
    • 5 Data organisation21 cartões
      • 5.1 Records and files7 cartões
      • 5.2 Arrays7 cartões
      • 5.3 Choosing and designing structures7 cartões
    • 6 Operating systems27 cartões
      • 6.1 Purpose and management14 cartões
      • 6.2 Utility software13 cartões
    • 7 Principles of programming20 cartões
      • 7.1 Levels of language7 cartões
      • 7.2 Choosing a language10 cartões
      • 7.3 What a high-level language hides3 cartões
    • 8 Algorithms and constructs61 cartões
      • 8.1 Describing algorithms13 cartões
      • 8.2 Subroutines and variables9 cartões
      • 8.3 Pseudo-code operations11 cartões
      • 8.4 Sorting8 cartões
      • 8.5 Searching9 cartões
      • 8.6 Validation and verification11 cartões
    • 9 Software development23 cartões
      • 9.1 Software tools19 cartões
      • 9.2 Compiling, linking and running4 cartões
    • 10 Program construction30 cartões
      • 10.1 Translators10 cartões
      • 10.2 Stages of compilation10 cartões
      • 10.3 Programming errors10 cartões
    • 11 Impacts of digital technology on wider society27 cartões
      • 11.1 Ethical, legal and cultural issues17 cartões
      • 11.2 Privacy, consent and the environment10 cartões
  • Component 2 Computer Programming200 cartões
    • 1 Investigation18 cartões
      • 1.1 Approach and decomposition5 cartões
      • 1.2 Modules and requirements5 cartões
      • 1.3 Stakeholders and requirements8 cartões
    • 2 Design19 cartões
      • 2.1 User interface and data6 cartões
      • 2.2 Routines in pseudo-code6 cartões
      • 2.3 Documenting the design7 cartões
    • 3 Implementation126 cartões
      • 3.1 Variables and data types10 cartões
      • 3.2 Operators and expressions9 cartões
      • 3.3 Input and output6 cartões
      • 3.4 Selection8 cartões
      • 3.5 Iteration10 cartões
      • 3.6 Subroutines8 cartões
      • 3.7 Strings14 cartões
      • 3.8 Lists, tuples and dictionaries16 cartões
      • 3.9 Files12 cartões
      • 3.10 Records and objects8 cartões
      • 3.11 Graphical user interfaces9 cartões
      • 3.12 Validation and authentication in code6 cartões
      • 3.13 Libraries and modules4 cartões
      • 3.14 Style and documentation6 cartões
    • 4 Testing18 cartões
      • 4.1 Test data and plans12 cartões
      • 4.2 Carrying out and reporting tests6 cartões
    • 5 Refinement19 cartões
      • 5.1 Improving a solution7 cartões
      • 5.2 Changing requirements4 cartões
      • 5.3 Evaluating given code8 cartões

Alguns dos cartões

  • What is the purpose of the CPU?
    To carry out the instructions of a program by fetching, decoding and executing them
  • What is a systematic approach to problem solving?
    Working through a problem in ordered stages, such as investigate, design, implement, test and refine
  • What is the Von Neumann architecture?
    A design in which program instructions and data are held in the same main memory and fetched over one shared path
  • What is decomposition?
    Breaking a large problem into smaller parts that can be designed, coded and tested separately
  • What does the control unit (CU) do?
    Directs the operation of the processor by decoding instructions and sending control signals to other components
  • What is abstraction?
    Removing details that do not affect the problem, so that only the features the solution needs are modelled
  • What does the arithmetic and logic unit (ALU) do?
    Carries out arithmetic calculations and logical comparisons
  • Why does abstraction help when modelling a real system?
    It keeps the features the solution needs and ignores details that do not change the result
  • What is main memory?
    The memory that holds the programs and data in use, which the CPU reads from and writes to directly
  • Why should a problem be decomposed before it is coded?
    Smaller parts are easier to design, write and test on their own

E mais 696 depois que você adicionar o baralho.