【24h】

Agile in Distress: Architecture to the Rescue

机译:危难中的敏捷:救援架构

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

摘要

For large-scale software-development endeavors, agility is enabled by architecture, and vice versa. The iterative, risk-driven life cycle inherent in agile approaches allows developers to focus early on key architectural decisions, spread these decisions over time, and validate architectural solutions early. Conversely, an early focus on architecture allows a large agile project to define an implementation structure that drives an organization into small teams, some focusing on common elements and their key relationships and some working more autonomously on features. Architects in agile software development typically work on three distinct but interdependent structures. architecture of the system, the structure of the development organization, and the production infrastructure. Architectural work supports the implementation of high-priority business features without risking excessive redesign later or requiring heavy coordination between teams. Architectural tactics provide a framework for identifying key concerns and guide the alignment of these three structures throughout the development life cycle.
机译:对于大规模软件开发,架构可实现敏捷性,反之亦然。敏捷方法中固有的迭代式,风险驱动的生命周期使开发人员可以及早专注于关键架构决策,随时间推移传播这些决策并尽早验证架构解决方案。相反,早期对体系结构的关注使大型敏捷项目可以定义将组织带入小型团队的实现结构,其中一些关注于公共元素及其关键关系,而另一些则更加自主地处理功能。敏捷软件开发中的架构师通常在三种不同但相互依赖的结构上工作。系统的体系结构,开发组织的结构和生产基础结构。架构工作支持实施高优先级的业务功能,而不必冒以后进行过多重新设计或团队之间需要大量协调的风险。架构策略提供了一个框架,用于识别关键问题并在整个开发生命周期中指导这三个结构的对齐。

著录项

相似文献

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

客服邮箱:kefu@zhangqiaokeyan.com

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

  • 服务号