The main metrics for software quality management are:

• Code Quality: To ensure good quality software we need to ensure the good quality of the code. The more efficient the code more efficient will be the software as it manages how the software is going to behave when the user is going to interact with it.

• Reliability: It defines that the software should be able to provide the services when a user wants to use it. If you have made software for shopping then it should be able to dot that otherwise, it is not reliable.

• Performance: It defines how is the performance of the software you have built. It tells whether your software is able to manage a large number of requests and a large chunk of data at the same time. It also determines the speed of your software means how fast your software is working.

• Usability: It means whether the user is able to use the software easily or not. It is related to the design of the software and how easily the user is able to navigate through the software.

• Correctness: Your software should do exactly the same thing that is built for. If your system is not able to perform the required task then it can be declared as the incorrect software. For example, you have made software that converts image text to readable text but if not able to do it then we can question the correctness of the software.

• Maintainability: Software quality is also related to the management of the software as time passes. We should build software that is easily maintainable and easy to understand by other team members.

• Integrity: Software should be integral and its behaviour, interface and design should determine this. It means the user should not feel that one part of your software is not connected to other parts of the software.

• Security: Security of the data, users, and the system is to be taken care of and the software will be made secured to negate the possibility of a cyber attack. User data should be encrypted as well.

These things can maintain the software quality.

Object-Oriented Design:

Object-oriented design works around the entities and their characteristics instead of functions involved in the software system. This design strategies focus on entities and their characteristics. The whole concept of software solutions revolves around the engaged entities. 

Concepts of the Object-Oriented Approach:

Objects – All entities involved in the solution design are known as objects. For example, people, banks, companies and customers are treated as objects. Every entity has some attributes associated with it and has some methods to perform on the attributes.

Classes – A class is a generalized description of an object. An object is an instance of a class. Class defines all the attributes, which an object can have and methods, which define the functionality of the object.

In the solution design, attributes are stored as variables and functionalities are defined by means of methods or procedures.

Encapsulation – In OOD, the attributes (data variables) and methods (operation on the data) are bundled together is called encapsulation. Encapsulation not only bundles important information of an object together but also restricts access to the data and methods from the outside world. This is called information hiding.

Inheritance – OOD allows similar classes to stack up in a hierarchical manner where the lower or sub-classes can import, implement and re-use allowed variables and methods from their immediate superclasses. This property of OOD is known as inheritance. This makes it easier to define specific classes and to create generalized classes from specific ones.

Polymorphism – OOD languages provide a mechanism where methods performing similar tasks but vary in arguments, can be assigned the same name. This is called polymorphism, which allows a single interface performing tasks for different types. Depending upon how the function is invoked, the respective portion of the code gets executed