1、Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,Chapter 2軟體程序,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,學習目標,軟體程序簡介ETVXM架構 軟體程序的輪廓 預先開發程序 軟體開發程序,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,學習目標,軟體生
2、命周期模型 同步與穩定模型 無塵室程序模型 將通用軟體程序模型特殊化,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,軟體程序簡介,通用等級 精練等級 基元等級,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.1軟體程序的等級與架構,Software Engineering An Engineering Approach, James F. Peters & Witold
3、 Pedrycz,圖2.2軟體程序的回饋系統,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,ETVXM架構,最早由Watts Humphrey於1989年所提出 圖2.2中的裁定因子、效應因子與測量，定義出一個伴隨著回饋的ETVXM程序架構（Entry、Task、Verify、Exit、Measure）,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.3回饋與ETVXM
4、間的關聯,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.4預先設計的效應因子程序,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.5設計的效應因子程序,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,軟體程序的輪廓,軟體的驗證與確認 軟體進化 軟體生命周期
5、程序,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.8V&V程序的應用,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.9軟體文件的進化,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.10進化樣式的框架,Software Engineering A
6、n Engineering Approach, James F. Peters & Witold Pedrycz,圖2.12SLCM的範例,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,預先開發程序,概念探索 系統配置 分析功能 定義架構 取得欲開發系統的硬體與軟體需求,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,軟體開發程序,需求：決定系統必須的功能、活動、風險與測試計
7、劃 設計：確定系統的運算方式、明確的功能及結構 實作：產生程式碼（source code）、文件及測試；確認與驗證,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,軟體生命周期模型,瀑布、增量及螺旋式模型 系統風險評估 雙贏的螺旋模型 進化式模型 塑型式模型 物件導向模型 嵌入式系統程序模型,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.13瀑布模型,Software
8、Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.14增量式生命周期模型,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.15螺旋式生命周期模型,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,表2.3風險評估表,Software Engineering An Engineer
9、ing Approach, James F. Peters & Witold Pedrycz,風險評估時考量的因子,不當事件可能發生的機率 p （0 = p = 1） 不當事件發生時，預估的損失 L（如：軟體瑕疵造成的損失、喪失生命的數量）,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.16A雙贏的螺旋模型,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.16B雙
10、贏的協商模型,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.17進化式生命周期模型,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.18軟體開發的塑型方法,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.19物件導向生命周期模型,Software E
11、ngineering An Engineering Approach, James F. Peters & Witold Pedrycz,同步與穩定模型,計劃階段 設計階段 穩定化階段,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,圖2.23同步與穩定模型,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,無塵室程序模型,Entry（進入）：展開工作前須符合的條件 Feedba
12、ck（回饋）：對於一個工作，來自其它程序的輸入；工作的輸出作為其它程序之輸入 Task（工作）：須完成的是什麼，由誰、如何及何時去完成,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,無塵室程序模型,Verification（驗證）：確認工作的完成，檢查工作產品是否符合規 Exit（離開）：結束工作前須符合的結果、格式及準則 Measurement（測量）：必要的工作測量、輸出與回饋,Software Engineering An Engineering Approach, James F. Peters & Witold Pedrycz,將通用軟體程序模型特殊化,能引導軟體增量工作依序進行揭示展開工作所需要的細節 如何與何時進行結果的測量 每個程序預期的產出結果,
