35.080 - Software
ICS 35.080 Details
Software
Softwareentwicklung. Systemdokumentation
Logiciels
Programska oprema
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 35.080 - Software
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document contains guidance for certification that can be used by certification or qualification bodies regarding the description of knowledge, skill and competence within their particular schemes based on ISO/IEC 24773-1.
- Standard21 pagesEnglish languagesale 15% off
This document establishes the major concepts required to understand and use the ISO/IEC 29110 series. It specifies the characteristics and requirements of a VSE, and clarifies the rationale for VSE-specific profiles, documents, profile specifications and guidelines. This document introduces the taxonomy (catalogue) of ISO/IEC 29110 profiles and the ISO/IEC 29110 series. This document is applicable to a VSE but can also be used by an entity that is larger than a VSE.
- Standard14 pagesEnglish languagesale 15% off
This document defines the terms common to the ISO/IEC 29110 series. This document is applicable to very small entities (VSEs), and their customers, assessors, standards producers, tool vendors and methodology vendors.
- Standard18 pagesEnglish languagesale 15% off
This document provides guidance on aspects of the design of human-system interaction, including conceptual design, user-system interaction design, user interface design and navigation design for interactive systems.
This document applies to all design and development approaches and methodologies, including human-centred design, object-oriented, waterfall, human factors integration (HFI), agile and rapid development.
It is intended for the following types of users:
— user interface designers, who will apply the guidance during the development process;
— developers, who will apply the guidance during the design and implementation of system functionality;
— evaluators, who are responsible for ensuring that products meet the recommendations;
— designers of user interface development tools and style guides to be used by user interface designers;
— project managers, who are responsible for managing development processes.
- Draft32 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides guidance for the life cycle management of systems and software, complementing the processes described in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207. This document: — addresses systems concepts and life cycle concepts, models, stages, processes, process application, key points of view, adaptation and use in various domains and by various disciplines; — establishes a common framework for describing life cycles, including their individual stages, for the management of projects that provide or acquire either products or services; — defines the concept of a life cycle; — supports the use of the life cycle processes within an organization or a project; organizations and projects can use these life cycle concepts when acquiring and supplying either products or services; — provides guidance on adapting a life cycle model and the content associated with a life cycle or a part of a life cycle; — describes the relationship between life cycles and their use in applying the processes in ISO/IEC/IEEE 15288 (systems aspects) and ISO/IEC/IEEE 12207 (software systems aspects); — shows the relationships of life cycle concepts to the hardware, human, services, process, procedure, facility and naturally occurring entity aspects of projects; — describes how its concepts relate to detailed process standards, for example, in the areas of measurement, project management, risk management and model-based systems and software engineering.
- Standard76 pagesEnglish languagesale 15% off
This document describes a methodology for calculating the rate of carbon emissions for a software system; that is, its SCI score. The purpose of this score is to increase awareness and transparency of an application's sustainability credentials. The score will help software practitioners make better, evidence-based decisions during system design, development, and deployment, that will ultimately minimize carbon emissions. A reliable, consistent, fair and comparable measure allows targets to be defined during development and progress to be tracked.
- Standard9 pagesEnglish languagesale 15% off
The proposed project is a revision of ISO/IEC/IEEE 24748-2:2018, Systems and software engineering — Life cycle management — Part 2: Guidelines for the application of ISO/IEC/IEEE 15288 (System life cycle processes). There are no scope changes. ISO/IEC/IEEE 24748-2 is a guideline for the application of ISO/IEC/IEEE 15288. It addresses system, life cycle, organizational, project, and process, concept application, principally through reference to ISO/IEC/IEEE 24748-1 and ISO/IEC/IEEE 15288. It gives guidance on applying ISO/IEC/IEEE 15288 from the aspects of strategy, planning, application in organizations, and application on projects. It also provides comparison of the differences between ISO/IEC/IEEE 15288 current revision and the prior version, ISO/IEC 15288:2015.
- Standard63 pagesEnglish languagesale 15% off
This document describes information items enabling systematic human-centred design for interactive
systems.
Some of these information items are elaborated by separate International Standards, named the
Common Industry Format (CIF) for usability-related information.
This document provides the framework of information items, including definitions and the content for
each information item.
This document includes the following:
— the intended users of the information items;
— consistent terminology;
— the high-level content structure to be used for documenting each information item.
The information items are intended to be used as part of system-level documentation resulting from
development processes such as those in ISO 9241-210, ISO 9241-220 and ISO/IEC JTC 1/SC 7 process
standards (e.g. ISO/IEC/IEEE 15288, ISO/IEC/IEEE 29148).
This document focuses on those information items needed for design, development and evaluation
of usable systems, rather than prescribing a specific process. It is intended to be used in conjunction
with existing International Standards, including the standards of the ISO 9241 series and the SQuaRE
documents.
This document does not prescribe any kind of method, life cycle or process.
NOTE The information items produced by human-centred design activities can be incorporated in design
approaches as diverse as object-oriented, waterfall, HFI (human factors integration), agile and rapid development.
- Technical report28 pagesEnglish languagesale 10% offe-Library read for1 day
This document establishes a framework for defining quality models which are composed of quality characteristics and sub-characteristics. In particular, this document provides: — the concept of a quality model; — the structure and semantics of quality models; — the relationship between quality models and the other concepts, including measurement, requirement definition, and evaluation; — guidelines, requirements and examples for using quality models.
- Standard17 pagesEnglish languagesale 15% off
1.1 This document specifies the process and technical requirements for the development of software
for programmable electronic systems for use in:
— control, command for signalling applications,
— applications on-board of rolling stock.
This document is not intended to be applied in the area of electric traction power supply (fixed
installations) or for power supply and control of conventional applications, e.g. station power supply
for offices, shops. These applications are typically covered by standards for energy distribution and/or
non-railway sectors and/or local legal frameworks.
1.2 This document is applicable exclusively to software and the interaction between software and the
system of which it is part.
1.3 Intentionally left blank
1.4 This document applies to software as per subclause 1.1 of this document used in railway systems,
including:
— application programming,
— operating systems,
— support tools,
— firmware.
Application programming comprises high level programming, low level programming and special
purpose programming (for example: programmable logic controller ladder logic).
1.5 This document also addresses the use of pre-existing software (as defined in 3.1.16) and tools.
Such software can be used if the specific requirements in 7.3.4.7 and 6.5.4.16 on pre-existing
software and for tools in 6.7 are fulfilled.
1.6 Intentionally left blank
1.7 This document considers that modern application design often makes use of software that is
suitable as a basis for various applications. Such software is then configured by application data for
producing the executable software for the application.
1.8 Intentionally left blank
1.9 This document is not intended to be retrospective. It therefore applies primarily to new
developments and only applies in its entirety to existing systems if these are subjected to major
modifications. For minor changes, only 9.2 applies. However, application of this document during
upgrades and maintenance of existing software is advisable.
1.10 For the development of User Programmable Integrated Circuits (e.g. field programmable gate
arrays (FPGA) and complex programmable logic devices (CPLD)) guidance is provided in
EN 50129:2018 Annex F for safety related functions and in EN 50155:2017 for non-safety related
functions. Software running on softcore processors of User Programmable Integrated Circuits is within
the scope of this document.
- Standard125 pagesEnglish languagesale 10% offe-Library read for1 day
This document provides specifications for a transport format which enables the digital encapsulation of this data. This document refers to an encapsulation of hardware identification (HWID) data as a HWID tag, just as ISO/IEC 19770-2 refers to software identification (SWID) tags for software identification. This document applies to the following. — Tag producers: organizations that create HWID tags for use by others in the market. A tag producer can be part of the organization creating the hardware or a third-party organization. These organizations can be broken down into two major categories. — Device or component providers: entities responsible for the manufacturing or creation of the hardware device and/or associated operating system, virtual environment, or application platform. Platform providers which support this document can additionally provide tag management capabilities at the level of the platform or operating system. — Tag tool providers: entities that provide tools to create hardware identification tags. For example, tools within development environments that generate hardware identification tags, or installation tools that can create tags on behalf of the installation process, and/or desktop management tools that can create tags for underlying hardware, virtual machines, or platforms that did not originally have a hardware identification tag. — Tag consumers: tools and/or organizations who utilize information from HWID tags are broken down into the following two major categories. — Device or component consumers: entities that purchase, install, integrate, and/or otherwise deploy physical or virtual hardware or components. — IT discovery and processing tool providers: entities that provide tools to collect, store, and process hardware identification tags. These tools may be targeted at a variety of different market segments, including security, asset management, and logistics. This document deals only with hardware device or component identification. This document does not detail information technology asset management (ITAM) processes required for discovery and management of hardware (which is provided in ISO/IEC 19770-1) software identification tags (as defined by ISO/IEC 19770-2), entitlement tags (as defined by ISO/IEC 19770-3), or resource utilization measurements (as defined by ISO/IEC 19770-4).
- Standard41 pagesEnglish languagesale 15% off
This document provides guidance for evaluation of artificial intelligence (AI) systems using an AI system quality model. The document is applicable to all types of organizations engaged in the development and use of AI.
- Technical specification20 pagesEnglish languagesale 15% off
This document defines a quality-in-use model composed of three characteristics (which are further subdivided into sub-characteristics) 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 a set of quality characteristics for specifying, measuring, evaluating and improving quality-in-use. In this document, because context of use is specified as prerequisite of quality-in-use, context of use is necessary to be re-specified to change prerequisite when a product or service intend to fulfil to context of use changes. The model can be applied, in particular, by those responsible for specifying and evaluating software product quality, such as developers, acquirers, quality assurance and control staff, and independent evaluators. 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; — presenting evaluation items for ethics considerations when using information system and IT service system; — supporting governance of digitalization activities.
- Standard31 pagesEnglish languagesale 15% off
Modification to Scope
Add the following note after the paragraph in 1.6:
"NOTE This document was derived from the signalling standard EN 50128 which in many cases was also applied in Rolling Stock applications. Subclause 1.6 ensures continuity in the application of the standards, i.e., software that was developed in accordance with EN 50128 can still be re-used for new projects."
- Amendment5 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines a product quality model, which is applicable to ICT (information and communication technology) 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 a reference model for the quality of the products to be specified, measured and evaluated. NOTE 1 In this document, a product refers to an ICT product that is part of an information system. ICT product components include subsystems, software, firmware, hardware, data, communication infrastructure, and other elements that are part of the ICT 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 in the 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. NOTE 2 Usage of the quality model for measurement is explained in Annex C.
- Standard22 pagesEnglish languagesale 15% off
Add the following note after the paragraph in 1.6: 'NOTE This document was derived from the signalling standard EN 50128 which in many cases was also applied in Rolling Stock applications. Subclause 1.6 ensures continuity in the application of the standards, i.e., software that was developed in accordance with EN 50128 can still be re-used for new projects.'
- Amendment5 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the concept of integrity levels with the corresponding integrity level requirements for achieving the integrity levels. 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 document 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 document 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 document in Annex A.
- Standard21 pagesEnglish languagesale 15% off
This document: — describes frequently occurring risks during development and maintenance of custom software; — describes possible controls for frequently occurring risks; — describes the related: — activities, facilities and roles typically used for these controls; — properties of products and processes; — standards, measurements, testing and assessment of the properties of products and processes.
- Technical report36 pagesEnglish languagesale 15% off
This document defines system engineering and management requirements for the life cycle of websites, including strategy, design, engineering, testing and validation, and management and sustainment for intranet and extranet environments. This document applies to those using web technology to present information and communications technology (ICT) information, such as information for users of systems and services, plans and reports for systems and software engineering projects, and documentation of policies, plans, and procedures for IT service management. This document provides requirements for website owners and website providers, managers responsible for establishing guidelines for website development and operations, website engineers, designers, developers, and operations and maintenance staff, who can be external or internal to the website owner's organization. It applies to websites for public access and for limited access, such as for users, customers, and subscribers seeking information on IT systems, products and services. The requirements and recommendations in this document address the following aspects of usability of informational websites and ease of maintenance of managed website operations: a) locating relevant and timely information; b) applying information security management; c) facilitating accessibility and ease of use; d) providing for consistent and efficient development and maintenance practices. This document is not particularly applicable to websites used primarily for marketing or sales, to deliver instructional material (tutorials), or to provide graphical user interfaces (GUI) for business or consumer transactional application processing. However, this document can provide useful insights for managing such sites. This document does not address vendor and product considerations for website engineering and management. This document does not include specifications for application development tools, programming and scripting languages used for websites, metadata tags, or protocols for network communications. It does not address tools or systems used for management or storage of information content (data, documents) that can be presented on websites. This document does not address the design and architecture of software and systems supporting the Internet.
- Standard57 pagesEnglish languagesale 15% off
This document: — provides supplemental requirements and guidance for the planning and performing of the integration processes given in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207; — provides guidance on the relationship between the integration process and other life cycle processes. — specifies requirements for information items to be produced as a result of using the integration process, including the content of the information items. This document is applicable to: — those who use or plan to use ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288, or both, on projects dealing with human-made systems, software-intensive systems, and products and services related to those systems, regardless of the project scope, methodology, size, or complexity; — anyone planning or performing integration activities to aid in ensuring that the application of the integration process and its relationships to other system life cycle processes conform to ISO/IEC/IEEE 15288 or ISO/IEC/IEEE 12207.
- Standard42 pagesEnglish languagesale 15% off
This document elaborates requirements and recommendations for certifications schemes based on ISO/IEC 24773-1, which are specific to the domain of software engineering.
- Standard14 pagesEnglish languagesale 15% off
This document outlines a quality model for AI systems and is an application-specific extension to the standards on SQuaRE. The characteristics and sub-characteristics detailed in the model provide consistent terminology for specifying, measuring and evaluating AI system quality. The characteristics and sub-characteristics detailed in the model also provide a set of quality characteristics against which stated quality requirements can be compared for completeness.
- Standard15 pagesEnglish languagesale 15% off
This document provides requirements and guidance on the application of system and software engineering processes to systems for epidemic prevention and control. This document provides guidance that can be employed for adopting and applying system and software life cycle processes within an organization or a project in an epidemic emergency. It includes system of systems considerations in the context of epidemic emergency. This document applies to acquisition, supply, development, operation, maintenance, and disposal (whether performed internally or externally to an organization) of system or system of systems in an epidemic emergency. Many of the requirements and recommendations in this document are also applicable to other systems developed rapidly to respond to emergency conditions affecting the public.
- Standard41 pagesEnglish languagesale 15% off
This document deals with the tool capabilities and methods for model-based systems and software engineering (MBSSE). This document: — specifies a reference model for the overall structure and processes of MBSSE-specific processes, and describes how the components of the reference model fit together; — specifies interrelationships between the components of the reference model; — specifies MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, outcomes and tasks; — specifies methods to support the defined tasks of each process; — specifies tool capabilities to automate or semi-automate tasks or methods. This document does not bring any additional life cycle processes for system and software but specifies an MBSSE reference model considered as activities, not only from the life cycle perspectives of systems engineering problem solving and the system-of-interest evolution, but also from the cognitive perspectives of modelling and model management, which can sustain and facilitate the system and software life cycle processes during digital transformation and in the digital age. The processes defined in this document are applicable for a single project, as well as for an organization performing multiple projects or an enterprise. These processes are applicable for managing and performing the systems and software engineering activities based on models within any stage in the life cycle of a system-of-interest.
- Standard85 pagesEnglish languagesale 15% off
This document establishes a common framework of process descriptions for describing the life cycle of systems created by humans, defining a set of processes and associated terminology from an engineering viewpoint. These processes can be applied to systems of interest, their system elements, and to systems of systems. Selected sets of these processes can be applied throughout the stages of a system's life cycle. This is accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. This document defines a set of processes to facilitate system development and information exchange among acquirers, suppliers, and other stakeholders in the life cycle of a system. This document specifies processes that support the definition, control, and improvement of the system life cycle processes used within an organization or a project. Organizations and projects can use these processes when acquiring and supplying systems. This document applies to organizations in their roles as both acquirers and suppliers. This document applies to the full life cycle of systems, including conception, development, production, utilization, support and retirement of systems, and to the acquisition and supply of systems, whether performed internally or externally to an organization. The life cycle processes of this document can be applied iteratively and concurrently to a system and recursively to the system elements. This document applies to one-of-a-kind systems, mass-produced systems, and customised, adaptable systems. It also applies to a complete stand-alone system and to systems that are embedded and integrated into larger more complex and complete systems. This document does not prescribe a specific system life cycle model, development methodology, method, modelling approach or technique. This document does not detail information items in terms of name, format, explicit content, and recording media. ISO/IEC/IEEE 15289 addresses the content for life cycle process information items (documentation).
- Standard116 pagesEnglish languagesale 15% off
This document describes information items enabling systematic human-centred design for interactive
systems.
Some of these information items are elaborated by separate International Standards, named the
Common Industry Format (CIF) for usability-related information.
This document provides the framework of information items, including definitions and the content for
each information item.
This document includes the following:
— the intended users of the information items;
— consistent terminology;
— the high-level content structure to be used for documenting each information item.
The information items are intended to be used as part of system-level documentation resulting from
development processes such as those in ISO 9241-210, ISO 9241-220 and ISO/IEC JTC 1/SC 7 process
standards (e.g. ISO/IEC/IEEE 15288, ISO/IEC/IEEE 29148).
This document focuses on those information items needed for design, development and evaluation
of usable systems, rather than prescribing a specific process. It is intended to be used in conjunction
with existing International Standards, including the standards of the ISO 9241 series and the SQuaRE
documents.
This document does not prescribe any kind of method, life cycle or process.
NOTE The information items produced by human-centred design activities can be incorporated in design
approaches as diverse as object-oriented, waterfall, HFI (human factors integration), agile and rapid development.
- Technical report28 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes information items enabling systematic human-centred design for interactive systems. Some of these information items are elaborated by separate International Standards, named the Common Industry Format (CIF) for usability-related information. This document provides the framework of information items, including definitions and the content for each information item. This document includes the following: — the intended users of the information items; — consistent terminology; — the high-level content structure to be used for documenting each information item. The information items are intended to be used as part of system-level documentation resulting from development processes such as those in ISO 9241-210, ISO 9241-220 and ISO/IEC JTC 1/SC 7 process standards (e.g. ISO/IEC/IEEE 15288, ISO/IEC/IEEE 29148). This document focuses on those information items needed for design, development and evaluation of usable systems, rather than prescribing a specific process. It is intended to be used in conjunction with existing International Standards, including the standards of the ISO 9241 series and the SQuaRE documents. This document does not prescribe any kind of method, life cycle or process. NOTE The information items produced by human-centred design activities can be incorporated in design approaches as diverse as object-oriented, waterfall, HFI (human factors integration), agile and rapid development.
- Technical report20 pagesEnglish languagesale 15% off
This document provides an overview of process assessment and interprets the requirements of ISO/IEC 33002 and ISO/IEC 33004 through the provision of guidance on the selection and use of assessment models, documented assessment processes, and instruments or tools for assessment. Process assessment is applicable in the following circumstances: a) by or on behalf of an organization with the objective of understanding the state of its own processes for process improvement; b) by or on behalf of an organization with the objective of determining the suitability of its own processes for a particular requirement or class of requirements; c) by or on behalf of one organization with the objective of determining the suitability of another organization's processes for a particular contract or class of contracts.
- Technical specification22 pagesEnglish languagesale 15% off
This document specifies requirements for efficient development and management of information produced — throughout the life cycle of a system and software product; — for the provision of information for users of systems and software; — for the management of IT and support services. This document is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content management process presented in Clauses 6 to 10 is a specialization (lower-level process) of the information management process specified in ISO/IEC/IEEE 15288 and ISO/IEC/IEEE 12207.
- Standard53 pagesEnglish languagesale 15% off
This document, within the context of methods and tools that support the configuration management (CM) capability of software and systems product line engineering: — specifies processes for product line CM (the processes are described in terms of purpose, inputs, tasks, and outcomes); — specifies method capabilities to support the defined tasks of each process; — specifies tool capabilities that automate or semi-automate tasks and methods. This document does not concern the processes and capabilities of tools and methods for a single system but rather deals with those for a family of products.
- Standard34 pagesEnglish languagesale 15% off
This document, within the context of methods and tools that support the product line measurement and management and that demonstrate the quality of the products and a product line: — specifies processes for product line measurement (the processes are described in terms of purpose, inputs, tasks and outcomes); — specifies method capabilities to support the defined tasks of each process; — specifies tool capabilities that automate or semi-automate tasks and methods. This document does not concern the processes and capabilities of tools and methods for a single system but rather deals with those for a family of products.
- Standard39 pagesEnglish languagesale 15% off
This document: — gives information for software testers for the systematic, risk-based testing of biometric systems and larger systems which include biometric subsystems; — establishes the importance of both biometric standards and software testing standards and provides overviews of both areas and their standardization; — specifies the most important biometric standards for software testers of biometric systems; — provides information for software testers who wish to conform to both the relevant biometrics standards and the ISO/IEC/IEEE 29119 series of software testing standards by providing mappings between the two sets of standards; — is not limited to the testing of the technical performance of biometric systems in terms of error rates and throughput rates, but instead covers the testing of the full range of relevant quality characteristics, such as reliability, availability, maintainability, security, conformance, usability, human factors, and privacy regulation compliance; — gives information on applying a risk-based testing approach to the testing of biometric systems that covers the full range of product and project risks; — provides testers with an example set of product and project risks associated with biometric systems along with suggestions on how these risks can be treated as part of a risk-based approach to the testing; — includes mappings between the documentation requirements of ISO/IEC 19795-1, ISO/IEC 19795-2 and ISO/IEC 19795-6 and the software test documentation defined by ISO/IEC/IEEE 29119-3.
- Technical report274 pagesEnglish languagesale 15% off
The standard establishes a set of processes by which engineers and technologists can include consideration of ethical values throughout the stages of concept exploration and development, which encompass system initiation, analysis, and design. This standard provides engineers and technologists with an implementable process aligning innovation management processes, system design approaches, and software engineering methods to help address ethical concerns or risks during system design. IEEE Std 7000™ does not give specific guidance on the design of algorithms to apply ethical values such as fairness and privacy.
- Standard69 pagesEnglish languagesale 15% off
This document specifies requirements for structure terminology of assurance cases. This document is applicable for developing and maintaining assurance cases.
- Standard20 pagesEnglish languagesale 15% off
This document specifies requirements for the structure and expression of an architecture description (AD) for various entities, including software, systems, enterprises, systems of systems, families of systems, products (goods or services), product lines, service lines, technologies and business domains. This document distinguishes the architecture of an entity of interest from an AD expressing that architecture. Architectures are not the subject of this document. This document specifies requirements for use of the architectural concepts and their relationships as captured in an AD. It does not specify requirements for any entity of interest or its environment. This document specifies requirements for an architecture description framework (ADF), an architecture description language (ADL), architecture viewpoints and model kinds in order to usefully support the development and use of an AD. This document specifies conformance to the requirements for an AD, ADF, ADL, architecture viewpoint and model kind. This document does not specify the processes, architecting methods, models, notations, techniques or tools by which an AD is created, utilized or managed. This document does not specify any format or media for recording an AD.
- Standard62 pagesEnglish languagesale 15% off
This document provides requirements and guidance on the implementation of DevOps to define, control, and improve software life cycle processes. It applies within an organization or a project to build, package, and deploy software and systems in a secure and reliable way. This document specifies practices to collaborate and communicate effectively in groups including development, operations, and other key stakeholders. This document applies a common framework for software life cycle processes, with well-defined terminology. It contains processes, activities, and tasks that are to be applied to the full life cycle of software systems, products, and services, including conception, development, production, utilization, support, and retirement. It also applies to the acquisition and supply of software systems, whether performed internally or externally to an organization. These life cycle processes are accomplished through the involvement of stakeholders, with the ultimate goal of achieving customer satisfaction. The life cycle processes of this document can be applied concurrently, iteratively, and recursively to a software system and incrementally to its elements. This document applies to software systems, products, and services, and the software portion of any system. Software includes the software portion of firmware. Those aspects of system definition needed to provide the context for software systems, products, and services are included. There is a wide variety of software systems in terms of their purpose, domain of application, complexity, size, novelty, adaptability, quantities, locations, life spans, and evolution. This document describes the processes that comprise the life cycle of software systems. It therefore applies to one-of-a-kind software systems, software systems for wide commercial or public distribution, and customized, adaptable software systems. It also applies to a complete stand-alone software system and to software systems that are embedded and integrated into larger, more complex, and complete systems.
- Standard81 pagesEnglish languagesale 15% off
This document defines the quality model of cloud services. The quality model of cloud services is composed of nine characteristics (some of which are further subdivided into subcharacteristics), which provide consistent terminology for specifying, measuring and evaluating cloud services so that the stakeholders, cloud service customer (CSC), cloud service provider (CSP) and cloud service partner (CSN) have a common understanding. Since the quality model in this document is the extension to the existing quality models defined in ISO/IEC 2501n, it can be used with the product quality model, IT service quality model, data quality model, and quality-in-use model according to evaluation purposes. As there are several cloud service categories, this document focuses on the quality model of SaaS (Software as a Service). NOTE Future documents are intended to address PaaS (Platform as a Service) and IaaS (Infrastructure as a Service).
- Technical specification15 pagesEnglish languagesale 15% off
This Handbook provides advice, interpretations, elaborations and software engineering best practices for the implementation of the requirements specified in EN 16603-40 (based on ECSS-E-ST-40C). The handbook is intended to be applicable to both flight and ground. It has been produced to complement the EN 16603-40 Standard, in the area where space project experience has reported issues related to the applicability, the interpretation or the feasibility of the Standard. It should be read to clarify the spirit of the Standard, the intention of the authors or the industrial best practices when applying the Standard to a space project.
The Handbook is not a software engineering book addressing the technical description and respective merits of software engineering methods and tools.
- Standard198 pagesEnglish languagesale 10% offe-Library read for1 day
This Handbook provides recommendations for the implementation of an Agile approach in space software projects complying with EN 16603-40 (based on ECSS-E-ST-40) and EN 16602-80 (based on ECSS-Q-ST-80).
This handbook is not an Agile development book, though it provides an Agile reference model based on Scrum and also covers other major Agile methods and techniques. Scrum has been selected as reference because of its widespread application in industry and its flexibility as a development framework to introduce or merge with other Agile methods and techniques. In relation to the EN 16603-40 and EN 16602-80, this handbook does not provide any tailoring of their requirements due to the use of the Agile approach, but demonstrates how compliance towards ECSS can be achieved. This handbook does not cover contractual aspects for this particular engineering approach, although it recognises that considering the approach of fixing cost and schedule and making the scope of functionalities variable, the customer and supplier need to establish specific contractual arrangements. Furthermore, it does not impose a particular finality for the use of Agile, either as a set of team values, project management process, specific techniques or supporting exploration by prototypes.
- Technical report105 pagesEnglish languagesale 10% offe-Library read for1 day
This Handbook provides recommendations for the implementation of an Agile approach in space software projects complying with EN 16603-40 (based on ECSS-E-ST-40) and EN 16602-80 (based on ECSS-Q-ST-80).
This handbook is not an Agile development book, though it provides an Agile reference model based on Scrum and also covers other major Agile methods and techniques. Scrum has been selected as reference because of its widespread application in industry and its flexibility as a development framework to introduce or merge with other Agile methods and techniques. In relation to the EN 16603-40 and EN 16602-80, this handbook does not provide any tailoring of their requirements due to the use of the Agile approach, but demonstrates how compliance towards ECSS can be achieved. This handbook does not cover contractual aspects for this particular engineering approach, although it recognises that considering the approach of fixing cost and schedule and making the scope of functionalities variable, the customer and supplier need to establish specific contractual arrangements. Furthermore, it does not impose a particular finality for the use of Agile, either as a set of team values, project management process, specific techniques or supporting exploration by prototypes.
- Technical report105 pagesEnglish languagesale 10% offe-Library read for1 day
This Handbook provides advice, interpretations, elaborations and software engineering best practices for the implementation of the requirements specified in EN 16603-40 (based on ECSS-E-ST-40C). The handbook is intended to be applicable to both flight and ground. It has been produced to complement the EN 16603-40 Standard, in the area where space project experience has reported issues related to the applicability, the interpretation or the feasibility of the Standard. It should be read to clarify the spirit of the Standard, the intention of the authors or the industrial best practices when applying the Standard to a space project.
The Handbook is not a software engineering book addressing the technical description and respective merits of software engineering methods and tools.
- Standard198 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies general concepts in software testing and presents key concepts for the ISO/IEC/IEEE 29119 series.
- Standard47 pagesEnglish languagesale 15% off
- Standard55 pagesEnglish languagesale 15% off
- Standard51 pagesFrench languagesale 15% off
This document provides guidance for the maintenance of software, based on the maintenance process and its activities and tasks defined in ISO/IEC/IEEE 12207:2017, 6.4.13. Moreover, this document describes the maintenance process in greater detail and establishes definitions for the various types of maintenance. This includes maintenance for multiple software products with the same maintenance resources. “Maintenance” in this document means software maintenance unless otherwise stated. The document does not address the operation of software and the operational functions, e.g. backup, recovery, system administration, which are normally performed by those who operate the software. However, it does include the related disposal process defined in ISO/IEC/IEEE 12207:2017, 6.4.14. This document is written primarily for managers, maintenance organizations, quality managers, users and acquirers of systems containing software. Many of the activities and tasks discussed in this document apply equally to maintenance services, as well as to maintained software products. For example, in a COTS intensive system, maintenance services are performed to sustain the product in operations. While the scope of this document is software maintenance, hardware and hardware costs are important considerations for maintenance.
- Standard36 pagesEnglish languagesale 15% off
This document covers the development process for designers and developers of information for users of software. It describes how to establish what information users need, how to determine the way in which that information should be presented, and how to prepare the information and make it available. It is not limited to the design and development stage of the life cycle, but includes information on design throughout the life cycle, such as design strategy and maintaining a design. This document provides requirements for the structure, information content, and format of information for users of software. This document can be applied to developing the following types of information, although it does not cover all aspects of them: — information for users of products other than software; — multimedia systems using animation, video, and sound; — computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs; — maintenance information describing the internal operation of systems software; — information for users incorporated into the user interface itself. This document is applicable to information architects and information developers, including a variety of specialists: — information architects who plan the structure and format of information products; — usability specialists and business analysts who identify the tasks that the intended users can perform with the software; — developers and editors of the written content of information for users; — graphic designers with expertise in electronic media; — user interface designers and ergonomics experts working together to design the presentation of the information on the screen. This document is also a reference for those with other roles and interests in the process of developing information for users: — managers of the software development process or the information-development process; — acquirers of information for users prepared by suppliers; — usability testers, reviewers of information for users, subject-matter experts; — developers of tools for creating information for users; — human-factors experts who identify principles for making information for users more accessible and easily used.
- Standard64 pagesEnglish languagesale 15% off
This document defines the LIFE CYCLE requirements for development and maintenance of HEALTH SOFTWARE needed to support conformance to IEC 62443-4-1 – taking the specific needs for HEALTH SOFTWARE into account. The set of PROCESSES, ACTIVITIES, and TASKS described in this document establishes a common framework for secure HEALTH SOFTWARE LIFE CYCLE PROCESSES. The purpose is to increase the CYBERSECURITY of HEALTH SOFTWARE by establishing certain ACTIVITIES and TASKS in the HEALTH SOFTWARE LIFE CYCLE PROCESSES and also by increasing the SECURITY of SOFTWARE LIFE CYCLE PROCESSES themselves. It is important to maintain an appropriate balance of the key properties SAFETY, effectiveness and SECURITY as discussed in ISO 81001-1. This document excludes specification of ACCOMPANYING DOCUMENTATION contents.
- Draft52 pagesEnglish languagesale 15% off
This document defines enrichments, extensions and structuring mechanisms of Petri nets, applied on the definitions proposed in ISO/IEC 15909-1. This document facilitates the definitions of new kinds of Petri nets and their interoperability, while remaining compatible with those defined in ISO/IEC 15909-1. This document is written as a reference for designers of new Petri net variants, by defining common enrichments, extensions and structuring mechanisms, as well as a generalized process for defining new ones. This document is applicable to a wide variety of concurrent discrete event systems and in particular distributed systems. Generic fields of application include: — requirements analysis; — development of specifications, designs and test suites; — descriptions of existing systems prior to re-engineering; — modelling business and software processes; — providing the semantics for concurrent languages; — simulation of systems to increase confidence; — formal analysis of the behaviour of systems; — and development of Petri net support tools. This document can be applied to the design of a broad range of systems and processes, including aerospace, air traffic control, avionics, banking, biological and chemical processes, business processes, communication protocols, computer hardware architectures, control systems, databases, defence command and control systems, distributed computing, electronic commerce, fault-tolerant systems, games, hospital procedures, information systems, Internet protocols and applications, legal processes, logistics, manufacturing systems, metabolic processes, music, nuclear power systems, operating systems, transport systems (including railway control), security systems, telecommunications and workflow.
- Standard15 pagesEnglish languagesale 15% off
- Standard15 pagesEnglish languagesale 15% off
This document defines test design techniques that can be used during the test design and implementation process that is defined in ISO/IEC/IEEE 29119‑2. Each technique follows the test design and implementation process that is defined in ISO/IEC/IEEE 29119‑2 and shown in Figure 1. This document is intended for, but not limited to, testers, test managers, and developers, particularly those responsible for managing and implementing software testing.
- Standard135 pagesEnglish languagesale 15% off
- Standard135 pagesEnglish languagesale 15% off
This document specifies test processes that can be used to govern, manage and implement software testing for any organization, project or testing activity. It comprises generic test process descriptions that define the software testing processes. Supporting informative diagrams describing the processes are also provided. This document is applicable to testing in all software development lifecycle models. This document is intended for, but not limited to, testers, test managers, developers and project managers, particularly those responsible for governing, managing and implementing software testing.
- Standard54 pagesEnglish languagesale 15% off
- Standard54 pagesEnglish languagesale 15% off