A Discipline for Software Engineering (年代久遠紙質泛黃不介意再下單)
暫譯: 軟體工程的學科

Watts S. Humphrey

A Discipline for Software Engineering (年代久遠紙質泛黃不介意再下單)
  • 出版商: Addison Wesley
  • 出版日期: 1995-01-10
  • 售價: $3,600
  • 貴賓價: 9.5 折 $3,420
  • 語言: 英文
  • 頁數: 816
  • 裝訂: Hardcover
  • ISBN: 0201546108
  • ISBN-13: 9780201546101
  • 相關分類: 軟體工程

    • 立即出貨(限量) (庫存=1)

買這商品的人也買了...

商品描述

 

Description

 

This book from Watts Humphrey broadens his disciplined approach to software engineering. In his earlier book, Managing the Software Process, Humphrey developed concrete methods for managing software development and maintenance. These methods, now commonly practiced, provide programmers and managers specific steps for evaluating and improving their software capabilities. In this book, he scales down those methods to a personal level, helping software practitioners develop the skills and habits they need to plan, track, and analyze large and complex projects more carefully and successfully.

Back to Top

 

Table Of Contents

 

1. The Personal Process Strategy.

 

The Logic for a Software Engineering Discipline.
What is a Software Process?
Process Maturity.
Your Personal Responsibilities.
The Personal Software Process (PSP) Strategy.
The Logic for the PSP.
Productivity and the PSP.
Caveats.


2. The Baseline Personal Process.

 

The Baseline Process.
Why Forms are Helpful.
The PSP Process Elements.
The PSPO Process.
PSPO Measures.
Time Recording Log.
Defect Recording Log.
PSPO Project Plan Summary.
Customizing the Initial Process


3. Planning I: The Planning Process.

 

 

Why Make Plans.
What is a Plan.
Contents of a Software Plan.
Planning a Software Project.
Producing a Quality Plan.

 


4. Planning II: Measuring Software Size.

 

 

Size Measures.
A Size Measurement Framework.
Establishing a Counting Standard.
Using LOC Counts.
Reuse Considerations.
Line of Code Accounting.
Calculating Productivity.
LOC Counters.


5. Planning III: Estimating Software Size.

 

 

Background.
Popular Estimating Methods.
Proxy-based Estimating.
The PROBE Size Estimating Method.
Object Categories.
Estimating Considerations.


6. Planning IV: Planning.

 

 

Resource Planning.
Estimating Development Time.
Estimating Task Time.
Combining Multiple Estimates.
Using Multiple Regression.
Schedule Estimating.
Earned Value Tracking.
Estimating Accuracy.


7. Measurement In The Personal Software Process.

 

 

Measurement Overview.
Fundamental Process Measures.
Goal-Question-Metric Paradigm.
General PSP Objectives, Goals, and Questions.
A GQM Example .
Gathering Data.
The Impact of Data Gathering.
Establishing a Baseline for Your Personal Process.


8. Design and Code Reviews.

 

 

What are Reviews?
Why Review Programs.
Personal Reviews.
Review Principles.
Separate Design and Code Reviews.
Design Review Principles.
Review Measures.
Checklists.
Reviewing before or after You Compile.
The Relationship between Reviews and Inspections.


9. Software Quality Management.

 

 

What is Software Quality?.
The Economics of Software Quality.
Developing a Quality Strategy.
Process Benchmarking.
Yield Management.
Defect Removal Strategies.
Defect Prevention Strategies.


10. Software Design.

 

 

The Design Process.
Design Quality.
Structuring the Design Process.
Design Notation.
Design Templates.
The Functional Specification Template.
The State Specification Template.
The Logic Specification Template.
The Operational Scenario Template.
Using Templates in Design
Design Guidelines.


11. Scaling Up The Personal Software Process.

 

 

Using Abstractions.
The Stages of Product Size.
Developing Large-scale Programs.
A Potential Problem with Abstractions.
The Development Strategy.


12. Design Verification.

 

 

Selecting Verification Methods.
Design Standards.
Verification Methods.
Verifying the Object State Machine.
Program Tracing.
Verifying Program Correctness.
Comments on Verification Methods.


13. Defining the Software Process.

 

 

