• 主题
高级搜索  >
历史搜索 清空历史
首页> 外文会议>Annual IEEE International Systems Conference >Applying standard independent verification and validation (IVV) techniques within an Agile framework: Is there a compatibility issue?
【24h】

Applying standard independent verification and validation (IVV) techniques within an Agile framework: Is there a compatibility issue?

机译：在敏捷框架内应用标准独立验证和确认（IV＆V）技术：是否存在兼容性问题？

获取原文
页面导航
  • 摘要
  • 著录项
  • 相似文献
  • 相关主题

摘要

Agile methods have gained wide acceptance over the past several years, to the point that they are now a standard management and execution approach for small-scale software development projects. While conventional Agile methods are not generally applicable to large multi-year and mission-critical systems, Agile hybrids are now being developed (such as SAFe) to exploit the productivity improvements of Agile while retaining the necessary process rigor and coordination needs of these projects. From the perspective of Independent Verification and Validation (IV&V), however, the adoption of these hybrid Agile frameworks is becoming problematic. Hence, we find it prudent to question the compatibility of conventional IV&V techniques with (hybrid) Agile practices. This paper documents our investigation of (a) relevant literature, (b) the modification and adoption of Agile frameworks to accommodate the development of large scale, mission critical systems, and (c) the compatibility of standard IV&V techniques within hybrid Agile development frameworks. Specific to the latter, we found that the IV&V methods employed within a hybrid Agile process can be divided into three groups: (1) early lifecycle IV&V techniques that are fully compatible with the hybrid lifecycles, (2) IV&V techniques that focus on tracing requirements, test objectives, etc. are somewhat incompatible, but can be tailored with a modest effort, and (3) IV&V techniques involving an assessment requiring artifact completeness that are simply not compatible with hybrid Agile processes, e.g., those that assume complete requirement specification early in the development lifecycle.
机译：在过去的几年中，敏捷方法已得到广泛认可，以至于它们已成为小型软件开发项目的标准管理和执行方法。尽管常规的敏捷方法通常不适用于大型的多年任务关键型系统，但现在正在开发敏捷混合动力（例如SAFe）来利用敏捷的生产率提高，同时保留这些项目的必要流程严格性和协调需求。但是，从独立验证和确认（IV＆V）的角度来看，采用这些混合敏捷框架变得有问题。因此，我们谨慎地质疑传统IV＆V技术与（混合）敏捷实践的兼容性。本文记录了我们对（a）相关文献，（b）修改和采用敏捷框架以适应大规模，关键任务系统的开发以及（c）标准IV＆V技术在混合敏捷开发框架中的兼容性的调查。针对后者，我们发现在混合敏捷过程中采用的IV＆V方法可分为三类：（1）与混合生命周期完全兼容的早期生命周期IV＆V技术;（2）专注于跟踪需求的IV＆V技术，测试目标等在某种程度上是不兼容的，但是可以通过适度的努力进行定制，并且（3）IV＆V技术涉及评估要求工件完整性的评估，而工件完整性根本不与混合敏捷流程兼容，例如，那些早就采用了完整需求规范的流程在开发生命周期中。

著录项

相似文献

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

客服邮箱：kefu@zhangqiaokeyan.com

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

  • 客服微信

  • 服务号