Agile Architecture Method Explained - Chapter 6 - Step 5: Candidate Solutions

From Guidance Share

Jump to: navigation, search

- J.D. Meier , Alex Homer, David Hill, Jason Taylor , Prashant Bansode , Lonnie Wall, Rob Boucher Jr, Akshay Bogawat.


Overview

After you define the key hotspots, you can create your first high-level design and then start to fill in the details to produce a candidate architecture. You then move back to step 2 of the process to validate the candidate solution design against the key scenarios and requirements you have defined, before iteratively following the cycle and improving the design.

Architectural spikes are a design prototype you use to determine the feasibility of a specific design path. Use architectural spikes to reduce your risk and quickly determine the viability of different approaches. Test architectural spikes against key scenarios and hotspots.


What to Do Next

After you complete the architecture modeling activity, you can begin to refine the design, plan tests, and communicate the design to others.

Carry out the following steps:

  • If you capture your candidate architectures and architectural test cases in a document, keep the document lightweight and avoid over-formatting so that you can easily update it. Key content to be included in the document is your objectives, application type, deployment topology, key scenarios, requirements, technologies, quality attributes, and tests.
  • Use the quality attributes to help shape your design and implementation. For example, developers should be aware of anti-patterns related to the identified architectural risks, and use patterns to help address the issues.
  • Use the architectural frame to plan and scope your architectural tests.
  • Communicate the information you capture to relevant team members. This may include your application development team, your test team, and your network and system administrators.
Personal tools