Projects are at risk of spending time developing an architecture that will not support the requirements of the system.
This task mitigates the risk of reworking the architecture by describing at least one potential architecture via the Architectural Proof-of-Concept. The objective is to describe just enough of the
architecture before building it to be confident that the approach will succeed.
Demonstrating that an architectural approach will succeed can be very informal or very formal. If a team is building
software similar to systems they've done in the past, or on top of well understood frameworks (e.g. J2EE), it may take
very little explanation to be confident of the architectural approach. If the team is new, or is building software
based on new technology, significant research, description, and prototyping may be required before achieving
enough confidence to proceed with a specific architecture.
|