Procedural versus Object Oriented Languages
- Procedural: High performance, supporting functions of math, logic, and animation; can be platform-specific
- Object-oriented: Enables the development of complex or distributed applications; can be used to produce reusable objects (an object in this case is a small sub-routine).
- Data Manipulation Language: Provides direct access to DBMS; creates both read and write access to the database
- Scripting languages: Easy to learn and have average performance in terms of complexity of functionality; can contribute to screen functions within a browser
- Markup languages: Support the display of text or objects; standardized to be multi-platform
Object Oriented Software Development
Although many people find this bit of information surprising, object-oriented (OO) software development has been around since the early 1960s. Objects are now used throughout the software development industry.
It is no secret that the software industry can be slow-moving at times. It is also true that, when systems are working fine,
there has to be a compelling reason to replace them.
This has somewhat slowed the propagation of OO systems.There are many non-OO legacy systems
(that is, older systems that are already in place) that are doing the job so why risk potential disaster by changing them?
In most cases you should not change them, at least not simply for the sake of change.
There is nothing inherently wrong with systems written in non-OO code.
However, new development definitely warrants the consideration of using OO technologies.
Although there has been a steady and significant growth in OO development in the past 15 years, the continued reliance on the Internet has helped catapult it even further
into the mainstream.
The emergence of day-to-day business transactions on the Internet has opened a brand-new arena, where much of the software development is new and
mostly unencumbered by legacy concerns. Even when there are legacy concerns, there is a trend to wrap the legacy systems in object wrappers.
Procedural programming is a programming paradigm, derived from structured programming, based upon the concept of the procedure call. Procedures, also known as routines, subroutines, methods, or functions contain a series of computational steps to be carried out.
Any given procedure might be called at any point during the execution of a program, including by other procedures or itself.
Procedural programming is a list or set of instructions telling a computer what to do step by step and how to perform from the first code to the second code.
Procedural programming is a term used to denote the way in which a computer programmer writes a program.
This method of developing software revolves around keeping code as concise as possible.
It also focuses on a very specific end result to be achieved. Imperative programming is another term used to signify this type of development and it is mandatory that a program complete certain steps to achieve specific results, the code is said to have been written according to procedural programming.
Software developers who program according to this concept usually write a preliminary plan in plain language prior to actually writing code.
Procedural programming often is taught to beginner students of computer science because of the logic behind it.
They are encouraged to think in terms of a series of necessary steps that must be taken to accomplish a goal.