Object Oriented Analysis and Design

Object-Oriented Analysis (OOA) is the first technical activity performed as part of object-oriented software engineering. OOA introduces new concepts to investigate a problem. It is based on a set of basic principles, which are as follows-

1. The information domain is modeled.
2. Behavior is represented.
3. The function is described.
4. Data, functional, and behavioral models are divided to uncover greater detail.
5. Early models represent the essence of the problem, while later ones provide implementation details.

The above notes principles form the foundation for the OOA approach. 

Object-Oriented Design (OOD): An analysis model created using object-oriented analysis is transformed by object-oriented design into a design model that works as a plan for software creation. OOD results in a design having several different levels of modularity i.e., The major system components are partitioned into subsystems (a system-level “modular”), and data manipulation operations are encapsulated into objects (a modular form that is the building block of an OO system.). In addition, OOD must specify some data organization of attributes and a procedural description of each operation. Shows a design pyramid for object-oriented systems. It is having the following four layers.

1. The Subsystem Layer : It represents the subsystem that enables software to achieve user requirements and implement technical frameworks that meet user needs.
2. The Class and Object Layer : It represents the class hierarchies that enable the system to develop using generalization and specialization. This layer also represents each object.
3. The Message Layer : It represents the design details that enable each object to communicate with its partners. It establishes internal and external interfaces for the system.
4. The Responsibilities Layer : It represents the data structure and algorithmic design for all the attributes and operations for each object.

The Object-Oriented design pyramid specifically emphasizes specific product or system design. Note, however, that another design layer exists, which forms the base on which the pyramid rests. It focuses on the core layer the design of the domain object, which plays an important role in building the infrastructure for the Object-Oriented system by providing support for human/computer interface activities, task management.

Some of the terminologies that are often encountered while studying Object-Oriented Concepts include:

1. Attributes: a collection of data values that describe a class.

2. Class: encapsulates the data and procedural abstractions required to describe the content and behavior of some real-world entity. In other words,  A class is a generalized description that describes the collection of similar objects.

3. Objects: instances of a specific class. Objects inherit a class’s attributes and operations.

4. Operations: also called methods and services, provide a representation of one of the behaviors of the class.

5. Subclass: specialization of the super class. A subclass can inherit both attributes and operations from a super class.

6. Superclass:  also called a base class, is a generalization of a set of classes that are related to it.

Advantages of OOAD:

1. Improved modularity: OOAD encourages the creation of small, reusable objects that can be combined to create more complex systems, improving the modularity and maintainability of the software.
2. Better abstraction: OOAD provides a high-level, abstract representation of a software system, making it easier to understand and maintain.
3. Improved reuse: OOAD encourages the reuse of objects and object-oriented design patterns, reducing the amount of code that needs to be written and improving the quality and consistency of the software.
4. Improved communication: OOAD provides a common vocabulary and methodology for software developers, improving communication and collaboration within teams.

Disadvantages of OOAD:

1. Complexity: OOAD can add complexity to a software system, as objects and their relationships must be carefully modeled and managed.
2. Overhead: OOAD can result in additional overhead, as objects must be instantiated, managed, and interacted with, which can slow down the performance of the software.
3. Steep learning curve: OOAD can have a steep learning curve for new software developers, as it requires a strong understanding of OOP concepts and techniques.

My Personal Notes arrow_drop_up

Save