Requirements Are the Keystone

A keystone is “the architectural piece at the crown of a vault or arch which marks its apex, locking the other pieces into position.” It may also be defined as an anchor, “or central cohesive source of support and stability or a central building block.

Requirements are the keystone of a successful project implementation. Imagine an arch. On one side of the arch you have the business stakeholders and users, and on the other side you have the solution delivery teams. The requirements bind the two sides together and keep the arch from falling apart.

Below is a rough illustration of the composition of the requirements “keystone” that joins the problem (business) domain to the solution domain.

The keystone metaphor is one that has helped me on a few occasions to describe the importance of requirements and their role in enabling project success. I hope a few of you will be able to make use of it as well.

I’d be interested in hearing of any similar types of  metaphors or analogies you might use to describe the role and importance of requirements and business analysis.

Keystone image by MMGoode


About the Author

Jonathan Babcock is a management and IT consultant with expertise in business analysis, process optimization and solution delivery methodology. Practical Analyst is his outlet for sharing what he's learned, and for interacting with solution delivery professionals across the globe.

Author Archive Page


  1. Great Timing! I am studying the Business Domain Model in BABOK V1.6. Kept confusing Business Domain Model with Solution Model. Thanks for the diagram.

Post a Reply to JB Cancel Comment

Your email address will not be published. Required fields are marked *