The various phases of SDLC are explained below:
The prime focus of this phase is to gather the essential requirements from the customer. This information gets collected by the business analyst from their target customer(s) and plans the BRS (Business requirement Specification) for the development of the product. The team of all the designers and BA will do brainstorming to extract all the requirements and plan accordingly for the new system to be developed? Some popular questions that this meeting picks up are - Who will use the product? What must be the output data by the product?
When the BRS documentation is done, there are another set of employees like Human Resource (HR), Finance Analyst, Architect, a Business analyst as well as Project manager will sit jointly discuss as well as analyze how to proceed and whether it is feasible and possible in the allotted budget. Such decisions are taken depending on the cost, resources, time, etc. Documentation is made, which is the SRS (Software Requirement Specification) document, which contains a detailed explanation of product requirements, right from design to development.
This phase is when the design specification is organized from the prerequisite document when the project is approved to go further. This phase contributes to the next phase for development. This phase portrays a blueprint of the product, which helps to specify the hardware and requirements of your system as well as assist in crafting a significant architecture of your system.
As you are preparing with the design document, this phase deals with the developers to start writing the code or prepare for the engineering so that a prototype of the product can be created using some specific tools and techniques. This is considered the longest phase of SDLC.
As your product is prepared for deployment, it needs a prior testing environment by the test engineers to check for bugs and run-time errors, and they check in this phase whether the functionality of the product is working as per the requirement or not. The bugs or defects which are encountered in the test phase are reported to the developers, who fix the bug and revert to the test engineers for further testing. This is an iterative process that continues until your application is free from bugs and defects and works stably.
Once your prototype or product is developed, tested, and completely in working form as per the requirement, and then it is installed or deployed in the customer's workplace or system for their use.
This is an additional phase, and in many cases, this phase does not come under the count of SDLC, when your customer(s) begin using your product and encounter with some issues which they want us (as developers) to fix from time to time. The developer fixes the issue, and software testers test the product and hand it over the back to the customer.
No comments:
Post a Comment