object oriented life cycle model in software engineering

Object Oriented Life Cycle Model

While not strictly a software life cycle model. Object Oriented development employs an object oriented strategy. Object Oriented software engineering is also gearing up (Jacobson 1992).

The primary activities are:

Notice that much of the testing phases and certain aspects of the other phases follow and traditional approaches. The main difference between Object-oriented development and other development life cycles is in the modelling of the system components. Other development life cycles operated on a separation of events and data, while the object oriented model development encapsulate the events for the specific data for which the data is valid.

Object oriented analysis develops an object-oriented model of the application domain. Object-oriented design develops an object-oriented model of the software system. object-oriented programming realize the software design with an object-oriented programming language that support direct implementation of objects, classes, and inheritance.

There are a wide range of methodologies that have been proposed common to almost all of the methodologies are.

• Object identification- system objects and their characteristics and events.
• Object organisation- shows how objects are related via ‘part-of’ relationships.
• Object interface- shows how objects interact with each other.

The requirements analysis stage strives to achieve an understanding of the client’s application domain. The tasks that a software solution must address emerge in the course of the requirements analysis.

The requirements analysis phase remains completely independent of the implementation technique that might be applied later.

In the system specification phase the requirements definition describes what the software product must do, but not how’s this goal is to be achieved.

One point of divergence from conventional phase model arises because implementation with the 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 classes provided by one project can increase the productivity in subsequent projects.

Newly created classes must be tested for their general usability. If there is the chance that a component could be used in other projects as well, it must be included in the class library and documented accordingly. This also meals that the new class must be announced and made accessible to other programmers who might profit from it. This places new requirements on the in-house communication structures.

Advantages:

• 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
• Design and implementation become more closely.
• Duration of the implementation phase is reduced.
• A new job title emerges, the class librarian, who is responsible for ensuring the efficient usability of the class library.

Originally published at https://www.csmates.com.