Iso/Iec/Ieee 29119-2 Ed1.0: Title Software and Systems Engineering - Software Testing - Part 2: Test Processes
Iso/Iec/Ieee 29119-2 Ed1.0: Title Software and Systems Engineering - Software Testing - Part 2: Test Processes
Iso/Iec/Ieee 29119-2 Ed1.0: Title Software and Systems Engineering - Software Testing - Part 2: Test Processes
Information technology -- Open Distributed Processing -- Unified Modeling Language (UML) Version
1.4.2
ISO/IEC 19501:2004 describes the Unified Modeling Language (UML), a graphical language for
visualizing, specifying, constructing and documenting the artifacts of a software-intensive system.
The UML offers a standard way to write a system's blueprints, including conceptual things such as
business processes and system functions, as well as concrete things such as programming language
statements, database schemas, and reusable software components.
ISO/IEC/IEEE
29119-2 ed1.0
Title Software and systems engineering -- Software testing -- Part 2: Test
processes
The purpose of the ISO/IEC/IEEE 29119 series of software testing standards is to define an
internationally-agreed set of standards for software testing that can be used by any organization
when performing any form of software testing. ISO/IEC/IEEE 29119-2:2013 comprises test process
descriptions that define the software testing processes at the organizational level, test management
level and dynamic test levels. It supports dynamic testing, functional and non-functional testing,
manual and automated testing, and scripted and unscripted testing. The processes defined in
ISO/IEC/IEEE 29119-2:2013 can be used in conjuntion with any software development lifecycle
model. Since testing is a key approach to risk-mitigation in software development, ISO/IEC/IEEE
29119-2:2013 follows a risk-based approach to testing. Risk-based testing is a common industry
approach to strategizing and managing testing. Risk-based testing allows testing to be prioritzed and
focused on the most important features and functions.
IEC 62304:2006
Medical device software -- Software life cycle processes
Defines the life cycle requirements for medical device software. The set of processes, activities, and
tasks described in this standard establishes a common framework for medical device software life
cycle processes.
ISO/IEC TR 24715:2006
Information technology -- Programming languages, their environments and system software
interfaces -- Technical Report on the Conflicts between the ISO/IEC 9945 (POSIX) and the Linux
Standard Base (ISO/IEC 23360)
ISO/IEC TR 24715:2006 is based on ISO/IEC 23360 (Linux Standard Base Core Specification 3.1, which
was submitted to ISO/IEC on 2005/10/31 for publication), and ISO/IEC 9945:2003 edition dated
2003/8/15 with ISO/IEC 9945:2003/Cor.1:2004 (published 2004/9/15).
The scope of this Technical Report is to identify areas of conflict between ISO/IEC 23360 (the Linux
Standard Base 3.1 specification) and the ISO/IEC 9945 (POSIX) International Standard.
The audience for this Technical Report is the technical workgroups that develop the standards; that
is, the Austin Group and the Linux Standard Base workgroup. It is also intended to be of interest to
systems engineers, technical managers and procurement officers.
ISO/IEC 19775-2:2010
Information technology -- Computer graphics and image processing -- Extensible 3D (X3D) -- Part 2:
Scene access interface (SAI)
ISO/IEC 19775 defines a software system that integrates network-enabled 3D graphics and
multimedia. Conceptually, each X3D application is a 3D time-based space that contains graphic and
aural objects that can be dynamically modified through a variety of mechanisms.
ISO/IEC 19775-2:2010 specifies a standard set of services that are made available by a browser so
that an author can access the scene graph while it is running. Such access is designed to support
interaction with, and modification of, the scene graph.
ISO 16739:2013
Industry Foundation Classes (IFC) for data sharing in the construction and facility management
industries
ISO 16739:2013 specifies a conceptual data schema and an exchange file format for Building
Information Model (BIM) data. The conceptual schema is defined in EXPRESS data specification
language. The standard exchange file format for exchanging and sharing data according to the
conceptual schema is using the Clear text encoding of the exchange structure. Alternative exchange
file formats can be used if they conform to the conceptual schema.
ISO 16739:2013 represents an open international standard for BIM data that is exchanged and
shared among software applications used by the various participants in a building construction or
facility management project.
ISO 16739:2013 consists of the data schema, represented as an EXPRESS schema specification, and
reference data, represented as definitions of property and quantity names and descriptions.
A subset of the data schema and referenced data is referred to as a model view definition. A
particular model view definition is defined to support one or many recognized workflows in the
building construction and facility management industry sector. Each workflow identifies data
exchange requirements for software applications. Conforming software applications need to identity
the model view definition they conform to.
ISO/IEC TR 19765:2007
Information technology -- Survey of icons and symbols that provide access to functions and facilities
to improve the use of information technology products by the elderly and persons with disabilities
Different users of information technology products possess different sets of abilities. Some abilities
may not ever be present in a user as they may have been born without them. Some abilities are
acquired, developed or deteriorate over time due to education, maturity, injury, illness or age. Just
as it is possible that a user possesses a combination of abilities, it is also possible that they may lack
a combination of abilities.
ISO/IEC TR 19765:2007 presents icons and symbols currently used to provide access to facilities and
tools to support the needs of elderly and disabled users of information technology (IT) products, and
could form the basis of a future International Standard which would provide a recommended
collection of icons and symbols.
These icons and symbols have been collected from a variety of sources including other standards,
contemporary software products, web sites and hardware devices. These sources are cross-
referenced and listed in a bibliography.
ISO/IEC/TR 14471 ed2.0
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 29110-1 ed1.0
Software engineering -- Lifecycle profiles for Very Small Entities (VSEs) -- Part 1: Overview
ISO/IEC TR 29110-1:2011 introduces the major concepts required to understand and use the ISO/IEC
29110 series. It introduces the characteristics and requirements of a Very Small Entity (VSE), and
clarifies the rationale for VSE-specific profiles, documents, standards and guides.
It also introduces process, lifecycle and standardization concepts and defines the business terms
common to the ISO/IEC 29110 series.
ISO/IEC TR 29110-1:2011 is applicable to VSEs. The lifecycle processes described in ISO/IEC 29110
are not intended to preclude or discourage their use by an entity that is larger than a VSE.
P-IEC 61713 ed1.0
Software dependability through the software life-cycle processes- Application guide
Provides guidance on software life-cycle activities to achieve dependable software. The activities
identified can be part of a dependability programme for a system or related to a product containing
software. This guide is intended to support IEC 60300-3-6. This guide can be used by acquirers,
suppliers, developers, operators or maintainers of software. This guide is intended for all project
participants who develop or use systems or products containing software.