| Name |
Description |
Abstract |
Status |
Publication date |
Edition |
Number of pages |
Technical committee |
ICS |
| ISO/IEC TR 24772:2010 |
Information technology — Programming languages — Guidance to avoiding vulnerabilities in programming languages through language selection and use |
ISO/IEC TR 24772:2010 specifies software programming language vulnerabilities to be avoided in the development of systems where assured behaviour is required for security, safety, mission critical and business critical software. In general, this guidance is applicable to the software developed, reviewed, or maintained for any application. Vulnerabilities are described in a generic manner that is applicable to a broad range of programming languages.
|
Withdrawn |
2010-10 |
Edition : 1 |
Number of pages : 131 |
Technical Committee |
35.060
Languages used in information technology
|
| ISO/IEC TR 24772:2013 |
Information technology — Programming languages — Guidance to avoiding vulnerabilities in programming languages through language selection and use |
ISO/IEC TR 24772:2013 specifies software programming language vulnerabilities to be avoided in the development of systems where assured behaviour is required for security, safety, mission-critical and business-critical software. In general, this guidance is applicable to the software developed, reviewed, or maintained for any application.
Vulnerabilities are described in a generic manner that is applicable to a broad range of programming languages.
|
Withdrawn |
2013-03 |
Edition : 2 |
Number of pages : 319 |
Technical Committee |
35.060
Languages used in information technology
|
| ISO/IEC 25436:2006 |
Information technology — Eiffel: Analysis, Design and Programming Language |
ISO/IEC 25436:2006 provides the full reference for the Eiffel language.
Eiffel is a method of software construction and a language applicable to the analysis, design, implementation and maintenance of software systems. ISO/IEC 25436:2006 covers only the language, with an emphasis on the implementation aspects.
|
Published |
2006-12 |
Edition : 1 |
Number of pages : 172 |
Technical Committee |
35.060
Languages used in information technology
|
| ISO/IEC TR 25438:2006 |
Information technology — Common Language Infrastructure (CLI) — Technical Report: Common Generics |
The CLI standard libraries (ISO/IEC 23271) provide a collection of common types that can be used by multiple languages. With the addition of generics to the CLI, the standard libraries have been extended to include a number of common generic types, in particular, collections. However, at present, these libraries do not include many simple generic types found in a number of different languages. Any language which uses these common types must implement them rather than deferring to the CLI library, thereby reducing language inter-operability. ISO/IEC TR 25438:2006 addresses this issue by providing a number of these common types.
|
Published |
2006-08 |
Edition : 1 |
Number of pages : 63 |
Technical Committee |
35.060
Languages used in information technology
|
| ISO/IEC TS 29113:2012 |
Information technology — Further interoperability of Fortran with C |
ISO/IEC TS 29113:2012 specifies the form and establishes the interpretation of facilities that extend the Fortran language defined by ISO/IEC 15391:2010. The purpose of ISO/IEC TS 29113:2012 is to promote portability, reliability, maintainability and efficient execution of programs containing parts written in Fortran and parts written in C, for use on a variety of computing systems.
|
Withdrawn |
2012-12 |
Edition : 1 |
Number of pages : 54 |
Technical Committee |
35.060
Languages used in information technology
|
| ISO/IEC 29124:2010 |
Information technology — Programming languages, their environments and system software interfaces — Extensions to the C++ Library to support mathematical special functions |
ISO/IEC 29124:2010 specifies extensions to the C++ standard library as defined in the International Standard for the C++ programming language (ISO/IEC 14882:2003). ISO/IEC 29124:2010 specifies extensions to the C++ standard library to support mathematical special functions.
|
Withdrawn |
2010-09 |
Edition : 1 |
Number of pages : 21 |
Technical Committee |
35.060
Languages used in information technology
|
| ISO/IEC TR 29166:2011 |
Information technology — Document description and processing languages — Guidelines for translation between ISO/IEC 26300 and ISO/IEC 29500 document formats |
OASIS Open Document Format ODF 1.0 (ISO/IEC 26300) and Office Open XML (ISO/IEC 29500) are both open document formats for saving and exchanging word processing documents, spreadsheets and presentations. Both formats are XML based but differ in design and scope.
ISO/IEC TR 29166:2012 aims at analysing the two International Standards and their underlying concepts in terms of interoperability issues for a selected set of features. It analyses the way these features are implemented in both International Standards and estimates the degree of translatability between them using a table-based comparison. ISO/IEC TR 29166:2012 serves as a preliminary technical translation guideline for evaluating translatability between certain parts of the two International Standards. It does not compare different implementations which can cause additional kinds of interoperability problems.
It starts by studying common use cases to identify how the most important functionalities of one document format can be represented in the other format. This is followed by a thorough review of the concepts, architectures and various features of the two document formats in order to provide a good understanding of the commonalities and differences. It is expected that functionalities will be able to be translated with different degrees of fidelity to the other format. As an illustrative sample of this functionality, detailed information is provided on the extent to which those functionalities can be translated.
ISO/IEC TR 29166:2012 addresses both developers seeking to implement either ISO/IEC 26300 or ISO/IEC 29500 and template designers and other power users whose competences cut across the spectrum of XML and XML-related technologies which directly or remotely deal with one or both of the two International Standards. ISO/IEC TR 29166:2012 will be of great assistance to those seeking to exchange documents between formats, to extract data from or import data into documents, or to write applications supporting the two formats. ISO/IEC TR 29166:2012 is a necessary step to the goal of helping achieve interoperability and harmonization between the two formats. It should encourage standards bodies as well as the developers of office suites to translate some of the ideas into future versions of the standards and products.
|
Published |
2011-12 |
Edition : 1 |
Number of pages : 156 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 2382-7:1989 |
Information technology — Vocabulary — Part 7: Computer programming |
|
Withdrawn |
1989-10 |
Edition : 2 |
Number of pages : 24 |
Technical Committee |
35.080
Software
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 29500-1:2008 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 1: Fundamentals and Markup Language Reference |
ISO/IEC 29500-1:2008 defines a set of XML vocabularies for representing word-processing documents, spreadsheets and presentations, based on the Microsoft Office 2008 applications. It specifies requirements for Office Open XML consumers and producers that comply to the strict conformance category.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 5560 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-1:2008/Amd 1:2010 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 1: Fundamentals and Markup Language Reference — Amendment 1 |
|
Withdrawn |
2010-08 |
Edition : 1 |
Number of pages : 151 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-1:2008/Cor 1:2010 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 1: Fundamentals and Markup Language Reference — Technical Corrigendum 1 |
|
Withdrawn |
2010-05 |
Edition : 1 |
Number of pages : 173 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-1:2011 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 1: Fundamentals and Markup Language Reference |
ISO/IEC 29500-1:2011 defines a set of XML vocabularies for representing word-processing documents, spreadsheets and presentations, based on the Microsoft Office 2008 applications. It specifies requirements for Office Open XML consumers and producers that comply to the strict conformance category.
|
Withdrawn |
2011-08 |
Edition : 2 |
Number of pages : 5577 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-1:2012 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 1: Fundamentals and Markup Language Reference |
ISO/IEC 29500-1:2012 defines a set of XML vocabularies for representing word-processing documents, spreadsheets and presentations, based on the Microsoft Office 2008 applications. It specifies requirements for Office Open XML consumers and producers that comply to the strict conformance category.
|
Withdrawn |
2012-09 |
Edition : 3 |
Number of pages : 5018 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-1:2016 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 1: Fundamentals and Markup Language Reference |
ISO/IEC 29500-1:2016 defines a set of XML vocabularies for representing word-processing documents, spreadsheets and presentations. On the one hand, the goal of ISO/IEC 29500 is to be capable of faithfully representing the pre-existing corpus of word-processing documents, spreadsheets and presentations that had been produced by the Microsoft Office applications (from Microsoft Office 97 to Microsoft Office 2008, inclusive) at the date of the creation of ISO/IEC 29500. It also specifies requirements for Office Open XML consumers and producers. On the other hand, the goal is to facilitate extensibility and interoperability by enabling implementations by multiple vendors and on multiple platforms.
ISO/IEC 29500-1:2016 specifies concepts for documents and applications of both strict and transitional conformance.
|
Published |
2016-11 |
Edition : 4 |
Number of pages : 5024 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-2:2008 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 2: Open Packaging Conventions |
ISO/IEC 29500-2:2008 defines a general-purpose file/component packaging facility, which is built on top of the widely used ZIP file structure.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 129 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-2:2008/Cor 1:2010 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 2: Open Packaging Conventions — Technical Corrigendum 1 |
|
Withdrawn |
2010-05 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-2:2011 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 2: Open Packaging Conventions |
ISO/IEC 29500-2:2011 defines a general-purpose file/component packaging facility, which is built on top of the widely used ZIP file structure.
|
Withdrawn |
2011-08 |
Edition : 2 |
Number of pages : 129 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-2:2012 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 2: Open Packaging Conventions |
ISO/IEC 29500-2:2012 specifies a set of conventions that are used by Office Open XML documents to define the structure and functionality of a package in terms of a package model and a physical model.
|
Withdrawn |
2012-09 |
Edition : 3 |
Number of pages : 129 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-2:2021 |
Document description and processing languages — Office Open XML file formats — Part 2: Open packaging conventions |
This document defines a set of conventions for packaging one or more interrelated byte streams (parts) as a single resource (package). These conventions are applicable not only to Office Open XML specifications as described in ISO/IEC 29500-1 and ISO/IEC 29500-4, but also to other markup specifications.
|
Published |
2021-08 |
Edition : 4 |
Number of pages : 65 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-3:2008 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 3: Markup Compatibility and Extensibility |
ISO/IEC 29500-3:2008 defines a general-purpose mechanism to extend an XML vocabulary.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 40 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-3:2008/Cor 1:2010 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 3: Markup Compatibility and Extensibility — Technical Corrigendum 1 |
|
Withdrawn |
2010-05 |
Edition : 1 |
Number of pages : 4 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-3:2011 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 3: Markup Compatibility and Extensibility |
ISO/IEC 29500-3:2008 defines a general-purpose mechanism to extend an XML vocabulary.
|
Withdrawn |
2011-08 |
Edition : 2 |
Number of pages : 40 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-3:2012 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 3: Markup Compatibility and Extensibility |
ISO/IEC 29500-3:2012 describes a set of conventions that are used by Office Open XML documents to clearly mark elements and attributes introduced by future versions or extensions of Office Open XML documents, while providing a method by which consumers can obtain a baseline version of the Office Open XML document (a version without extensions) for interoperability.
|
Withdrawn |
2012-09 |
Edition : 3 |
Number of pages : 38 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-3:2015 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 3: Markup Compatibility and Extensibility |
This Part of ISO/IEC 29500 defines a set of conventions for forward compatibility of markup specifications, applicable not only to Office Open XML specifications as described in Parts 1 and 4 of this Standard, but also to other markup specifications. These conventions allow XML documents created by applications of later versions or extensions to be handled by applications of earlier versions.
|
Published |
2015-07 |
Edition : 4 |
Number of pages : 33 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-4:2008 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 4: Transitional Migration Features |
ISO/IEC 29500-4:2008 defines a set of XML elements and attributes, over and above those defined by ISO/IEC 29500-1, that provide support for legacy Microsoft Office applications; that is, those prior to the 2008 release. It specifies requirements for Office Open XML consumers and producers that comply to the transitional conformance category.
|
Withdrawn |
2008-11 |
Edition : 1 |
Number of pages : 1464 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-4:2008/Amd 1:2010 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 4: Transitional Migration Features — Amendment 1 |
|
Withdrawn |
2010-08 |
Edition : 1 |
Number of pages : 115 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-4:2008/Cor 1:2010 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 4: Transitional Migration Features — Technical Corrigendum 1 |
|
Withdrawn |
2010-05 |
Edition : 1 |
Number of pages : 35 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-4:2011 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 4: Transitional Migration Features |
ISO/IEC 29500-4:2011 defines a set of XML elements and attributes, over and above those defined by ISO/IEC 29500-1, that provide support for legacy Microsoft Office applications; that is, those prior to the 2008 release. It specifies requirements for Office Open XML consumers and producers that comply to the transitional conformance category.
|
Withdrawn |
2011-08 |
Edition : 2 |
Number of pages : 1569 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-4:2012 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 4: Transitional Migration Features |
ISO/IEC 29500-4:2012 defines features for backward-compatibility and that are useful for high-quality migration of existing binary documents to ISO/IEC 29500. These features are used only by documents of conformance class WML Transitional, SML Transitional, or PML Transitional.
|
Withdrawn |
2012-09 |
Edition : 3 |
Number of pages : 1534 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 29500-4:2016 |
Information technology — Document description and processing languages — Office Open XML File Formats — Part 4: Transitional Migration Features |
ISO/IEC 29500-4:2016 defines a set of XML vocabularies for representing word-processing documents, spreadsheets and presentations. On the one hand, the goal of ISO/IEC 29500 is to represent faithfully the existing corpus of word-processing documents, spreadsheets and presentations that have been produced by Microsoft Office applications (from Microsoft Office 97 to Microsoft Office 2008, inclusive). It also specifies requirements for Office Open XML consumers and producers. On the other hand, the goal is to facilitate extensibility and interoperability by enabling implementations by multiple vendors and on multiple platforms.
ISO/IEC 29500-4:2016 defines features for backward-compatibility and that are useful for high-quality migration of existing binary documents to ISO/IEC 29500. These features are used only by documents of conformance class WML Transitional (§2.1), SML Transitional (§2.1), or PML Transitional (§2.1). These features are sometimes needed for high-quality migration of existing binary documents to ISO/IEC 29500.
|
Published |
2016-11 |
Edition : 4 |
Number of pages : 1533 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC TR 30114-1:2016 |
Information technology — Extensions of Office Open XML file formats — Part 1: Guidelines |
ISO/IEC TR 30114-1:2016 gives guidelines for the use of extensibility mechanisms in ISO/IEC 29500 (Office Open XML). In particular, it makes clear which of these mechanisms supports lossless round tripping.
|
Published |
2016-12 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 30114-2:2018 |
Information technology — Extensions of Office Open XML file formats — Part 2: Character repertoire checking |
ISO/IEC 30114-2:2018 provides an extension of OOXML for embedding CREPDL scripts within an OOXML document, and validating character contents in the OOXML document against these CREPDL scripts.
|
Published |
2018-04 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
35.060
Languages used in information technology
;
35.240.30
IT applications in information, documentation and publishing
|
| ISO/IEC 30170:2012 |
Information technology — Programming languages — Ruby |
ISO/IEC 30170:2012 specifies the syntax and semantics of the computer programming language Ruby, and the requirements for conforming Ruby processors, strictly conforming Ruby programs, and conforming Ruby programs.
It does not specify
the limit of size or complexity of a program text which a conforming processor evaluates,
the minimal requirements of a data processing system that is capable of supporting a conforming processor,
the method for activating the execution of programs on a data processing system, and
the method for reporting syntactic and runtime errors.
|
Published |
2012-04 |
Edition : 1 |
Number of pages : 313 |
Technical Committee |
35.060
Languages used in information technology
|
| ISO/IEC DIS 39075 |
Information technology — Database languages — GQL |
|
Under development |
|
Edition : 1 |
Number of pages : 554 |
Technical Committee |
35.060
Languages used in information technology
|
| ISO 1028:1973 |
Information processing — Flowchart symbols |
|
Withdrawn |
1973-12 |
Edition : 1 |
Number of pages : 3 |
Technical Committee |
35.080
Software
;
01.080.50
Graphical symbols for use on information technology and telecommunications technical drawings and in relevant technical product documentation
|
| ISO/IEC 2382-20:1990 |
Information technology — Vocabulary — Part 20: System development |
Sreves to facilitate international communication in information processing. Presents English and French terms and definitions of selected concepts as regards the field of information processing and defines relationsships between the entries. The provided concepts concern a system life cycle ranging from the requirements analysis to the implementation including system design and quality assurance.
|
Withdrawn |
1990-02 |
Edition : 1 |
Number of pages : 15 |
Technical Committee |
35.080
Software
;
01.040.35
Information technology (Vocabularies)
|
| ISO 2636:1973 |
Information processing — Conventions for incorporating flowchart symbols in flowcharts |
|
Withdrawn |
1973-05 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
35.080
Software
;
01.080.50
Graphical symbols for use on information technology and telecommunications technical drawings and in relevant technical product documentation
|
| ISO 3535:1977 |
Forms design sheet and layout chart |
Lays down the basic principles for the design of forms, whether discrete forms or continuous forms, and establishes a forms design sheet and a layout chart based on these principles. Applies to the design of forms for administrative, commercial and technical use, whether for completion in handwriting or by mechanical means such as typewriters and automatic printers.
|
Withdrawn |
1977-01 |
Edition : 1 |
Number of pages : 5 |
Technical Committee |
35.080
Software
|
| ISO/IEC 5055:2021 |
Information technology — Software measurement — Software quality measurement — Automated source code quality measures |
The measures in this standard were calculated from detecting and counting violations of good architectural and coding practices in the source code that could result in unacceptable operational risks or excessive costs. Establishing standards for these measures at the source code level is important because they have been used in outsourcing and system development contracts without having international standards to reference. For instance, the ISO/IEC 25000 series of standards that govern software product quality provide only a small set of measures at the source code level.
A primary objective of updating these measures was to extend their applicability to embedded software, which is especially important for the growing implementation of embedded devices and the Internet of Things. Functionality that has traditionally been implemented in IT applications is now being moved to embedded chips. Since the weaknesses included in the measures specified in this document have been found to be applicable to all forms of software, embedded software is not treated separately in this specification.
|
Published |
2021-03 |
Edition : 1 |
Number of pages : 235 |
Technical Committee |
35.080
Software
|
| ISO 5806:1984 |
Information processing — Specification of single-hit decision tables |
The basic format of single-hit decision tables and relevant definitions are described, together with recommended conventions for preparation and use. Is concerned with the use of decision tables in the context of documentation of computer-based information systems.
|
Published |
1984-12 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.080
Software
|
| ISO 5807:1985 |
Information processing — Documentation symbols and conventions for data, program and system flowcharts, program network charts and system resources charts |
Defines symbols to be used in information processing documentation and gives guidance on conventions tor their use in data flowcharts, program flowcharts, system flowcharts, program network charts, system resources charts. Applicable in conjunction with ISO 2382/1.
|
Published |
1985-02 |
Edition : 1 |
Number of pages : 25 |
Technical Committee |
35.080
Software
;
01.080.50
Graphical symbols for use on information technology and telecommunications technical drawings and in relevant technical product documentation
|
| ISO/IEC 5962:2021 |
Information technology — SPDX® Specification V2.2.1 |
This Software Package Data Exchange® (SPDX®) specification defines a standard data format for communicating the component and metadata information associated with software packages. An SPDX document can be associated with a set of software packages, files or snippets and contains information about the software in the SPDX format described in this specification.
|
Published |
2021-08 |
Edition : 1 |
Number of pages : 145 |
Technical Committee |
35.080
Software
|
| ISO 6592:1985 |
Information processing — Guidelines for the documentation of computer-based application systems |
|
Withdrawn |
1985-11 |
Edition : 1 |
Number of pages : 17 |
Technical Committee |
35.080
Software
|
| ISO/IEC 6592:2000 |
Information technology — Guidelines for the documentation of computer-based application systems |
|
Withdrawn |
2000-03 |
Edition : 1 |
Number of pages : 31 |
Technical Committee |
35.080
Software
|
| ISO 6593:1985 |
Information processing — Program flow for processing sequential files in terms of record groups |
Describes two alternative general procedures for any program for precessing sequential files logically organized in groups of records: Method A - checking of control head conditions after termination of appropriate level; Method B - checking of control head condition before initiation of appropriate level.
|
Withdrawn |
1985-11 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
35.080
Software
|
| ISO/IEC 8211:1994 |
Information technology — Specification for a data descriptive file for information interchange |
Cancels and replaces the first edition (1985). Specifies an interchange format to facilitate the moving of files or parts of files containing data records between computer systems. Specifies: media-independent file and data record descriptions for information interchange; the description of data elements, vectors, arrays and hierarchies containing character strings, bit strings and numeric forms; a data descriptive file; a data descriptive record; three levels of complexity of file and record structure; FTAM unstructured and structured document types.
|
Published |
1994-10 |
Edition : 2 |
Number of pages : 69 |
Technical Committee |
35.080
Software
|
| ISO 8631:1986 |
Information processing — Program constructs and conventions for their use |
|
Withdrawn |
1986-12 |
Edition : 1 |
|
Technical Committee |
35.080
Software
|
| ISO/IEC 8631:1989 |
Information technology — Program constructs and conventions for their representation |
Is concerned with the expression of procedure-oriented algorithms. Defines: 1 - the nature of program constructs; 2 - the manner in which constructs can be combined; 3 - specifications for a set of constructs; a variety of subsets of the defined constructs.
|
Published |
1989-08 |
Edition : 2 |
Number of pages : 7 |
Technical Committee |
35.080
Software
|
| ISO 8790:1987 |
Information processing systems — Computer system configuration diagram symbols and conventions |
Defines graphical symbols and their conventions for use in configuration diagrams for computer systems, including autamatic data processing systems.
|
Published |
1987-09 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.080
Software
;
01.080.50
Graphical symbols for use on information technology and telecommunications technical drawings and in relevant technical product documentation
|
| ISO 9000-3:1997 |
Quality management and quality assurance standards — Part 3: Guidelines for the application of ISO 9001:1994 to the development, supply, installation and maintenance of computer software |
|
Withdrawn |
1997-12 |
Edition : 2 |
Number of pages : 32 |
Technical Committee |
35.080
Software
;
03.100.70
Management systems
;
03.120.10
Quality management and quality assurance
|
| ISO/IEC 9126-1:2001 |
Software engineering — Product quality — Part 1: Quality model |
|
Withdrawn |
2001-06 |
Edition : 1 |
Number of pages : 25 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 9126-2:2003 |
Software engineering — Product quality — Part 2: External metrics |
ISO/IEC TR 9126-2:2003 provides external metrics for measuring attributes of six external quality characteristics defined in ISO/IEC 9126-1. ISO/IEC TR 9126-2:2003 defines external metrics, ISO/IEC TR 9126-3 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.
The metrics listed in ISO/IEC TR 9126-2:2003 are not intended to be an exhaustive set. Developers, evaluators, quality managers and acquirers may select metrics from ISO/IEC TR 9126-2:2003 for defining requirements, evaluating software products, measuring quality aspects and other purposes.
Users of ISO/IEC TR 9126-2:2003 can select or modify and apply metrics and measures from ISO/IEC TR 9126-2:2003 or may define application-specific metrics for their individual application domain.
ISO/IEC TR 9126-2:2003 is intended to be used together with ISO/IEC 9126-1.
ISO/IEC TR 9126-2:2003 contains an explanation of how to apply software quality metrics, a basic set of metrics for each subcharacteristic and an example of how to apply metrics during the software product life cycle.
ISO/IEC TR 9126-2:2003 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.
|
Withdrawn |
2003-07 |
Edition : 2 |
Number of pages : 86 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 9126-3:2003 |
Software engineering — Product quality — Part 3: Internal metrics |
ISO/IEC TR 9126-3:2003 provides internal metrics for measuring attributes of six external quality characteristics defined in ISO/IEC 9126-1. ISO/IEC TR 9126-2 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.
The metrics listed in ISO/IEC TR 9126-3:2003 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 for defining requirements, evaluating software products, measuring quality aspects and other purposes.
Users of ISO/IEC TR 9126-3:2003 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.
ISO/IEC TR 9126-3:2003 is intended to be used together with ISO/IEC 9126-1.
ISO/IEC TR 9126-3:2003 contains:
an explanation of how to apply software quality metrics;a basic set of metrics for each subcharacteristic;an example of how to apply metrics during the software product life cycle.
ISO/IEC TR 9126-3:2003 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.
|
Withdrawn |
2003-07 |
Edition : 2 |
Number of pages : 62 |
Technical Committee |
35.080
Software
|
| ISO/IEC 13235-1:1998 |
Information technology — Open Distributed Processing — Trading function: Specification — Part 1: |
The scope of this Recommendation | International Standard is:
? an enterprise specification for the trading function;
? an information specification for the trading function;
? a computational specification for traders (i.e. objects providing the trading function);
? conformance requirements in terms of conformance points.
It is not a goal of this Recommendation | International Standard to state how the trading function should be realized. Therefore
this Recommendation | International Standard does not include an engineering specification.
The field of application for this Recommendation | Intenational Standard is any ODP system in which it is required to introduce
and discover services incrementally, dynamically and openly.
|
Published |
1998-12 |
Edition : 1 |
Number of pages : 80 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 9126-4:2004 |
Software engineering — Product quality — Part 4: Quality in use metrics |
ISO/IEC TR 9126-4:2004 provides quality in use metrics for measuring the attributes defined in ISO/IEC 9126-1. ISO/IEC TR 9126-2 defines external metrics and ISO/IEC TR 9126-3 defines internal metrics for measurement of the subcharacteristics defined in ISO/IEC 9126-1. 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.
The metrics listed in ISO/IEC TR 9126-4 are not intended to be an exhaustive set. Developers, evaluators, quality managers and acquirers may select metrics from ISO/IEC TR 9126-4 for defining requirements, evaluating software products, measuring quality aspects and other purposes.
ISO/IEC TR 9126-2 is intended to be used together with ISO/IEC 9126-1.
ISO/IEC TR 9126-4 contains:
-- an explanation of how to apply software quality metrics;
-- a basic set of metrics for each characteristic; and
-- an example of how to apply metrics during the software product life cycle.
It includes as informative annexes a quality in use evaluation process and a reporting format.
|
Withdrawn |
2004-04 |
Edition : 1 |
Number of pages : 59 |
Technical Committee |
35.080
Software
|
| ISO/IEC 9126:1991 |
Software enginnering — Product quality |
|
Withdrawn |
1991-12 |
Edition : 1 |
Number of pages : 13 |
Technical Committee |
35.080
Software
|
| ISO 9127:1988 |
Information processing systems — User documentation and cover information for consumer software packages |
Describes user documentation and cover information supplied with software packages. Is applicable to software packages sold off-the-shelf to consumers for business, scientific, educational and home use. References: ISO 6592; ISO 7185.
|
Withdrawn |
1988-09 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 9294:1990 |
Information technology — Guidelines for the management of software documentation |
Addresses the policies, standards, procedures, resources and plans to produce an effective software. Applicable to all types of software from the simplest program to the most complex software system and to all stages of the software lifecycle. Detailed advice on the content and layout of software documentation is not provided. Annex A contains checklists of the policies, standards, procedures and project planing on the software production.
|
Withdrawn |
1990-11 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 9294:2005 |
Information technology — Guidelines for the management of software documentation |
ISO/IEC TR 9294:2005 offers guidance on the management of software documentation to managers responsible for the production of software or software-based products. This guidance is intended to assist managers in ensuring that effective documentation is produced in their organizations.
ISO/IEC TR 9294:2005 addresses the policies, standards, procedures, resources and plans with which managers must concern themselves in order to manage software documentation effectively.
The guidance given is intended to be applicable to all types of software, from the simplest program to the most complex software suite or software system. All types of software documentation are covered, relating to all stages of the software life cycle.
The principles of software documentation management are the same whatever the size of a project. For small projects, much of the detail given in ISO/IEC TR 9294:2005 may not apply, but the principles remain the same. Managers may tailor the recommendations to their particular needs.
The guidance given is from the point of view of software documentation management. Detailed advice is not provided on, for example, the content and layout of software documents.
|
Withdrawn |
2005-02 |
Edition : 2 |
Number of pages : 14 |
Technical Committee |
35.080
Software
|
| ISO/IEC CD 9837-1 |
Software and systems engineering — Systems resilience — Part 1: Concepts and vocabulary |
|
Under development |
|
Edition : 1 |
|
Technical Committee |
35.080
Software
;
01.040.35
Information technology (Vocabularies)
|
| ISO/IEC 10746-1:1998 |
Information technology — Open Distributed Processing — Reference model: Overview — Part 1: |
This Recommendation | International Standard:
? gives an introduction and motivation for ODP;
? provides an overview of the Reference Model of Open Distributed Processing (RM-ODP) and an
explanation of its key concepts;
? gives guidance on the application of the RM-ODP.
This Recommendation | International Standard covers both overview and detailed explanation, and can be consulted in
various ways when reading the standards:
a) if you intend to read only this Recommendation | International Standard, to gain a general understanding of
the importance of ODP to your organization, concentrate on clause 6;
b) if you intend to study the whole RM-ODP, you should also read clause 6 before moving on to
ITU-T Rec. X.902 | ISO/IEC 10746-2 and ITU-T Rec. X.903 | ISO/IEC 10746-3;
c) as you read ITU-T Rec. X.902 | ISO/IEC 10746-2 and ITU-T Rec. X.903 | ISO/IEC 10746-3 you may
wish to consult clauses 7 to 10, which give supporting explanation for the various concepts that these
common texts define;
d) when you have completed a first reading of ITU-T Rec. X.902 | ISO/IEC 10746-2 and ITU-T Rec. X.903 |
ISO/IEC 10746-3, read clauses 11 and 12 which discuss the use of standards in ODP system
specifications, and provide some examples of applying the ODP concepts in the specification of systems.
|
Published |
1998-12 |
Edition : 1 |
Number of pages : 76 |
Technical Committee |
35.080
Software
|
| ISO/IEC 10746-2:1996 |
Information technology — Open Distributed Processing — Reference Model: Foundations |
Contains the concepts which are needed to perform the modelling of ODP systems, and the principles of conformance to ODP systems.
|
Withdrawn |
1996-09 |
Edition : 1 |
Number of pages : 20 |
Technical Committee |
35.080
Software
|
| ISO/IEC 10746-2:2009 |
Information technology — Open distributed processing — Reference model: Foundations — Part 2: |
ISO/IEC 10746 provides a coordinating framework for the standardization of open distributed processing (ODP). This supports distribution, interworking, portability, and platform and technology independence. It establishes an enterprise architecture framework for the specification of ODP systems.
ISO/IEC 10746 defines the essential concepts necessary to specify open distributed processing systems from five prescribed viewpoints. It provides a well-developed framework for the structuring of specifications for large-scale, distributed systems.
The framework for system specification provided by ISO/IEC 10746 has four fundamental elements:
an object modelling approach to system specification;
the specification of a system in terms of separate but interrelated viewpoint specifications;
the definition of a system infrastructure providing distribution transparencies for system applications;
a framework for assessing system conformance.
ISO/IEC 10746-2:2009 contains the definition of the concepts and analytical framework for normalized description of any distributed processing system. It introduces the principles of conformance to ODP standards and the way in which they are applied. These concepts and principles are used in ISO/IEC 10746-3 and to establish requirements for new ODP specification techniques.
|
Published |
2009-12 |
Edition : 2 |
Number of pages : 22 |
Technical Committee |
35.080
Software
|
| ISO/IEC 10746-3:1996 |
Information technology — Open Distributed Processing — Reference Model: Architecture |
Defines how ODP systems are specified, making use of concepts in ITU-T Recommendation X.902 (ISO/IEC 10746-2); identifies the characteristics that qualify systems as ODP systems.
|
Withdrawn |
1996-09 |
Edition : 1 |
Number of pages : 56 |
Technical Committee |
35.080
Software
|
| ISO/IEC 10746-3:2009 |
Information technology — Open distributed processing — Reference model: Architecture — Part 3: |
ISO/IEC 10746 provides a coordinating framework for the standardization of open distributed processing (ODP). This supports distribution, interworking, portability, and platform and technology independence. It establishes an enterprise architecture framework for the specification of ODP systems.
ISO/IEC 10746 defines the essential concepts necessary to specify open distributed processing systems from five prescribed viewpoints. It provides a well-developed framework for the structuring of specifications for large-scale, distributed systems.
The framework for system specification provided by ISO/IEC 10746 has four fundamental elements:
an object modelling approach to system specification;
the specification of a system in terms of separate but interrelated viewpoint specifications;
the definition of a system infrastructure providing distribution transparencies for system applications;
a framework for assessing system conformance.
ISO/IEC 10746-3:2009 specifies the required characteristics that qualify distributed processing as open, i.e. the constraints to which ODP standards must conform. It uses the descriptive techniques from ISO/IEC 10746-2 to define five ISO/IEC 10746 viewpoints. These viewpoints are subdivisions of the specification of a whole system, established to bring together the particular pieces of information relevant to some stakeholder or particular area of concern. ISO/IEC 10746-3:2009 also defines a taxonomy for functions and structures to realize distribution transparencies.
|
Published |
2009-12 |
Edition : 2 |
Number of pages : 54 |
Technical Committee |
35.080
Software
|
| ISO/IEC 10746-4:1998 |
Information technology — Open Distributed Processing — Reference Model: Architectural semantics — Part 4: |
The rapid growth of distributed processing has lead to a need for a coordinating framework for the standardization of
Open Distributed Processing (ODP). This Reference Model of ODP provides such a framework. It creates an
architecture within which support of distribution, interworking, interoperability and portability can be integrated.
The Basic Reference Model of Open Distributed Processing (RM-ODP), (see ITU-T Recs. X.901 to X.904 | ISO/IEC
10746), is based on precise concepts derived from current distributed processing developments and, as far as possible,
on the use of formal description techniques for specification of the architecture.
The RM-ODP consists of:
? ITU-T Rec. X.901 | ISO/IEC 10746-1: 2YHUYLHZ:_ Contains a motivational overview of ODP giving
scooping, justification and explanation of key concepts, and an outline of ODP architecture. This part is
not normative.
? ITU-T Rec. X.902 | ISO/IEC 10746-2: )RXQGDWLRQV:_ Contains the definition of the concepts and
analytical framework and notation for normalized description of (arbitrary) distributed processing
systems. This is only to a level of detail sufficient to support ITU-T Rec. X.903 | ISO/IEC 10746-3 and to
establish requirements for new specification techniques. This part is normative.
? ITU-T Rec. X.903 | ISO/IEC 10746-3: $UFKLWHFWXUH: Contains_ the specification of the required
characteristics that qualify distributed processing as open. These are the constraints to which ODP
standards must conform. It uses the descriptive techniques from ITU-T Rec. X.902 | ISO/IEC 10746-2.
This part is normative.
? ITU-T Rec. X.904 | ISO/IEC 10746-4: $UFKLWHFWXUDO_6HPDQWLFV:_Contains a formalisation of the ODP
modeling concepts defined in ITU-T Rec. X.902 | ISO/IEC 10746-2, clauses 8 and 9, and a formalisation
of the viewpoint languages of ITU-T Rec. X.903 | ISO/IEC 10746-3. The formalisation is achieved by
interpreting each concept in terms of the constructs of the different standardized formal description
techniques. This part is normative.
The purpose of this Recommendation | International Standard is to provide an architectural semantics for ODP. This
essentially takes the form of an interpretation of the basic modeling and specification concepts of ITU-T Rec. X.902 |
ISO/IEC 10746-2 and viewpoint languages of ITU-T Rec. X.903 | ISO/IEC 10746-3, using the various features of
different formal specification languages. An architectural semantics is developed in four different formal specification
languages: LOTOS, ESTELLE, SDL and Z. The result is a formalization of ODP's architecture. Through a process of
iterative development and feedback, this has improved the consistency of ITU-T Rec. X.902 | ISO/IEC 10746-2 and
ITU-T Rec. X.903 | ISO/IEC 10746-3.
An architectural semantics provides the additional benefits of:
? assisting the sound and uniform development of formal descriptions of ODP systems; and
? of permitting uniform and consistent comparison of formal descriptions of the same standard in different
formal specification languages.
Rather than provide a mapping from all the concepts of ITU-T Rec. X.902 | ISO/IEC 10746-2, this Recommendation |
International Standard focuses on the most basic. A semantics for the higher level architectural concepts is provided
indirectly through their definition in terms of the basic ODP concepts.
Examples of the use of some of the formal specification languages in this report can be found in TR 10167 (Guidelines
for the Application of ESTELLE, LOTOS and SDL).
In the following clauses, the concepts are numbered in accordance with the scheme used in ITU-T Rec. X.902 |
ISO/IEC 10746-2.
This Recommendation | International Standard specifies an architectural semantics for ODP. This is required to:
? provide formalisation of the ODP modelling concepts;
? assist sound and uniform development of formal descriptions of standards for distributed systems;
? act as a bridge between the ODP modelling concepts and the semantic models of the specification
languages: LOTOS, SDL, ESTELLE and Z;
? provide a basis for uniform and consistent comparison between formal descriptions of the same standard
in specification languages that are used to develop an architectural semantics.
This part is normative.
|
Published |
1998-12 |
Edition : 1 |
Number of pages : 29 |
Technical Committee |
35.080
Software
|
| ISO/IEC 10746-4:1998/Amd 1:2001 |
Information technology — Open Distributed Processing — Reference Model: Architectural semantics — Part 4: — Amendment 1: Computational formalization |
|
Published |
2001-12 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
35.080
Software
|
| ISO/IEC 11411:1995 |
Information technology — Representation for human communication of state transition of software |
Defines diagrams and symbols for representing software functions and transitions and in improving human communication. Covers development, communication and review of software requirement analysis and design. Effective in interactive software, data communication software and language/command.
|
Published |
1995-04 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
35.080
Software
|
| ISO/IEC 12119:1994 |
Information technology — Software packages — Quality requirements and testing |
Applicable to software packages. Establishes requirements for software packages and instructions on how to test a software package against these requirements. Deals only with software packages as offered and delivered. Does not deal with their production process. The quality system of a supplier is outside the scope of this standard.
|
Withdrawn |
1994-11 |
Edition : 1 |
Number of pages : 16 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 12182:1998 |
Information technology — Categorization of software |
|
Withdrawn |
1998-11 |
Edition : 1 |
Number of pages : 14 |
Technical Committee |
35.080
Software
|
| ISO/IEC 14143-1:1998 |
Information technology — Software measurement — Functional size measurement — Part 1: Definition of concepts |
|
Withdrawn |
1998-06 |
Edition : 1 |
Number of pages : 6 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 8802-1X:2013/Amd 1:2016 |
Information technology — Telecommunications and information exchange between systems — Local and metropolitan area networks — Part 1X: Port-based network access control — Amendment 1: MAC security key agreement protocol (MKA) extensions |
|
Withdrawn |
2016-02 |
Edition : 1 |
Number of pages : 91 |
Technical Committee |
35.110
Networking
|
| ISO/IEC TR 12182:2015 |
Systems and software engineering — Framework for categorization of IT systems and software, and guide for applying it |
ISO/IEC TR 12182 specifies the manner in which categorizations of IT systems and software are organized and expressed. It provides the framework for categorizations, and a guide for applying it. This allows any community to clarify their scope of the systems by using their own definition of categories.
The scope of application of the framework is intended to IT systems and software, including services provided by IT systems, where they can be of main targets but not limited to.
The purpose of this Technical Report includes the following:
a) developers of systems and software engineering standards can define their applicability to different categories of target systems and software using annexes or guidelines, so that their users can easily identify relevant standards and clauses that they can apply;
b) suppliers of systems and software engineering tools and methods can clarify the types of target systems and software to which their technologies are applicable or limited so that their users can easily choose the right tools and methods among many candidates for their use;
c) providers of services can define characteristics of their services using classification axes so that they can specify the quality of their services;
d) developers and evaluators of the systems and software can categorize systems and software of similar characteristics by using classification axes so that they can obtain a better estimation and quality evaluation of their target systems and software to be developed;
e) the systems and software engineering community can exchange their research ideas and best practices with defined scope of application.
ISO/IEC TR 12182 does not provide a specific set of categorizations but the framework for categorizations and a guide for applying it to achieve the above purposes.
It is important that standards on systems and software engineering are properly applied to the procurement or development of certain kinds of systems. This Technical Report provides a categorization framework and a guide for applying it to assist in (1) defining the area of application of standards, and (2) positioning new standards. The annex of this Technical Report provides descriptive examples for relevant standards, each of which describes the area of application of the standard by using defined categorization.
NOTE Giving guidance on applicability might not be relevant to all standards.
|
Published |
2015-05 |
Edition : 2 |
Number of pages : 20 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 12207-2:2020 |
Systems and software engineering — Software life cycle processes — Part 2: Relation and mapping between ISO/IEC/IEEE 12207:2017 and ISO/IEC 12207:2008 |
This document provides the mapping expressing corresponding relations between software life cycle processes in ISO/IEC/IEEE 12207:2017 and the processes in ISO/IEC 12207:2008.
These relations are demonstrated by means of mapping tables that show relationships between activities and tasks, and process outcomes.
This mapping assists users of ISO/IEC 12207:2008 to transition to using ISO/IEC/IEEE 12207:2017.
This document will help users understand the differences between the reference processes and requirements of the two editions of ISO/IEC/IEEE 12207, and any potential gaps or process enhancements that can be needed in seeking conformance to and/or using ISO/IEC/IEEE 12207:2017. Also, this document provides to such users the mapping which helps to identify corresponding process outcomes, activities and tasks of processes for software systems in ISO/IEC/IEEE 12207:2017.
The mapping between ISO/IEC/IEEE 12207:2017 and ISO/IEC 12207:2008 in this document can be used as a basis to continuously conduct, improve and extend current process assets including software specific process assets based on ISO/IEC 12207:2008 for effective implementation of ISO/IEC/IEEE 12207:2017. These process activities and tasks can be applied iteratively.
|
Published |
2020-10 |
Edition : 1 |
Number of pages : 267 |
Technical Committee |
35.080
Software
|
| ISO/IEC 12207:1995 |
Information technology — Software life cycle processes |
Establishes a system for software life cycle processes with well-defined terminology. Contains processes, activities and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product and software services.
|
Withdrawn |
1995-07 |
Edition : 1 |
Number of pages : 57 |
Technical Committee |
35.080
Software
|
| ISO/IEC/IEEE 12207:2017 |
Systems and software engineering — Software life cycle processes |
ISO/IEC/IEEE 12207:2017 also provides processes that can be employed for defining, controlling, and improving software life cycle processes within an organization or a project.
The processes, activities, and tasks of this document can also be applied during the acquisition of a system that contains software, either alone or in conjunction with ISO/IEC/IEEE 15288:2015, Systems and software engineering?System life cycle processes.
In the context of this document and ISO/IEC/IEEE 15288, there is a continuum of human-made systems from those that use little or no software to those in which software is the primary interest. It is rare to encounter a complex system without software, and all software systems require physical system components (hardware) to operate, either as part of the software system-of-interest or as an enabling system or infrastructure. Thus, the choice of whether to apply this document for the software life cycle processes, or ISO/IEC/IEEE 15288:2015, Systems and software engineering?System life cycle processes, depends on the system-of-interest. Processes in both documents have the same process purpose and process outcomes, but differ in activities and tasks to perform software engineering or systems engineering, respectively.
|
Published |
2017-11 |
Edition : 1 |
Number of pages : 145 |
Technical Committee |
35.080
Software
|
| ISO/IEC 12207:1995/Amd 1:2002 |
Information technology — Software life cycle processes — Amendment 1 |
|
Withdrawn |
2002-05 |
Edition : 1 |
Number of pages : 53 |
Technical Committee |
35.080
Software
|
| ISO/IEC 12207:1995/Amd 2:2004 |
Information technology — Software life cycle processes — Amendment 2 |
|
Withdrawn |
2004-11 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
35.080
Software
|
| ISO/IEC 12207:2008 |
Systems and software engineering — Software life cycle processes |
ISO/IEC 12207:2008 establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a software product or service and during the supply, development, operation, maintenance and disposal of software products. Software includes the software portion of firmware.
ISO/IEC 12207:2008 applies to the acquisition of systems and software products and services, to the supply, development, operation, maintenance, and disposal of software products and the software portion of a system, whether performed internally or externally to an organization. Those aspects of system definition needed to provide the context for software products and services are included.
ISO/IEC 12207:2008 also provides a process that can be employed for defining, controlling, and improving software life cycle processes.
The processes, activities and tasks of ISO/IEC 12207:2008 - either alone or in conjunction with ISO/IEC 15288 - may also be applied during the acquisition of a system that contains software.
|
Withdrawn |
2008-02 |
Edition : 2 |
Number of pages : 123 |
Technical Committee |
35.080
Software
|
| ISO/IEC 13235-3:1998 |
Information technology — Open Distributed Processing — Trading Function — Part 3: Provision of Trading Function using OSI Directory service |
This Specification describes how the ODP Trading Function can be realised using information entries and support mechanisms of the OSI Directory. This Specification is to be used in conjunction with the ODP Trading Function Standard (ITU-T Rec. X.950 | ISO/IEC 13235-1). If there are any discrepancies between the prescriptive statements in ITU-T Rec. X.950 | ISO/IEC 13235-1 and those in this Specification, the prescriptive statements in ITU-T Rec. X.950 | ISO/IEC 13235-1 take precedence.
The scope of this Specification is:
? standardised templates for Trading Function information objects in the DIT;
? descriptions of mapping of Trading Function operations to appropriate Directory operations;
? description of use of other Directory features to provide the support mechanisms for implementing the ODP Trading Function.
This Specification does not prescribe that a trader must be engineered by using OSI Directory. But if OSI Directory is used, this Specification defines standardised templates for information entries (e.g. service offer and link information objects) in the Directory DIT. This Specification does not put any restrictions on where these entries are placed in the Directory DIT. That is, this Specification does not standardise any structure rules. This Specification does describe a mechanism to provide the Trading Function using OSI Directory.
The field of application of this Specification is for the construction of the ODP Trading Function using the OSI Directory, when required.
|
Published |
1998-12 |
Edition : 1 |
Number of pages : 49 |
Technical Committee |
35.080
Software
|
| ISO/IEC 13235-3:1998/Cor 1:2006 |
Information technology — Open Distributed Processing — Trading Function — Part 3: Provision of Trading Function using OSI Directory service — Technical Corrigendum 1 |
|
Published |
2006-06 |
Edition : 1 |
Number of pages : 2 |
Technical Committee |
35.080
Software
|
| ISO/IEC 13244:1998 |
Information technology — Open Distributed Management Architecture |
This Recommendation | International Standard describes the Open Distributed Management Architecture (ODMA). ODMA provides an architecture for the specification and development both of systems management as an open distributed application and of the management of open distributed applications. ODMA also provides the architectural framework for the development of the standards needed within the architecture. The management will be of a distributed nature; this implies:
– distribution of the managing activity;– management of distributed applications; and– management of resources that may be distributed.
ODMA is compliant with the ODP-RM, so that in a distributed environment OSI Systems Management can be used in combination with other techniques that are engineered and implemented according to ODP principles.
This Recommendation | International Standard is the base document of a (potential) range of standards and Recommendations to be developed within ODMA. Figure 1 provides an overview of the relationship between this Recommendation | International Standard and other standards.
Other standards that may be developed within ODMA are:
− ODMA supports: Based on the General Framework of ODMA, these standards give descriptions of specific systems support of ODMA. For example, the OSI Systems Management and CORBA support of ODMA have been identified.− ODMA viewpoint notations: These component standards provide standardised notations for describing the ODP viewpoints for ODMA (see for example Annex D). These notations are described in separate documents for the ODMA viewpoint notations.− ODMA functions: These component standards describe functions that are necessary for the construction of an Open Distributed Management System. Some example functions like the operation dispatcher function or the notification dispatcher function are outlined in this Recommendation | International Standard.− ODMA inter-domain functions: These component standards describe the interworking between different paradigms providing support for ODMA, for example, between OSI Systems Management and CORBA.
As illustrated in Figure 1 this Recommendation | International Standard only elaborates a subset of supporting ODMA systems but allows for developments of other clauses. As a consequence, this Recommendation | International Standard consists of two sections:
1) General Framework
This clause describes ODMA as a specific interpretation of the Reference Model of Open Distributed Processing for the purpose of management. It introduces general terms that are needed for open distributed management. It may also identify tools for the description of the open distributed management applications.
2) OSI management support for ODMA
This clause describes the OSI management support for ODMA. It relates the current OSI systems management concepts to ODMA concepts. However, it extends the current systems management standards to support the distribution of the management activities and the distribution of resources to be managed. As this specific interpretation reflects the current OSI standards, limitations may be imposed. For instance, only a number of distribution transparencies may be supported by the (extended) OSI management mechanisms.
|
Published |
1998-12 |
Edition : 1 |
Number of pages : 52 |
Technical Committee |
35.080
Software
|
| ISO/IEC 13244:1998/Amd 1:1999 |
Information technology — Open Distributed Management Architecture — Amendment 1: Support using Common Object Request Broker Architecture (CORBA) |
|
Published |
1999-09 |
Edition : 1 |
Number of pages : 8 |
Technical Committee |
35.080
Software
|
| ISO/IEC 13800:1996 |
Information technology — Procedure for the registration of identifiers and attributes for volume and file structure |
|
Published |
1996-08 |
Edition : 1 |
Number of pages : 7 |
Technical Committee |
35.080
Software
|
| ISO/IEC 14102:1995 |
Information technology — Guideline for the evaluation and selection of CASE tools |
Provides guidance on identifying organizational requirements for CASE tools, on mapping those requirements to CASE tool characteristics to be evaluated and describes a process for selecting the most appropriate CASE tool from several tools, based on measurements of the defined characteristics.
|
Withdrawn |
1995-11 |
Edition : 1 |
Number of pages : 55 |
Technical Committee |
35.080
Software
|
| ISO/IEC 14102:2008 |
Information technology — Guideline for the evaluation and selection of CASE tools |
Within systems and software engineering, Computer-Aided Software Engineering (CASE) tools represent a major part of the supporting technologies used to develop and maintain information technology systems. Their selection must be carried out with careful consideration of both the technical and management requirements.
ISO/IEC 14102:2008 defines both a set of processes and a structured set of CASE tool characteristics for use in the technical evaluation and the ultimate selection of a CASE tool. It follows the software product evaluation model defined in ISO/IEC 14598-5:1998.
ISO/IEC 14102:2008 adopts the general model of software product quality characteristics and subcharacteristics defined in ISO/IEC 9126-1:2001 and extends these when the software product is a CASE tool; it provides product characteristics unique to CASE tools. This larger set of characteristics is then organized into four groups:
characteristics related to life cycle process functionality;
characteristics related to CASE tool usage functionality;
general quality characteristics;
general characteristics not related to quality.
This grouping provides a more manageable approach to the overall evaluation and selection process.
The technical evaluation can indicate how well a CASE tool meets its user's stated requirements. It can also indicate how well the tool meets its claimed functionality.
The objective of the technical evaluation process is to provide quantitative results on which the final selection can be based. Measurement assigns numbers (or other ratings) to attributes of entities; a major activity of evaluation is to obtain these measurements for use in selection. The final selection results should aim to achieve objectivity, repeatability and impartiality. These objectives and the confidence in the outcomes will in part depend on the resources allocated to the overall evaluation and selection process. The user of ISO/IEC 14102:2008 is asked to deal with these issues at an early stage.To be widely acceptable, these CASE tool evaluation and selection processes must be of value to the users of CASE tools, and to the suppliers of CASE to the community at large. The information outlined in ISO/IEC 14102:2008 should lead to more cost effective selections of CASE tools and to a greater uniformity in how CASE tool functions and features are described.
|
Published |
2008-11 |
Edition : 2 |
Number of pages : 41 |
Technical Committee |
35.080
Software
|
| ISO/IEC 14143-1:2007 |
Information technology — Software measurement — Functional size measurement — Part 1: Definition of concepts |
ISO/IEC 14143-1:2007 defines the concepts of FSM (Functional Size Measurement). The concepts of Functional Size Measurement (FSM) are designed to overcome the limitations of earlier methods of sizing software by shifting the focus away from measuring how the software is implemented to measuring size in terms of the functions required by the user.
|
Published |
2007-02 |
Edition : 2 |
Number of pages : 6 |
Technical Committee |
35.080
Software
|
| ISO/IEC 14143-1:2007/Cor 1:2011 |
Information technology — Software measurement — Functional size measurement — Part 1: Definition of concepts — Technical Corrigendum 1 |
|
Published |
2011-12 |
Edition : 2 |
Number of pages : 1 |
Technical Committee |
35.080
Software
|
| ISO/IEC 14143-2:2002 |
Information technology — Software measurement — Functional size measurement — Part 2: Conformity evaluation of software size measurement methods to ISO/IEC 14143-1:1998 |
|
Withdrawn |
2002-11 |
Edition : 1 |
Number of pages : 32 |
Technical Committee |
35.080
Software
|
| ISO/IEC 14143-2:2011 |
Information technology — Software measurement — Functional size measurement — Part 2: Conformity evaluation of software size measurement methods to ISO/IEC 14143-1 |
ISO/IEC 14143-2:2011:
establishes a framework for the conformity evaluation of a Candidate FSM Method against the provisions of ISO/IEC 14143-1;
describes a process for conformity evaluation of whether a Candidate FSM Method meets the (type) requirements of ISO/IEC 14143-1 such that it is an actual FSM method, i.e. they are of the same type;
describes the requirements for performing a conformity evaluation in order to ensure repeatability of the conformity evaluation process, as well as consistency of decisions on conformity and the final result;
aims to ensure that the output from the conformity evaluation process is objective, impartial, consistent, repeatable, complete and auditable;
provides informative guidelines for determining the competence of the conformity evaluation teams;
provides an example checklist to assist in the conformity evaluation of a Candidate FSM Method; and
provides an example template for the conformity evaluation report.
|
Published |
2011-09 |
Edition : 2 |
Number of pages : 29 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 14143-3:2003 |
Information technology — Software measurement — Functional size measurement — Part 3: Verification of functional size measurement methods |
ISO/IEC TR 14143-3:2003 establishes a framework for verifying the statements of an FSM Method and/or for conducting tests requested by the verification sponsor, relative to the following performance properties:
repeatability and reproducibility;accuracy;convertibility;discrimination threshold;applicability to Functional Domains.
NOTE Statements and test requests relative to other performance properties are outside the scope of ISO/IEC TR 14143-3:2003.
ISO/IEC TR 14143-3:2003 aims to ensure that the output from the verification is objective, impartial, consistent and repeatable.
The verification report, produced as a result of applying ISO/IEC TR 14143-3:2003, will enable the prospective user to select the FSM Method which best meets their needs.
|
Published |
2003-04 |
Edition : 2 |
Number of pages : 23 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 14143-4:2002 |
Information technology — Software measurement — Functional size measurement — Part 4: Reference model |
Part 4 of ISO/IEC 14143 defines the reference model (Figure 0.1) to be used when verifying a Functional Size
Measurement (FSM) method.
The reference model consists of two components:
- a classification framework of Reference User Requirements (RUR) which can be sized using an FSM
Method. Included are examples of such RUR as well as references to further publications of User
Requirements (UR) which can be used for RUR, and
- guidance on selecting Reference FSM Methods, against which an FSM Method can be compared.
The reference model is an input to the evaluation process of an FSM Method. The formulation and execution of
evaluation tests and the interpretation of their results is outside the scope of this Technical Report.
The RUR and additional references contained in this Technical Report only represent examples of UR in some
domains and situations. Additional RUR and RUR for domains and situations not covered by Annex A, B, or C may
be generated with the assistance of the framework described in this Technical Report.
The requirements for Reference FSM Methods may assist in selecting Reference FSM Methods.
|
Published |
2002-08 |
Edition : 2 |
Number of pages : 95 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 14143-5:2004 |
Information technology — Software measurement — Functional size measurement — Part 5: Determination of functional domains for use with functional size measurement |
ISO/IEC TR 14143-5:2004 describes the characteristics of Functional Domains and the procedures by which characteristics of Functional User Requirements (FUR) can be used to determine Functional Domains. Two example methods for implementing these principles are provided in the annexes.
Either of the methods may be used directly, or by using Functional Domains defined locally by:
FSM Method to determine if a particular FSM Method is applicable to the Functional Domain(s) represented by their specific FUR;Describing, for a given set of FUR, the Functional Domain to which the FUR belong; andFSM Method owners and designers describing the Functional Domain(s) to which the FSM Method can be applied as outlined in ISO/IEC 14143-1:1998.
|
Published |
2004-04 |
Edition : 2 |
Number of pages : 27 |
Technical Committee |
35.080
Software
|
| ISO/IEC TS 33061:2021 |
Information technology — Process assessment — Process assessment model for software life cycle processes |
This document defines a process assessment model for software life cycle processes, conformant with the requirements of ISO/IEC 33004, for use in performing a conformant assessment in accordance with the requirements of ISO/IEC 33002.
|
Published |
2021-04 |
Edition : 1 |
Number of pages : 74 |
Technical Committee |
35.080
Software
|
| ISO/IEC 14143-6:2006 |
Information technology — Software measurement — Functional size measurement — Part 6: Guide for use of ISO/IEC 14143 series and related International Standards |
ISO/IEC 14143-6:2006 provides a summary of the FSM (Functional Size Measurement) related International Standards and the relationship between;
the ISO/IEC 14143 series FSM framework International Standards that provide the definitions and concepts of FSM and conformance and verification of FSMMs (Functional Size Measurement Methods), and the ISO/IEC standard FSMMs, i.e. ISO/IEC 19761, ISO/IEC 20926, ISO/IEC 20968 and ISO/IEC 24570.
An FSMM is a software sizing method that conforms to the mandatory requirements of ISO/IEC 14143-1.
ISO/IEC 14143-6 also provides a process to assist users to select an FSMM that meets their requirements. It also gives guidance on how to use Functional Size (FS).
FSMMs include, but are not limited to, ISO/IEC 19761, ISO/IEC 20926, ISO/IEC 20968 and ISO/IEC 24570, as well.
Recommending a specific FSMM is outside the scope of ISO/IEC 14143-6.
|
Withdrawn |
2006-06 |
Edition : 1 |
Number of pages : 21 |
Technical Committee |
35.080
Software
|
| ISO/IEC 14143-6:2012 |
Information technology — Software measurement — Functional size measurement — Part 6: Guide for use of ISO/IEC 14143 series and related International Standards |
ISO/IEC 14143-6:2012 provides a summary of the FSM (Functional Size Measurement) related standards and the relationship between:
a) the ISO/IEC 14143 series FSM framework standards that provide the definitions and concepts of FSM and conformance and verification of FSMMs (Functional Size Measurement Methods), and
b) the ISO/IEC standard FSMMs, i.e. ISO/IEC 19761 (COSMIC), ISO/IEC 20926 (IFPUG), ISO/IEC 20968 (Mk II), ISO/IEC 24570 (NESMA), and ISO/IEC 29881 (FiSMA).
An FSMM is a software sizing method that conforms to the mandatory requirements of ISO/IEC 14143-1.
ISO/IEC 14143-6:2012 also provides a process to assist users to select an FSMM that meets their requirements.
It also gives guidance on how to use Functional Size (FS).
FSMMs include, but are not limited to, ISO/IEC 19761, ISO/IEC 20926, ISO/IEC 20968, ISO/IEC 24570, and ISO/IEC 29881 as well.
Recommending a specific FSMM is outside the scope of ISO/IEC 14143-6:2012.
|
Published |
2012-11 |
Edition : 2 |
Number of pages : 21 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 14471:1999 |
Information technology — Software engineering — Guidelines for the adoption of CASE tools |
|
Withdrawn |
1999-05 |
Edition : 1 |
Number of pages : 19 |
Technical Committee |
35.080
Software
|
| ISO/IEC TR 14471:2007 |
Information technology — Software engineering — Guidelines for the adoption of CASE tools |
Since CASE (computer aided software engineering) adoption is a subject of the broader technology transition problem, ISO/IEC TR 14471:2007 addresses the adoption practices appropriate for a wide range of computing organizations. ISO/IEC TR 14471:2007 neither dictates nor advocates particular development standards, software processes, design methods, methodologies, techniques, programming languages, or life-cycle paradigms.
ISO/IEC TR 14471:2007 will:
identify critical success factors (CSF);
propose a set of adoption processes;
guide successful adoption in consideration of organizational and cultural environment.
The following groups are targeted as potential audiences:
CASE users;
information systems managers;
chief information officers (CIO);
CASE suppliers;
software engineering consultants;
those involved in the acquisition of CASE tools and technology.
Therefore ISO/IEC TR 14471:2007 addresses aspects of CASE tools adoption. It is best used in conjunction with ISO/IEC 14102 for CASE tool evaluation and selection. It is complementary to related ISO/IEC documents which deal with the general aspects of these topics.
The purpose of ISO/IEC TR 14471:2007 is to provide a recommended practice for CASE adoption. It provides guidance in establishing processes and activities that are to be applied for the successful adoption of CASE technology. The use of ISO/IEC TR 14471:2007 will help to maximize the return and minimize the risk of investing in CASE technology. However, ISO/IEC TR 14471:2007 does not establish compliance criteria.
|
Published |
2007-10 |
Edition : 2 |
Number of pages : 22 |
Technical Committee |
35.080
Software
|
| ISO/IEC 14598-1:1999 |
Information technology — Software product evaluation — Part 1: General overview |
|
Withdrawn |
1999-04 |
Edition : 1 |
Number of pages : 19 |
Technical Committee |
35.080
Software
|
| ISO/IEC 14598-2:2000 |
Software engineering — Product evaluation — Part 2: Planning and management |
|
Withdrawn |
2000-02 |
Edition : 1 |
Number of pages : 12 |
Technical Committee |
35.080
Software
|