One of the leading causes of failure in distributed systems occurs when developers defer consideration of system performance until after implementation.  Following implementation, it is not uncommon for systems to be "tweaked" mercilessly to get them to perform according to requirements.  In the process, critical internal design elements are often sacrificed, and the system ages almost overnight.

     So what can be done differently?  What type of systematic approach can be taken to ensure that the system under development will meet not only stated functional requirements, but also performance and other non-functional requirements?

     Because SABRE focuses upon the intedependency between requirements and software architecture, it provides a solution to this problem.