Modularity, from Their Side

Today’s lecture went over software modularity. Specifically, we got to learn about concept design. This involves three steps

  • 1) Name the Concept
  • 2) Say the Purpose
  • 3) Explain the Operational Priciple
  • I never knew that designing a user interface (front-end) involves such meticulous process. It is very eye-opening, and I can’t help but see a parallelism between code modularity (in OOP) and concept design.

    When developing an object, we first want to define the scope of the program. This is somewhat analogous to naming a concept. For example, if I want to some sort of program that helps me to process of database, I would name such a class something related to “data_processor”.

    After we’ve defined the scope, we can start adding attributes. This step here is similar to saying the purpose of a concept. Python-ically, it is like adding dunder methods to a class. The focus here is to give an overview of what the class is capable doing, just like informing users of what the concept does in concept design.

    Finally, we can actually define the attributes by adding code and docstring, thereby fulfilling each method’s functionality. This step is like explaining the operational principle of each concept. We are able to see what how each concept works and how it’s used to fulfill its purpose, just like in OOP.

    Overall, the lecture today is quite insightful. It helps me to see that many things related to software development can be interdisciplinary. I look forward to the next lecture.