Find the standard you are looking for at Engineering360. Documents are available for purchase from the IHS Standards Store.

1 - 20 of 54 results

IEEE - IEEE P730.2 DRAFT - IEEE GUIDE FOR SOFTWARE QUALITY ASSURANCE PLANNING Organization: IEEE
Date: 1995-04-01
Description: Purpose  This guide presents the current consensus of those in the software development and maintenance community with expertise or experience in generating, implementing, evaluating, and modifying an SQAP. The SQAP should describe the plans and activities for the Software Quality Assurance (SQA) staff. The SQA staff observes the development process and reports deficiencies observed in the procedures and the resulting products.
IEEE - IEEE 983 - GUIDE FOR SOFTWARE QUALITY ASSURANCE PLANNING (IEEE COMPUTER SOCIETY DOC.) Organization: IEEE
Date: 1986-01-13
Description: The purpose of this guide is to explain and clarify the contents of each section of a Software Quality Assurance Plan (SQAP) that satisfies the requirements of ANSI / IEEE Std 730-1984 [2].
IEEE - IEEE 1012A - SUPPLEMENT TO IEEE STANDARD FOR SOFTWARE VERIFICATION AND VALIDATION: CONTENT MAP TO IEEE/EIA 12207.1-1997 - IEEE COMPUTER SOCIETY DOCUMENT Organization: IEEE
Date: 1998-09-16
Description: Both IEEE Std 1012-1998 and IEEE/EIA 12207.1-1997 place requirements on plans for verification of soft- ware and validation of software.
IEEE - IEEE 730.1 - GUIDE FOR SOFTWARE QUALITY ASSURANCE PLANNING - REVISION AND REDESIGNATION OF IEEE STD 938-1986; IEEE COMPUTER SOCIETY DOCUMENT Organization: IEEE
Date: 1995-01-01
Description: Purpose This guide presents the current consensus of those in the software development and maintenance community with expertise or experience in generating, implementing, evaluating, and modifying an SQAP. The SQAP should describe the plans and activities for the Software Quality Assurance (SQA) staff. The SQA staff observes the development process and reports deficiencies observed in the procedures and the resulting products.
DSF/ISO/IEC/IEEE DIS 24748-5 - SYSTEMS AND SOFTWARE ENGINEERING -- LIFE CYCLE MANAGEMENT-- PART 5: SOFTWARE DEVELOPMENT PLANNING Organization: DS
Description: This International Standard ● specifies the required information items to be produced through the implementation of the required planning and control processes, ● specifies the required content of the required information items, and ● gives guidelines for the format and content of the required and related information items. 1.1 Applicability This International Standard is intended to provide guidance for parties involved in the planning of software engineering at all stages of the software life cycle. This standard is applicable to: ● those who use ISO/IEC/IEEE 12207 on projects dealing with software products and services related to those products, ● those who are responsible for the technical management of the development of software systems, ● organizations and individuals performing software development activities, and ● organizations and individuals developing information items during the development of software.
ISO/IEC/IEEE FDIS 24748-5 - SYSTEMS AND SOFTWARE ENGINEERING - LIFE CYCLE MANAGEMENT - PART 5: SOFTWARE DEVELOPMENT PLANNING Organization: ISO
Date: 2017-01-18
Description: This document is intended to provide guidance for parties involved in the planning of software engineering at all stages of the software life cycle. It is intended to provide a common framework for two‐party and multi‐party collaborations and can be applied where the parties are from the same organization.
IEEE - IEEE P24748-5 DRAFT - SYSTEMS AND SOFTWARE ENGINEERING LIFE CYCLE MANAGEMENT PART 5: SOFTWARE DEVELOPMENT PLANNING - IEEE COMPUTER SOCIETY Organization: IEEE
Date: 2016-12-01
Description: This International Standard is intended to provide guidance for parties involved in the planning of software engineering at all stages of the software life cycle. It is intended to provide a common framework for two-party and multi-party collaborations and may be applied where the parties are from the same organization.
IEEE - IEEE 1219 - STANDARD FOR SOFTWARE MAINTENANCE - IEEE COMPUTER SOCIETY DOCUMENT Organization: IEEE
Date: 1998-06-25
Description: The criteria established apply to both the planning of maintenance for software while under development, as well as the planning and execution of software maintenance activities for existing software products.
IEEE - IEEE 730 - SOFTWARE QUALITY ASSURANCE PROCESSES - IEEE COMPUTER SOCIETY Organization: IEEE
Date: 2014-03-27
Description: This standard establishes requirements for initiating, planning, controlling, and executing the Software Quality Assurance (SQA) processes of a software development or maintenance project.
IEEE - IEEE 1008 - SOFTWARE UNIT TESTING Organization: IEEE
Date: 1987-01-01
Description: Inside the Scope Software unit testing is a process that includes the performance of test planning, the acquisition of a test set, and the measurement of a test unit against its requirements.
DSF/ISO/IEC/IEEE FDIS 24748-4 - SYSTEMS AND SOFTWARE ENGINEERING -- LIFE CYCLE MANAGEMENT-- PART 4: SYSTEMS ENGINEERING PLANNING Organization: DS
Description: In this part of ISO/IEC/IEEE 24748 that plan for technical project management is termed the Systems Engineering Management Plan (SEMP). This part of ISO/IEC/IEEE 24748 is applicable to— those who use or plan to use ISO/IEC/IEEE 15288 on projects dealing with man-made systems including software-intensive systems, software products, and services related to those systems and products,— those who are responsible for the technical management of projects concerned with the engineering of systems,— those responsible for executing ISO/IEC/IEEE 15288 system life cycle processes at a project level,— organizations and individuals who are subcontracting a project management effort,— anyone developing engineering management documentation to complete technical planning aspects of their project's processes.
DS/ISO/IEC/IEEE 24748-4 - SYSTEMS AND SOFTWARE ENGINEERING – LIFE CYCLE MANAGEMENT – PART 4: SYSTEMS ENGINEERING PLANNING Organization: DS
Date: 2016-06-01
Description: In this part of ISO/IEC/IEEE 24748 that plan for technical project management is termed the Systems Engineering Management Plan (SEMP). This part of ISO/IEC/IEEE 24748 is applicable to— those who use or plan to use ISO/IEC/IEEE 15288 on projects dealing with man-made systems including software-intensive systems, software products, and services related to those systems and products,— those who are responsible for the technical management of projects concerned with the engineering of systems,— those responsible for executing ISO/IEC/IEEE 15288 system life cycle processes at a project level,— organizations and individuals who are subcontracting a project management effort,— anyone developing engineering management documentation to complete technical planning aspects of their project’s processes.In many organizations, the various responsibilities of technical management are assigned to more than one person.
ISO/IEC/IEEE 24748-4 - SYSTEMS AND SOFTWARE ENGINEERING - LIFE CYCLE MANAGEMENT - PART 4: SYSTEMS ENGINEERING PLANNING - FIRST EDITION Organization: ISO
Date: 2016-05-15
Description: This part of ISO/IEC/IEEE 24748 is applicable to - those who use or plan to use ISO/IEC/IEEE 15288 on projects dealing with man-made systems including software-intensive systems, software products, and services related to those systems and products, - those who are responsible for the technical management of projects concerned with the engineering of systems,  - those responsible for executing ISO/IEC/IEEE 15288 system life cycle processes at a project level, - organizations and individuals who are subcontracting a project management effort, - anyone developing engineering management documentation to complete technical planning aspects of their project’s processes.
IEEE - IEEE 24748-4 - SYSTEMS AND SOFTWARE ENGINEERING - LIFE CYCLE MANAGEMENT - PART 4: SYSTEMS ENGINEERING PLANNING Organization: IEEE
Date: 2016-05-15
Description: This part of ISO/IEC/IEEE 24748 is applicable to - those who use or plan to use ISO/IEC/IEEE 15288 on projects dealing with man-made systems including software-intensive systems, software products, and services related to those systems and products, - those who are responsible for the technical management of projects concerned with the engineering of systems, - those responsible for executing ISO/IEC/IEEE 15288 system life cycle processes at a project level, - organizations and individuals who are subcontracting a project management effort, - anyone developing engineering management documentation to complete technical planning aspects of their project’s processes.
IEEE - IEEE P24748-4 DRAFT - SYSTEMS AND SOFTWARE ENGINEERING - LIFE CYCLE MANAGEMENT - PART 4: SYSTEMS ENGINEERING PLANNING - IEEE COMPUTER SOCIETY Organization: IEEE
Date: 2015-12-01
Description: This part of ISO/IEC/IEEE 24748 is applicable to - those who use or plan to use ISO/IEC/IEEE 15288 on projects dealing with man-made systems including software-intensive systems, software products, and services related to those systems and products, - those who are responsible for the technical management of projects concerned with the engineering of systems, - those responsible for executing ISO/IEC/IEEE 15288 system life cycle processes at a project level, - organizations and individuals who are subcontracting a project management effort, - anyone developing engineering management documentation to complete technical planning aspects of their project’s processes.
IEEE - IEEE 1042 - GUIDE TO SOFTWARE CONFIGURATION MANAGEMENT - IEEE COMPUTER SOCIETY DOCUMENT Organization: IEEE
Date: 1987-01-01
Description: The text of the guide introduces the essential concepts of SCM, particularly those of special significance (for example, libraries and tools) to software engineering. It then presents the planning for SCM in terms of documenting a Plan following the outline of ANSI/IEEE Std 828-1983 [2] so that a user who is unfamiliar with the disciplines of software configuration management can gain some insight into the issues.
DS/ISO/IEC/IEEE 24765 - SYSTEMS AND SOFTWARE ENGINEERING - VOCABULARY Organization: DS
Date: 2011-05-27
Description: Terms have been excluded if they were - considered to be parochial to one group or organization; - company proprietary or trademarked; - multi-word terms whose meaning could be inferred from the definitions of the component words; - terms whose meaning in the information technology (IT) field could be directly inferred from their common English meaning. 1.1 Relationship of the print and internet-accessible versions The primary tool for maintaining this vocabulary is a database that is modified in a controlled fashion. Hosted by the IEEE Computer Society, the SEVOCAB (systems and software engineering vocabulary) database is publicly accessible at www.computer.org/sevocab.
ISO/IEC/IEEE 24765 - SYSTEMS AND SOFTWARE ENGINEERING - VOCABULARY - FIRST EDITION Organization: ISO
Date: 2010-12-15
Description: Relationship of the print and internet-accessible versions The primary tool for maintaining this vocabulary is a database that is modified in a controlled fashion. Hosted by the IEEE Computer Society, the SEVOCAB (systems and software engineering vocabulary) database is publicly accessible at www.computer.org/sevocab.
BSI - BS ISO/IEC 16326 - SOFTWARE ENGINEERING - LIFE CYCLE PROCESS - PROJECT MANAGEMENT Organization: BSI
Date: 2010-01-31
Description: This International Standard also quotes the extracted purpose and outcome statements from the project processes of ISO/IEC 12207:2008 (IEEE Std 12207-2008) and ISO/IEC 15288:2008 (IEEE Std 15288-2008), and adds detailed guidance for managing projects that use these processes for software products and software-intensive systems.
IEEE - IEEE 1012 - SYSTEM AND SOFTWARE VERIFICATION AND VALIDATION - IEEE COMPUTER SOCIETY Organization: IEEE
Date: 2012-03-29
Description: Purpose The purpose of this standard is to — Establish a common framework for V&V processes, activities, and tasks in support of all software life cycle processes, including acquisition, supply, development, operation, and maintenance processes — Define the V&V tasks, required inputs, and required outputs — Identify the minimum V&V tasks corresponding to a four-level software integrity scheme — Define the content of a software V&V plan (SVVP) 

1 - 20 of 54 results