Software Quality related

[0]

In a nutshell, software quality is "the degree to which software is consistent with the need for explicit and implicit definitions."

Specifically, software quality is the degree to which the software complies with clearly described functional and performance requirements, the development standards clearly described in the documentation, and the extent to which all specialized software development should be consistent with the implied features.

[1]

Software development is increasingly being done in accordance with established engineering and scientific principles. In order for software engineering to truly become a science discipline, the process and quantification of software products produced are often mandatory.

The first feature of the Software Quality Assurance feature defines the standard for software products developed in its organizational unit. The second major function of the Software Quality Assurance organization is the designation and implementation of tools or assistive tools for evaluating the quality of software products. The third major function of the Software Quality assurance organization is to apply these tools to assess the extent to which the software products developed by their organizational units comply with the standards that they have established for the product.

The following is a definition of some of the more common software quality factors:

Software Quality factors	Describe
Correctness	The degree to which the program satisfies its specifications and meets the user's task objectives.
Reliability	Scaling to a program can expect to perform its intended function with the desired precision.
Efficiency	The amount of compute resources and code required for the program to execute the function.
Integrity	You can control the extent to which unauthorized people access software or data.
Availability of	Learn, manipulate, prepare input and interpret program output for the effort required.
Maintainability	The effort required to locate and fix errors in the operating program.
Testability	The effort required to test the program to ensure that it performs its intended function.
Flexibility	The effort required to modify the operating procedure.
Portability	You need to transfer the program from one hardware configuration or software system environment to another hardware configuration or software system.
Re-usability	The extent to which programs can be used in other applications is related to the packaging and scope of the functions that the program performs.
Interoperability	The effort required to couple one system with another.

Tab 1 Quality factors and indicators

[2]

Software quality describes the required properties of the software. An in-depth understanding of the impact of software quality and quality on users helps to make users ' needs clearer. The user's dissatisfaction with these attributes affects the health and sustainability of the software. Lack of insight into the impact of software quality and software quality on users makes it impossible for stakeholders to ensure that users are satisfied with the software. The following is a study of the relationship between the quality of the software and the quality of the user experience, in order to evaluate the software products, functions and needs.

Software quality analysis provides an assessment of the quality of the software on a certain standard, but it does not describe the user's satisfaction with quality.

User feedback can reflect the user experience of using the software, but it does not reveal the software quality factors that affect the bad experience.

Unlike pure software quality analysis or pure user feedback, the combination of software quality analysis and user feedback reflects the level of software quality that can make users happy. Similarly, if users are dissatisfied, user feedback can help explain quality weaknesses in root-cause analysis.

a quality -impact assessment method is described below. This method periodically collects continuous usage logs, along with user feedback from different user groups. This method measures the user's experience quality during software use to identify how users perceive the quality of the software and how they can meet the functionality they provide.

as mentioned earlier, analysis of software quality and user-perceived quality is important for product owners to evaluate software products. The quality -impact approach identifies four processes, including preparation, measurement, analysis, and decision-making to determine the relationship between software quality and quality for the quality of user experience, and gain insight into the evaluation of software products, features, and requirements. The preparation process includes activities such as installation tools (i.e., analysis tools, feedback tools), and the development of user feedback requests. During the measurement process, data is collected about software quality measurement and user perceived quality (quality measurement is related to the perceived quality of the user during the analysis process). In this process, the qualitative analysis of user feedback is also performed to facilitate the interpretation of the correlation analysis. The analysis results are used in decision making processes to determine product functionality based on acceptable and desired quality levels.

This method periodically collects user feedback to measure the quality of experience of the user during use. The correlation analysis can then help the product owner to interpret the user's dissatisfaction by aligning it with the measured quality level.

to illustrate how the quality-impact approach works, the left part of Figure 1 presents a timeline-based scenario that highlights the events and activities involved in data collection and analysis.

starting the user experience, data collection is continuously started to collect usage logs, providing periodic user feedback requests to collect the quality of the user experience. The received user feedback and quality analysis helps to perform a correlation analysis between user acceptance quality and software quality, as well as qualitative user feedback analysis. the right part of Figure 1 shows an example of this correlation analysis.

Correlation analysis will be used to evaluate software product features and more. This analysis helps product owners assess user satisfaction or dissatisfaction with the quality level of the measurement and identify possible levels of quality that may interfere with the user in order to validate requirements. In addition, the analysis can be used to elicit the right level of quality by determining the acceptable impact.

The above is a simple interpretation of the quality-impact assessment method based on the correlation analysis between software quality and user experience quality.

The method needs to collect a lot of user feedback to achieve relevance analysis, which has a certain challenge.

Readers who want to delve deeper into this subject can read the literature:

[0] http://baike.baidu.com/link?url= Obrsu1kdvw623svjnvjfgv1qfte2eb01dozwq-euplhde74mrmjvbudqwouhp7qxiatmkzkzxhex22orxps9ctf01s9kw8apos02vtygnjeodkp-rsezvezg7 _60ra37

[1] J. E. Gaffney, "Metrics in software Quality Assurance", presented at Tutorial Abstract, ACM ' Bayi, November 9-11, 1981.

[2] F. Fotrousi, "quality-impact Assessment of Software Systems", presented at the IEEE 24th International Requirements En Gineering Conference, Karlskrona, Sweden, 2016.

Software Quality related