**Software Testing Tutorial #6 - Software Development Life Cycle (SDLC) - Notes** **Software Development Life Cycle (SDLC) Phases:** 1. **Requirement Gathering and Analysis:** - Initial phase. - Focus: Collecting necessary software requirements. - Customer provides requirements, such as features and functionalities. - Requirements are documented for clear understanding. 2. **Design:** - Follows requirement gathering. - Technical architects and experts involved. - Blueprint for software's architecture is established. - Design phase plans software's structure and component interactions. 3. **Development:** - Coding phase. - Developers write code based on the design. - Translates design into actual software. - Similar to constructing a building as per architectural plans. 4. **Testing:** - After development phase. - Rigorous testing of software's functionality and performance. - Testing team scrutinizes features and functionalities. - Defects and issues identified and reported for resolution. 5. **Deployment:** - Post successful testing and stakeholder approval. - Software moves from testing to production environment. - Made accessible to end-users or customers. - Equivalent to releasing a product to the market. 6. **Maintenance:** - Ongoing phase after deployment. - Software is monitored and maintained. - Addresses reported issues and ensures continued functionality. - Ensures software's reliability over time. **Importance for Software Testing:** - Crucial knowledge for software testers. - Provides foundation for understanding Software Testing Life Cycle (STLC). - Equips for confident discussions in software testing interviews. **Consistency Across Development Approaches:** - SDLC phases remain consistent across various development approaches (Waterfall, V-Model, Agile). - Timeline variations, but core phases-Requirement Gathering, Design, Development, Testing, Deployment, Maintenance-stay constant.
Your videos are amazing, thank you so much. You are one of those teachers who really explain it in a way that is fully understandable to everyone, and not all teachers know how to do so. Thank you again so much for your efforts in creating this videos for us :)
You are doing Excellent job. I have a question regarding this video. In SDLC, the last part is Maintenance. Kindly explain that if software need to be fix again so a tester is also re-testing the new or fixed part of the software?
If it's a fix, re-development is done and Quality Assurance (read: testers) will need to check that the bug has been fixed. And they need to also test that this fix has not impacted changes in other parts of the application (see more about: regression testing).
I have a question. Is there any strategy that in your experience works better when it comes to managing defects found before and after production? How to prioritize them or if they shouldn't be handled and measured together? In my case, the same developers work with both. The problem is that defects found in Production affect other teams in the company (Support and Customer facing roles) and they want defects to be prioritized, but we haven't found a good balance to make sure we prioritize impactful defects while also continue with the regular development cycle.
Good question Faisal, it depends which development approach is followed. If it’s waterfall approach then testing team was involved late in the cycle and that was the biggest disadvantage of waterfall model. Because if this disadvantage other models came in picture like, v-model, Scrum etc. Hope this helps. Thanks, Manish
Thank you for such a superb explanation.One doubt regarding documets,i am confused between frd brs and al. at what stage and who prepare these documets like frd/brs/srs. some says frd brs provided by client and srs by dev BA.Can you please help me in clearing these doubts who created these doc and at what stages of sdlc.Thanks in advance.
Hello, I really appreciate you making these excellent videos. I have a quick question, As there are different teams performing a specific role at each stage in an SDLC, let's say testers do testing, developers do development. SO who is responsible for Maintenance is it the testing team? I look forward to your response THANK YOU :)
I'd suggest checking L1-L3 IT support concepts. L3, the last level of support, needs the most technical knowledge of the application, so if a ticket goes that far it needs developer's attention. That's my guess when it comes to maintenance. Of course one could also include Project Manager, Business Analyst etc. when it comes to customer's change requests to the existing application.
I am a fresher, I do not know anything about testing but your videos are very educative, which area of IT do you advice that I go into???, DEVOP, PROGRAMMING & CODING OR TESTING I AM CONFUSED. Pls what is your email
