2 - Lists and Arrays: Structure and Introduction to Big O Notation — Topics & Learning Outcomes

Module Topics

Introduction to Lists and Arrays

• What Are Data Structures? — Data structures are organized ways of storing and managing data in a computer so that it can be accessed and modified efficiently.
• Defining Arrays — An array is a collection of elements stored in contiguous memory locations, all sharing the same data type.
• Defining Lists — A list is a flexible, ordered collection of elements that can typically grow or shrink in size and may allow elements of different types.
• Key Characteristics: Ordered and Indexed — Both lists and arrays are ordered, indexed collections, meaning each element has a specific position that can be referenced directly.
• Storing and Organizing Data — Lists and arrays are used to group related data together under a single variable name, making programs cleaner and more manageable.
• Arrays vs. Lists: Key Differences — While arrays and lists are conceptually similar, they differ in flexibility, memory management, and typical use cases.

Array Structure and Memory Layout

• What Is an Array? — An array is a fundamental data structure that stores a collection of elements of the same type under a single variable name.
• Contiguous Memory Storage — Arrays store their elements in contiguous, or back-to-back, blocks of memory, which is the defining characteristic of their internal layout.
• Zero-Based Indexing — Each element in an array is identified by an index, and most programming languages begin counting from zero rather than one.
• Direct Address Calculation — Because of contiguous storage and uniform element size, the memory address of any element can be computed instantly using a simple formula.
• Fixed Size and Static Allocation — A traditional array has a fixed size that must be declared at creation time and cannot change during program execution.
• Element Access vs. Search — Accessing an element by index is immediate, but finding an element by its value requires scanning through the array.

List Structure and Dynamic Behavior

• What Makes a List Dynamic — Unlike arrays, lists are dynamic data structures that can grow or shrink in size as elements are added or removed during program execution.
• Variable Sizing and Memory Allocation — Lists manage their own memory behind the scenes, abstracting away the complexity of tracking how much space is needed at any given time.
• Element Management in Lists — Lists provide built-in operations for adding, removing, and accessing elements, making element management more straightforward than with fixed-size arrays.
• Ordered Nature and Element Access — Lists maintain an ordered sequence of elements, meaning each element has a defined position or index that can be used to retrieve it.
• Flexibility for Diverse Data Storage — Lists are highly flexible containers that can store elements of varying types in many programming languages, making them adaptable for a wide range of use cases.
• Lists vs. Arrays: Key Structural Differences — While both lists and arrays store ordered collections of elements, they differ fundamentally in how they manage size, memory, and flexibility.

Core Data Operations on Lists and Arrays

• Accessing Elements — Accessing an element in a list or array involves retrieving a value stored at a specific position using an index.
• Searching for Elements — Search operations locate a specific value within a list or array by examining its contents.
• Inserting Elements — Insertion adds a new element into a list or array at a specified position, such as the beginning, end, or middle.
• Deleting Elements — Deletion removes an existing element from a list or array, requiring the structure to be updated to remain coherent.
• Comparing Operation Costs Across Positions — The efficiency of each core operation depends heavily on where in the list or array it is performed.
• Why These Operations Form the Basis of Efficiency Analysis — Access, search, insertion, and deletion are the foundational operations used to evaluate and compare the practical performance of data structures.

Introduction to Computational Complexity

• What Is Computational Complexity? — Computational complexity is the study of how the resources required by an algorithm — primarily time and memory — scale as the size of the input grows.
• Why Efficiency Matters as Input Grows — An algorithm that works acceptably on small datasets can become unusably slow or memory-intensive when applied to large ones, making scalability a critical concern.
• Input Size as the Key Variable — Computational complexity analysis centers on a variable — commonly written as n — that represents the number of elements or the size of the data being processed.
• Operations and Their Costs — Different operations performed on data structures — such as reading, inserting, deleting, or searching — each carry their own computational cost that can vary by structure type.
• Worst, Best, and Average Cases — When analyzing how long an operation takes, it is important to consider not just one scenario but the range of possible outcomes: the best case, worst case, and average case.
• The Purpose of Abstraction in Complexity — Computational complexity intentionally abstracts away hardware details, programming language specifics, and exact instruction counts to focus on fundamental growth patterns.

Big O Notation Fundamentals

• What Is Big O Notation? — Big O notation is a standardized mathematical language used to describe how the runtime or space requirements of an algorithm scale as the input size grows.
• O(1) — Constant Time Complexity — An algorithm runs in O(1) time when its execution time remains the same regardless of how large the input is.
• O(n) — Linear Time Complexity — An algorithm runs in O(n) time when its cost grows proportionally to the number of elements in the input.
• O(n²) — Quadratic Time Complexity — An algorithm runs in O(n²) time when its cost grows proportionally to the square of the input size, commonly caused by nested loops.
• Comparing Complexity Classes — Understanding how O(1), O(n), and O(n²) relate to each other allows developers to make informed decisions when choosing or designing algorithms.
• Dropping Constants and Non-Dominant Terms — Big O notation simplifies expressions by dropping constant multipliers and lower-order terms, keeping only the fastest-growing factor.
• Why Big O Matters for Lists and Arrays — Applying Big O thinking to list and array operations helps developers predict performance and avoid bottlenecks when working with data structures.

Applying Big O to List and Array Operations

• Access by Index: O(1) Constant Time — Accessing an element in an array or list by its index is one of the most efficient operations possible, classified as O(1) or constant time.
• Search: O(n) Linear Time — Searching an unsorted list or array for a specific value requires examining elements one by one, resulting in O(n) linear time complexity.
• Insertion and Deletion: Position Matters — The efficiency of inserting or deleting an element in an array or list depends heavily on where in the structure the operation occurs.
• Using Big O to Compare List and Array Operations — Big O notation provides a common language for directly comparing the efficiency of the same operation across different data structures.
• Reasoning About Efficiency Trade-offs — No single data structure is optimal for every operation; understanding Big O for lists and arrays allows students to reason about which trade-offs are acceptable for a given use case.

Student Learning Outcomes

By the end of this module, students will be able to:

Course Outcomes (reference)