定价： 0元

定价： 382元

定价： 149元

定价： 149元

定价： 0元

定价： 67元

定价： 0元

定价： 0元

This guide recommends a procedure to be used to perform and document a failure analysis and the reporting and statistical analysis of reliability of power transformers and shunt reactors used on electric power systems.

定价： 104元 / 折扣价： 89 元

定价： 404元

定价： 0元

定价： 0元

This clause presents the scope, purpose, organisation, and candidate uses of this International Standard.This International Standard will support the interest of technical authors and associated roles responsible for producing user documentation for software and systems developed within an agile environment. This standard takes a process standard approach to specify the way in which user documentation can be developed in agile development projects.This standard provides requirements on… read more information management and documentation processes appropriate for software projects that are using agile development methods.The first part of this International Standard in Clause 5 covers the differences between agile development methodologies and traditional development methodologies.The second part of this International Standard in Clause 6 describes how the information development lead or project manager may plan and manage the user documentation development team in an agile environment.The third part of this International Standard in Clause 7 covers the relationship between the user documentation process and life cycle documentation process in agile development.This International Standard is intended neither to encourage nor to discourage the use of any particular agile development tools or methods.This Internal Standard provides guidance on processes appropriate for developers of user documentation in software and systems projects that are using agile development methodologies. It will not be limited to the development phase of the life cycle of user documentation, but includes activities throughout the user documentation life cycle.This International Standard is intended for use in all organisations that are using agile development, or are considering implementing their projects using these techniques. It is assumed that readers have experience or general knowledge of traditional user documentation processes. read less

定价： 52元 / 折扣价： 45 元

This document specifies the purpose and content of all identified systems and software life‐cycle and service management information items (documentation). The information item contents are defined according to generic document types, as presented in Clause 7, and the specific purpose of the document, as presented in Clause 10. This document assumes an organization is performing life‐cycle processes, or delivering system or software engineering services, using either or both of the following:… read more ISO/IEC/IEEE 12207:2017 software life cycle processes; ISO/IEC/IEEE 15288:2015 system life cycle processes. ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015 define an Information Management process, but do not "detail information items in terms of name, format, explicit content, and recording media" (ISO/IEC/IEEE 12207:2017, 1.4). These standards identify, recommend or require a number of documentation items. This document provides a mapping of processes from the above standards to a set of information items. It provides a consistent approach to meeting the information and documentation requirements of systems and software engineering and engineering service management. The generic document types defined in this document are used to identify the information necessary to support the processes required by ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 15288:2015. The generic document types (which can be referred to as information item types) are used to identify the information necessary to support the processes. For each life‐cycle process or service, it would be possible to prepare a policy, plan, procedures and reports, as well as numerous records, requests, descriptions and specifications. Such an elaboration of the documentation schema would be more rigorous than specified by ISO/IEC/IEEE 12207:2017 or ISO/IEC/IEEE 15288:2015. As ISO/IEC/IEEE 15288:2015, 1.4 points out, "The users of this document are responsible for selecting a life cycle model for the project and mapping the processes, activities, and tasks in this document into that model. The parties are also responsible for selecting and applying appropriate methodologies, methods, models and techniques suitable for the project." Thus, information items are combined or subdivided consistent with the life cycle model, as needed for project or organizational purposes, as further defined in Clause 4 and Clause 5. This document is not a management system standard and does not establish a service management system, quality management system, or asset management system. The scope of this document does not include the following: a) the format or content of recommended input data or input information items, except for the content of those input items that are also output information items; b) instructions on combining or subdividing information items and information item contents of a similar nature; c) guidance on selecting an appropriate presentation format, delivery media and maintenance technology for systems or software life‐cycle data, records, information items or documentation, such as electronic publishing systems, content management systems or data repositories; d) detailed content for information items related to general business, contractual, organizational and financial management that is not specific to systems and software engineering and engineering service management, such as business strategies, contract change notices (agreement change report), human resources and investment policies, personnel selection criteria, financial budgeting and accounting policies and procedures, cost reports, or payroll data; e) information items showing only approval of an ISO/IEC/IEEE 12207:2017 or ISO/IEC/IEEE 15288:2015 subclause, such as ISO/IEC/IEEE 12207:2017, 6.4.10.3 c) 3); f) any ISO/IEC/IEEE 15288:2015 or ISO/IEC/IEEE 12207:2017 subclause not explicitly or implicitly identifying the recording of information about a process, activity or task, for example, ISO/IEC/IEEE 12207:2017, 6.2.4.3 c); g) work products, models, software, and other artifacts of life‐cycle products and services that are not information items or records used in information items. read less

定价： 106元 / 折扣价： 91 元

This document specifies software test documentation templates that can be used for any organization, project or testing activity. It describes the test documentation that is an output of the processes specified in ISO/IEC/IEEE 29119-2. 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.

定价： 109元 / 折扣价： 93 元