Words to be avoided while preparing the Requirement Document

Acceptable
Adequate
As Much As Possible
At Least
No More Than
At A Minimum
Convincing
Sufficient
Usually
Sometimes
When Necessary
Where Appropriate
Optional
Optimal
Some

The scope of Business Analyst role

The role of Project Manager and Business Analyst

Business analyst will gather the requirement and will describe the scope of the project and the required quality. The business analyst is not responsible for the project success. He must make sure that the scope of the project is delivered.

Project manager has to go through the requirement and must fix the time line and the budget for the project. The project manager is responsible for the project success. 

In short the business analyst will provide the content for the project. The project manager has to provide the process for the given content. 

Use Case

Use case is a diagrammatic representation of the actions that the system will perform. It will also include the deviation that the system will have. The use case diagram will include the actors who are involved in the interaction. The diagram will explain the different ways of interaction that the actor will do with the system.

There are two types of use case. One is business use case and the other is system use case. 

The business use case will describe the actor’s interaction with respect to the business process. The business use case diagram will be prepared by the business analyst. 

The system use case will explain the actor’s interaction with IT system. The system use case diagram will be prepared by the system analyst.

Types of standard Requirements

Business Requirements

The requirement which achieves the business needs of the client is called as business requirement. The business requirement will include the goal and desires of the client. These requirements will also give the reason for developing the project. 

User Requirements 

This requirement serves as a bridge between Business Requirements and the various classes of solution requirements. This Requirement will tell us how the user will interact with the system. 

Functional Requirement 

This requirement describes the functionality of the project. It will describe the behavior and operation of the system. 

Quality of service requirements 

This requirement will describe the qualities that the project must have. This requirement will not describe the behavior or functionality of the system. This requirement will be additional or non functional requirement. 

Software Requirements Specification (SRS)

SRS is a document which describes the organization understanding of the client’s requirement. The SRS will be prepared by the business analyst. In some organization technical writer will prepare the SRS. The SRS is the main input given to the technical people for developing the project. SRS will reduce the time for the developers to achieve the goal. It will also minimize the development time and cost.

The SRS can be defined as the blue print for the project. It is also referred as the parent document of the project. The SRS contains only the functional and non functional input of the project. The High Level Design Document will be prepared by the technical team based on the SRS.

The quality team will prepare the test cases based on the SRS. The SRS will provide the feedback to the customer and it will also give the assurance that the organization has understood the requirement given.  

Difference between system analyst and business analyst

The role of a business analyst and system analyst is different. 

System analyst is a person who must have good technical knowledge. The system analyst is responsible for converting the business requirement into technical solution. The system analyst acts as an intermediate between the business and the IT project. The system analysts communicate and provide the solution to the developers. They are responsible for troubleshooting and resolve the problem. 

Business analyst is a person who must have good business knowledge. The business analyst is responsible for getting the requirement and documenting the requirement. BA must have domain knowledge and must have experience in IT projects.  

Both the system analyst and business analyst play an important role in the software development life cycle. The person who does the job of both business analysis and system analysis are called as Business System Analyst or Technical Business Analyst.

Skills Required for Business Analyst

• Business analyst must have excellent communication to interact with the client. 
• He must have good analytical and logical skills.
• He must have good listening skills to understand the requirement of the client.
• He must have good documentation skills.
• He must have the skill to convert the business need of the client to business requirement.
• He does not need to have technical knowledge.
• But he must have basic computer knowledge.
• He must have the ability to plan the project.
  
  
  

Role of a Business Analyst

In initial role of business analyst will be gathering the requirement from the client.

After gathering the requirement, they have to prepare the document like Business Requirement Document, Use Case Diagram, and Test case. 

After preparing the documents, they have to interact with the Project Manager and Software Developers to meet the business requirement.

They must also interact with the Testing Team and clarify the doubts against the requirement. 

 Business Analyst is responsible for giving the demo to the client.