Software Development Life Cycle

SDLC is the process of creating the system. It is a process developed by the system analyst to develop the project. The SDLC should be of high quality and must meet the requirement of the client

The flow of SDLC is given below

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.