Why Define Processes.
Software Process Basics.
Process Definition.
Defining Process Phases.
Process Development Considerations.
Process Evolution.
The Process-development Process.


14. Using the Personal Software Process.

 

 

Making Personal Commitments.
Using the PSP in an Organization.
The Personal Costs of a PSP.
The Personal Benefits of a PSP.
Coaching.
The Responsible Software Professional.
Your Future in Software Engineering. 0201546108T04062001

 

 


Back to Top

 

 

 

 

商品描述(中文翻譯)

描述

這本書來自 Watts Humphrey，擴展了他對軟體工程的嚴謹方法。在他之前的書籍《Managing the Software Process》中，Humphrey 開發了管理軟體開發和維護的具體方法。這些方法現在已被廣泛實踐，為程式設計師和管理者提供了評估和改善其軟體能力的具體步驟。在這本書中，他將這些方法縮小到個人層面，幫助軟體從業人員發展他們所需的技能和習慣，以更仔細和成功地計劃、追蹤和分析大型和複雜的專案。

目錄

1. 個人過程策略
- 軟體工程學科的邏輯
- 什麼是軟體過程？
- 過程成熟度
- 你的個人責任
- 個人軟體過程 (PSP) 策略
- PSP 的邏輯
- 生產力與 PSP
- 注意事項

2. 基準個人過程
- 基準過程
- 為什麼表單有幫助
- PSP 過程要素
- PSPO 過程
- PSPO 測量
- 時間記錄日誌
- 缺陷記錄日誌
- PSPO 專案計畫摘要
- 自訂初始過程

3. 計畫 I：計畫過程
- 為什麼要制定計畫
- 什麼是計畫
- 軟體計畫的內容
- 計畫一個軟體專案
- 產出高品質計畫

4. 計畫 II：測量軟體大小
- 大小測量
- 大小測量框架
- 建立計數標準
- 使用 LOC 計數
- 重用考量
- 程式碼行會計
- 計算生產力
- LOC 計數器

5. 計畫 III：估算軟體大小
- 背景
- 常見的估算方法
- 基於代理的估算
- PROBE 大小估算方法
- 物件類別
- 估算考量

6. 計畫 IV：計畫
- 資源計畫
- 估算開發時間
- 估算任務時間
- 結合多個估算
- 使用多重回歸
- 排程估算
- 獲得價值追蹤
- 估算準確性

7. 個人軟體過程中的測量
- 測量概述
- 基本過程測量
- 目標-問題-度量範式
- 一般 PSP 目標、目標和問題
- GQM 範例
- 收集數據
- 數據收集的影響
- 為你的個人過程建立基準

8. 設計與程式碼審查
- 什麼是審查？
- 為什麼要審查程式
- 個人審查
- 審查原則
- 分開設計和程式碼審查
- 設計審查原則
- 審查測量
- 檢查清單
- 在編譯前或後進行審查
- 審查與檢查之間的關係

9. 軟體品質管理
- 什麼是軟體品質？
- 軟體品質的經濟學
- 制定品質策略
- 過程基準
- 產量管理
- 缺陷移除策略
- 缺陷預防策略

10. 軟體設計
- 設計過程
- 設計品質
- 結構化設計過程
- 設計符號
- 設計範本
- 功能規範範本
- 狀態規範範本
- 邏輯規範範本
- 操作情境範本
- 在設計中使用範本
- 設計指導方針

11. 擴展個人軟體過程
- 使用抽象
- 產品大小的階段
- 開發大型程式
- 抽象的潛在問題
- 開發策略

12. 設計驗證
- 選擇驗證方法
- 設計標準
- 驗證方法
- 驗證物件狀態機
- 程式追蹤
- 驗證程式正確性
- 關於驗證方法的評論

13. 定義軟體過程
- 為什麼要定義過程
- 軟體過程基礎
- 過程定義
- 定義過程階段
- 過程開發考量
- 過程演變
- 過程開發過程

14. 使用個人軟體過程
- 制定個人承諾
- 在組織中使用 PSP
- PSP 的個人成本
- PSP 的個人利益
- 輔導
- 負責任的軟體專業人員
- 你在軟體工程的未來

類似商品

最後瀏覽商品 (1)