The most important task of a Business Analyst is to gather the detailed requirements that completely define the project. We use the wordgather rather than invent or assume because the Business Analyst must be sure to ask the right questions of the right people to gatheraccurate requirements.
B2T Training uses the terms Business Requirements and Functional Requirements to differentiate between the business needs and the software functionality. It is critical that the Business Analyst initially gather Business Requirements and completely understand the business needs before defining a software solution.
The Business Analyst must assess the type of project, the people involved, and the volume of information required; and then determine how and where to find the requirements. Business Analysts have a variety of techniques available to them including interviews, facilitated information gathering sessions, surveys, questionnaires, observation, and existing documentation from which to choose. In addition, the Business Analyst will often have many people with whom to talk and several existing automated systems about which to learn.
Gathering complete, detailed requirements is an iterative process that involves the Business Analyst asking questions, pondering answers, asking follow-up questions, and bringing divergent opinions to consensus. It also involves prioritizing the requirements to assure that the most critical issues are addressed by the project solution.