OOP AND AOSD

OOP and AOSD

OOP and AOSD

Introduction

There are many issues that a software development team should determine its attention like understanding the problem, understand their environment, project management, team development, technical aspects, among others. Technical and security, persistence, presentation, error handling, etc. have given rise to aspect-oriented paradigm.

Object-oriented programming (OOP), or object-oriented programming is a paradigm of computer programming developed by Alan Kay in the 1970s. It involves the definition and interaction of software components called objects , an object represents a concept, idea or any entity in the physical world, like a car, person or even a page of a book. It has an internal structure and behavior, that knows how to communicate with peers. It is therefore to represent these objects and their relationships; communication between objects via their relationships allows the functionalities expected to resolve the problem or problems.

OOP enables software developers to write, so it is operated in the same way that the problem is modeled. Conventional programming languages are little more than a list of actions to be performed on a set of data in sequence. If at any point in the program, modify the structure of the data or the action performed on them, the program changes.

OOP provides a new approach, converting the data structure on which the operations . Thus, any modification of the data structure immediate effect on the actions to perform on it, being one of the radical differences with respect to structured programming.

For those not familiar with structured programming say that one of the foundations of this part of the design programmay vary up and down. In this form of design requirements are broken down step by step program, up to a level that would express through procedures and functions . OOP data structure objects that can store manipulate and combine information .

Over the past 35 years, designers of computer hardware fell from machine the size of a shed in small notebooks based on minuscule microprocessors. During the same years, software developers switched from writing programs in assembler and COBOL programs to writing even greater in C and C + +. We can speak of progress (although this is debatable), but it is clear that the software world is not progressing as fast as the hardware. What the developers of hardware and the software developers do not have? The answer is given by the components. If the engineers had electronic equipment from a pile of sand each time they design a new system, if their first step is to extract the silicon to fabricate integrated circuits, they would not progress very quickly. However, a hardware designer always builds a system from components prepared, each loaded with a particular function and providing a range of services through defined interfaces. The task of the designers of hardware is greatly simplified by the work of their predecessors. Reuse is also a way to create better software. Even today, software developers are still using some form of sand ...