Informējam, ka Sistēma pielāgota darbam ar interneta pārlūkprogrammu Internet Explorer (8. un jaunākām versijām) un Mozilla Firefox (3.6 un jaunākām versijām).
Izmantojot citu interneta pārlūkprogrammu, brīdinām, ka Sistēmas funkcionalitāte var tikt traucēta.
<p>ISO/IEC TR 9126-3:2003<i> </i>provides internal metrics for measuring attributes of six external quality characteristics defined in ISO/IEC 9126-1. ISO/IEC TR 9126-2<i> </i>defines external metrics, ISO/IEC TR 9126-3:2003 defines internal metrics and ISO/IEC 9126-4 defines quality in use metrics, for measurement of the characteristics or the subcharacteristics. Internal metrics measure the software itself, external metrics measure the behaviour of the computer-based system that includes the software, and quality in use metrics measure the effects of using the software in a specific context of use.</p>
<p>The metrics listed in ISO/IEC TR 9126-3:2003<i> </i>are not intended to be an exhaustive set. Developers, evaluators, quality managers, maintainers, suppliers, users and acquirers may select metrics from ISO/IEC TR 9126-3:2003<i> </i>for defining requirements, evaluating software products, measuring quality aspects and other purposes.</p>
<p>Users of ISO/IEC TR 9126-3:2003<i> </i>can select or modify and apply metrics and measures from ISO/IEC TR 9126-3:2003 or may define application-specific metrics for their individual application domain. For internal metrics view, there are pure internal metrics proposed for reference purposes.</p>
<p>ISO/IEC TR 9126-3:2003<i> </i>is intended to be used together with ISO/IEC 9126-1.</p>
<p>ISO/IEC TR 9126-3:2003<i> </i>contains:</p>
<ul><li>an explanation of how to apply software quality metrics;</li><li>a basic set of metrics for each subcharacteristic;</li><li>an example of how to apply metrics during the software product life cycle.</li></ul>
<p>ISO/IEC TR 9126-3:2003<i> </i>does not assign ranges of values of these metrics to rated levels or to grades of compliance, because these values are defined for each software product or a part of the software product, by its nature, depending on such factors as category of the software, integrity level and users' needs. Some attributes may have a desirable range of values, which does not depend on specific user needs but depends on generic factors; for example, human cognitive factors.</p>
Reģistrācijas numurs (WIID)
22891
Darbības sfēra
<p>ISO/IEC TR 9126-3:2003<i> </i>provides internal metrics for measuring attributes of six external quality characteristics defined in ISO/IEC 9126-1. ISO/IEC TR 9126-2<i> </i>defines external metrics, ISO/IEC TR 9126-3:2003 defines internal metrics and ISO/IEC 9126-4 defines quality in use metrics, for measurement of the characteristics or the subcharacteristics. Internal metrics measure the software itself, external metrics measure the behaviour of the computer-based system that includes the software, and quality in use metrics measure the effects of using the software in a specific context of use.</p>
<p>The metrics listed in ISO/IEC TR 9126-3:2003<i> </i>are not intended to be an exhaustive set. Developers, evaluators, quality managers, maintainers, suppliers, users and acquirers may select metrics from ISO/IEC TR 9126-3:2003<i> </i>for defining requirements, evaluating software products, measuring quality aspects and other purposes.</p>
<p>Users of ISO/IEC TR 9126-3:2003<i> </i>can select or modify and apply metrics and measures from ISO/IEC TR 9126-3:2003 or may define application-specific metrics for their individual application domain. For internal metrics view, there are pure internal metrics proposed for reference purposes.</p>
<p>ISO/IEC TR 9126-3:2003<i> </i>is intended to be used together with ISO/IEC 9126-1.</p>
<p>ISO/IEC TR 9126-3:2003<i> </i>contains:</p>
<ul><li>an explanation of how to apply software quality metrics;</li><li>a basic set of metrics for each subcharacteristic;</li><li>an example of how to apply metrics during the software product life cycle.</li></ul>
<p>ISO/IEC TR 9126-3:2003<i> </i>does not assign ranges of values of these metrics to rated levels or to grades of compliance, because these values are defined for each software product or a part of the software product, by its nature, depending on such factors as category of the software, integrity level and users' needs. Some attributes may have a desirable range of values, which does not depend on specific user needs but depends on generic factors; for example, human cognitive factors.</p>
