ITU-T Z 400-1993 Structure and Format of Quality Manuals for Telecommunications Software (Study Group X) 9 pp《电信软件质量手册的结构和格式(第10研究组)9页》.pdf

《ITU-T Z 400-1993 Structure and Format of Quality Manuals for Telecommunications Software (Study Group X) 9 pp《电信软件质量手册的结构和格式(第10研究组)9页》.pdf》由会员分享，可在线阅读，更多相关《ITU-T Z 400-1993 Structure and Format of Quality Manuals for Telecommunications Software (Study Group X) 9 pp《电信软件质量手册的结构和格式(第10研究组)9页》.pdf（9页珍藏版）》请在麦多课文档分享上搜索。

1、ITU-T RECMN*Z-400 93 m 4862593 0583538 333 m INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU MAN-MACHINE LANGUAGE 2.400 (03/93) STRUCTURE AND FORMAT OF QUALITY MANUALS FOR TELECOMMUNICATIONS SOFTWARE ITU-T Recommendation 2.400 (Previously “CCIlT Recommenda

2、tion”) ITU-T RECMN*Z.400 93 W 4Bb259L 05BL539 05T = FOREWORD The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecommunication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them

3、 with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. ITU-T Recommen

4、dation 2.400 was prepared by the ITU-T Study Group X (1988-1993) and was approved by the WTSC (Helsinki, March 1-12,1993). NOTES 1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCIT ceased to exist as of 28 February 1993. In its place, the ITU Telec

5、ommunication Standardization Sector (IT-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. In order not to delay publication of this Recommendation, no change has been made in the text to references contain

6、ing the acronyms “CCIT, CCIR or IFRB” or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new ITU structure. 2 telecommunication administration and a recognized operating agency. In this Re

7、commendation, the expression “Administration” is used for conciseness to indicate both a O ITU 1993 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writin

8、g from the ITU. ITU-T RECMN*Z-1400 93 = 4862573 05815140 871 CONTENTS 1 Introduction 2 Definitions 3 Types of quality manuals . 4 scope 5 Format of the quality manual . Annex A . Recommended format of a quality manual. sections and contents of sections . A.l Title pages . A.2 Table of contents . A.3

9、 General information A.4 Quality system - Framework A.5 A.6 Quality system - Supporting activities . Quality systems - Life cycle activities . Bibliography Recommendation 2.400 (03/93) Page 1 1 1 2 2 2 2 2 3 3 4 5 6 i ITU-T RECMN*Z=400 73 W 4862571 05815Yl 708 W Recommendation 2.400 STRUCTURE AND FO

10、RMAT OF QUALITY MANUALS FOR TELECOMMUNICATION SOFTWARE (Helsinki, 1993) 1 Introduction As telecommunication applications have grown in functionality, size and complexity, so has the importance of their quality. In order to meet requirements for quality, suppliers of telecommunication products and se

11、rvices need to develop, adopt, and follow a well defined quality system. The quality system should define the organizational structure, responsibilities, procedures, processes, and resources that are needed and used for implementing these requirements. International standards on quality systems for

12、general products/services are provided by IS0 9001. Guidelines for applying IS0 9001 to the development, supply, and maintenance of software are provided in IS0 9000-3, Part 3. 2 Definitions For the purposes of this document, the definitions given in IS0 2382-1 Part 01, IS0 8402 and IS0 9126 apply.

13、3 Types of quality manuals Quality manuals are documents describing quality systems. There are two types of quality manuals: 1) Operational quality manuals Operational quality manuals are used in the internal suppliers operations, and their target audience is all the suppliers employees. The purpose

14、s of these manuals are: - to serve as a reference for the procedures, rules, and practices that the suppliers employees should follow in order to ensure that the requirements for quality are met; - to serve as the basis for auditing, so that the suppliers management can determine whether these requi

15、rements are being met. 2) Demonstrational quality manuals Demonstrational quality manuals are used to demonstrate the quality system to people outside the suppliers organization, and their target audience is the suppliers customers and potential customers. The purposes of these manuals are: - to dem

