Requirement Analysis

Requirement Analysis

Our Requirements Analysis Techniques course covers these techniques and how to identify the most appropriate technique(s) to best support your critical thinking, understanding, and problem solving and communicate to stakeholders.

Software requirement is a functional or non-functional need to be implemented in the system. Functional means providing particular service to the user.

For example, in context to banking application the functional requirement will be when customer selects “View Balance” they must be able to look at their latest account balance.

Software requirement can also be a non-functional, it can be a performance requirement. For example, a non-functional requirement is where every page of the system should be visible to the users within 5 seconds.
Basically software requirement is a

  • Functional
  • Non-functional

As a Business Analyst, requirement analysis is the most important part of your Job. It will help you determining the actual needs of stakeholders. At the same time, enable you to communicate with the stakeholders in a language they understand (like charts, models, flow-charts) instead of complex text.

A requirement analysis has a —

  • Specific Goal
  • Specific Input
  • Specific Output
  • Uses resources
  • Has a number of activities to be performed in some order
  • May affect more than one organization unit
  • Creates value of some kind for the customer

Gallery