Requirements gathering & Analysis phase

-

 ​What is done in the Requirements gathering & Analysis phase?  


 Requirement gathering is the first and basic phase of the software development life cycle. this phase is essential for developing software. the requirement serves the detail descriptions of functions that software should provide. requirement specifies the need of the client. Business analysts and subject experts are responsible for the requirement gathering process. 
The most important phase of the SDLC is the requirement gathering and analysis phase because this is when the project team begins to understand what the customer wants from the project. During the analysis phase, the project team needs to ensure they can deliver the requirements. 
After the customer provides requirements for the product, the project manager and members of the project team begin to analyze the requirements. The business managers analyze each requirement to ensure the requirement can be included in the software without causing breaks or problems with system functionality.  

 There are two documents are created :  
● BRS ( Business Requirement Specification) 
● SRS (System Requirement Specification)   

 BRS ( Business Requirement Specification) ​: 
● It describes at a very high level the functional specifications of the software. 
● It is a formal document describing the requirement provided by the client (written, verbal). 
● Usually, its created by the Business Analyst who interacts with clients.  

 SRS (System Requirement Specification) ​: 
● It describes at a high level, the functional and technical specification of the software. 
● It specifies the functional and non-functional requirements of the software to be developed. 
● Usually, its created by the System Architect who is a technical expert. 
● It is derived from the BRS    
Requirement gathering process contains a list of activities are follows:  
● Capture initial requirements from users and clients for defining the project scope. 
● Do interface analysis for software. 
● Brainstorm on all ideas collected from the user and client. 
● Prepare requirement document and prototype. 
● Review them from experts. 
● Make changes according to expert’s suggestions. 
● Reviews changes from experts. 
● A client signs off from the requirement.  

 Importance of requirement gathering ​:  
It is helpful for capturing all the needs of users and clients. It avoids reworking. It is necessary to clear the views of all stakeholders regarding software to be developed. It increases the quality of software to be developed. It saves time for all further stages of the software development life cycle.

Comments

Post a Comment

Popular posts from this blog

Implicit and Explicit requirements

-
Implicit and Explicit requirements Explicit Requirements​ :    ● The Things business analyst Wrote Down.  ● These are the requirements explicitly stated or mentioned by the customer.  ● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.   ● This is the simplest type and the easiest to test.  ● The development team might take the form of an elaborate design specification, a set of acceptance criteria.  ● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.   Implicit Requirements​ :  ● The Things client Will Expect  ● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer.  ● These are all the things that users are going to expect that were not captured explicitly.  ● Examples include performance...
Read more

Software Configuration Management (SCM)

-
Software configuration management (SC) is a software engineering discipline consisting of standard processes and techniques often used by organizations to manage the changes introduced to its software products. SC helps in identifying individual elements and configurations tracing changes and version selection control and baselining.   SC is also known as software control management. SC aims to control changes introduced to large complex software systems through reliable version selection and version control.   Software Configuration Management does​ ​   ● Introduction to Software Configuration management and Configuration management for software Testers.  ● Software configuration management (SC) is the discipline for systematically controlling the changes that tae place during Software evelopment.  ● Software development software consists of a collection of items (such as program documents etc..) that can easily be changed. uring software...
Read more

Identified for Configuration Management

-
The term configuration item (CI) refers to the fundamental structural unit of a configuration management system. Examples of CIs include individual requirements documents software models and plans. The configuration-management system oversees the life of the CIs through a combination of processes and tools by implementing and enabling the fundamental elements of identification change management status accounting and audits. This system aims to avoid the introduction of errors related to lack of testing as well as incompatibilities with other CIs.     Configuration Management Activities ​:     1. ​Configuration Item Identification ​:  ​In this phase, the item will be identified for making changes.  Example: ​Requirement document design document source code etc    2. ​Change Control ​: ​ Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the change...
Read more