• 主题
高级搜索  >
历史搜索 清空历史
首页> 外文会议>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.
机译：敏捷方法在过去几年中获得了广泛的接受，以至于它们现在是小型软件开发项目的标准管理和执行方法。虽然常规敏捷方法通常不适用于大型多年和关键任务系统，但现在正在开发敏捷混合动力车（如安全），以利用敏捷的生产力改进，同时保留这些项目的必要流程和协调需求。然而，从独立验证和验证（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 六维联合信息科技 (北京) 有限公司©版权所有

  • 客服微信

  • 服务号