培養學員熟悉軟體生命週期管理的內容、目的與技術。To train students to be familiar with the content, purpose and technology of software life cycle management.
軟體生命週期(software lifecycle)是指軟體從尚未存在前的需求發展階段、到進入實際的軟體開發階段、再到軟體發展完成後的上線應用與維護階段、以及最終被淘汰同時進入下一個新生命週期，或者也可以簡單稱之為「舊案翻新」階段的整個過程。軟體在其整個生命週期中要維持「健康」，就必須要能確保：需求做對(Right)、品質做好(Good)、以及使用上可被依恃 (Dependable)。所謂可被依恃的軟體，基本上應具備「可用性」(availability)、「能用性」(usability)、「可靠性」(reliability)、以及「安全性」(security)等四個要求。RGD(對的、好的、可依恃的)基本上可說是一個軟體的健康指標。然而就像人一樣，軟體一生的健康與其生命週期中的個個階段，具備環環相扣的關係。例如在需求發展階段，如果無法定義出軟體的真正需求，那麼即時在開發階段做出最好的軟體，最終也會因為不對而無法使用；即使一個軟體在開發階段順利被發展成最好的軟體，假如無法在應用與維護階段有效面對需求變更，最終這個軟體可能仍無可依恃。因此，要維繫一個軟體在整個生命週期過程中的健康，那麼從需求管理、生產流程規劃、人員調度、使用工具、相關產出物的建構管理、權限管理、測試管理、需求變更、時程管控、議題追蹤、建置部署、與指標監控等，這些與工程有關的管理工作，便必須有效落實。而以上這些工作正是「軟體生命週期管理」(Software Lifecycle Management, SLM)的核心課題。
Software lifecycle refers to the development stage of software before it exists, to the actual software development stage, to the online application and maintenance stage after the software development is completed, and finally to being eliminated and entering the next new life. cycle, or the entire process that can simply be called the "renovation of old cases" phase. For software to maintain "health" throughout its life cycle, it must be able to ensure that: the requirements are right (Right), the quality is good (Good), and the use can be relied on (Dependable). The so-called software that can be relied on should basically meet the four requirements of "availability", "usability", "reliability", and "security". RGD (right, good, dependable) is basically a software health indicator. However, just like people, the health of software throughout its life is closely related to each stage in its life cycle. For example, in the requirements development stage, if the real requirements of the software cannot be defined, even if the best software is made during the development stage, it will eventually become unusable because of errors; even if a software is successfully developed into the best software during the development stage , if it cannot effectively face demand changes during the application and maintenance stages, the software may ultimately be unreliable. Therefore, to maintain the health of a software throughout its life cycle, it is necessary to start from demand management, production process planning, personnel scheduling, use of tools, construction management of related outputs, authority management, test management, demand changes, and schedule control. , issue tracking, construction deployment, and indicator monitoring, etc. These project-related management tasks must be effectively implemented. The above tasks are the core topics of "Software Lifecycle Management" (SLM).
自編講義與其他刊物資料
Roger S. Pressman, Software Engineering: A Practitioner's Approach, McGraw-Hill
Ian Sommerville, Software Engineering, Addison-Wesley
CNS 14837: ISO/ITC 12207
CNS 14785: ISO/ITC 15504
CMMI: Guidelines for Process Integration and Product Improvement
Self-compiled handouts and other publications
Roger S. Pressman, Software Engineering: A Practitioner's Approach, McGraw-Hill
Ian Sommerville, Software Engineering, Addison-Wesley
CNS 14837: ISO/ITC 12207
CNS 14785: ISO/ITC 15504
CMMI: Guidelines for Process Integration and Product Improvement
| 評分項目 Grading Method | 配分比例 Grading percentage | 說明 Description |
|---|---|---|
| 期中考期中考 midterm exam |
25 | |
| 期末考期末考 final exam |
35 | |
| 專題討論表現與參與度專題討論表現與參與度 Panel discussion performance and participation |
20 | |
| 分組報告表現分組報告表現 Group reporting performance |
20 |
