首页> 外文期刊>Cutter IT Journal >When CMMI Is Not Enough: A Case for Using itil V3 in Application Lifecycle Management
【24h】

When CMMI Is Not Enough: A Case for Using itil V3 in Application Lifecycle Management

机译:CMMI不足时:在应用程序生命周期管理中使用itil V3的案例

获取原文
获取原文并翻译 | 示例
           

摘要

Watts Humphrey, the "father of software quality," often said that a software product is only as good as the process used to create it. But today's complex IT environment demands that we take an even wider system view of the business of IT. Fortunately, there are industry best practice reference models that we can employ to guide us through this complexity. As applications developers, many of us quickly and easily embraced first the Capability Maturity Model for Software (CMM-SW) from the Software Engineering Institute (SEI) and then the Capability Maturity Model Integration for Development (CMMI-DEV) that succeeded it. But is CMMI-DEV enough?
机译:瓦特·汉弗莱(Watts Humphrey)是“软件质量之父”,他经常说软件产品的质量和创建过程相同。但是,当今复杂的IT环境要求我们对IT业务采取更广阔的系统视野。幸运的是,我们可以采用一些行业最佳实践参考模型来指导我们克服这种复杂性。作为应用程序开发人员,我们许多人迅速而轻松地接受了软件工程学院(SEI)的软件能力成熟度模型(CMM-SW),然后是继承它的开发能力成熟度模型集成(CMMI-DEV)。但是,CMMI-DEV是否足够?

著录项

  • 来源
    《Cutter IT Journal》 |2012年第6期|p.35-39|共5页
  • 作者

    Bill Phifer;

  • 作者单位
  • 收录信息
  • 原文格式 PDF
  • 正文语种 eng
  • 中图分类
  • 关键词

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号