1. Software Quality Assurance (SQA) is simply a way to assure quality in the It is the set of activities which ensure processes, procedures as well as standards are suitable for the project and implemented correctly. Software Quality Assurance is a process which works parallel to development of software.

Advantages of software metrics for assuring software quality:

Productivity: One of the most valuable aspects of an app is fast data processing. The less time it spends on performing the tasks, the better. Some metrics help to increase and track the project’s productivity and solve urgent issues.

Decision making: Such metrics can come in handy when estimating the influence of the decisions made. PMs and CEOs can sort out objectives, priorities, and avoid impulsive resolutions. It helps them to make deliberate compromises, optimize the project, and achieve the goals of software quality assurance.

Data sorting: You can use metrics to reduce misunderstandings and ambiguities in complex projects. Through the software organization, you will get objective information.

Priorities: With metrics, managers will no longer have difficulties while tracking, identifying, or prioritizing the project’s issues. They can communicate at all the organization’s levels.

Progress management: Is the project meeting the schedule? Is everything going well? It is important to control the work’s progress and result, and always have answers to these questions. Such metrics show the software product’s status as well as its quality and changes it in.

Management strategy: There are some risks that you have to instantly estimate, control, and prioritize. Metrics help to manage such issues and avoid future costly solutions. They determine errors and correct technical parts of the project as well as facilitate management strategies.

1. Object-oriented software engineering metrics are units of measurement that are used to characterize: object-oriented software engineering products, e.g., designs source code, and the test cases. object-oriented software engineering processes, g., designing and coding.

Object-oriented development including the following:

• Attributes and classes of objects: Data and its states are Attributes define the data that characterize classes.
• Classes with attributes and methods: These are essential factors for describing and structuring software programs. Classes define the variables and methods common to all objects of a certain
• Cohesion: Is a measure of how logically related are the parts of an individual component (class) to each other, and to the overall.
• Coupling: Is a measure of the strength of the connection between any two system components such as classes.
• Interfaces: These are lists of
• Inheritance: Is the process by which one object acquires characteristics from one or more other
• Message: Means of communication and interaction between
• Method: Operations that manipulate or process
• Objects: These are instances of
• Object identity: Objects are unique and have a storage

Metrics for the Analysis Model-
These metrics are used to examine the analysis model with the objective of predicting the size of the resultant system. Size acts as an indicator of increased coding, integration, and testing effort; sometimes it also acts as an indicator of complexity involved in the software design. Function point and lines of code are the commonly used methods for size estimation.

Function Point (FP) Metric:
The function point metric, which was proposed by A.J Albrecht, is used to measure the functionality delivered by the system, estimate the effort, predict the number of errors, and estimate the number of components in the system.

Lines of Code (LOC):

Lines of code (LOC) is one of the most widely used methods for size estimation. LOC can be defined as the number of delivered lines of code, excluding comments and blank lines. It is highly dependent on the programming language used as code writing varies from one programming language to another.

Metrics for design model-
The success of a software project depends largely on the quality and effectiveness of the software design. Hence, it is important to develop software metrics from which meaningful indicators can be derived. With the help of these indicators, necessary steps are taken to design the software according to the user requirements. Various design metrics such as architectural design metrics, component-level design metrics, user-interface design metrics, and metrics for object-oriented design are used to indicate the complexity, quality, and so on of the software design.

Architectural Design Metrics:
These metrics focus on the features of the program architecture with stress on architectural structure and effectiveness of components (or modules) within the architecture.

Many software quality indicators that are based on measurable design characteristics of a computer program have been proposed. One of them is Design Structural Quality Index (DSQI), which is derived from the information obtained from data and architectural design. To calculate DSQI, a number of steps are followed, which are listed below.

1. To calculate DSQI, the following values must be determined.

Number of components in program architecture (S1)
Number of components whose correct function is determined by the Source of input data (S2)
Number of components whose correct function· depends on previous processing (S3)
Number of database items (S4)
Number of different database items (S5)
Number of database segments (S6)
Number of components having single entry and exit (S7).