【正文】 omputer Science (3) 系統(tǒng)設計：概要設計和詳細設計，給出軟件的結構、模塊和功能的劃分等。編寫概要設計、詳細設計說明書和測試計劃初稿。 (4) 詳細設計：源程序編碼，把軟件設計轉換成計算機可以接受的程序代碼。編寫用戶手冊、操作手冊和單元測試計劃。 (5)編碼： (6)測試：設計測試用例，檢驗軟件各個組成部分。編寫測試分析報告。 2 軟件開發(fā) — 軟件要“怎么做” School of Computer Science 3 軟件運行 和維護 (7) 軟件投入運行，維護 (進行擴充和刪改 )。 School of Computer Science Traditional Development Phase 傳統(tǒng)開發(fā)階段 軟件生命周期的開發(fā)步驟 School of Computer Science Analysis分析 ? A major goal of analysis is to identify what the proposed system should acplish ? Requirements（需求） ? The needs of the potential users ? Stated in terms of the application rather than in the technical terminology ? Specifications（說明書） ? Technical descriptions of the requirements School of Computer Science Design設計 ? Design concentrates on how the system will acplish the goals set in analysis ? System structure is established in design ? The best structure is a modular one ? Modularity（模塊化） ? Division of a software into manageable units, each performs only part of the overall task ? Modular deposition ? Makes the implementation of large systems possible ? Allows changes to be made on a modular basis School of Computer Science Implementation and Testing 實現(xiàn)和測試 ? Implementation involves the actual writing of programs, creation of data files, and development of database ? Each module is normally tested as it is implemented ? Stubs（樁模塊） ? Simplified versions of modules used to test a certain module ? Feature（功能） test and load test ? Reliability growth test and certification test School of Computer Science 軟件 Development Models開發(fā)模型 Recent Trends 趨勢 ? Waterfall（瀑布模型） ? Performs analysis, design, implementation, and testing in a strictly manner ? Incremental（迭代模型） ? Software system is constructed in increments ? Prototyping（原型法） ? Inplete versions of the proposed system (prototypes) are built and evaluated ? Evolutionary prototyping（演化式原型） ? Early prototyping and throwaway prototyping（拋棄式原型） School of Computer Science Testing Methodology Based on Pareto Principle（基于 Pareto法則的測試方法） ? Pareto principle ? The results can often be increased more rapidly by applying efforts in a concentrated area ? Thus a small number of modules within a large software system tend to be more problematic than the rest School of Computer Science Testing 方法 ? Glassbox testing（白盒測試） ? Identify problematic modules ? Basis path testing ? Blackbox testing（黑盒測試） ? Boundary（邊界） value analysis ? Apply redundancy（冗余：兩個公司開發(fā)同一套系統(tǒng)） ? Beta testing（初始版本） School of Computer Science Extreme Programming (XP極限編程 ) ? Suitable for a team of less than a dozen individuals ? A discipline of software development based on values of simplicity（簡易） , munication（交流） , and courage ? 12 practices School of Computer Science ComputerAided Software Engineering (CASE)計算機輔助軟件工程 ? Application of puter technology to the software development process itself ? Project planning tools ? Project management tools（ Microsoft Project 202 2022） ? Documentation tools ? Prototyping and simulation tools ? Interface design tools ? Programming tools (. code generator) School of Computer Science Documentation文檔 ? User documentation ? Manual ? Tutorial（指南） ? Installation guide ? Reference manual ? Help packages ? System documentation ? Source codes ? Record of specification development ? System specifications（說明書） School of Computer Science Software Ownership(所有權） and Liability（責任） ? Copyright laws（版權法） ? Literary（文學） works vs. software ? Look and feel of a software system ? Lotus vs. Mosaic ? Patents（專利） ? A longstanding principle ? RSA algorithm（一種加密算法） ? Trade secret laws ? Liability limitations（有限責任） ? Disclaimer ? Level of care School of Computer Science 作業(yè) ? 第 5章： P167: 1 42 ? 第 6章： P210： 21 ? 第 7章： 30