Passer au contenu

Eduqas GCSE Computer Science

GCSE · EduqasComputer Science706 cartes

706 flashcards, créée par cookie, dans 88 sous-paquets qui suivent les sujets du programme.

Réviser ces cartes

Sélectionné pour le même cours parmi les ressources les plus utilisées. Tout est consultable sans compte.

Tout pour Computer Science

Tu cherches de l’aide en Computer Science ?

Cookie Tutoring, notre service de cours particuliers, propose peut-être des professeurs pour Computer Science. Les cours ont lieu en direct et en tête-à-tête. Les 15 premières minutes avec chaque professeur sont gratuites.

Trouver un tuteur

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.

En l’ajoutant, tu en obtiens ta propre copie, avec tous ses sous-paquets. Chaque carte revient juste avant que tu ne l’oublies, et chaque réponse juste ou fausse contribue à ta maîtrise de son sujet. Une fois le paquet ajouté, tu peux supprimer ou suspendre les parties que tu n’étudies pas.

Contenu (88 sous-paquets)

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

Quelques-unes de ses cartes

  • 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

Et 696 de plus une fois le paquet ajouté.