Skip to main content
Engineering LibreTexts

9.10: Data Encapsulation

  • Page ID
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \) \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)\(\newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\) \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\) \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\) \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\) \( \newcommand{\Span}{\mathrm{span}}\) \(\newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\) \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\) \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\) \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\) \( \newcommand{\Span}{\mathrm{span}}\)\(\newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    Chapter 16 demonstrates a development plan we might call “object-oriented design.” We identified objects we needed—Time, Point and Rectangle—and defined classes to represent them. In each case there is an obvious correspondence between the object and some entity in the real world (or at least a mathematical world).

    But sometimes it is less obvious what objects you need and how they should interact. In that case you need a different development plan. In the same way that we discovered function interfaces by encapsulation and generalization, we can discover class interfaces by data encapsulation.

    Markov analysis, from Section 13.8, provides a good example. If you download my code from, you’ll see that it uses two global variables—suffix_map and prefix—that are read and written from several functions.

    suffix_map = {}        
    prefix = ()            

    Because these variables are global we can only run one analysis at a time. If we read two texts, their prefixes and suffixes would be added to the same data structures (which makes for some interesting generated text).

    To run multiple analyses, and keep them separate, we can encapsulate the state of each analysis in an object. Here’s what that looks like:

    class Markov(object):
        def __init__(self):
            self.suffix_map = {}
            self.prefix = ()    

    Next, we transform the functions into methods. For example, here’s process_word:

        def process_word(self, word, order=2):
            if len(self.prefix) < order:
                self.prefix += (word,)
            except KeyError:
                # if there is no entry for this prefix, make one
                self.suffix_map[self.prefix] = [word]
            self.prefix = shift(self.prefix, word)        

    Transforming a program like this—changing the design without changing the function—is another example of refactoring (see Section 4.7).

    This example suggests a development plan for designing objects and methods:

    1. Start by writing functions that read and write global variables (when necessary).
    2. Once you get the program working, look for associations between global variables and the functions that use them.
    3. Encapsulate related variables as attributes of an object.
    4. Transform the associated functions into methods of the new class.

    Exercise \(\PageIndex{1}\)

    Download my code from Section 13.8 (, and follow the steps described above to encapsulate the global variables as attributes of a new class called Markov.

    Solution: (note the capital M).

    This page titled 9.10: Data Encapsulation is shared under a CC BY-NC-SA 3.0 license and was authored, remixed, and/or curated by Allen B. Downey (Green Tea Press) .

    • Was this article helpful?