Managing Requirements Change

Requirements change. And when they do, you need to be able to determine what else is impacted by requirement changes. There might be test cases, issues, and even source code impacted.

How will you know what happens when your requirements change? Doing a change impact analysis should be your first step.

How to Do Impact Analysis in Software Development

Doing an impact analysis helps you reduce the risk of missing changes, eliminate unexpected consequences, and identify new requirements. 

In this white paper, you'll learn how to do impact analysis in software development.

  • Types of impact analysis.
  • When to do impact analysis. 
  • How to do impact analysis.

Do Impact Analysis the Easy Way

A traceability matrix makes it easier to understand the impact of change. But it isn’t always easy to create the matrix in the first place. Consult this guide for help using traceability.

Get traceability tips >

Additional Resources on Change Management

Interested in learning more about requirements change and change management? Explore the following resources: