质量体系tl9000-30标准(编辑修改稿)

质量体系tl9000-30标准(编辑修改稿)内容摘要：

d processes 与顾客有关的过程 Determination of requirements related to the product 与产品有关的要求的确定 Review of requirements related to the product 与产品有关的要求的评审 1: The contract review process should include: 注解 1：合同评审 过程应包括： a) product acceptance planning and review, 产品验收策划和评审 9 b) handling of problems detected after product acceptance, including customer plaints and claims, and 产品验收后发现问题的处理，包括客户投诉及要求，等 c) responsibility of removal and/or correction of nonconformities after applicable warranty period or during product maintenance contract period. [9] 在保证期或维修合约有效期间有责任删除和 /或修正不符合项目。 [9] 2: The product acceptance plan should include as appropriate: 注解 2：产品验收策划应当包括以下内容作为补充： a) acceptance review process, 验 收评审过程， b) acceptance criteria, 验收标准 c) documented test procedure(s), 文件化的检测程序 d) test environment, 检测环境 e) test cases, 检测实例 f) test data, 检测数据 g) resources involved, 相关资源 h) method(s) for problem tracking and resolution, and 问题追 踪及解决方法，等 i) required acceptance test reports. [10] 必要的检验报告 Customer munication 顾客沟通 Notification About Problems – The anization shall establish and maintain a documented procedure(s) to notify all customers who may be affected by a reported problem that is service affecting. [5] 关于问题的通知－ 组织应建立并维护一套程序文件以通知可能受已报告的服务问题影响的所有顾客。 Problem Severity – The anization shall assign severity levels to customer reported problems based on the impact to the customer in accordance with the definitions of critical, major, and minor problem reports contained in the glossary of this handbook. The severity level shall be used in determining the timeliness of the anization’s response. [11] 问题严重性－组织应根据对顾客的影响向顾客指明问题的严重程度，根据手册中的术语可分为严重，重 大，一般问题。 组织根据严重程度确定答复时间。 1: The customer and the anization should jointly determine the priority for resolving customerreported problems. 注解 1：顾客和组织共同确定解决顾客报告问题的优先程度。 Problem Escalation – The anization shall establish and maintain a documented escalation procedure(s) to resolve customerreported problems. [11] 问题升级－ 组织应建立并维护一套程序文件解决升级的顾客报告问题。 [11] Customer Feedback – The anization shall establish and maintain a documented procedure(s) to provide the customer with feedback on their problem reports in a timely manner. 顾客反馈－组织应建立并维护一套程序文件及时处理顾客问题反馈。 10 Organization’s Recall Process – The anization shall establish and maintain a documented procedure(s) for identifying and recalling products that are unfit to remain in service. 组织的回收过程－组织应建立并维护一套程序文件以鉴定和回收不适合维修的产品。 Design and development 设计和开发 Design and development planning 设计和开发策划 Project Plan – The anization shall establish and maintain a project plan based on the defined product life cycle model. The plan should include: 方案策划－ 组织应依据定义的产品生命周期模式建立并维护一个方案计划。 该计划应包括： a) project anizational structure, 方案组织结构 b) project roles and responsibilities, 方案角色及职责 c) interfaces with internal and external anizations, 与内部或外部组 织交流 d) means for scheduling, tracking, issue resolution, and reporting, 计划进度、跟踪、问题决定及报告的方式 e) budgets, staffing, and schedules associated with project activities, 与方案活动相关的预算、人员、进度 f) method(s), standards, documented procedure(s), and tools to be used, 方法，标准，程序文件以应用工具 g) references to related plans (., development, testing, configuration management, and quality), 策划相关的参考资料（例如：发展，测试，配置管理，及质量） h) projectspecific environment and physical resource considerations (., development, user documentation, testing, and operation), 方案详细考虑的环境及物质资源（例如：发展，用户证书，测试及操作） i) customer, user, and supplier involvement during the product life cycle (., joint reviews, informal meetings, and approvals), 产品生命周期内顾客，用户及厂商（例如：联合评审，非正式会议，以及批准） j) management of project quality, 方案质量管理 k) risk management and contingency plans (., technical, cost and schedules), 风险管理及意外事故策划（例如：技术，成本以及进度） l) performance, safety, security, and other critical requirements, 执行、保险、安全以及其它紧急需求 m) projectspecific training requirements, 方案详细培训需求 n) required certifications, 必须的证明， o) proprietary, usage, ownership, warranty, licensing rights, and 所有者，用法，所有权，授权，许可权力，等 p) postproject analysis. [10] 方案定位分析 . [10] 1: The project plan and any related plans may be an independent document, a part of another document, or prised of several documents. 注解 1：方案策划或其它相关策划可能是独立的文件，其它文件的由部分或由几个文件组成。 2: General work instructions defining tasks and responsibilities mon to all development projects need not be replicated as part of a project plan. 注解 2：总的工作指令定义的对于所有的开发方案都有效的任务和职则不必再在方案策划中重复引用。 Requirements Traceability – The anization shall establish and maintain a method to trace documented requirements through design and test. [11] 必要的可追踪性－组织应建立并维护一种方法对设计和测试过程的文件进行必要的追踪。 [11] 11 1: The anization should establish munication methods for dissemination of product requirements and changes to requirements to all impacted parties identified in the project plan. 注解 1：组织应建立一种联系方法来贯彻产品的要求并改进各种要求以符合方案策划的定义。 Test Planning – Test plans shall be documented and results recorded. Test plans should include: 检测策划－检测策划应形成文件并对结果加以记录。 检测策划应包括： a) scope of testing (., unit, feature, integration, system, acceptance), a) 检测范围（例如：单位、特性、综合性能、系统、验收） b) types of tests to be performed (., functional, boundary, usability, performance, regression, interoperability), b) 检测的执行形式（如：功能、范围、用途、性能、退步、协同工作能力） c) traceability to requirements, c) 必要的可追踪性 d) test environment (., relevancy to customer environment, operational use), d) 检测环境（例如：相关顾客环境，操作效用） e) test coverage (degree to which a test verifies a product’s functions, sometimes expressed as a percent of functions tested), e) 检测规模（验证产品功能的程度，有时表现为功能测试的百分比） f) expected results, f) 期望结果，。