Programming Paradigms (OCR A Level Computer Science)

Revision Note

Callum Davies

Expertise

Computer Science

Programming Paradigms

  • Programming paradigms are established conventions and practices that dictate how computer programs are structured and developed

  • Programming paradigms offer varied methodologies for software construction

  • Different paradigms are suited to different tasks, e.g. simple web applications can be achieved with light-weight procedural languages, complex enterprise-level software can only be achieved with a complex object-oriented paradigm

  • New paradigms arise, and existing ones adapt in response to changes in computing and software challenges

Overview of Programming Paradigms

Paradigm

Description

Examples of Languages

Key Concepts

Procedural

A subtype of imperative, structured around procedure calls.

C, Go, Rust

Procedures, function calls, structured programming

Object-Oriented

Organises code around "objects" (which combine data and functionality) rather than functions.

Java, C#, Swift

Classes, inheritance, polymorphism, encapsulation

Assembly

Low-level mnemonic representation of machine code for a specific computer architecture.

x86-64 Assembly, ARMv8 Assembly

Registers, mnemonics, memory addresses, opcodes

Strengths & Weaknesses of Programming Paradigms

Paradigm

Strengths

Weaknesses

Procedural

  • Efficient execution of straightforward tasks

  • A clear flow of control (top to bottom)

  • Ease of implementation for algorithms

  • Strong emphasis on step-by-step procedure execution

  • Can become unwieldy for large programs

  • Lack of modularity can lead to code redundancy

  • Not ideal for applications with complex states or behaviours

  • Difficulty in managing and scaling the system as it grows

Object-Oriented

 

  • Enhances modularity with encapsulation

  • Enables real-world modelling using objects

  • Code reuse through inheritance

  • Polymorphism allows flexibility in interface design

  • Can lead to unnecessary complexity

  • Inefficiency due to overhead (e.g., memory for objects)

  • Not always intuitive for all types of problems

  • Misuse can lead to overly complex inheritance hierarchies

Assembly

  • Direct control over hardware

  • Optimised performance due to low-level operations

  • A transparent understanding of how the machine operates

  • Potential for very efficient code

  • Extremely steep learning curve

  • Hardware-specific, leading to a lack of portability

  • Tedious and error-prone due to manual memory management.

  • Difficult to write, debug, and maintain large programs

You've read 0 of your 0 free revision notes

Get unlimited access

to absolutely everything:

  • Downloadable PDFs
  • Unlimited Revision Notes
  • Topic Questions
  • Past Papers
  • Model Answers
  • Videos (Maths and Science)

Join the 100,000+ Students that ❤️ Save My Exams

the (exam) results speak for themselves:

Did this page help you?

Callum Davies

Author: Callum Davies

Callum is an experienced teacher of GCSE and A-Level Computer Science. He has 4 years of teaching experience and has detailed knowledge of how to achieve exam success, having marked for OCR A-Level. Callum is now a software engineer and regularly mentors new engineers.