The Pros and Cons of Object-Oriented Software Engineering
The Pros and Cons of Object-Oriented Software Engineering If we trace our steps down the spiraling routes of software history, searching for the origin of the object oriented programming, we will notice that it was back in 1967 that the first object-oriented ideas emerged. The advent of these new concepts took place in the context of the language Simula67, which was created in order to satisfy the growing need that the scientific community was experiencing with regard to a language for a simulation modeling. However, a gradual evolution, which spanned more than 20 years, could be observed before the new object oriented approach became widely applied. Ever since its origin about four decades ago, the object technologies have been gradually replacing the classical software development approaches, and it was in the 90-ies, that object-oriented software engineering turned into the paradigm of choice for the majority of software builders. Naturally, the question concerning the reason for this gradual transition to object-oriented technologies is to arise and there is still no clear-cut answer to it. Some people simply speculate that most software professionals crave for novelties in the software engineering arena,
A class can simultaneously be a subclass of another class and a super class for its own subclasses. The use of ADT permits each module to have a high degree of semantic cohesion. This memory was fixed; it could neither grow nor shrink. You know what a procedural program looks like: data definitions and function calls. So it is controversial if the augmented design time is a benefit or a disadvantage. Encapsulation helps achieve this goal. During design many new objects invariably appear to facilitate the implementation of some computer specific problems. By providing another, higher level of abstraction, object-oriented programming languages give you a larger vocabulary and a richer model to program in. Abstract data types work almost exactly like built-in types: You can create variables of a type (called objects or instances in object-oriented parlance) and manipulate those variables (called sending messages or requests; you send a message and the object figures out what to do with it). This is a more flexible and powerful language abstraction than what we have had before. The object-oriented approach is sometimes called a revolution, since it requires a new way of conceptualizing about software development. To use a function that belongs to an object, you first create the object (thus giving it its internal data structure), then you tell the object which function it should invoke. This limitation has been overcome by the concept of dynamic loading. Encapsulation keeps the implementation of an object out of its interface. These days, these efficiency penalties seem to be of relatively little importance compared with the software engineering benefits.
Common topics in this essay:
Engineering Approach,
Dataflow Diagrams,
Inheritance Using,
Software Engineering,
Polymorphism Polymorphism,
Classes Objects,
Objects Functions,
Fortran BASIC,
Dynamic Loading,
Encapsulation Information,
object-oriented programming,
software engineering,
base class,
object oriented,
super class,
object-oriented software,
software development,
object-oriented software engineering,
abstract data,
derived class,
data types,
abstract data types,
object oriented programming,
derived class type,
class super class,
|
Acceptance Essays
