Over deze norm
||Software and systems engineering
NEN-ISO/IEC 25051 is applicable to Ready to Use Software Product (RUSP). In this International Standard, the term ?RUSP? is used as an adjective and stands for ?Ready to Use Software Product?. NOTE 1 Examples of Ready to Use Software Product (RUSP) include but are not limited to text processors, spreadsheets, database control software, graphics packages, software for technical, scientific or real-time embedded functions, human resources management software, sales management, smartphone application, freeware and web software such as generators of websites/pages. NOTE 2 Open source software is not part of Ready to Use Software Product (RUSP). This International Standard establishes: a) Quality requirements for Ready to Use Software Product (RUSP); b) Requirements for test documentation for the testing of Ready to Use Software Product (RUSP), including test plan, test description, and test results; NOTE The collection of documents for test is called ?test documentation?. c) Instructions for conformity evaluation of Ready to Use Software Product (RUSP). It includes also recommendations for safety or business critical Ready to Use Software Product (RUSP). This International Standard deals only with providing the user with confidence that the Ready to Use Software Product (RUSP) will perform as offered and delivered. It does not deal with the production realization (including activities and intermediate products, e.g. specifications). The quality system of a supplier is outside the scope of this International Standard. The intended users of this International Standard include: a) suppliers when: 1) specifying requirements for a Ready to Use Software Product (RUSP); 2) assessing their own software products against the claimed performance; 3) issuing declarations of conformity (ISO/IEC 17050); 4) applying for certificates or marks of conformity (ISO/IEC Guide 23); b) certification bodies that may wish to establish a certification scheme (international, regional or national) (ISO/IEC Guide 28); c) testing laboratories which will have to follow the instructions for testing when testing for a certificate or a mark of conformity (ISO/IEC 17025); d) accreditation bodies for accrediting registration or certification bodies and testing laboratories; e) potential acquirers who may: 1) compare the requirements for the intended work task with the information in product descriptions of existing software products; 2) look for certified Ready to Use Software Product (RUSP); 3) check if the requirements are otherwise met; f) end users who may profit from better software products; g) organizations: 1) establishing management and engineering environments based on the quality requirements and methods of this International Standard; and 2) managing and improving their quality processes ?and personnel?. h) regulatory authorities who may require or recommend the requirements of this International Standard for Ready to Use Software Product (RUSP) used in safety or business-critical applications.