Analysis to build good software

Requirement analysis is the one of the most important phase in the software development life cycle. Once gathering the requirement form the client or stakeholders need to analysis the requirement to develop the project. And it is the process of the understanding the requirement, analysing and documenting the needs and the expectations of stakeholders for a software system. The project need develop based on the customer requirements and needs, and documents need to prepare for the development team to develop the project and understand the project needs and outcomes. If we gather unclear requirements the project may delay and the project may gets failure, every successful software system is begin with clear information and understanding the customer needs and want. Even sometimes the customer will come to change there requirement in the middle of the project in this time also the project may gets delay and misunderstanding needs from the client. It's very difficult to change sometime, the whole team need to understand the changes in the project so that the team can work on the change request. Clear documents and requirements are very important for the project success. The requirement analysis process start one we collected each and everything requirement from client, stakeholders and users. Based on the requirement and problem the business analyst will prepare the documents. Usually we have two types of requirements that are Functional and non-functional requirements. Functional requirements are tell what the system need to do and how it respond for example: Register, login, search option etc. Non-Functional requirements are like quality and scalability of the application. During the requirement analysis, the collected requirements are need to carefully analysed and remove the bugs, errors and conflicts. The business analyst will work very close to the stakeholders to get clear information about the project and clarify the doubts to the stakeholders and project need to get 100% successful. And the business analyst will clarify the doubts to the development team and other team's. In the requirement analysis the most important document is software requirement specification (SRS) because the functional and non-functional document are very clearly in the software requirement specification document. And in the requirement analysis the business analyst will face some challenges like changing requirements in the middle of the project the business analyst will have to keep more efforts to prepare the document and handle the change request's. The business will understand clearly what the stakeholder needs and the requirements, Business analyst need to think from customer side also to get more information and problems this will make the project succuss. Which requirements are collect from the stakeholders that need to analysis and prepare based on the request. So, the business analyst need to understand the requirements clearly. And the Business analyst need to keep daily meetings with the stakeholder to give updates about the project and take feedback about the project. The daily meetings will conducted by the business analyst to take more information and clarify the doubts this meetings will help to get project success and clear.