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.<\/p>\n
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:<\/p>\n
information management;<\/p>\n<\/li>\n
information design and development;<\/p>\n<\/li>\n
information editing and review coordination;<\/p>\n<\/li>\n
information testing, particularly usability testing;<\/p>\n<\/li>\n
information production and packaging;<\/p>\n<\/li>\n
information distribution and delivery;<\/p>\n<\/li>\n
advice on the selection and implementation of information development tools and supporting systems; and<\/p>\n<\/li>\n
information development process improvement.<\/p>\n<\/li>\n<\/ul>\n
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.<\/p>\n
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.<\/p>\n
This document might be helpful for acquiring and supplying the following types of information, although it does not cover all aspects of them:<\/p>\n
multimedia systems using animation, video, and sound;<\/p>\n<\/li>\n
computer-based training (CBT) packages and specialized course materials intended primarily for use in formal training programs;<\/p>\n<\/li>\n
maintenance documentation describing the internal operation of systems software;<\/p>\n<\/li>\n
collaboratively generated, often known as \u201cwiki\u201d, documentation, which will usually need to be curated periodically; and<\/p>\n<\/li>\n
information for users incorporated into the user interface.<\/p>\n<\/li>\n<\/ul>\n
This document is applicable to acquirers and suppliers of information for users, including a variety of specialists:<\/p>\n
analysts (e.g., business analysts, human factors engineers) who identify the tasks that the intended users will perform with the system;<\/p>\n<\/li>\n
managers of the software or system development process or the information management process;<\/p>\n<\/li>\n
managers of the acquisition process, and those who authorize and approve acquisitions; and<\/p>\n<\/li>\n
managers and authors involved in proposal preparation.<\/p>\n<\/li>\n<\/ul>\n
It can also be consulted by those with other roles and interests in the information development process:<\/p>\n
information designers and architects who plan the structure, format, and content requirements of information products;<\/p>\n<\/li>\n
experienced authors and editors who develop the written content for information for users;<\/p>\n<\/li>\n
graphic designers with expertise in electronic media;<\/p>\n<\/li>\n
user interface designers and ergonomics experts working together to design the presentation of the information on the screen;<\/p>\n<\/li>\n
usability testers, information development reviewers, technical contacts;<\/p>\n<\/li>\n
developers of tools for creating on-screen information for users.<\/p>\n<\/li>\n<\/ul>\n
| PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
|---|---|---|---|---|---|---|---|
| 2<\/td>\n | undefined <\/td>\n<\/tr>\n | ||||||
| 10<\/td>\n | 1 Scope <\/td>\n<\/tr>\n | ||||||
| 11<\/td>\n | 2 Normative references 3 Terms and definitions <\/td>\n<\/tr>\n | ||||||
| 16<\/td>\n | 4 Conformance 4.1 General 4.2 Definition of conformance 4.3 Conformance situations <\/td>\n<\/tr>\n | ||||||
| 17<\/td>\n | 5 Information for users within a system\/software life cycle <\/td>\n<\/tr>\n | ||||||
| 19<\/td>\n | 6 Agreement processes within a system\/software life cycle 6.1 General <\/td>\n<\/tr>\n | ||||||
| 20<\/td>\n | 6.2 Information for users acquisition process 6.2.1 Purpose of the acquisition process 6.2.2 Outcomes of the acquisition process 6.3 Information for users acquisition activities and tasks 6.3.1 General 6.3.2 Acquisition preparation <\/td>\n<\/tr>\n | ||||||
| 21<\/td>\n | 6.3.2.1 Describing the need 6.3.2.2 Defining the requirements for information for users 6.3.2.3 Identifying an acquisition strategy 6.3.2.4 Preparing an acquisition plan 6.3.2.5 Preparing the request for proposal <\/td>\n<\/tr>\n | ||||||
| 22<\/td>\n | 6.3.2.6 Appropriately publishing and publicizing the acquisition requirement 6.3.3 Supplier selection 6.3.4 Negotiating and agreeing to the contract 6.3.5 Contract management and monitoring <\/td>\n<\/tr>\n | ||||||
| 23<\/td>\n | 6.3.6 Acquirer acceptance 6.3.7 Acquisition closure 6.4 Information for users supply process 6.4.1 Purpose of the supply process 6.4.2 Outcomes of the supply process 6.5 Information for users supply activities and tasks 6.5.1 General <\/td>\n<\/tr>\n | ||||||
| 24<\/td>\n | 6.5.2 Opportunity identification and evaluation 6.5.3 Proposal preparation 6.5.4 Negotiating and agreeing to the contract 6.5.5 Contract performance <\/td>\n<\/tr>\n | ||||||
| 25<\/td>\n | 6.5.5.1 Information Development Plan 6.5.5.2 Quality management 6.5.5.3 Configuration management <\/td>\n<\/tr>\n | ||||||
| 26<\/td>\n | 6.5.6 Delivery 7 Defining information for users requirements and constraints 7.1 Aspects of requirements and constraints 7.2 Schedule constraints <\/td>\n<\/tr>\n | ||||||
| 27<\/td>\n | 7.3 Usability requirements 7.4 Product modification requirements <\/td>\n<\/tr>\n | ||||||
| 28<\/td>\n | 7.5 Localization and translation requirements 7.6 Legal requirements <\/td>\n<\/tr>\n | ||||||
| 29<\/td>\n | 7.7 Safety requirements 7.8 Security requirements 7.9 Standards and conventions 7.10 Quality management requirements <\/td>\n<\/tr>\n | ||||||
| 30<\/td>\n | 8 Specification of the information for users 9 Statement of work <\/td>\n<\/tr>\n | ||||||
| 31<\/td>\n | 10 Request for proposal 10.1 Request for proposal topics <\/td>\n<\/tr>\n | ||||||
| 32<\/td>\n | 10.2 Project objectives 10.3 Requirements for supporting processes 10.4 Supplier capabilities and experience 10.5 Instructions for bidders 10.6 List of deliverable information for users products or services <\/td>\n<\/tr>\n | ||||||
| 33<\/td>\n | 10.7 Confidentiality and intellectual property 10.8 Proposal evaluation criteria 11 Information for users proposal 11.1 Information for users proposal contents <\/td>\n<\/tr>\n | ||||||
| 34<\/td>\n | 11.2 Understanding of requirements <\/td>\n<\/tr>\n | ||||||
| 35<\/td>\n | 11.3 Scope of the project 11.4 Processes 11.5 Experience, capabilities, and available resources <\/td>\n<\/tr>\n | ||||||
| 36<\/td>\n | 11.6 Schedule 11.7 Deliverables 11.8 Price proposal <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Systems and software engineering. Requirements for acquirers and suppliers of information for users<\/b><\/p>\n |