Similarities between Structured programming and object oriented programming?

Answer 1

Both types of programming utilize algorithms when processing data. Procedural and object oriented programming will also logically compute the tasks assigned to it using different programming languages.

Answer 2

The most fundamental concepts in object-oriented programming languages are 1) abstraction, 2) encapsulation, 3) inheritance, and 4) polymorphism.

These four concepts can each take a chapter by themselves, so just very briefly in practical terms:

Abstraction is a concept that allows you to 'abstract' the actual manipulation of data/objects/code and synthesize it into instructions of business logic. For example, Car->Start();

Encapsulation allows you to encapsulate data and methodsinto containers to prevent them from interfering with similar data and methods of a different nature other. For example, you might have a method named Start() for your car, and a method named Start() for your stove. To prevent the namespaces from colliding, these go into containers/objects/classes as such: Car->Start(); and Oven->Start();

Inheritance is the idea of letting an object inherit properties from another object. For example, the object Lamborghini inherits all the properties and methods from the object Car.

Polymorphism is the ability of objects to dynamically adapt themselves to another container. This is the most complicated of the concepts and it's a very poor explanatory statement.

Structured programming languages aren't object-oriented - they are function-oriented, so they have none of the attributes above. Those are the key differences.

For more information, I recommend you read a good C++/Smalltalk/Java tutorial. Like for examplehttp://www.desy.de/gna/html/cc/Tutorial/...

Answer 3

Structured programming can be thought of as using a series of steps and simple constructs to solve a problem. At a basic level, consider writing a set of instructions for a factory worker assembling a widget. These instructions might look like:

1. Attach part 'a' to part 'b' and call that part 'ab'

2. Attach part 'c' to part 'd' and call that part 'cd'

3. Attach part 'ab' to part 'cd'

4. Put the widget in the box

5. Ship the widget

6. Repeat

In this scenario, the problem is solved by a linear, repetition of events performed by an external actor.

Object oriented programming, on the other hand models the object that being worked on. Instead of giving a list of instructions to an external actor, the widget would be given the ability to construct itself. While it is a different way of thinking than people are generally used to applying to problem solving, it is ultimately much more flexible than a structured methods.

Answer 4

In structured programming...the idea was that the overall flow of control of the program was laid out using a function call hierarchy - sort of like an inverted tree. The main routine was at the top and then called routines branched out in successive layers under that. When these functional "trees" were implemented as skeleton code without any real business logic or other body, this was called "Top Down" programming, because the tree was implemented from the "top down" to give it structure, before any of the detail was filled in. In this way the overall flow and structure of a progam can be tested before being overwhelmed by detail.

Object Oriented programming doesn't think of a single flow of control through the program. Instead, real-world business entities in the problem space are implented as individual objects with (a) their own data and (b) their own behaviour. The progam is then put together by implementing logical flow of control from object to object, with each one doing "it's own thing" and then calling on other objects to "do their own thing". In this way, it's hoped that overall functionality within the program is encapsulated and divided up logically so that each bit can be implemented separately and, hopefully, re-used in other programs.

Answer 5

Structures encapsulate only data whereas objects capture both data and behavior in the form of methods.