Differences

This shows you the differences between two versions of the page.

--- java:object-orientation_fundamentals [2020/09/11 21:59] – [Prototype-based object-orientation] mithat
+++ programming_general:object-orientation_fundamentals [2020/09/14 00:08] – [Why object-orientation?] mithat
@@ Line 9: / Line 9: @@
 But why objects?
-OOAD was created to try to solve some of the issues involved in designing and managing large applications. It represents a shift in the way you typically approach a problem using procedural/structured programming thinking. With procedural/structured programming thinking, a developer will typically think in terms of, "What needs to _happen_." It tends to focus on creating a set of functions or subroutines to do the things that need to get done. If you like, it's modularity derives primarily from the "verbs" in the system.
+OOAD was created to try to solve some of the issues involved in designing and managing large applications. It represents a shift in the way you typically approach a problem using procedural/structured programming thinking. With procedural/structured programming thinking, a developer will typically think in terms of, "What needs to //happen//?" It tends to focus on creating a set of functions or subroutines to do the things that need to get done. The modularity in procedural/structured programming derives primarily from the "verbs" in the system.
-In object-oriented thinking, you start with, "What are the components (objects) that make up the problem?" Once you identify those. Once you have a those, you then ask, "How do they behave?" and then, "How do the components interact?" The modularity in object-oriented thinking derives primarily from the "nouns" in the system.
+In object-oriented thinking, you start with, "What are the components (objects) that make up the problem?" Once you identify those, you then ask, "How do they behave?" and then, "How do the components interact?" The modularity in object-oriented thinking derives primarily from the "nouns" in the system.
-While it is possible to analyze and design systems (i.e., applications) using this approach and implement the design in any language, the implementation is made _much_ easier and more robust when the language has the necessary support for defining and using objects. Such a language is an **object-oriented language**.
+While it is possible to analyze and design systems (i.e., applications) using this approach and implement the design in any language, the implementation is made //much// easier and more robust when the language has the necessary support for defining and using objects. Such a language is an **object-oriented language**.
 So, OOAD facilitates a higher level of modular thinking. And, especially with an object-oriented language, it allows for very effective project management of large applications.