Thinking Procedurally (OCR A-Level Computer Science): Flashcards
📚Flashcards
Practise the cards
12 cards from this deck
ShowHide
Practise the cards
12 cards from this deck
Computational thinking
Computational thinking
Breaking complex problems into smaller, manageable parts
Components of a problem (definition)
Components of a problem (definition)
Individual elements or tasks making up a larger problem
Purpose of identifying problem components
Purpose of identifying problem components
Clarifies what needs solving & ensures nothing overlooked
Components of a solution (definition)
Components of a solution (definition)
Individual steps/modules that work together to solve the problem
Purpose of breaking solution into components
Purpose of breaking solution into components
Makes implementation and testing more manageable
3 key elements in problem statement
3 key elements in problem statement
Inputs, processes, and expected outputs
What structure charts show
What structure charts show
Hierarchy of modules & how program parts interact
What flowcharts represent
What flowcharts represent
Flow of processes or decisions in a solution
What pseudocode provides
What pseudocode provides
High-level outline of solution in language-agnostic format
Common mistake: overlooking dependencies
Common mistake: overlooking dependencies
Not recognising component interactions leads to incomplete solutions
Common mistake: early implementation focus
Common mistake: early implementation focus
Jumping to coding before identifying components causes errors
Common mistake: ignoring constraints
Common mistake: ignoring constraints
Failing to account for data limits/input formats causes errors