词条 | Agile Architecture |
释义 |
Waterman, Nobel and Allan (2015) [2] explored the tensions between spending too little time designing an up-front architecture, increasing risk, and spending too much time, negatively impacting of the delivery of value to the customer. They identify six forces that can affect agile architecture: Requirements instability, technical risk, early value, team culture, customer agility and experience. These forces may be addressed by six strategies: Respond to change, address risk, emergent architecture, big design up front and use frameworks and template architectures. Several attempts have been made to specify what makes up an agile approach to architecture. According to the SAFe framework, the principles of agile architecture are:[3]
At the Enterprise Architecture level, Scott Ambler (2016)[4] proposes the following principles
References1. ^Kruchten, P. (2010). Software Architecture and Agile SoftwareDevelopment — A Clash of Two Cultures? Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering {{software-eng-stub}}2. ^Waterman, Nobel and Allan. (2015). How Much Up-Front? A Grounded Theory of Agile Architecture. In Proceedings of the 37th International Conference on Software Engineering 3. ^{{Cite web|url=https://scalingsoftwareagility.wordpress.com/2008/07/10/agile-architecture-%e2%80%93-the-whitepaper-now-on-line/|title=Agile Architecture – The Whitepaper Now On Line|last=Leffingwell|first=Dean|date=2008-07-10|website=Scaling Software Agility|access-date=2017-02-06}} 4. ^Ambler, S. (2016). Agile Enterprise Architecture – Disciplined and Pragmatic Strategies. [video] Retrieved from: https://www.youtube.com/watch?v=AaIiG73QE3c 2 : Architectural theory|Agile software development |
随便看 |
|
开放百科全书收录14589846条英语、德语、日语等多语种百科知识,基本涵盖了大多数领域的百科知识,是一部内容自由、开放的电子版国际百科全书。