Methods of Business Requirements Validation

About this Resource

All companies conduct projectseither to improve their processes or products, or to develop new ones. These projects are situatedin any part of the companywhether it be HR, Finance, Facility Services, IT or any other business unit. One of the common elements of all these projects is a set of business requirements that is realized as the outcome of the project.

In this paper, Michael Poulin introduces two methods that he uses in his architectural practice to validate business requirementspicked up through his experience of working with numerous teams of Solution Architects and Business Analysts. These methods suggest that regardless of the business or IT domain, those who gather requirements may accidentally leave a gap between the project objectives and goals and the business requirements. Michael’s methods aim to close or minimize this gap.

Already a Member? Sign in here

Related Resources

Methods of Business Requirements Validation
  • Register to Download

  • The email address is already in use, please login
  • Checking your email address . . .

  • Please add your Job Title

  • Please add your Industry

  • Please add an Interest

  • Please add your Country

  • * Minimum 6 characters long, including lower and uppercase letters, a number and symbol (!/=+_-@ )

  • Please complete missing fields
  • Passwords need to be minimum 6 characters long, including lower and uppercase letters, a number and symbol.

DEMO Search