in the context of software engineering, software quality refers to two related but distinct notions that exist wherever quality is defined in a business context: * software functional quality reflects how well it complies with or conforms to a given design, based on functional requirements or specifications. that attribute can also be described as the fitness for purpose of a piece of software or how it compares to competitors in the marketplace as a worthwhile product;pressman, scott (2005), software engineering: a practitioner's approach (sixth, international ed.), mcgraw-hill education  * software structural quality refers to how it meets non-functional requirements that support the delivery of the functional requirements, such as robustness or maintainability, the degree to which the software was produced correctly. structural quality is evaluated through the analysis of the software inner structure, its source code, at the unit level, the technology level and the system level, which is in effect how its architecture adheres to sound principles of software architecture outlined in a paper on the topic by omg. in contrast, functional quality is typically enforced and measured through software testing. historically, the structure, classification and terminology of attributes and metrics applicable to software quality management have been derived or extracted from the iso 9126-3 and the subsequent iso 25000:2005 quality model, also known as square. based on these models, the consortium for it software quality (cisq) has defined five major desirable structural characteristics needed for a piece of software to provide business value: reliability, efficiency, security, maintainability and (adequate) size. software quality measurement quantifies to what extent a software or system rates along each of these five dimensions. an aggregated measure of software quality can be computed through a qualitative or a quantitative scoring scheme or a mix of both and then a weighting system reflecting the priorities. this view of software quality being positioned on a linear continuum is supplemented by the analysis of "critical programming errors" that under specific circumstances can lead to catastrophic outages or performance degradations that make a given system unsuitable for use regardless of rating based on aggregated measurements. such programming errors found at the system level represent up to 90% of production issues, whilst at 
Software_quality Software_testing Source_code Systems_thinking