Software Engineering Best Practices: Lessons from Successful Projects in the Top Companies (Hardcover)
暫譯: 軟體工程最佳實踐:來自頂尖公司成功專案的教訓 (精裝版)

Capers Jones

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

相關主題

商品描述

Proven techniques for software engineering success

This in-depth volume examines software engineering topics that are not covered elsewhere: the question of why software engineering has developed more than 2,500 programming languages; problems with traditional definitions of software quality; and problems with common metrics, "lines of code," and "cost per defect" that violate standard economic assumptions. The book notes that a majority of "new" projects are actually replacements for legacy applications, illustrating that data mining for lost requirements should be a standard practice. Difficult social engineering issues are also covered, such as how to minimize harm from layoffs and downsizing.

Software Engineering Best Practices explains how to effectively plan, size, schedule, and manage software projects of all types, using solid engineering procedures. It details proven methods, from initial requirements through 20 years of maintenance. Portions of the book have been extensively reviewed by key engineers from top companies, including IBM, Microsoft, Unisys, and Sony.

  • Manage Agile, hierarchical, matrix, and virtual software development teams
  • Optimize software quality using JAD, OFD, TSP, static analysis, inspections, and other methods with proven success records
  • Use high-speed functional metrics to assess productivity and quality levels
  • Plan optimal organization, from small teams through more than 1,000 personnel

商品描述(中文翻譯)

軟體工程成功的驗證技術

本書深入探討了其他地方未涵蓋的軟體工程主題:為什麼軟體工程已經發展出超過 2,500 種程式語言的問題;傳統軟體品質定義的問題;以及常見指標「程式碼行數」和「每缺陷成本」違反標準經濟假設的問題。書中指出,大多數「新」專案實際上是舊應用程式的替代品,這表明資料挖掘遺失需求應該是一項標準實踐。書中還涵蓋了困難的社會工程問題,例如如何最小化裁員和縮編帶來的傷害。

軟體工程最佳實踐 解釋了如何有效地規劃、評估規模、排定時間表以及管理各類型的軟體專案,使用穩健的工程程序。它詳細說明了從初始需求到 20 年維護的驗證方法。本書的部分內容已被來自 IBM、Microsoft、Unisys 和 Sony 等頂尖公司的關鍵工程師廣泛審查。


  • 管理敏捷、層級、矩陣和虛擬軟體開發團隊

  • 使用 JAD、OFD、TSP、靜態分析、檢查和其他成功記錄的驗證方法來優化軟體品質

  • 使用高速功能指標來評估生產力和品質水平

  • 規劃最佳組織,從小型團隊到超過 1,000 人的團隊