ISO/IEC/IEEE 26512:2018
(Main)Systems and software engineering — Requirements for acquirers and suppliers of information for users
Systems and software engineering — Requirements for acquirers and suppliers of information for users
This document supports the interest of system users in having consistent, complete, accurate, and usable information. It addresses both available approaches to standardization: a) process standards, which specify the way that information products are to be acquired and supplied; and b) information product standards, which specify the characteristics and functional requirements of the information. As defined in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288:2015, the acquisition and supply activities make up the agreement processes of the software or system life cycle. Acquisition and supply of information for users and related services are specializations of those processes. Such services can be acquired and supplied for any part of the information management process, such as the following: - information management; - information design and development; - information editing and review coordination; - information testing, particularly usability testing; - information production and packaging; - information distribution and delivery; - advice on the selection and implementation of information development tools and supporting systems; and - information development process improvement. This document provides an overview of the information management processes that are relevant to the acquisition and supply of information for users. It applies the Agreement processes (acquisition and supply) to information for users, and addresses the preparation of requirements for this information. These requirements are central to the information for users specification and statement of work discussed in this document. This document also addresses requirements for primary document outputs of the acquisition and supply process: the request for proposal and the proposal for documentation products and services. This document is intended for use in acquiring or supplying any type of information for users and is independent of information development or management tools or methodologies. This document might be helpful for acquiring and supplying the following types of information, although it does not cover all aspects of them: - 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 documentation describing the internal operation of systems software; - collaboratively generated, often known as "wiki", documentation, which will usually need to be curated periodically; and - information for users incorporated into the user interface. This document is applicable to acquirers and suppliers of information for users, including a variety of specialists: - analysts (e.g., business analysts, human factors engineers) who identify the tasks that the intended users will perform with the system; - managers of the software or system development process or the information management process; - managers of the acquisition process, and those who authorize and approve acquisitions; and - managers and authors involved in proposal preparation. It can also be consulted by those with other roles and interests in the information development process: - information designers and architects who plan the structure, format, and content requirements of information products; - experienced authors and editors who develop the written content for 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; - usability testers, information development reviewers, technical contacts; - developers of tools for creating on-screen information for users.
Ingénierie du logiciel et des systèmes — Exigences pour acquéreurs et fournisseurs de documentation utilisateur
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC/
STANDARD IEEE
Second edition
2018-06
Systems and software engineering —
Requirements for acquirers and
suppliers of information for users
Ingénierie du logiciel et des systèmes — Exigences pour acquéreurs et
fournisseurs de documentation utilisateur
Reference number
©
ISO/IEC 2018
©
IEEE 2018
© ISO/IEC 2018
© IEEE 2018
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO or IEEE at the
respective address below or ISO’s member body in the country of the requester.
ISO copyright office Institute of Electrical and Electronics Engineers, Inc
CP 401 • Ch. de Blandonnet 8 3 Park Avenue, New York
CH-1214 Vernier, Geneva NY 10016-5997, USA
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org Email: stds.ipr@ieee.org
Website: www.iso.org Website: www.ieee.org
Published in Switzerland
© ISO/IEC 2018 – All rights reserved
ii © IEEE 2018 – All rights reserved
Contents
1 Scope . 1
2 Normative references . 2
3 Terms and definitions . 2
4 Conformance . 7
4.1 General . 7
4.2 Definition of conformance . 7
4.3 Conformance situations . 7
5 Information for users within a system/software life cycle . 8
6 Agreement processes within a system/software life cycle . 10
6.1 General . 10
6.2 Information for users acquisition process . 11
6.2.1 Purpose of the acquisition process . 11
6.2.2 Outcomes of the acquisition process . 11
6.3 Information for users acquisition activities and tasks . 11
6.3.1 General . 11
6.3.2 Acquisition preparation . 11
6.3.3 Supplier selection . 13
6.3.4 Negotiating and agreeing to the contract . 13
6.3.5 Contract management and monitoring . 13
6.3.6 Acquirer acceptance . 14
6.3.7 Acquisition closure . 14
6.4 Information for users supply process . 14
6.4.1 Purpose of the supply process . 14
6.4.2 Outcomes of the supply process . 14
6.5 Information for users supply activities and tasks . 14
6.5.1 General . 14
6.5.2 Opportunity identification and evaluation . 15
6.5.3 Proposal preparation . 15
6.5.4 Negotiating and agreeing to the contract . 15
6.5.5 Contract performance . 15
6.5.6 Delivery . 17
7 Defining information for users requirements and constraints . 17
7.1 Aspects of requirements and constraints . 17
7.2 Schedule constraints . 17
7.3 Usability requirements . 18
7.4 Product modification requirements . 18
7.5 Localization and translation requirements . 19
7.6 Legal requirements . 19
7.7 Safety requirements . 20
7.8 Security requirements . 20
7.9 Standards and conventions . 20
7.10 Quality management requirements . 20
8 Specification of the information for users . 21
9 Statement of work . 21
10 Request for proposal . 22
10.1 Request for proposal topics . 22
10.2 Project objectives . 23
10.3 Requirements for supporting processes . 23
iii
© ISO/IEC 2018 – All rights reserved
© IEEE 2018 — All rights reserved
10.4 Supplier capabilities and experience . 23
10.5 Instructions for bidders . 23
10.6 List of deliverable information for users products or services . 23
10.7 Confidentiality and intellectual property . 24
10.8 Proposal evaluation criteria . 24
11 Information for users proposal . 24
11.1 Information for users proposal contents . 24
11.2 Understanding of requirements . 25
11.3 Scope of the project . 26
11.4 Processes . 26
11.5 Experience, capabilities, and available resources . 26
11.6 Schedule . 27
11.7 Deliverables . 27
11.8 Price proposal . 27
Annex A (informative) Requirements clauses and checklist for acquirers . 28
Annex B (informative) Requirements clauses and checklist for suppliers . 31
iv
© ISO/IEC 2018 – All rights reserved
© IEEE 2018 — All rights reserved
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are
members of ISO or IEC participate in the development of International Standards through technical
committees established by the respective organization to deal with particular fields of technical activity.
ISO and IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non‐governmental, in liaison with ISO and IEC, also take part in the work.
In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC
JTC 1.
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE‐SA) Standards Board. The IEEE develops its
standards through a consensus development process, approved by the American National Standards
Institute, which brings together volunteers representing varied viewpoints and interests to achieve the
final product. Volunteers are not necessarily members of the Institute and serve without compensation.
While the IEEE administers the process and establishes rules to promote fairness in the consensus
development process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the
information contained in its standards.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of ISO/IEC JTC 1 is to prepare International Standards. Draft International Standards
adopted by the joint technical committee are circulated to national bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is called to the possibility that implementation of this document may require the use of subject
matter covered by patent rights. By publication of this document, no position is taken with respect to the
existence or validity of any patent rights in connection therewith. ISO/IEC and IEEE is not responsible for
identifying essential patents or patent claims for which a license may be required, for conducting
inquiries into the legal validity or scope of patents
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.