1、Systems and software engineering Requirements for acquirers and suppliers of information for usersIngnierie du logiciel et des systmes Exigences pour acqureurs et fournisseurs de documentation utilisateurINTERNATIONAL STANDARDISO/IEC/IEEE26512Reference numberISO/IEC/IEEE 26512:2017(E)Second edition2
2、017-1s ISO/IEC 2017 IEEE 2017 ISO/IEC 2017 All rights reservedii IEEE 2017 All rights reservedISO/IEC/IEEE 26512:2017(E)COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2017, Published in Switzerland IEEE 2017 the respective address below. Ch. de Blandonnet 8 CP 401 3 Park Avenue, New YorkCH-1214 Vernier, Genev
3、a, Switzerland NY 10016-5997, USATel. +41 22 749 01 11 Fax +41 22 749 09 47 7 7www.iso.org www.ieee.orgISO/IEC/IEEE 26512:2017(E) iii ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Contents 1 Scope 1 2 Normative references 2 3 Terms and definitions 2 4 Conformance . 7 4.1 General 7 4
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
5、.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 the contract 13 6.3.5 Contract management and monitoring . 13 6.3.6 Acquirer acceptan
6、ce . 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 Pro
7、posal preparation . 15 6.5.4 Negotiating and agreeing the contract 15 6.5.5 Contract performance 15 6.5.6 Delivery . 16 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 Prod
8、uct 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 20 9 S
9、tatement of work . 21 10 Request for proposal 22 10.1 Request for proposal topics . 22 10.2 Project objectives 22 10.3 Requirements for supporting processes 23 ISO/IEC/IEEE 26512:2017(E) iv ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved 10.4 Supplier capabilities and experience . 23
10、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 o
11、f requirements 25 11.3 Scope of the project . 25 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 c
12、lauses and checklist for suppliers 31 ISO/IEC/IEEE 26512:2017(E) v ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Foreword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standa
13、rdization. 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
14、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 wit
15、hin 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
16、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
17、 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
18、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
19、 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 re
20、quired, for conducting inquiries into the legal validity or scope of patents or patent claims or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance or a Patent Statement and Licensing Declaration Form, if any, or in any licensing agr
21、eements are reasonable or non-discriminatory. Users of this document are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from ISO or the IEEE Standards As
22、sociation. ISO/IEC/IEEE 26512:2017 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 7, Software and systems engineering, in cooperation with the Software and Systems Engineering Standards Committee of the IEEE Computer Society, under the Partner Standa
23、rds Development Organization cooperation agreement between ISO and IEEE. This second edition of ISO/IEC/IEEE 26512 cancels and replaces ISO/IEC/IEEE 26512:2010 with minor revisions: removal of superfluous definitions; updated version of the information management process from the normative standard
24、ISO/IEC/IEEE 15288:2015; the addition of cross-reference Table 1, Acquirer and supplier processes; updates to the Bibliography; editorial changes. vi ISO/IEC 2017 All rights reserved IEEE 2017 All rights reservedISO/IEC/IEEE 26512:2017(E) Introduction This document was developed to assist users of I
25、SO/IEC/IEEE 15288:2015 or ISO/IEC 12207 to acquire or supply systems and software information for users and information services as part of the life cycle processes. It defines the information development process from the acquirers standpoint and the suppliers standpoint. This document addresses the
26、 identification, definition, and fulfillment of requirements for information for users as part of the acquisition and supply processes. This document covers the requirements for information items used in the acquisition of information for users: the acquisition plan, document specification, statemen
27、t of work, request for proposals, and the proposal. It also discusses the use of a Document Plan in the acquisition and supply processes. This document is independent of the software tools that can be used to produce information for users, and applies to both printed and on-screen material, and to o
28、ther media such as video or augmented reality systems. Much of its guidance is applicable to information for users for systems including hardware as well as software. Earlier standards tended to view the results of the information development process as a single book or multivolume set: a one-time d
29、eliverable. Increasingly, information acquirers and suppliers recognize that most information for users is now produced from managed re-use of previously developed information (single-source documentation) adapted for new software or system versions, or presentation in various on-screen and printed
30、media. While this document does not describe how to set up a content management system, it is applicable for organizations practicing single-source documentation, as well as for acquirers and suppliers of one-time deliverables. Anyone who uses products that contain software needs accurate informatio
31、n about how the software will help the user accomplish a task. Information for users can be the first tangible item that the user sees, and so influences the users first impressions of the product. If the information is supplied in a convenient form and is easy to find and understand, the user can q
32、uickly become proficient at using the product. Therefore, well-designed information for users not only assists the user and helps to reduce the cost of training and support, but also enhances the reputation of the product, its producer, and its suppliers. Although software developers intend to desig
33、n user interfaces that behave so intuitively that very little separate information is needed, this is rarely possible. Todays software offers increasingly robust functionality, not only within applications, but also across applications which intelligently exchange information with one another. Furth
34、er, most software includes underlying rules and calculations, or algorithms that affect the results a user can obtain when using the software. These underlying programming mechanics are discernable by users, but only through laborious testing. For these and other reasons, information for users remai
35、ns an essential component of usable software products and systems. Information for users is often regarded as something done after the system has been implemented. However, for high-quality information, its development needs to be regarded as an integral part of the software or system life cycle. In
36、 fact, quality information for users or information management services are important enough to require specific planning. Related standards for those acquiring and supplying information for software users include ISO/IEC 26514:2008 (IEEE Std 26514-2010), Systems and software engineering Requirement
37、s for designers and developers of user documentation, and ISO/IEC/IEEE 26513, Systems and software engineering Requirements for testers and reviewers of information for users. Other International Standards address the information for users and information management processes from the viewpoint of m
38、anagers and agile projects. ISO/IEC/IEEE 26512:2017(E) vii ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved This document is consistent with ISO/IEC 12207 and ISO/IEC 15288:2015 as an implementation of the Acquisition and Supply processes, which comprise the Agreement processes, and of
39、 the Information Management process. This document is intended for use in all types of organizations, whether they have a dedicated documentation department or not. It can be used as a basis for local standards and procedures. Readers are assumed to have experience or knowledge of general agreement
40、processes for acquisition and supply of products and services. The order of clauses in this document does not imply that the acquisition activities need to be performed in this order, nor that information for users needs to be developed in this order or presented to the user in this order. In each c
41、lause, the requirements are media-independent, as far as possible. The checklists in Annexes A and B can be used to track conformance with the requirements of this document for acquirers and suppliers of information products. The Bibliography contains references to source material used in the develo
42、pment of this document, as well as sources of additional information that might be useful to acquirers and suppliers. ISO/IEC/IEEE 26512:2017(E) 1 ISO/IEC 2017 All rights reserved IEEE 2017 All rights reserved Systems and software engineering Requirements for acquirers and suppliers of information f
43、or users 1 Scope 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
44、 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 a
45、nd 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 re
46、view coordination; information testing, particularly usability testing; information production and packaging; information distribution and delivery; advice on the selection and implementation of information de velopment tools and supporting systems; and information development process improvement. T
47、his 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 sp
