Object Oriented System Development

The key motivating factor in the invention of object-oriented strategy is to salvage some of the flaws encountered in the procedural strategy. Developments in computer software technologies continues to be dynamic. New tools and methods are announced in fast succession. This has forced the software program industry and software package engineers to continuously appear for new approaches to software design and development, which is becoming much more and a lot more critical in view of the rising complexity of software package systems as well as the extremely competitive nature of the business. Software program engineers have been attempting different tools, methods, and procedures to manage the procedure of software program development in order to construct high-good quality software program with improved productivity.

The object-oriented paradigm draws heavily on the general systems theory as a conceptual background. A method can be viewed as a collection of entities that interact together to achieve certain objectives. Entities may represent physical objects such as gear and people, and abstract concepts such as information files and functions. In object-oriented analysis, the entities are named the objects. As the name indicates, the object-oriented paradigm places higher emphasis on the objects that encapsulate information and procedures. They play the central function in all the stages of the software program development and consequently there exists a high degree of overlap and iteration among the stages. The entire development process becomes evolutionary in nature. Any graphical representation of the object-oriented version of the software package development life cycle must consequently take into account these two elements of overlap and iteration. The result is a “fountain model” in place of the classic “water fall model”.

Object-oriented analysis (OOA) refers to the strategies of specifying specifications of the software package in terms of actual-planet objects, their behaviour, and their interactions. Object-oriented style (OOD) on the other hand, turns the software program requirements into specifications foe objects and derives class hierarchies from which the objects can be developed. Finally, Object-oriented programming (OOP) refers to the implementation of the programs using objects, in an object-oriented programming language, such as C++.

OOA provides us with a simple, but strong, mechanism for identifying objects, the constructing blocks of the software to be developed. The evaluation is basically concerned with the decomposition of a issue into its component parts and establishing a logical model to describe the system functions.

OOD is concerned with the mapping of objects in the issue space into objects in the solution space and generating an overall structure and computational models of the program. This stage generally utilizes the bottom-up method to build the structure of the program and the best-down functional decomposition approach to design the class member functions that give services. It is specifically crucial to construct structured hierarchies, to determine abstract classes, and to simplify the inner-object communications. Reusability of classes from the previous designs, classification of the objects into subsystems and determination of suitable protocols are some of the considerations of the style stage.