About an Architecture-Based Analysis Requirements Life Cycle
Good Requirements Life Cycles (RLCs) provide a framework to define the decisions and resulting requirement products that occur throughout the phases of a business transformation. If your organization has an RLC, you in a better position than a majority of organizations (see article in BA Times).
​
Incorporating business analysis activities improves the quality of requirement products by weaving critical thinking into the RLC. This elevates a requirement from "what was said" to what is truly needed.
​
Incorporating architecture improves the quality of requirements through the use of visual models which help your stakeholders envision how your enterprise is now and where it seeks to be. The value of these models is that they "bring to light" aspects of the proposed change which would otherwise be missed or uncovered much later when changes are up to 24 times more expensive to fix.
​
An ABA RLC integrates both business analysis and architecture, helping you maximize the chance for an efficient, effective business transformation. And an ABA RLC is scalable, meaning that it works for small projects as well as mission critical enterprise initiatives.
​
Hard Cost Benefits Associated with an ABA RLC:
​
-
Business outcomes are less costly to deliver because delivery risk is mitigated
-
Internal resource costs are lower because the intellectual capital of your organization is stored as rules in the requirements repository rather than the mind of a subject matter expert. Once defined, rules and requirements can also be reused, saving further time and costs to your organization.
-
If external contractors are used, an ABA RLC reduces the costs they charge to learn your organization. Because their work in stored in your repository rather than their tools, valuable project knowledge does not walk out the door when their engagement ends.
.png)