Requirements Analysis or Feasibility Study?

Info-Tech Advisor: Research Note

Published: February 06, 2007


Every software project starts with some kind of a reality check. Project managers ask questions like:

  • What is the purpose of the software and what problem will it solve?
  • What is the business impact of the project?
  • How much will the project cost?

Two methods for assessing a software project's viability are requirements analysis and feasibility studies. Increase the odds of project success by recognizing the difference between these methods and knowing which projects are ideal for each.

No Feasibility Study, No Funding

With the increase in enterprise complexity, and the proliferation of multiple technological alternatives, C-level executives have significantly changed the way they justify software projects. For example, a director of a utility company used a feasibility study to determine if they should change...

«  Previous ITA Research Note Back to Current Research Next ITA Research Note »
This article is available in full to members of Info-Tech Advisor.
Already a member? Please log in.

Username:

Password:

Remember me:

I forgot my password.

E-mail address:

 

I am not an Info-Tech Advisor member, but...
  • I would like to become a member (starting at $495/yr).
  • I would like to learn more.