...
首页> 外文期刊>Systems Engineering >Anticipatory development processes for reducing total ownership costs and schedules
【24h】

Anticipatory development processes for reducing total ownership costs and schedules

机译:减少总拥有成本和进度的预期开发流程

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

摘要

Many systems and software processes overfocus on getting a project and product from an initial set of requirements to an Initial Operational Capability (IOC). Examples are most waterfall and V models. Projects following such processes may pass acceptance tests for functionality and performance, but may leave the product with serious maintainability shortfalls. Many agile processes focus on users' initial usage priorities, but often make development commitments for earlier needs that are incompatible with achieving later critical needs (eg, security, safety). Incremental development process models can do better, but often later increments may find that the earlier increments have not prepared them for ease of modification and repair. Besides increasing Total Ownership Costs (TOCs), long mean times to repair result in long downtimes, which can be critical to an organization's income and reputation. Furthermore, many of these shortfalls take the form of Technical Debt (TD), in that the later they are fixed, the more slow and expensive will be the fixes. This paper summarizes three process frameworks and tools providing more anticipatory ways to improve systems and software maintainability and life-cycle cost-effectiveness. The first framework is an Opportunity Tree for identifying and anticipating such ways. The second framework, Software Quality Understanding by Analysis of Abundant Data (SQUAAD), is a toolset for tracking a software project's incremental code commits, and analyzing and visualizing each commit's incremental and cumulative TD. The third framework is a Software/Systems Maintenance Readiness Framework (SMRF), that identifies needed maintenance readiness levels at development decision reviews, similar to the Technology Readiness Levels (TRLs) framework.
机译:许多系统和软件过程过度关注于将项目和产品从最初的一组要求转变为一个初始操作能力(IOC)。示例是大多数瀑布模型和V模型。遵循此类流程的项目可能会通过功能和性能的验收测试,但可能会使产品严重缺乏可维护性。许多敏捷过程专注于用户的初始使用优先级,但通常针对较早的需求做出开发承诺,而这些需求与实现较后的关键需求(例如安全性,安全性)不兼容。增量开发过程模型可以做得更好,但是通常以后的增量可能会发现早期的增量并没有为便于修改和修复做好准备。除了增加总体拥有成本(TOC)外,长时间的平均维修时间还会导致较长的停机时间,这对于组织的收入和声誉至关重要。此外,许多缺陷都以技术债务(TD)的形式出现,因为修正的越晚,修复的速度就越慢且成本越高。本文总结了三个过程框架和工具,它们提供了更多预期的方式来改善系统和软件的可维护性以及生命周期的成本效益。第一个框架是机会树,用于识别和预测这种方式。第二个框架是“通过分析大量数据来了解软件质量”(SQUAAD),它是一个工具集,用于跟踪软件项目的增量代码提交,并分析和可视化每个提交的增量和累积TD。第三个框架是软件/系统维护准备框架(SMRF),它在开发决策审核时确定所需的维护准备水平,类似于技术准备水平(TRL)框架。

著录项

相似文献

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

客服邮箱:kefu@zhangqiaokeyan.com

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

  • 服务号