The Object-Oriented approach of 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 chequebook is an object, and even an account is an object.
Object-oriented model employs an object-oriented strategy. The primary objectives are:
1. Object-oriented analysis, 2. Object-oriented design, 3. Object-oriented programming
Obiect-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 realizes the software design with an object-oriented programming language that supports direct implementation of objects, classes, and inheritance.
There are a variety of object-oriented methodologies such as:
- Object Identification:
System objects and their characteristics and events.
- Object Organization:
Shows how objects are related via “part-of” relationships.
- Object Interfaces:
Shows how objects interact with other objects.
These activities tend to be overlapping and in general and 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 an implementation technique that might be applied later.
In the system specification section, 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:
- 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 associated.
- 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.
- Software Engineering | Project size estimation techniques
- Types of Software Testing
- Software Testing | Basics
- Software Engineering | Architectural Design
- Software Engineering | Halstead’s Software Metrics
- Beta Testing | Software Testing
- Software Engineering | Debugging Approaches
- Pairwise Software Testing
- Software Engineering | COCOMO Model
- Software Engineering | Classification of Software Requirements
- Software Engineering | Classical Waterfall Model
- Software Engineering | Iterative Waterfall Model
- Software Engineering | Spiral Model
- Software Engineering | Requirements Engineering Process
- Software Engineering | Requirements Elicitation
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.