16、onstrate to customers and potential customers that the supplier developed, adopted, and followed a quality system; - to present to customers and potential customers the outlines of the quality system; - to assure customers and potential customers that the quality system is adequate for their require

17、ments for quality. Some suppliers may prefer to develop one quality manual to be used for both operational and demonstrational purposes. Other suppliers may prefer to develop two separate quality manuals, one for each purpose. International standards and guidelines for developing quality manuals for

18、 general productdservices are currently being developed by ISO. Recommendation 2.400 (03/93) 1 ITU-T RECMN*Z=400 93 W 48b2.591 058l1.542 b44 = 4 Scope This Recommendation specifies the format of demonstrational quality manuals for telecommunication software. The Recommendation should be used when a

19、supplier of telecommunication products and/or services needs to demonstrate to customers and potential customers the quality system used for creating the software part of the telecommunication products. Suppliers may also use this Recommendation as guidelines for writing their operational quality ma

20、nual. NOTES 1 Suppliers may develop manuals describing the quality system of the whole telecommunication product rather than just of its software. In that case it is recommended that the demonstration of the quality systems elements applicable to the software follow the format described below. Eleme

21、nts of the quality system that are not applicable to the software part of the telecommunication product should be demonstrated in additional sections of the quality manual. 2 Elements of the quality system may contain proprietary information. In describing the various elements, the keyword is “demon

22、strate”. That is, the quality manual should prove that the quality system elements are implemented and that they satisfy their requirements. The level of disclosure of actual procedures and tools that constitute the quality system elements should be mutually agreed upon by the supplier and the custo

23、mer. 5 Format of the quality manual Annex A outlines the recommended format of a quality manual, its sections and the contents of each section. Annex A Recommended format of a quality manual, sections and contents of sections (This annex forms an integral part of this Recommendation) A.l Title pages

24、 A.1. Approval and authorization The quality manual should be accepted at the highest level of the suppliers management. The front page of the manual should contain the necessary statements and signatures of the approving managers to certify full acceptance of the quality manual. A.2 Issue identific

25、ation This section of the quality manual should show the suppliers document identification of the manual and should provide a summary of the different text units version numbers as well as the dates that they became official. A.2 Table of contents A table of contents should show the names of the sec

26、tions within the quality manual and how they can be found. The numberinglcoding system of sections, subsections, pages, figures, exhibits, diagrams, tables, etc. should be clear and logical. 2 Recommendation 2.400 (03/93) ITU-T RECMN*Z-400 93 W 4A6259L 0583543 580 A.3 General information A.3.1 Intro

27、duction This section should provide an introductory overview of the quality manual. A.3.2 Scope This section should describe the purpose of the quality manual and its intended audience. It should state whether the manual describes the quality system for all the suppliers telecommunication products o

28、r the quality system for some specific products; whether it describes the quality system for the whole product or only its software part; and whether it is used as a demonstrational quality manual, operational quality manual, or both. A.3.3. Revisions and maintenance procedures This section should d

29、escribe or reference the procedures for maintaining and changing the quality manual. It should show how the quality manual is maintained, who reviews its content and how often, who is authorised to change the manual, and who is authorised to approve the changes. A.3.4 History of changes This section

30、 should contain the history of the quality manual, including dates of previous issues and a brief description of the changes from one issue to the next. A.3.5 Distribution control This section should briefly describe the procedures used to control distribution of the quality manual. If appropriate,

31、the section may include a distribution list showing the number of quality manuals in existence and the holders of the numbered copies. A.4 Quaiity system - Framework A.4.1 Quaiity policy This section is where the suppliers management documents its quality policy, goals, and values; how they are bein

32、g communicated to and made understood by all levels of the organization; and how their implementation is ensured. This section should reflect section 4.1.1/ISO 9001: The suppliers management shall define and document its policy and objectives for, and commitment to, quality. The supplier shall ensur

