Programutveckling och systemdokumentation

Kommittébeteckning: SIS/TK 611 (Informationsteknik)
Källa: ISO
Svarsdatum: den 21 dec 2022
Se merSe mindre
 

This part of ISO/IEC/IEEE 15026 specifies the concept of integrity levels with corresponding integrity level requirements that are required to be met in order to show the achievement of the integrity level.
Requirements and recommended methods are provided for defining and using integrity levels and their corresponding integrity level requirements. This document covers systems, software products, and their elements, as well as relevant external dependences.
This part of ISO/IEC/IEEE 15026 is applicable to systems and software and is intended for use by:
a) definers of integrity levels such as industry and professional organizations, standards organizations, and government agencies;
b) users of integrity levels such as developers and maintainers, suppliers and acquirers, system or software users, assessors of systems or software and administrative and technical support staff of systems and/or software products.
One important use of integrity levels is by suppliers and acquirers in agreements; for example, to aid in assuring safety, financial, or security characteristics of a delivered system or product.
This part of ISO/IEC/IEEE 15026 does not prescribe a specific set of integrity levels or their integrity level requirements. In addition, it does not prescribe the way in which integrity level use is integrated with the overall system or software engineering life cycle processes. It does, however, provide an
example of use of this part of ISO/IEC/IEEE 15026 in Annex A.

Kommittébeteckning: SIS/TK 611 (Informationsteknik)
Källa: ISO
Svarsdatum: den 25 jan 2023
Se merSe mindre
 

This part of ISO/IEC 19770 establishes a set of terms and definitions which describe hardware components. It also provides specifications for a transport format which enables the digital encapsulation of this data. An encapsulation of HWID data will be referred to as a HWID tag, just as ISO/IEC 19770-2 refers to SWID tags for software identification.

Kommittébeteckning: SIS/TK 611 (Informationsteknik)
Källa: ISO
Svarsdatum: den 25 jan 2023
Se merSe mindre
 

The stated and implied needs of stakeholders relating to information systems are represented as quality models in the SQuaRE series. Quality models enumerate the range of quality characteristics that should be considered as potential requirements for target entities including information systems,
ICT products, data, and IT services. This document establishes a framework for defining quality models which are composed from quality characteristics and subcharacteristics. In particular, this document provides:
— the concept of a quality model,
— definitions of quality model terms,
— the structure and semantics of quality models,
— the relationship between quality models and the other concepts, including measurement, requirement definition, and evaluation, and
— guidelines and examples for using quality models.

Kommittébeteckning: SIS/TK 611 (Informationsteknik)
Källa: ISO
Svarsdatum: den 25 jan 2023
Se merSe mindre
 

This document defines a product quality model, which is applicable to ICT products and software products. The product quality model is composed of nine characteristics (which are further subdivided into subcharacteristics) that relate to quality properties of the products. The characteristics and
subcharacteristics provide consistent terminology and reference model for the quality of the products to be specified, measured and evaluated.
NOTE 1 “product” is used for the same meaning as “ICT product and software product”.
This model can be used for requirements specification and evaluation of the target products’ quality throughout their lifecycle by several stakeholders, including developers, acquirers, quality assurance and control staff and independent evaluators. Activities during product lifecycle that can benefit from the use of this model include:
— eliciting and defining product and information system requirements;
— validating the comprehensiveness of requirements definition;
— identifying product and information system design objectives, and design necessary process for
achieving quality;
— identifying product and information system testing objectives;
— identifying quality control criteria as the part of quality assurance;
— identifying acceptance criteria for a product and/or an information system;
— establishing measures of product quality characteristics in support of these activities.

Kommittébeteckning: SIS/TK 611 (Informationsteknik)
Källa: ISO
Svarsdatum: den 25 jan 2023
Se merSe mindre
 

As information system (ICT products, software, data) and IT services are widely used, the target of their effect and influence of using them can extend from their direct users to organizations and society. To control the effect and influence as much as possible is a social responsibility of enterprises and public/ society administrations.
This document defines a quality-in-use model composed of three characteristics (which are further subdivided into subcharacteristics) that can influence stakeholders when products or systems are used in a specified context of use. This model is applicable to the entire spectrum of information system and IT service system, including both computer systems in use and software products in use.
This document provides consistent terminology for a set of quality characteristics for specifying, measuring, evaluating and improving quality-in-use.
The purpose of the "quality-in-use” model is to represent the effects and influences that can be experienced by using information system and IT service system; that is, to define, measure, evaluate and improve the quality of systems and software products and IT services when using them. Quality-inuse can be influenced by many factors including the quality of software, data and IT services.
Context of use is defined as "combination of users, goals and tasks, resources, and environment". If context of use changes, effect and influence on a stakeholder also changes.
Such context of use changes is to be monitored through quality evaluation from views of quality-inuse characteristics/subcharacteristics so that changes/gaps from initially specified context of use are identified and fed back to the next quality improvement cycle.
In this document, as prerequisite of quality-in-use is specified context of use, context of use is necessary to be re-specified to change prerequisite when a product or service intend to fulfill to context of use changes.
The model can, for example, be used by developers, acquirers, quality assurance and control staff, and independent evaluators, particularly those responsible for specifying and evaluating software product
quality. Activities during product development that can benefit from the use of the quality model can include, but are not limited to:
— identifying requirements for information system and IT service system in use;
— validating the comprehensiveness of a quality-in-use requirements specification;
— identifying information system and IT service system design objectives for quality-in-use;
— identifying quality-in-use control criteria as part of overall quality assurance;
— identifying acceptance criteria for information system and IT service system or information
systems;
— establishing measures to address the consequences of using products in specified context-of -use;
— present evaluation items for ethics considerations when using information system and IT service
system; and

— support governance of digitalization activities.