ISO/IEC 25000:2014 provides guidance for the use of the new series of International Standards named Systems and software Quality Requirements and Evaluation (SQuaRE). The purpose of ISO/IEC 25000:2014 is to provide a general overview of SQuaRE contents, common reference models and definitions, as well as the relationship among the documents, allowing users of the Guide a good understanding of those series of standards, according to their purpose of use. It also contains an explanation of the transition process between the old ISO/IEC 9126 and the ISO/IEC 14598 series and SQuaRE.
This standard contributes to the following Sustainable Development Goal: 9 Industry, Innovation and Infrastructure Buy this standard en Format Language std 1 145 PDF + ePub English std 2 145 Paper English CHF145 Buy
Buy this standard Life cycle Previously Withdrawn ISO/IEC 25000:2005 Now Published ISO/IEC 25000:2014 A standard is reviewed every 5 yearsStage: 90.93 (Confirmed) 00 Preliminary 10 Proposal 20 Preparatory 30 Committee 40 Enquiry 40.99 2013-08-05 Full report circulated: DIS approved for registration as FDIS 50 Approval 50.00 2013-08-23 Final text received or FDIS registered for formal approval 50.20 2013-09-18 Proof sent to secretariat or FDIS ballot initiated: 8 weeks 50.60 2013-11-20 Close of voting. Proof returned by secretariat 60 Publication 60.00 2013-12-13 International Standard under publication 60.60 2014-03-14 International Standard published 90 Review 90.20 2019-01-15 International Standard under systematic review 90.60 2019-06-05 Close of review 90.93 2020-06-11 International Standard confirmed 90.20 International Standard under systematic review 90.60 Close of review 90.99 Withdrawal of International Standard proposed by TC or SC 95 Withdrawal 95.99 Withdrawal of International Standard Got a question?Check out our FAQs
Download Free Iso Iec 25000
The series of standards ISO/IEC 25000, also known as SQuaRE (System and Software Quality Requirements and Evaluation), has the goal of creating a framework for the evaluation of software product quality.
ISO/IEC 25000 is the result of the evolution of several other standards; specifically from ISO/IEC 9126, which defines a quality model for software product evaluation, and ISO/IEC 14598, which defines the process for software product evaluation. The series of standards ISO/IEC 25000 consists of five divisions.
The SQALE method has been developed to answer a generic and permanent need for assessing the quality of source code. Standards like ISO 9126 and ISO/IEC 15939 do not provide effective support for this challenge, and that's why ISO 25000 was created for.
The SQALE method is particularly devoted to the management of the Technical Debt (or Design Debt) of software developments and it conforms to ISO 25000. It allows: - To define clearly what creates the technical debt - To estimate correctly this debt - To analyse this debt upon technical and business perspective - To offer different prioritisation strategies allowing establishing optimised payback plan.
During the software lifecycle, the maintenance of the software is usually the biggest overall expense, totaling even up to 90 percent of all life cycle costs [1] . Knowing this, it is rather surprising, that the software development processes do not focus more on the maintenance phase. Instead development processes focus to enhance and offer product quality and quality-in-use improvements within the development and quality assurance steps. For example, the Scrum software process model which is favored in many SME organizations [2] , does not take into account any activities which happen before or after the active sprints, even though majority of the software related costs are not realized within this period. This issue is glaring for example in the game software development, where the current business models such as live-ops or any other free-2-play model [3] , mean that basically all profits are generated during the maintenance period, not at the commitment to develop software or after delivery.
Some activity models, such as continuous delivery (CD) [4] or DevOps [5] promote more thorough integration of maintenance activities into the development activities, but the runtime monitoring and control of the quality characteristics supporting maintenance are not included. Actions such as the delivery of hotfixes, patches or customer-tailored features are part of the continuous release cycle, where development and maintenance are concurrent activities, with the development phase being one iteration ahead of the maintenance phase. However, the general infrastructure in this area is not very systematically studied. In more abstract terms, technical evaluation of the software quality is not very straightforward, since the maintenance issues and quality assurance needs are usually related to the preferred quality: Usually quality assurance during maintenance assesses, if the software system delivers the expected features or services, and achieves the necessary quality requirements. However, there are several different types of quality involved [6] , and if we consider quality models such as defined by the ISO/IEC 25000-family [7] , there are tens of different measurements and methods to assess the quality and quality-in-use from different perspectives.
The ISO/IEC 9126 model is probably the most applied standardized model but it is not the most current or extensive standard in existence. The ISO/IEC 25000 Software Quality Requirements and Evaluation (SQUARE) model [7] in its core is the upgraded version of the ISO/IEC 9126 model, with the added definitions for quality in software product, and a separate model for software quality-in-use. Overall, the objective of the ISO/IEC 25000 standard family is to clarify the requirements, which should be identified to assess the software quality and ensure the success on the evaluation and reaching of the set quality objectives. Overall, the models cover 5 characteristics with 11 sub-characteristics for the quality-in-use, and 8 characteristics with 31 sub-characteristics for software product quality. These models and their characteristics are summarized in Figure 1 and Figure 2.
The metrics library consists of different testing methods. These methods are collected from previous experiences and research work with the software industry, from different models, for example, Swebok [27] , Test Process Improvement (TPI) model [28] and Test Maturity Model integration (TMMi) model [29] . The objective of the library is to offer a wide list of different testing techniques and tools, and recommend at least one feasible approach for evaluating any ISO/IEC 25000 family model characteristic.
This work begun by using the ISO/IEC 25,000 software quality and software quality-in-use models as the starting point. In the presented framework, we have covered examples of quality characteristics of the models. The limitations are related to quality-in-use characteristics that have an inherent subjective nature. For example, it is difficult to quantify user trust, pleasure or comfort through source code, but indirect run-time measurements may give useful information. Quality characteristics like freedom from risk or security can only partly be covered.
Illuminator HXP 200C (D) inclusive built-in power supply 310W, lamp module, infrared filter, CAN-BUS cable and country-specific mains cord. Fluorescence light source with integrated shutter with trigger capability (5V TTL), that works stepper motor controlled, fast and vibration free. With CAN interface for remote control of the shutter
Cold light source CL 1500 HAL - up to 600lm light flux at 9mm optical output dia., continuous electronically dimming, - LCD display for brightness in % or color temperature in K or power-on hours, - incl. bulb 15V 150W halogen reflector, lifetime ca. 150h at 80%=450lm, - 10mm clamping nut with sensor for light guide 1500, - filter slider for one filter d=28mm and with free opening, - max. 180W wide-range supply for flicker free light, silent axial fan, - country-specific mains cord
Cold-light source CL 6000 LED (D) - up to 600 lm light flux at 9 mm fiber output dia., ca. 6200K color temperature - min. 50,000 operating hours until intensity drop to 70% - control of intensity and 6 memory cells by rotary push knob and LCD - 10 mm collet chuck with sensor for 1500 light guides - filter slider for 2 mounted filters 35x26x4 mm and with free opening - max. 70W wide-range supply for flicker free light, silent fan - 2.5 mm jack bush for on/off via optional foot button S, USB socket - country-specific mains cord - Dimensions D241xW192xH118 mm, weight 3.1 kg
Cold-light source CL 9000 LED CAN (D) - up to 900 lm light flux at 9 mm fiber output dia., ca. 6500K color temperature - min. 50,000 operating hours until intensity drop to 70% - control of intensity and 6 memory cells by rotary push knob and LCD - 10 mm collet chuck with sensor for 1500 light guides - filter slider for 2 mounted filters 35 x 26 x 4 mm and with free aperture - max. 80W wide-range supply for flicker free light, silent fan - 2.5 mm jack bush for on/off via optional foot button S - BNC socket for trigger input - 2 CAN RJ45 sockets for light control by EMS 3 - CAN RJ45 cable 1 m, country-specific power cable - Dimensions D241xW192xH118 mm, weight 3.1 kg
Illuminator HXP 120 V (D) inclusive built in power supply, lamp module and infrared filter. Fluorescence light source with motorized brightness switch and integrated motorized shutter, that works stepper motor controlled, fast and vibration free. With CAN connection for switching the shutter and the motorized brightness switch via ZEN (blue edition) and ZEN 2 (black edition). Interfaces: - 1x CAN (CAN-HD15) - 1x Trigger in (BNC) - 1x Trigger out (BNC) - 1x EXT (BNC) for remote control unit The package includes light guide, cable BNC and cable CAN. 2ff7e9595c
Opmerkingen