Best methodology for BA

Waterfall Model is a very old and traditional model in IT Industries. It is a progressive implementation of the projects which is divided into different phases of SDLC methodology. As waterfall models have few limitation, still it was used earlier on a wide range. Later agile methodology took over the focus of the IT Industry. But Again it depends on the type and integrity of the project, which software models has to be followed. According to me Waterfall Methodology is best for business Analysis. Coming to the Waterfall model and the BAs role in the process we well discuss the phase under the waterfall model. Requirement gathering, Designing, Coding, Testing, Deployment, Maintenance. Lets Talk about Requirement gathering and Analysis From the initial stage, there is an involvement of the business analyst. He/She is the person who is responsible for preparing the BRD(business requirement document). Designing is phase of the architect will start designing the system based on the business analyst helps him to clear his doubts about the requirements. Coding is phase is quiet lengthy as the core development based on the requirement document prepared by BA .Developers to Ba regarding the requirement and he wants to answer their question as and when required. Its Artifacts as Code. Testing is After coding ,the phase will start BA help the testing team to understand requirement so that they will build proper functional test case. BA has review weather the test case covering the whole functionality . its artifacts test case and test result , Deployment means when once the code is developed and tested , its ready to deploy in the production in environment . the BA will verify the product is delivered as per the requirement and it is meeting the business need . its artifacts implementation review documents . lastly we talk about maintenance means when once the deployment is done the team has to give support by installing patches handling change request etc. A BA is a person who knows every knock and corner of the project . so every changes request has to reviewed by him and based on his input and reports the team will respond . its artifacts users satisfaction review , change request review. BA is a core part of the team and he knows all in and out of the project . so at any point in time , in any phase, he must be able to clarify the doubt within the team member and further communicate with them so that there will be no problem. IN waterfall feasibility evolution takes a long phase and it is done in advance to avoid the reworking in the next project phase. project planning is the done at the beginning of the project and it is not open to any changes later on it , project progress get monitor according to the project plan , and only the project manger communicates and carry out progress review on the basis of monthly or weekly. roles are not interchangeable.