33、e that this policy is understood, implemented and maintained at all levels of the organization. A.4.2 Organization A.4.2.1 General This section should provide a high level view of the suppliers organization. A.4.2.2 Quaiity organizations This section should provide a detailed description of the supp

34、liers quality organizations. The section should demonstrate that the responsibilities, authorities, and interrelations of all personnel and organizations who manage, perform, and verify work affecting quality are well defined. A.4.3 Quaiity system This section should show that the quality system as

35、described in the quality manual is an integrated process that is carried throughout the entire life cycle of the telecommunication software. The section should provide references to related documents that describe the quality systems implementation. Recommendation 2.400 (03/93) 3 ITU-T RECNN*Z.400 9

36、3 m 4862591 O581544 417 m A.4.4 Internal quality audits This section should demonstrate that the supplier implemented a comprehensive system of planned and documented audits to - - verify that all of the quality systems procedures, activities and elements are being followed; determine the effectiven

37、ess of the quality system. A.4.5 Corrective actions This section should describe the requirements for corrective actions and demonstrate that the supplier established, documented, and implemented procedures for - - - - analyzing processes and procedures to detect and eliminate potential causes of no

38、nconfonning software; investigating the causes of nonconforming software occurrences; applying corrective actions needed to prevent recurrence of nonconformity; implementing and recording the changes in processes and procedures that result from the corrective actions. AS Quality systems - Life cycle

39、 activities A.5.1 Contract review This section should demonstrate that the supplier established, documented, and implemented procedures for reviewing contracts. The procedures should be demonstrated as adequate for ensuring that - - - - the scope of the contract and its requirements are defined and

40、documented; the supplier has the capability to meet all contractual requirements; acceptance criteria are defined and documented; all information required by the customer from the supplier and by the supplier from the customer is well defined. A.5.2 Requirements specification This section should dem

41、onstrate that the supplier established, implemented, and documented procedures for creating a complete set of requirements and that the requirements satisfy the contractual agreement with the customer. A.5.3 Development planning This section should demonstrate that the supplier established, document

42、ed, and implemented procedures for planning the softwares development. It should be demonstrated that the development plan includes - allocation and organization of resources (human resources, non-human resources and subcontractors) that are adequate for developing the software; definitions of the q

43、uality objectives; - - assignment of responsibilities; - - - - schedule; - progress control. division of the development into logical phases; definitions of the required inputs to, outputs from, and verifications of each development phase; definitions of entrance and exit criteria for each phase; 4

44、Recommendation 2.400 (03/93) - ITU-T RECMN*Z*400 93 48b2593 0583545 353 = A.5.4 Design and implementation This section should demonstrate that the supplier established, documented, and implemented procedures for designing and implementing the telecommunication software. It should be clear that - the

45、 procedures constitute a systematic methodology that is appropriate and adequate for telecommunication software: the procedures ensure that the software satisfies all of its requirements. - ASS Testing and validation This section should demonstrate that the supplier established, documented, and impl

46、emented procedures for testing and validating the software. It should be demonstrated that these procedures ensure that - - the testing and validation are planned and the plan is documented; all the resources required for testing and validation, including hardware, test environment, and tools, are i

47、dentified and allocated; the testing and validation are complete; all of the software features (including quality features such as performance, robustness, usability, etc.) are tested and validated; all discovered problems and their possible impacts are recorded and solved: changed software and all

48、other parts of the software that may be affected by the change are retested. - - - A.5.6 Maintenance This section should demonstrate that the supplier established, documented, and implemented procedures for maintaining the software after it was delivered to the customer. It should be demonstrated th

49、at the procedures guarantee that - - - - the maintenance activities are planned and the plan is documented: an organization to coordinate and support the maintenance activities is defined: the interface between the supplier and the customer is well defined: the suppliers response time for addressing problems reported by the customer conforms to the contractual requirements: any changed or additional software conforms to the requirements for quality: interference with the customers operations due to the installation of changed or additional software does not exceed th