This Video SDLC | Software Development Life Cycle to non IT Professionals and Beginners. This SDLC video gives a brief explanation of about SDLC phases and SDLC models
For more Manual Testing Tools Material and notes visit :
• SDLC Phases
• SDLC Models
Software Development Life Cycle
Software Development Life Cycle Phases:
Any project development will have SDLC phases. Each models will have their own life cycle to develop the software.
Following are the SDLC Phases:
• Requirement Analysis
• Deployment & Maintenance
• In this phase client has to provide the requirements.
• Business Analyst will involve in this phase and discuss with the client on the needs, and it is an interactive process to discuss about the objective and scope of the project.
• This requirement information used to plan the basic project approach and to conduct product feasibility study in the technical, financial and resources areas.
• Once discussion is completed, then the entire requirement has documented in SRS, which useful for next phase.
• Requirements can be Functional and Non-Functional.
• After Requirements are finalized, then it is responsibility of the Developer or System architect to develop the system design, system design consists of hardware and software requirements in the project.
• All the technical details of system design is discussed with the client, based on the various parameters like risk assessments, technology to be used for developing the project, budget and time constraints and etc… are reviewed for the best design approach.
• Selected design approach will give the brief about all the architectural modules and components that need to be developed in the project along with database communication with external and any third party modules if required, this design details is usually kept in DSD(Design Specification Document) for next phase.
There are two stages in design:
• HLD – gives the architecture of the software product to be developed and is done by architects and senior developers
• LLD – done by senior developers. It describes how each feature in the product should work and how every component should work. Here, only the design will be there and not the code.
• The client should approve UI design.
• Technical manager has to approve the business logic.
• As a tester, we need only SRS and UI design box.
• After requirement and design phase is complete, now developers takes the responsibility to develop the application as per the requirements and design which has discussed in before phases.
• Based on the guidelines of the company, developers will develop the application in different high language like Java, C & C++, C#, PHP. This phase takes more time to complete.
• Developers also write unit test to verify the code that they have written is working as per the client requirements, once coding is complete, build will release for testing.
• Once we receive the build from the development team, testing is conducted on build to find defects.
• The main aim of testers is to find defects, and verify whether the developed application is working as per the customer’s requirements or not. Usually, different levels of testing is conducted on application, to ensure that application is working in all aspects.
• Identified defects shared with development, thus they will fix the defects and revert to testing team, now testers will retest the build.
• This chain will continue until software is defect free, and the software is ready to ship.
Deployment and Maintenance:
• Once the software has tested fully, then application goes to deployment stage and the customer can use the application. If any issue in the application, it is maintained by the production team.
• Here the customer uses the product, and finds certain bugs and defects, and sends the product back for error correction and bug fixing.
Visit Our Complete Video Tutorials channel
Visit for More Video Tutorials provided by Microsoft Certified Trainer in MS.NET Technologies