update OOD chapter

Author: rambasnet

notebooks/ObjectOrientedDesign.ipynb

@@ -30,21 +30,24 @@
     "\n",
     "- the process of converting requirements into an implementation specification\n",
     "- name the objects, define the behaviors, and their interactions with each other\n",
-    "- transforming *what* should be done into *how* \n",
+    "- transforming *what* should be done into *how* using OOP\n",
+    "\n",
+    "## Objects and Classes\n",
+    "- *object* is a collection of data with associated behaviors\n",
+    "- *class* is a kind or *type* of object\n",
+    "- Unified Modeling Language (UML) is commonly used to design the classes and their interactions\n",
     "\n",
     "## Object-oriented programming (OOP)\n",
     "- process of converting a design into a working program that does what the product owner originally requested\n",
+    "- use OOP concepts to implement the OOD\n",
+    "\n",
+    "## Software Development Models\n",
     "- some popular development models are: **waterfall**, **iterative**, **agile**, etc.\n",
     "- **waterfall** is the traditional model where each phase is completed before the next phase begins\n",
     "- **agile** is a more modern model where focus is on delivering working software in short iterations\n",
     "    - ci-cd (continuous integration, continuous deployment) is a popular agile model\n",
     "    - scrum, kanban, pair programming, etc. are popular agile methodologies\n",
-    "    - focus is on delivering working software quickly and frequently as a team effort with high customer satisfaction\n",
-    "\n",
-    "## Objects and Classes\n",
-    "- *object* is a collection of data with associated behaviors\n",
-    "- *class* is a kind or *type* of object\n",
-    "- Unified Modeling Language (UML) is commonly used to design the classes and their interactions"
+    "    - focus is on delivering working software quickly and frequently as a team effort with high customer satisfaction\n"
    ]
   },
   {