Sdlc in software

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. What are the drawbacks of the Waterfall model? What do you understand by the waterfall model?

What is the Analysis phase? What is the Design phase? What is the Testing phase? He has extensive experience in the field of Software Testing. Furthermore, he loves to be with his wife and a cute little kid 'Freedom'. Your email address will not be published. Skip to content In this Software Development Life Cycle tutorial, we are going to discuss the following.

Table of Contents. Like This Post? Subscribe and get free access to subscriber-only guides, templates, and checklists. Yes, I'm In! You are subscribing to email updates. Unsubscribe anytime. Your data is safe. Post navigation Previous Previous. Next Continue. Similar Posts. Thank you Rajkumar for your article. SRS is the reference for product architects to come out with the best architecture for the product to be developed.

Based on the requirements specified in SRS, usually more than one design approach for the product architecture is proposed and documented in a DDS - Design Document Specification. This DDS is reviewed by all the important stakeholders and based on various parameters as risk assessment, product robustness, design modularity, budget and time constraints, the best design approach is selected for the product.

A design approach clearly defines all the architectural modules of the product along with its communication and data flow representation with the external and third party modules if any. The internal design of all the modules of the proposed architecture should be clearly defined with the minutest of the details in DDS.

In this stage of SDLC the actual development starts and the product is built. The programming code is generated as per DDS during this stage. If the design is performed in a detailed and organized manner, code generation can be accomplished without much hassle. Developers must follow the coding guidelines defined by their organization and programming tools like compilers, interpreters, debuggers, etc. The development team fixes the bug and send back to QA for a re-test.

This process continues until the software is bug-free, stable, and working according to the business needs of that system. Once the software testing phase is over and no bugs or errors left in the system then the final deployment process starts. Based on the feedback given by the project manager, the final software is released and checked for deployment issues if any. Once the system is deployed, and customers start using the developed system, following 3 activities occur.

The main focus of this SDLC phase is to ensure that needs continue to be met and that the system continues to perform as per the specification mentioned in the first phase. The waterfall is a widely accepted SDLC model. In this approach, the whole process of the software development is divided into various phases of SDLC. In this SDLC model, the outcome of one phase acts as the input for the next phase.

This SDLC model is documentation-intensive, with earlier phases documenting what need be performed in the subsequent phases. The incremental model is not a separate model. It is essentially a series of waterfall cycles. The requirements are divided into groups at the start of the project. For each group, the SDLC model is followed to develop software. The SDLC life cycle process is repeated, with each release adding more functionality until all requirements are met.

In this method, every cycle act as the maintenance phase for the previous software release. Modification to the incremental model allows development cycles to overlap. After that subsequent cycle may begin before the previous cycle is complete. In this type of SDLC model testing and the development, the phase is planned in parallel.