IEEE 1465-1998 pdf download Adoption of International Standard ISO/IEC 12119: 1994(E) Information Technology—Software packages—Quality requirements and testing
2.1 function: The implementation of an algorithm inthe program with which the user or the program canperform part or all of a work task.
NOTES
1A function does not need to be callable by the user (e.g. automaticbackup or saving of data).
The notion of a function here is narrower than that used in ISO2382-14:1978 (n the definitions of failure, fault, maintenance and reliability), but wider than those defined in ISO 2382-2 and ISO 2382-15
2.2 requirements document: A document contain-ing any combination of recommendations，requirements or regulations to be met by a software package
NOTE – Exaples are a technicaor ergonomic standard, a requirements list (or model requirements specification) from a group (e.g. amarket sector, technical or user association), a law or a decree.
2.3 product description: A document stating properties of a software package, with the main purpose othelping potential buyers in the evaluation of the suitability for themselves of the product beforepurchasing it.
NOTE – This term is more specific than the term “system descriptionin ISO/EC 2382-20:1990. The purpose of the product descriptionincludes that of the “cover information” in ISO 9127. The product description is not a specification; it serves a different purpose.
2.4 user documentation: The complete set of docu-ments, available in printed or non-printed form, that isprovided for the application of the product and also isan integral part of the product.
2.5 package documentation: The product description and the user documentation.
2.6 test case: A documented instruction for thetester that specifies how a function or a combination offunctions shall or should be tested. A test case in-cludes detailed information on the following issues:
the test objective;
the functions to be tested;
the testing environment and other conditions(confiquration details and preparatory work);
27maintenance: That part of system maintenance(see A.5.2) which is concerned with modifying a soft-ware package.
3 Quality requirements
Subclauses 3.1 to 3.3 contain
the requirement that each software packagehas a product description and user documentation;
requirements for the product description. Inparticular, there is a requirement that it shall con-tain specified information and that all its statements shall be testable and correct;
requirements for the user documentation:
requirements for the programs and for data, ifany, included in the software package.
NOTES
The requirements on user documentation, programs and datacontain many general requirements (independent from what may bepromised in a product description), but they do not include all theproperties that users may desire.
UCertain properties, for example “understandability” and “ease ofoverview’ of the user documentation and of the program messages, areadmittedly required in the view of the user. However, due to thedifficulty of testing for them with clear-cut and reproducible resultsthese are formulated currently as recommendations only.
The requirements in 3.1 to 3.3 are arranged in the same order asthe characteristics which appear in ISOVEC 9126
A software package conforms to this internationalStandard if it complies with all the requirements in 3.1to 3.3. The recommendations (indicated by the use ofthe verbal form “should”) are optional.
NOTE 4 – Conformity of a product to the requirements in 3.1 to 3.3 maybe difficult or impossible to prove. However, a test (including review ofdocuments) according to clause 4 is deemed sufficient to provide theconfidence required for a certificate of conformity according to 1SO/IECGuide 2. No formal proof is needed.
IEEE 1465-1998 pdf download
PS:Thank you for your support!
