Object-oriented Programming (OOP) / Event-Driven Programming (EDP) versus Procedural Programming

OOP and EDP vs. PP Object-oriented Programming and Event-Driven Programming versus Procedural Programming While there are many different types and styles of programming, at the end of the day it is up to the programmer to determine which type of programming will be used to best fit the desired end-state of the project at hand. Throughout this document, I will be covering Object- Oriented Programming (OOP), Event-Driven Programming (EDP) and Procedural Programming (PP). The difference between procedural programming and object-oriented programming is that in procedural programming, the focus is on breaking down a single task into a group of subroutines, variables and data structures, whereas in object-oriented programming the focus is on breaking down the same task into objects. These will use interfaces to expose behavior and data. The most important distinction is that while procedural programming uses procedures to operate on data structures, object-oriented programming bundles the two together, so an 'object', which is an instance of a class, operates on its 'own' data structure.” (Stevenson, 2004). “Terminology invoking 'objects' and 'oriented' in the modern sense of object-oriented programming made its first appearance at MIT in the late 1950s and early 1960s. In the environment of the artificial intelligence group, as early as 1960, “object” could refer to identified items (LISP atoms) with properties (attributes); Alan Kay was later to cite a detailed understanding of LISP internals as a strong influence on his thinking in 1966” (Armstrong, 2006). According to Farrel (2013), Object-oriented programming is used when the desired endstate is a modular, reusable software system like Microsoft Outlook, Word and Powerpoint. One major benefit for many companies from using Object-oriented programming is that it can save