|
US$854.00 · In stock
Delivery: <= 5 days. True-PDF full-copy in English will be manually translated and delivered via email.
GB/T 16680-2015: Systems and software engineering -- Requirements for managers of user documentation
Status: Valid GB/T 16680: Evolution and historical versions
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| GB/T 16680-2015 | English | 854 |
Add to Cart
|
5 days [Need to translate]
|
Systems and software engineering -- Requirements for managers of user documentation
| Valid |
GB/T 16680-2015
|
| GB/T 16680-1996 | English | 719 |
Add to Cart
|
5 days [Need to translate]
|
Guidelines for the management of software documentation
| Obsolete |
GB/T 16680-1996
|
PDF similar to GB/T 16680-2015
Basic data | Standard ID | GB/T 16680-2015 (GB/T16680-2015) | | Description (Translated English) | Systems and software engineering -- Requirements for managers of user documentation | | Sector / Industry | National Standard (Recommended) | | Classification of Chinese Standard | L77 | | Classification of International Standard | 35.080 | | Word Count Estimation | 43,421 | | Date of Issue | 2015-12-31 | | Date of Implementation | 2016-07-01 | | Older Standard (superseded by this standard) | GB/T 16680-1996 | | Regulation (derived from) | State Standard Announcement 2015 No.43 | | Issuing agency(ies) | General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China, Standardization Administration of the People's Republic of China | GB/T 16680-2015: Systems and software engineering -- Requirements for managers of user documentation
---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
Systems and software engineering - Requirements for managers of user documentation
ICS 35.080
L77
National Standards of People's Republic of China
Replacing GB/T 16680-1996
Systems and Software Engineering
Managers of user documentation requirements
(ISO /IEC 26511.2011, IDT)
Issued on. 2015-12-31
2016-07-01 implementation
Administration of Quality Supervision, Inspection and Quarantine of People's Republic of China
Standardization Administration of China released
Table of Contents
Introduction Ⅲ
Introduction Ⅳ
1 Scope 1
2 Compliance 2
2.1 Compliance Definition 2
2.2 Compliance Scene 2
3 Normative references 2
4 Terms and definitions 2
5 during the life cycle management of user documentation 5
5.1 software life cycle management of user documentation 5
5.2 portfolio management and content management 6
5.3 Information Management Strategy and Approach 6
6 7 document management planning
WBS 6.1 document management tasks 7
6.2 user documentation prepared plan 8
6.2.1 determine the target audience and 9
6.2.2 Design Task 10
6.2.3 Development Tasks 10
6.2.4 translation and localization tasks 10
6.2.5 Production Task 11
6.2.6 Change management and maintenance tasks 11
7 User Documentation Program 11
7.1 user documentation and documentation management plan Program 11
Content 7.2 Document Management Plan 12
Content 7.3 documentation program 12
8 project started 13
8.1 authorization, procedures and specifications 13
8.2 Infrastructure 14
8.3 Information Development team 14
8.3.1 Role Definitions 14
Roles 8.3.2 User documentation Example 15
9 user documentation management control method 18
9.1 Documentation measuring 18
9.1.1 user documentation measure 18
9.1.2 User documentation productivity measurement 19
9.1.3 User documentation quality measurement 19
9.1.4 Process improvement measure 20
9.2 document estimates 20
10 management control in the document application 21
10.1 Purpose and outcomes 21
21 10.2 Change Management
Schedule and cost control 10.3 21
10.4 Explorer 22
10.4.1 Project Communication 22
10.4.2 Document management team members and suppliers 22
10.4.3 Management Translation Services 22
10.5 Quality Management 23
10.5.1 management of product quality evaluation and testing --- 23
10.5.2 and risk management issues 23
23 10.5.3 Process Improvement
Appendix A (informative) Document prepared by Program Example 24
Appendix B (normative) information management software, document management and process 31
References 34
Foreword
This standard was drafted in accordance with GB/T 1.1-2009 given rules.
This standard replaces GB/T 16680-1996 "Software Document Management Guide."
This standard GB/T 16680-1996 revision compared with the GB/T 16680-1996, the main changes are as follows.
--- Name to "Systems and Software Engineering Manager user documentation requirements";
--- Adds the second chapter of compliance;
--- Remove the role of software in Chapter 4 of the document;
--- Remove the role of managers in Chapter 5;
--- Increased by 5.1 during the software life cycle management of user documentation;
--- Chapter 6 adds document management planning;
--- Chapter 6 developed documentation policies (see 1996 edition) was adjusted to 5.3 information management policies and guidelines;
--- Deleted the Chapter 7 to develop documentation standards and guidelines;
--- Increased Chapter 7 User Documentation Project;
--- Increase the project started in Chapter 8;
--- Original standard documentation Chapter 8 Program (see 1996 edition) was adjusted to 6.2 user documentation prepared plan;
--- Deleted Chapter 9 develop documentation procedures;
--- Increased Chapter 9 User documentation management control method;
--- Increased Chapter 10 in the document management and control applications;
--- 10.1 staff (see 1996 edition) was adjusted to 8.3 Information Development team;
--- 10.2 equipment (see 1996 edition) was adjusted to 8.2 infrastructure.
This standard uses the translation method identical with ISO /IEC 26511.2011 "Systems and software engineering managers of user documentation requirements."
The Standard made the following editorial changes.
--- For ease of use, the ISO /IEC 12207.2008 6.3.6 and 7.2.1 excerpts in the form given in Table B.1.
Please note that some of the content of this document may involve patents. Release mechanism of the present document does not assume responsibility for the identification of these patents.
This standard by the National Information Technology Standardization Technical Committee (SAC/TC28) and focal points.
This standard drafting units. Network Zhuhai Southern Software Testing Center, China Electronics Standardization Institute, Beijing Normal University, Zhuhai
Branch, National Network Software Product Quality Supervision and Inspection Center (Jinan).
The main drafters of this standard. Hou Jianhua, Liang Yong, Sun Wei, Ni Yuhua, Pengyu Fan, Liang new Huangzhao Sen, Huang Shanshan, phases Fumin,
Zhang Xueli, He Chunjiang, Yang Jing, Yu Wen, Zhang Yan, Zhang Jiajia.
GB/T 16680 previous version release case.
--- GB/T 16680-1996.
Introduction
Effective management of software user documentation is essential work that ensures user documentation is available, accurate, and can be efficiently formed and soft
Member matches documentation, delivered on time when the user needs. This standard focuses on the management of user documentation, including software and user documentation
The whole process from initial development to the subsequent release of all user documentation management.
Any person using the application software requires an accurate understanding of how the software is to help users complete tasks. Document may be the first form
Now the user in front of a tangible product, so it will affect the users of the product first impression. If the document forms convenient, it is easy to check
Find and understand, so users can quickly proficient in the use of the software product. Therefore, good management documentation process can not only help with
Households, but also beneficial to reduce training and support costs, but also improve the reputation of our products, manufacturers and vendors.
While many software designers want to design manipulation by the user interface more intuitive ways to reduce write standalone document, but
This approach virtually infeasible. User documentation is an integral part of the available software products essential.
Documentation is often considered work after the completion of the software. However, for high-quality software documentation, its preparation should be from the software
Planning and design stage, is an indispensable part of the software life cycle process. The correct approach is. Documentation or
Information management needs to have its own process and plans to complete the work plan and content it contains.
This standard will help users with the following two criteria. ISO /IEC 15288.2008 "Systems and software engineering life cycle system
Process ", and ISO /IEC 12207.2008" engineering software systems and software life cycle process "to help them to manage software user files
File as part of the software life cycle to work. This standard defines the terms of the manager software development process documentation. To help him
They formulation, implementation and evaluation of the management of user documentation.
NOTE. The documentation and information management processes other ISO /IEC 265NN series of international standards described in the document from the designer/developer, test and evaluation
The presiding officer, demand-side and supply-side perspectives forth.
This standard applies to the production of a series of documents of individuals or organizations, but also for the organization to develop a single document projects that are suitable within the team
And outsourced document preparation. In addition to the development and production of user manuals, help systems, as well as a separate software product documentation set, it
Also applies to a wider range of document management, including end-user documentation installation, implementation, management and operation of the software needed. Normally
Under conditions, user documentation manager is also responsible for the information used in the following situations (CMS) development and reuse.
--- With the software version of the update, multiple update user documentation;
--- Repeatedly reused or adjusted information to support related software products;
--- User documentation multiple versions of translation or localization;
--- Manage a group within the organization not related Documentation Project.
This standard is not intended to promote printed or electronic (screen) use of media files, or any specific information management, content management, text
Use test files, project management tool or protocol, but for the medium is irrelevant as far as possible. This standard applies to systems containing software used
User documentation preparation, but also for individual software user documentation work.
Systems and Software Engineering
Managers of user documentation requirements
1 Scope
The software supports standard user documentation for consistency, completeness, accuracy and availability requirements. It provides strategies for the document manager,
Planning, execution and control. It indicates the user through the entire process of document management software life cycle. It also includes a user document management Off
Key process, that program documentation and document management plan.
This standard provides an overview of the software and documentation for the documentation of the information management process. It also describes a process for the preparation of documents
The combination of planning and content management. Specifically, it focuses on the following.
--- Project startup management requirements, including the establishment of procedures and specifications, building infrastructure, team building and include user documentation team
Required for a character;
--- Document management control measuring and estimating required;
--- User documentation work management control;
--- Support the use of processes, such as change management, schedule and cost control, resource management, quality management and process improvement.
Reference list management, user documentation prepared and tested process provides guidance.
Note 1. The process involved managers and other documents relevant standards. ISO /IEC 26514.2008 "Systems and software engineering design of user documentation
And developer requirements "(IEEE Standard 26514-2010, using ISO /IEC 26514.2008 The IEEE standard for systems and software engineering
User documentation designers and developers request), ISO /IEC 26513.2009 "Systems and software engineering to user documentation testers and reviewers
Requirements "(IEEE Standard 26513.2010, using ISO /IEC 26513. IEEE standard, Systems and Software Engineering 2009 test for user documentation
And reviewers requirements) and ISO /IEC /IEEE26512.2011 "engineering systems and software user documentation for demand-side and supply-side requirements."
This standard applies to the use of user documentation project managers, and is suitable for organizations with information design and documentation developers.
This standard also for other roles and personnel documentation process of interest Reference.
--- Manager software development process;
--- Supply-side purchasing user documentation;
--- Experienced content writing user documentation personnel;
--- Create a developer of electronic documentation tools;
--- Research and make the document easier to use human factors analysis expert;
--- Electronic media graphic designer;
--- Design documents show common form of user interface designers and ergonomics experts on the screen.
This standard can also be used to manage the following types of documents, even though it does not cover all aspects.
--- To help users, training and sales documentation and system documentation for product design and development, these documents are text-based user
Files theme reuse;
--- Non-software product documentation;
--- Animation, video and sound multimedia sales presentations;
--- Formal training in computer-based training courses in the use of [computer-basedtraining (CBT)] and special resource package
Set of curriculum materials;
--- Describes the inner workings of the system software maintenance documentation.
NOTE 2. ISO /IEC /IEEE15289.2011 provides information on the life cycle process information items (documents) more details.
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of GB/T 16680-2015_English be delivered?Answer: Upon your order, we will start to translate GB/T 16680-2015_English as soon as possible, and keep you informed of the progress. The lead time is typically 3 ~ 5 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of GB/T 16680-2015_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 16680-2015_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay. Question 5: Should I purchase the latest version GB/T 16680-2015?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 16680-2015 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically.
|