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

1 - 20 of 31 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.
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. Ideally, maintenance planning should begin during the stage of planning for software development (see A.3 for guidance).
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 P12207-CD4-1602 - DRAFT IEEE STANDARD SYSTEMS AND SOFTWARE ENGINEERING - SYSTEM LIFE CYCLE PROCESSES - IEEE COMPUTER SOCIETY Organization: IEEE
Date: 2016-02-27
Description: The processes, activities and tasks of this International Standard may 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.
IEEE - IEEE P12207-DIS-1610 - DRAFT IEEE STANDARD SYSTEMS AND SOFTWARE ENGINEERING - SYSTEM LIFE CYCLE PROCESSES - IEEE COMPUTER SOCIETY Organization: IEEE
Date: 2016-10-01
Description: The processes, activities, and tasks of this document may 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.
IEC 61636 - SOFTWARE INTERFACE FOR MAINTENANCE INFORMATION COLLECTION AND ANALYSIS (SIMICA) - EDITION 1.0 Organization: IEC
Date: 2016-11-01
Description: These interfaces will support service definitions for creating application programming interfaces (API) for the access, exchange, and analysis of historical diagnostic and maintenance information. The standard will use the information models of IEEE Std 1232 as a foundation.
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. This standard is harmonized with the software life cycle process of ISO/IEC/IEEE 12207:20081 and the information content requirements of ISO/IEC/IEEE 15289:2011.
ISO/IEC/IEEE DIS 12207 - SYSTEMS AND SOFTWARE ENGINEERING - SOFTWARE LIFE CYCLE PROCESSES Organization: ISO
Date: 2016-09-21
Description: 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.
IEEE - IEEE 1042 - GUIDE TO SOFTWARE CONFIGURATION MANAGEMENT - IEEE COMPUTER SOCIETY DOCUMENT Organization: IEEE
Date: 1987-01-01
Description: 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.
IEEE - IEEE 1636 - TRIAL-USE STANDARD FOR SOFTWARE INTERFACE FOR MAINTENANCE INFORMATION COLLECTION AND ANALYSIS (SIMICA) Organization: IEEE
Date: 2009-03-19
Description: These interfaces will support service definitions for creating application programming interfaces (API) for the access, exchange, and analysis of historical diagnostic and maintenance information. The trial-use standard will use the information models of IEEE Std 1232 as a foundation.
NPFC - DI-MGMT-82035 - SOFTWARE RESOURCES DATA REPORTING: DEVELOPMENT AND MAINTENANCE REPORTS AND DATA DICTIONARY Organization: NPFC
Date: 2016-06-02
Description: Format 2, DD Form 3026-2, “Software Maintenance Report”, consists of two parts. Part 1, Software Maintenance Technical Data, reports the size, context and technical information.
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.
SAE - EIA 12207.2 - SOFTWARE LIFE CYCLE PROCESSES – IMPLEMENTATION CONSIDERATIONS - FORMERLY TECHAMERICA IEEE-EIA-12207.2 Organization: SAE
Date: 2015-07-01
Description: This guide provides implementation consideration guidance for the normative clauses of IEEE/EIA 12207.0. The guidance is based on software industry experience with the life cycle processes presented in IEEE/EIA 12207.0.
DS/ISO/IEC/IEEE 23026 - SYSTEMS AND SOFTWARE ENGINEERING - ENGINEERING AND MANAGEMENT OF WEBSITES FOR SYSTEMS, SOFTWARE, AND SERVICES INFORMATION Organization: DS
Date: 2015-06-03
Description: The goal of ISO/IEC/IEEE 23026:2015 is to improve the usability of informational websites and ease of maintenance of managed Web operations in terms of locating relevant and timely information, applying information security management, facilitating ease of use, and providing for consistent and efficient development and maintenance practices.
IEEE - IEEE J-STD-016 - STANDARD FOR INFORMATION TECHNOLOGY SOFTWARE LIFE CYCLE PROCESSES SOFTWARE DEVELOPMENT ACQUIRER- SUPPLIER AGREEMENT - ISSUED FOR TRIAL USE Organization: IEEE
Date: 1995-09-30
Description: It is also intended to merge commercial and Government software development requirements within the framework of the software life cycle process requirements of the Electronic Industries Association (EIA), Institute of Electrical and Electronics Engineers (IEEE), and International Organization for Standardization (ISO). The term "software development" is used as an inclusive term encompassing new development, modification, reuse, reengineering, maintenance, and all other processes or activities resulting in software products.
IEEE - IEEE 1558 - STANDARD FOR SOFTWARE DOCUMENTATION FOR RAIL EQUIPMENT AND SYSTEMS Organization: IEEE
Date: 2004-09-23
Description: Variation in the interpretation of the existing IEEE software standards has occurred within the rail transit industry.
DSF/ISO/IEC FDIS 26511 - SYSTEMS AND SOFTWARE ENGINEERING - REQUIREMENTS FOR MANAGERS OF USER DOCUMENTATION Organization: DS
Description: NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering - Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering - Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering - Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering -Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software engineering - Requirements for acquirers and suppliers of user documentation.
ISO/IEC/IEEE 26511 - SYSTEMS AND SOFTWARE ENGINEERING - REQUIREMENTS FOR MANAGERS OF USER DOCUMENTATION - FIRST EDITION, CORRECTED VERSION 3/15/202 Organization: ISO
Date: 2011-12-01
Description: NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering — Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering — Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software Engineering — Requirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software engineering — Requirements for acquirers and suppliers of user documentation.
IEEE - IEEE 26511 - SYSTEMS AND SOFTWARE ENGINEERING - REQUIREMENTS FOR MANAGERS OF USER DOCUMENTATION - IEEE COMPUTER SOCIETY Organization: IEEE
Date: 2012-01-01
Description: NOTE 1: Related standards of value to documentation managers and others involved in the process include ISO/IEC 26514:2008, Systems and software engineering — Requirements for designers and developers of user documentation (also available as IEEE Std 26514-2010, IEEE Standard for Adoption of ISO/IEC 26514:2008, Systems and Software Engineering — Requirements for Designers and Developers of User Documentation); ISO/IEC 26513:2009, Systems and software engineering — Requirements for testers and reviewers of user documentation (also available as IEEE Std 26513-2010, IEEE Standard for Adoption of ISO/IEC 26513:2009, Systems and Software EngineeringRequirements for Testers and Reviewers of User Documentation); and ISO/IEC/IEEE 26512:2011, Systems and software engineering — Requirements for acquirers and suppliers of user documentation.
SAE - J-STD-016 - STANDARD FOR INFORMATION TECHNOLOGY SOFTWARE LIFE CYCLE PROCESSES SOFTWARE DEVELOPMENT ACQUIRER-SUPPLIER AGREEMENT (ISSUED FOR TRIAL USE) - FORMERLY TECHAMERICA J-STD-016 Organization: SAE
Date: 1995-09-30
Description: The term Òsoftware developmentÓ is used as an inclusive term encompassing new development, modiÞcation, reuse, reengineering, maintenance, and all other processes or activities resulting in software products.

1 - 20 of 31 results