The standards and models used in software industry are extremely various in their approach. The process of producing software is being still very emphasized (by models like CMMI®, ISO 15504, by ISO 9001:2000, AQAP, ISO 12207, by project management methodologies and software development methodologies), but approaches concentrating on software product characteristics and metrics (like ISO 9126 family or CC) are also being more and more accepted, together with models and approaches emphasizing the importance of the human factor (e.g. P-CMM, PSP, TSP).

As no approach, model or standard covers all the aspects of software quality (although new versions of earlier models are definitely more broad in their scope, in the number of objects they are dealing with), software companies have to quit relying exclusively on one certain quality model - in favor of choosing among several approaches, using more approaches in a synergic way, according to the specific business needs of a certain organisation.

The tutorial focuses on the issues arising when using multiple quality models. Based on our practical experience, we present problems and give tips to overcome them when completing an ISO 9001:2000-based quality management system (that takes into account ISO 90003:2004 recommendations also) with elements required by the CMMI® model, to make the company CMMI® ML2-conform, and to continue the SPI to reach higher levels of maturity and / or capability. Next, we present ideas about combining the usage of CMMI® with the usage of Automotive SPICE™. We show, how software product quality issues can be addressed in a process-oriented quality framework. We present ideas about measuring different attributes of the important objects of software production, emphasizing the importance of building context-dependent quality profiles. In the end, we address the subject of PSP and TSP, and we argue in favor of investing into conformancy rather than accepting the cost of nonconformancy resulting from correcting errors.