Architecture in the Life Cycle

• Stakeholder engagement models

Architecture in Agile Projects

• Agile Software Development

Architecture in Agile Projects

• How much Architecture?• Up-front work vs. Agility – trade off between

• Up-front design work on the architecture and up-front risk identification , planning, and resolution work• Rework due to fixing defects and addressing modification request.

Architecture in Agile Projects

• Agility and Architectural Methods• A successful architecture is resilient and loosely coupled. It is composed of a core set of well-reasoned design decisions but still contains rooms that allow modifications to be made and refactorings to be done, without ruining the original structure,

• An effective agile process will allow the architecture to grow incrementally as the system is deployed and matures. The key to success is to have decomposability, separation of concerns, and near-independence of the parts.

• To be agile, the architecture should be visible and self-evident in the code; this means making the design patterns, cross-cutting concerns, and other important decisions obvious, well communicated, and defended.

• Large amount of architecture work up front for large and complex system with relatively stable and well-understood requirements.

• For big projects with vague or unstable requirements, start by a quickly designing a complete candidate architecture, and be prepared to change and elaborate the architecture as circumstances dictate.