数位家庭软体开发管理SoftwareDevelopmentManagementfor

數位家庭軟體開發管理

SoftwareDevelopmentManagement

forDigitalHome

97年1月19日台科大資管系軟體工程與管理研究所黃世禎副教授AssociateProfessorSun-JenHuang,Ph.D.SoftwareEngineeringandManagementLab.DepartmentofInformationManagementNationalTaiwanUniversityofScience&Technology數位家庭軟體工程短期課程推廣活動海洋大學資訊工程學系SoftwareDevelopmentManagementforDigitalHome1HistoryofSoftwareEngineeringSoftwareEngineeringConferenceheldbyNATOin1968－

Softwareas“craftsmanship”(工匠技藝)and“SoftwareCrisis”arose“ThefirstinternationalconferenceonSoftwareEngineering”washeldin1973Thefirstissueofthe“IEEETransactiononSoftwareEngineering”waspublishedin1975“StructuredProgramDesignConcept”wasinitiatedbyLarryConstantineetal.in1974Thefirstbookon“SoftwareMetrics”waspublishedbyTomGilbin1977Thefirsteditionof“SoftwareEngineering”waspublishedbyIanSommervillein1982Thefirsteditionof“SoftwareEngineering:APractitioner’sApproach”,waspublishedbyRogerS.Pressmanin1982SoftwareDevelopmentManagementforDigitalHome2CurrentStatusinSoftwareIndustryReportinTheStandishGroupCHAOS200313,500softwareprojectswereinvestigated66%ofprojectswerefailure82%ofprojectswerelatedelivered48%ofprojectswerereleasedwithunsatisfiedfunctionalityrequirements43%ofprojectswerecostoverrun15%ofprojectswerecanceledbeforethedeliveryWhydidthishappen?SoftwareDevelopmentManagementforDigitalHome3ChallengesfortheSuccessofSoftwareDevelopmentProjectIncompleteandUncertainuserrequirementsRequirementsoftenchangeEstimatedeffort,costandscheduleisnotreasonableHowtowellmakeprojectmanagementplanandprojectmonitorandcontrolDifficultiesonperformingSoftwareVerificationandValidationHowtowellconductSoftwareConfigurationManagementHowtoevaluatesoftwarequality,projectperformance,developersproductivityetc軟體開發專案的夢魅：大多數的專案都無法如期、如質、如預算的完成SoftwareDevelopmentManagementforDigitalHome4NinecausesofsoftwareerrorsFaultyrequirementsdefinitionClient-developercommunicationfailuresDeliberatedeviationsfromsoftwarerequirementsLogicaldesignerrorsCodingerrorsNon-compliancewithdocumentationandcodinginstructionsShortcomingsofthetestingprocessUserinterfaceandprocedureerrorsDocumentationerrorsSoftwareDevelopmentManagementforDigitalHome5我國軟體危機與轉機軟體危機軟體人才專業素值的不足軟體流程未制度化軟體工程技術、模式、工具成熟度的不足軟體專案管理能力的不足軟體轉機軟體開發技術、人員能力的提昇軟體開發管理（SoftwareDevelopmentManagement)降低專案成本降低專案風險縮短專案時程提高專案產品品質SoftwareDevelopmentManagementforDigitalHome6DeterminantsofProjectSuccessThreemajordeterminantsofproductcost,scheduleandqualityWorkingsmarterthroughthedisciplinedprocessinsteadofworkingharderTechnologyprovidesthemostbenefitinthecontextofanappropriateprocessroadmapPeopleTechnologyProcessSoftwareDevelopmentManagementforDigitalHome7SWEBOK-2004(1)SoftwareRequirements(2)SoftwareDesign(3)SoftwareConstruction(4)SoftwareTesting(5)SoftwareMaintenance(6)SoftwareConfigurationManagement(7)SoftwareEngineeringManagement(8)SoftwareEngineeringProcess(9)SoftwareEngineeringToolsandMethods(10)SoftwareQualitySoftwareDevelopmentManagementforDigitalHome8CMMI-DEVPAsByML&Category

專案管理

流程管理

工程

支援

成熟度等級５

最佳化

組織創新與推展(OID)

原因分析與解決方案(CAR)

成熟度等級４

定量管理

定量專案管理(QPM)

組織流程績效(OPP)

成熟度等級３

定義

整合專案管理(IPM)

風險管理(RSKM)

組織流程焦點(OPF)

組織流程定義(OPD)

組織訓練(OT)

需求發展(RD)

技術解決方案(TS)

產品整合(PI)

驗證(VER)

確認(VAL)

決策分析與解決方案(DAR)

成熟度等級２

管理

專案規劃(PM)

專案監督與管制(PMC)

供應商協議管理(SAM)

需求管理(REQM)

度量與分析(MA)

流程與產品品質保證(PPQA)

構型管理(CM)

成熟度等級１

啟始

SoftwareDevelopmentManagementforDigitalHome9AdvancingthroughMaturityLevel初始

(ML1)管理(ML2)定義

(ML3)量化管理

(ML4)最佳

(ML5)規律化與監控標準化與文件化評量與量化持續改善依靠某些個人之努力與權威但績效/成本/交期/品質無法預測沒有任何文件化的軟體開發流程規範已建立文件化專案管理、品質保證等基本性

流程的作業規範作業規範可被依循，因此成功的經驗法則

可以被重複的使用在以後的專案差異產生的因果分析與預防創新的技術與流程已有組織標準化的流程作業規範

