【文章內(nèi)容簡(jiǎn)介】 maintenance contract period. [9]在保證期或維修合約有效期間有責(zé)任刪除和/或修正不符合項(xiàng)目。[9] 2: The product acceptance plan should include as appropriate:注解2：產(chǎn)品驗(yàn)收策劃應(yīng)當(dāng)包括以下內(nèi)容作為補(bǔ)充：a) acceptance review process, 驗(yàn)收評(píng)審過(guò)程，b) acceptance criteria, 驗(yàn)收標(biāo)準(zhǔn)c) documented test procedure(s), 文件化的檢測(cè)程序d) test environment, 檢測(cè)環(huán)境e) test cases, 檢測(cè)實(shí)例f) test data, 檢測(cè)數(shù)據(jù)g) resources involved, 相關(guān)資源h) method(s) for problem tracking and resolution, and 問(wèn)題追蹤及解決方法，等i) required acceptance test reports. [10] 必要的檢驗(yàn)報(bào)告 Customer munication 顧客溝通 Notification About Problems – The organization 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]關(guān)于問(wèn)題的通知－ 組織應(yīng)建立并維護(hù)一套程序文件以通知可能受已報(bào)告的服務(wù)問(wèn)題影響的所有顧客。 Problem Severity – The organization shall assign severity levels to customer reportedproblems 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 organization’s response. [11]問(wèn)題嚴(yán)重性－組織應(yīng)根據(jù)對(duì)顧客的影響向顧客指明問(wèn)題的嚴(yán)重程度，根據(jù)手冊(cè)中的術(shù)語(yǔ)可分為嚴(yán)重，重大，一般問(wèn)題。組織根據(jù)嚴(yán)重程度確定答復(fù)時(shí)間。 1: The customer and the organization should jointly determine the priority for resolving customerreported problems.注解1：顧客和組織共同確定解決顧客報(bào)告問(wèn)題的優(yōu)先程度。 Problem Escalation – The organization shall establish and maintain a documented escalation procedure(s) to resolve customerreported problems. [11]問(wèn)題升級(jí)－ 組織應(yīng)建立并維護(hù)一套程序文件解決升級(jí)的顧客報(bào)告問(wèn)題。[11] Customer Feedback – The organization shall establish and maintain a documentedprocedure(s) to provide the customer with feedback on their problem reports in a timely manner.顧客反饋－組織應(yīng)建立并維護(hù)一套程序文件及時(shí)處理顧客問(wèn)題反饋。 Organization’s Recall Process – The organization shall establish and maintain a documented procedure(s) for identifying and recalling products that are unfit to remain in service.組織的回收過(guò)程－組織應(yīng)建立并維護(hù)一套程序文件以鑒定和回收不適合維修的產(chǎn)品。 Design and development設(shè)計(jì)和開(kāi)發(fā) Design and development planning 設(shè)計(jì)和開(kāi)發(fā)策劃 Project Plan – The organization shall establish and maintain a project plan based on the defined product life cycle model. The plan should include:方案策劃－ 組織應(yīng)依據(jù)定義的產(chǎn)品生命周期模式建立并維護(hù)一個(gè)方案計(jì)劃。該計(jì)劃應(yīng)包括：a) project organizational structure, 方案組織結(jié)構(gòu)b) project roles and responsibilities, 方案角色及職責(zé)c) interfaces with internal and external organizations, 與內(nèi)部或外部組織交流d) means for scheduling, tracking, issue resolution, and reporting, 計(jì)劃進(jìn)度、跟蹤、問(wèn)題決定及報(bào)告的方式e) budgets, staffing, and schedules associated with project activities, 與方案活動(dòng)相關(guān)的預(yù)算、人員、進(jìn)度f(wàn)) method(s), standards, documented procedure(s), and tools to be used, 方法，標(biāo)準(zhǔn)，程序文件以應(yīng)用工具g) references to related plans (., development, testing, configuration management, and quality), 策劃相關(guān)的參考資料（例如：發(fā)展，測(cè)試，配置管理，及質(zhì)量）h) projectspecific environment and physical resource considerations (., development, userdocumentation, testing, and operation), 方案詳細(xì)考慮的環(huán)境及物質(zhì)資源（例如：發(fā)展，用戶(hù)證書(shū)，測(cè)試及操作）i) customer, user, and supplier involvement during the product life cycle (., joint reviews, informal meetings, and approvals), 產(chǎn)品生命周期內(nèi)顧客，用戶(hù)及廠(chǎng)商（例如：聯(lián)合評(píng)審，非正式會(huì)議，以及批準(zhǔn)）j) management of project quality, 方案質(zhì)量管理k) risk management and contingency plans (., technical, cost and schedules), 風(fēng)險(xiǎn)管理及意外事故策劃（例如：技術(shù)，成本以及進(jìn)度）l) performance, safety, security, and other critical requirements, 執(zhí)行、保險(xiǎn)、安全以及其它緊急需求m) projectspecific training requirements, 方案詳細(xì)培訓(xùn)需求n) required certifications, 必須的證明，o) proprietary, usage, ownership, warranty, licensing rights, and 所有者，用法，所有權(quán)，授權(quán)，許可權(quán)力，等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：方案策劃或其它相關(guān)策劃可能是獨(dú)立的文件，其它文件的由部分或由幾個(gè)文件組成。 2: General work instructions defining tasks and responsibilities mon to all development projects need not be replicated as part of a project plan.注解2：總的工作指令定義的對(duì)于所有的開(kāi)發(fā)方案都有效的任務(wù)和職則不必再在方案策劃中重復(fù)引用。 Requirements Traceability – The organization shall establish and maintain a method to trace documented requirements through design and test. [11] 必要的可追蹤性－組織應(yīng)建立并維護(hù)一種方法對(duì)設(shè)計(jì)和測(cè)試過(guò)程的文件進(jìn)行必要的追蹤。[11] 1: The organization should establish munication methods for dissemination of product requirements and changes to requirements to all impacted parties identified in the project plan. 注解1：組織應(yīng)建立一種聯(lián)系方法來(lái)貫徹產(chǎn)品的要求并改進(jìn)各種要求以符合方案策劃的定義。 Test Planning – Test plans shall be documented and results recorded. Test plans should include: 檢測(cè)策劃－檢測(cè)策劃應(yīng)形成文件并對(duì)結(jié)果加以記錄。檢測(cè)策劃應(yīng)包括：a) scope of testing (., unit, feature, integration, system, acceptance),a) 檢測(cè)范圍（例如：?jiǎn)挝?、特性、綜合性能、系統(tǒng)、驗(yàn)收）b) types of tests to be performed (., functional, boundary, usability, performance, regression,interoperability),b) 檢測(cè)的執(zhí)行形式（如：功能、范圍、用途、性能、退步、協(xié)同工作能力）c) traceability to requirements,c) 必要的可追蹤性d) test environment (., relevancy to customer environment, operational use),d) 檢測(cè)環(huán)境（例如：相關(guān)顧客環(huán)境，操作效用）e) test coverage (degree to which a test verifies a product’s functions, sometimes expressed as apercent of functions tested),e) 檢測(cè)規(guī)模（驗(yàn)證產(chǎn)品功能的程度，有時(shí)表現(xiàn)為功能測(cè)試的百分比）f) expected results,f) 期望結(jié)果，g) data definition and database requirements,g) 數(shù)據(jù)分類(lèi)及必要的數(shù)據(jù)庫(kù)h) set of tests, test cases (inputs, outputs, test criteria), and documented test procedure(s),h) 檢測(cè)裝置，檢測(cè)實(shí)例（輸入，輸出，檢測(cè)標(biāo)準(zhǔn)），及檢測(cè)程序文件，i) use of external testing, andi) 外部檢測(cè)方法，等j) method of reporting and resolving defects. [11]l) 報(bào)告方法及糾正措施. [11] 1: Testing may be covered at several levels. 注解1：檢測(cè)可能覆蓋幾個(gè)級(jí)別。 Integration Planning – The organization shall develop and document a plan to integrate the software ponents into the product to ensure they interact as designed. The plan shall include: 綜合策劃－組織應(yīng)建立計(jì)劃將軟件的部分組裝到產(chǎn)品中以確保其象設(shè)計(jì)的一樣相互作用，該計(jì)劃要形成文件。該計(jì)劃應(yīng)包括：a) methods and documented procedure(s),a) 方法和程序文件b) responsibilities,b) 職責(zé)c) schedule for integration, andc) 綜合進(jìn)度，等