...
首页> 外文期刊>Software Quality Journal >ER~2C SDMLC: enterprise release risk-centric systems development and maintenance life cycle
【24h】

ER~2C SDMLC: enterprise release risk-centric systems development and maintenance life cycle

机译:ER〜2C SDMLC:企业释放风险中心的系统开发和维护生命周期

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

获取外文期刊封面封底 >>

       

摘要

Traditional systems development life cycle models can be viewed as technical life cycle models in systems development projects. These life cycle models mostly focus on the initial delivery of systems as part of projects. However, many systems end up in a perpetual development mode and can be viewed as a continuum of releases rather than the deliverables of temporary projects. Newer versions of such systems are usually released as part of support/maintenance processes rather than through rigorous projects. In environments with quick-fix maintenance or loose release management regimes, lack of rigor may result in the compromise of quality, especially quality-in-use. This may cause end users' exposure to risks as a result of using potentially faulty releases and products. Minimizing product risks should be an inherent inclusion in product life cycle, regardless of whether the product is released as part of a project or as part of support/maintenance work. A novel systems development and maintenance life cycle model is proposed that models the life of a system as a sequence of releases. It covers non-project maintenance-related releases as well as major projectized releases under a unified consistent governance model. It proposes applying different levels of rigor depending on analyzed release risks via the enforcement of different thresholds to a set of metrics that are extracted from release artifacts. The proposed life cycle model supports iterative development and is conformant to ISO 15288:2015. Evaluations performed by a community of practice in a large government agency in Queensland, Australia, has demonstrated the success of the proposed model in a number of areas, especially in how risk is managed when changes are introduced to systems after their initial release.
机译:传统系统开发生命周期模型可以在系统开发项目中被视为技术生命周期模型。这些生命周期模型主要关注系统的初始交付作为项目的一部分。然而,许多系统最终以永久的开发模式结束,可以被视为释放的连续性而不是临时项目的可交付成果。此类系统的较新版本通常作为支持/维护流程的一部分而不是通过严格的项目释放。在快速修复维护或松散释放管理制度的环境中,缺乏严格可能导致质量的折衷,尤其是使用质量。由于使用潜在故障的释放和产品,这可能导致最终用户的风险暴露。最小化产品风险应该是产品生命周期中的固有含量,无论产品是否被释放为项目的一部分,也应该是产品的一部分或作为支持/维护工作的一部分。提出了一种新颖的系统开发和维护生命周期模型,将系统的寿命模拟作为一系列版本。它涵盖了非项目维护相关的发布以及统一一致的治理模型下的主要项目释放。它提出了根据不同阈值的分析的释放风险应用于从释放伪像中提取的一组测量来应用不同级别的严格程度。建议的生命周期模型支持迭代开发,并符合ISO 15288:2015。澳大利亚昆士兰州大型政府机构的实践社区进行的评估表明,在许多领域,拟议模型的成功,特别是当在初始发布后改变为系统时管理风险程度。

著录项

相似文献

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

客服邮箱:kefu@zhangqiaokeyan.com

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

  • 服务号