Patterns of Large Software Systems: Failure and Success
Patterns of Large Software Systems: Failure and Success
复制标题
大型软件系统的模式：失败与成功
作者：
Capers Jones
软件管理顾问与医生有一些共同点：当出现严重问题时，而不是一切正常时，他们更有可能被请来。检查出现问题的大型软件系统（超过 5000 个功能点（大约是 Cobol 或 Fortran 等过程编程语言中的 500000 条源代码语句））对于管理顾问来说是很常见的事情。不幸的是，在研究开始之前，这些系统通常已经迟到、超出预算，并显示出其他严重困扰的迹象。因此，顾问的参与有助于纠正问题并挽救系统——如果挽救确实是可能的话。大型软件系统的故障或取消率超过20%。在已完成的项目中，大约三分之二经历了进度延误和成本超支（可能接近 100%）。大约有相同数量的设备在部署的第一年就受到低可靠性和质量问题的困扰。然而，一些大型系统提前完成，满足预算，并且几乎没有质量问题（如果有的话）。当这么多项目失败时，这些项目如何成功？ >
Software management consultants have something in common with physicians: both are much more likely to be called in when there are serious problems rather than when everything is fine. Examining large software systems-those in excess of 5000 function points (which is roughly 500000 source code statements in a procedural programming language such as Cobol or Fortran)-that are in trouble is very common for management consultants. Unfortunately, the systems are usually already late, over budget, and showing other signs of acute distress before the study begins. The consultant engagements, therefore, serve to correct the problems and salvage the system-if, indeed, salvaging is possible. The failure or cancellation rate of large software systems is over 20 percent. Of those that are completed, about two thirds experience schedule delays and cost overruns that may approach 100 percent. Roughly the same number are plagued by low reliability and quality problems in the first year of deployment. Yet some large systems finish early, meet their budgets, and have few, if any, quality problems. How do these projects succeed, when so many fail?. >