Przejdź do treści

Eduqas GCSE Computer Science

GCSE · EduqasComputer Science706 fiszek

706 fiszek, przygotowane przez cookie, w 88 podzestawach z tematami zgodnymi z kursem.

Ucz się z tych kart

Wybrane dla tego samego kursu na podstawie tego, z czego ludzie najczęściej korzystają. Wszystko można przeczytać bez konta.

Wszystko dla Computer Science

Szukasz pomocy z Computer Science?

Cookie Tutoring, nasza własna usługa korepetycji, może mieć korepetytorów z przedmiotu Computer Science. Lekcje odbywają się na żywo i indywidualnie, a pierwsze 15 minut z każdym korepetytorem jest bezpłatne.

Znajdź korepetytora

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.

Dodając zestaw, otrzymasz własną kopię wraz ze wszystkimi podzestawami. Każda fiszka będzie wracać tuż przed tym, jak miałbyś(-abyś) ją zapomnieć, a każda odpowiedź dobra lub zła wpłynie na poziom opanowania danego tematu. Gdy zestaw będzie już twój, możesz usunąć lub zawiesić te części, których się nie uczysz.

Co zawiera (88 podzestawów)

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

Niektóre fiszki z tego zestawu

  • 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

I jeszcze 696, gdy dodasz talię.