與專案裁適的準則所有的專案都能依循組織一致性

的流程作業規範流程績效可被量化的度量、分析與管理SoftwareDevelopmentManagementforDigitalHome10ISOSEStandardsISO/IEC12207:1995SoftwarelifecycleprocessesISO/IEC9126:2001SoftwareproductqualityISO/IEC15504:2004SoftwareprocessassessmentISO/IEC14764:2006SoftwareLifeCycleProcesses–MaintenanceISO/IEC15846-ConfigurationManagementISO/IEC16085:2006Lifecycleprocesses--RiskmanagementISO/IEC90003:2004GuidelinesfortheapplicationofISO9001:2000tocomputersoftwareISO/IEC14143:2007FunctionalsizemeasurementISO:IEC20926:2003IFPUG4.1UnadjustedfunctionalsizemeasurementmethodISO/IEC20000:2005ITservicemanagementSoftwareDevelopmentManagementforDigitalHome11IEEESEStandardsIEEE730-SoftwareQualityAssurancePlansIEEE829-SoftwareTestDocumentationIEEE830-RecommendedPracticeforSoftwareRequirementsIEEE1012-SoftwareVerificationandValidationIEEE1042-SoftwareConfigurationManagementIEEE1062-RecommendedPracticeforSoftwareAcquisitionIEEE1074-DevelopingSoftwareLifeCycleProcessesIEEE1228-SoftwareSafetyPlansIEEE1540-SoftwareLifeCycleProcesses-RiskManagementIEEE1633-RecommendedPracticeonSoftwareReliabilitySoftwareDevelopmentManagementforDigitalHome12ISO12207-SoftwareLifeCycleProcessesAcquisitionSupplyDevelopmentOperationMaintenancePrimaryDocumentationConfigurationmanagementQualityassuranceVerificationValidationJointreviewAuditProblemresolutionSupportingManagementInfrastructureImprovementTrainingOrganizationalTrainingTailoringLifecycleSoftwareDevelopmentManagementforDigitalHome13PMBOKKnowledgeAreasIntegrationManag.確保專案獲取適當計畫專案計畫執行專案計畫監控變更專案控制的施行ScopeManagement專案工作授權制定範疇聲明規範專案範疇細分可行工作組合核對完成之範疇設計TimeManagement訂定時間表控制工作進度工作的定義、排序工作工程估算時程發展CostManagement估計各項資源成本人力/設備/原料/差旅成本估算與編列成本控制

(保持專案成本在預算內)QualityManagement品質確保達到品質要求品質管制逐步審視階段結果HumanResource

Management確定參與專案人力組織規劃人力職責與從屬關係人力資源的招攬與管理Communication

Management計畫/執行/監控等期間

與Stakeholder的溝通溝通計劃/資訊散佈績效報告/結案管理RiskManagement增加專案正向影響事件減少專案負面影響事件風險管理規劃/鑑別風險定性分析/定向分析回應專案可能遭遇的風險ProcurementManag.採購專案所需物品/服務決定採購物品發標單/估價單邀商規劃與作業/評選尋求供應廠商

簽訂採購合約/終止合約SoftwareDevelopmentManagementforDigitalHome14數位家庭軟體開發管理架構開發流程維護流程軟體流程改善與管理管理者軟體建

構管理數位家庭軟體開發管理基礎知識軟體專案管理軟體品

質管理軟體風

險管理軟體度量與分析開發者維護者軟體支援性流程SoftwareDevelopmentManagementforDigitalHome15課程一：數位家庭軟體開發管理導論1-1：數位家庭軟體開發管理的目的與重要性1-2：數位家庭軟體開發包含的知識範疇1-3：數位家庭軟體開發管理的效益1-4：數位家庭軟體開發管理1-5：數位家庭軟體開發管理的相關資源SoftwareDevelopmentManagementforDigitalHome16課程二：軟體專案管理2-1：軟體專案管理的概論2-2：軟體專案管理的相關標準2-3：軟體專案起始2-4：軟體專案規劃2-5：軟體專案執行2-6：軟體專案控制2-7：軟體專案結案2-8：個案研讀與討論2-9：重點回顧SoftwareDevelopmentManagementforDigitalHome17課程三：軟體品質管理3-1：軟體品質概論3-2：軟體品質成本3-3：軟體品質保證3-4：軟體品質模式3-5：軟體品質評估3-6：個案研讀與討論3-7：重點回顧SoftwareDevelopmentManagementforDigitalHome18課程四：軟體流程管理4-1：軟體流程改善概論4-2：軟體流程改善效益4-3：軟體流程改善流程4-4：能力成熟度整合模式4-5：Motorola公司的軟體改善4-6：個案研讀與討論4-7：重點回顧SoftwareDevelopmentManagementforDigitalHome19課程五：軟體建構管理5-1：軟體建構管理概論5-2：軟體建構項目識別5-3：軟體建構管制5-4：軟體構型狀態紀錄5-5：軟體建構稽核5-6：軟體建構軟體工具5-7：個案研讀與討論5-8：重點回顧SoftwareDevelopmentManagementforDigitalHome20課程六：軟體風險管理6-1：軟體風險管理概論6-2：軟體風險管理規劃6-3：軟體風險管理執行6-4：軟體風險管理評估6-5：軟體風險管理溝通6-6：軟體風險管理軟體工具6-7：個案研讀與討論6-8：重點回顧SoftwareDevelopmentManagementforDi