【正文】 ) 若要對(duì)已成為基準(zhǔn)的資料進(jìn)行異動(dòng)。 異動(dòng)追蹤與控制 (Track and Control Changes) 異動(dòng)追蹤 (Track Change)(1) 提出異動(dòng)申請(qǐng)(異動(dòng)申請(qǐng)單)。(2) 由建構(gòu)管理人員評(píng)估影響層面，並通知專案負(fù)責(zé)人。(3) 由專案負(fù)責(zé)人邀集受影響單位進(jìn)行評(píng)估，並決定是否準(zhǔn)予異動(dòng)。(4) 追蹤異動(dòng)的狀態(tài)(例如異動(dòng)時(shí)間)。 建構(gòu)控制小組 (Configuration Control Board)本專案之建構(gòu)控制小組(CCB)由專案負(fù)責(zé)人洪盟峰，(2)項(xiàng)建構(gòu)異動(dòng)授權(quán)事宜。 異動(dòng)控制 (Control Change)(1) 對(duì)於異動(dòng)的項(xiàng)目需要持續(xù)監(jiān)控。(2) 進(jìn)行異動(dòng)前需要先「取的授權(quán)」(由建構(gòu)管理人員決定時(shí)間點(diǎn))。(3) 簽入與簽出時(shí)請(qǐng)?jiān)俅未_認(rèn)其正確性。(4) 對(duì)於每一個(gè)異動(dòng)，需要清楚記錄異動(dòng)原因。 版本控制程式 (The Version Control Tool) 達(dá)成完整性 (Establish Integrity) 建構(gòu)管理記錄 (Establish CM Records)有關(guān)本專案所使用的CVS符合本項(xiàng)要求的部分，請(qǐng)參閱附錄三。 建構(gòu)審核 (Perform Configuration Audits)為達(dá)成對(duì)於建構(gòu)管理系統(tǒng)中的項(xiàng)目的正確性，本專案的建構(gòu)管理人員需要於每月定時(shí)檢視建構(gòu)管理項(xiàng)目以確認(rèn)其結(jié)構(gòu)的完整性。8. 度量與分析計(jì)畫(huà) (Mamp。A Plan) 目的度量與分析主要在蒐集本專案的各項(xiàng)資訊，以提供各種分析之用。 蒐集資訊的目的與資訊需求 (Information Needs and Objectives)序 號(hào)目 的資 訊 需 求1客戶滿意度客戶的反應(yīng)、支援客戶的狀況2時(shí)程與進(jìn)度里程碑完成狀況、工作單元進(jìn)度3資源與成本支出、各項(xiàng)資源支援的程度4產(chǎn)品品質(zhì)系統(tǒng)或功能品質(zhì)、介面的良劣5客戶需求的穩(wěn)定程度客戶需求的異動(dòng)6產(chǎn)品大小每個(gè)子系統(tǒng)的大小、功能大小 基礎(chǔ)度量 (Base Measurement)序 號(hào)度 量因 子1客戶滿意度度量經(jīng)由客戶問(wèn)題的反應(yīng)：與客戶互動(dòng)的時(shí)間2里程碑完成狀況、工作單元進(jìn)度里程碑完成的時(shí)間、階段中工作單元完成度3支出、各項(xiàng)資源支援的程度專案人員投入的工作時(shí)數(shù)、實(shí)際支出數(shù)4系統(tǒng)或功能品質(zhì)、介面的良劣系統(tǒng)或功能之錯(cuò)誤數(shù)、使用者反應(yīng)介面問(wèn)題數(shù)5客戶需求的異動(dòng)客戶需求異動(dòng)個(gè)數(shù)、可行個(gè)數(shù)、無(wú)法修改個(gè)數(shù)6每個(gè)子系統(tǒng)的大小、功能大小每個(gè)子系統(tǒng)的程式行數(shù)、功能數(shù) 度量與分析工具 (Measurement and Analysis Tool)本專案使用MS Project與MS Excel作為分析上述各項(xiàng)資訊的工具。9. 流程與產(chǎn)品品質(zhì)保證計(jì)劃 (PPQA Plan) 目的本專案的流程與產(chǎn)品品質(zhì)保證計(jì)劃主要是提供專案所有人員對(duì)於產(chǎn)品的品質(zhì)能以客觀且深入了解其流程與相關(guān)產(chǎn)品。 客觀檢視流程與產(chǎn)品 (Objectively Evaluate Process and WP)本專案的檢視流程為：(1) 與專案負(fù)責(zé)人共同檢查程式設(shè)計(jì)流程、程式單元審查與單元測(cè)試皆符合「程式設(shè)計(jì)規(guī)格書(shū)」中所述。 (2) 檢查由「程式單元審查」所獲得的執(zhí)行項(xiàng)目皆能處理並由專案負(fù)責(zé)人簽認(rèn)。(3) 確認(rèn)所有程式單元皆能符合「程式設(shè)計(jì)規(guī)格書(shū)」的規(guī)格來(lái)設(shè)計(jì)。(4) 檢視表專案軟體實(shí)作與單元測(cè)試流程檢核表專案名稱：資訊家電控制平臺(tái)軟體元件檢視日期： 年 月 日 製 表： 一、 程式設(shè)計(jì)____ Code and the traceability matrix are prepared and kept current and consistent based on approved software requirement changes.____Code walkthroughs (peer review) evaluate pliance of the code to the approved design, identify defects in the code, and alternatives are evaluated and reported.____Code walkthroughs are conducted in accordance with Peer Review Process.____Changes to code are identified, reviewed, and tracked to closure.____Code is maintained under configuration management.____Code changes undergo peer review before they are incorporated into the software baseline. ____Software coding is consistent with the coding methodology approved in the Software Development Plan (SDP).____The method, such as the Software Development Folder or Unit Development Folder, used for tracking and documenting the development/maintenance of a software unit is implemented and is kept current.二、 單元測(cè)試____Software unit testing is conducted in conformance with the approved standards and procedures described in the SDP. ____Ensure that passing criteria for unit test is documented, and that pliance has been recorded.____Results of unit testing are documented in the Software Development Folder or Unit Development Folder. Project Object Insight(1) 專案負(fù)責(zé)人隨時(shí)與客戶保持聯(lián)繫，務(wù)必讓客戶滿意產(chǎn)品。(2) 專案負(fù)責(zé)人隨時(shí)與專案發(fā)展人員溝通，確認(rèn)所有的問(wèn)題能得到解決。(3) 所有的問(wèn)題與解決流程皆需要建立記錄，此記錄以MS Excel的方式存放，可提供未來(lái)分析之用。 Management Architecture本專案的PPQA主要由本專案主持人洪盟峰負(fù)責(zé)。附件一. 專案生命週期模型 Waterfall Model is welldefined development process in which one phase has to be finished before the next phase. The model is very simple to use. The model can be used if the requirement is well understood and defined. Concurrent Model is that more than one processes (for example, SW development, HW development, Testing development) are progressed in concurrent. VShaped Model is similar to waterfall model. The difference is that each test phase matches each development phase: requirements with system testing, highlevel design with integration testing, and detailed design with unit testing. Prototyping Model is the technique which helps designers and users to clarify the requirement of the system. A throwaway prototype is developed by designers and is evaluated by users. From feedback of users, designers will understand the system better and improve the prototype. Incremental Model. The designers develop the software in a number of stages and are able to deliver the product early. At each phase the designers have a goal to deliver certain features to customers. Incremental model is good for fast delivering product to the marker place. Spiral Model is an iterative approach. The model carefully takes risks into account. The designers develop a small part of the project and evaluate the risks. If the risk is low, designers keep developing more features. For each iteration, there are six steps: o Determine objectives, alternatives, and constraints. o Identify and resolve risks. o Evaluate alternatives. o Develop deliverables and verify that they are correct. o Plan the next iteration. Commit to an approach for the next iteration.