Zum Inhalt springen

Eduqas GCSE Computer Science

GCSE · EduqasComputer Science706 Karten

706 Karteikarten, erstellt von cookie, in 88 Unterdecks, die den Kursthemen folgen.

Diese Karteikarten lernen

Für denselben Kurs ausgewählt, basierend darauf, was am häufigsten genutzt wird. Alles lässt sich ohne Konto lesen.

Alles für Computer Science

Suchst du Hilfe für Computer Science?

Cookie Tutoring, unser eigener Nachhilfedienst, hat möglicherweise Nachhilfelehrkräfte für Computer Science. Der Unterricht findet live und einzeln statt, und die ersten 15 Minuten bei jeder Lehrkraft sind kostenlos.

Nachhilfelehrkraft finden

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.

Wenn du das Deck hinzufügst, erhältst du eine eigene Kopie mit allen Unterdecks. Jede Karte kommt kurz bevor du sie vergessen würdest wieder. Jede richtige oder falsche Antwort zählt dafür, wie gut du das jeweilige Thema beherrschst. Sobald das Deck dir gehört, kannst du Teile, die du nicht lernst, löschen oder aussetzen.

Was ist enthalten (88 Unterdecks)

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

Einige Karten daraus

  • 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

Und 696 weitere, sobald du das Deck hinzufügst.