Object-oriented Life Cycle Model - Software Engineering

The Object-Oriented Approach to Building Systems takes the objects as the basis. For this, first, the system to be developed is observed and analyzed, and the requirements are defined as in any other method of system development. Once this is often done, the objects in the required system are identified. For example, in the case of a Banking System, a customer is an object, a checkbook is an object, and even an account is an object. The object-oriented model employs an object-oriented strategy. The primary objectives are:

1. Object-oriented analysis: Object-oriented analysis develops an object-oriented model of the application domain.
2. Object-oriented design: Object-oriented design develops an object-oriented model of the software system.
3. Object-oriented programming: Object-oriented programming realizes the software design with an object-oriented programming language that supports the direct implementation of objects, classes, and inheritance.

There are a variety of object-oriented methodologies such as:

1. Object Identification: System objects and their characteristics and events.
2. Object Organization: Shows how objects are related via "part-of" relationships.
3. Object Interfaces: Shows how objects interact with other objects.

These activities tend to overlap and in general parallel.

The requirements analysis stage strives to achieve an understanding of the client's application domain. The task that a software solution must address emerge in the course of requirement analysis. The requirement analysis phase remains completely independent of any implementation technique that might be applied later.

In the system specification stage, the wants' definition describes what the software product must do, but not how this goal is to be achieved.

One point of divergence from conventional phase model arises because implementation with object-oriented programming is marked by the assembly of already existing components. The class library serves as a tool that extends beyond the scope of an individual project because class provided by one project can increase productivity in subsequent projects.

Advantages of Object-Oriented Life Cycle Model

1. Design is no longer carried out independently of the later implementation because during the design phase we must consider which components are available for the solution of the problem.
2. Design and implementation become more closely associated.
3. Duration of the implementation phase is reduced.
4. A new job title emerges, the class librarian, who is responsible for ensuring the efficient usability of the class library.