Introduction to User Story STLC Detailed.pptx

User story - SDLC with a detailed presentation helps students on project ideas

1. Introduction to User Story with respect to SDLC process

2. User Story:     Who are all Involved? What is User Story ? It is a written description of a small piece of functionality in an application. Why we need User Story? It is the best way to understand the requirement of an application. Product owner Business Analysts Development team QA Team User Story

3. How will User Story look like?           Syntax : As a [user role] I want to [goal] so I can [reason] .            Ex : As a customer , I want to be able to reset my password so that I can regain access to my account if I  forget it . After the user story is created, what are the roles and responsibilities of the teams?               Development team : They will go through the user stories and understand the requirements; based on that, they will            start writing the code.             Testers or Quality Assurance (QA) team : The team will concentrate on the acceptance criteria of the user stories and          start to prepare the test cycle.  Is there any method, step, or procedure to design the test cycle?              Yes, there is a method called  Software Test Life Cycle (STLC) that will give the proper and best way to design these               procedure.

4. What is STLC, and what are all the phases that come under it?  It is the testing process which is executed in the systematic and planned manner Requirement analysis:  In this phase quality assurance team understands the requirements  Test Planning: The team will make a detailed plan for the testing activities. Test Case Development: In this phase testing team will write the test cases, Creating test data, Prepare Test scenarios. Test Execution:  In this phase testing team starts executing test cases. Test Cycle Closure: This phase is   to ensure that all testing-related activities have been completed. Requirement analysis Test Planning Test case development Test Execution Test Cycle Closure

5. Who are all involved in STLC process? QA Manager QA lead Manual Test Engineer Automation Test Engineer

6. What are all the different types of testing that will be done once code is released by the development team?  There are two approaches  Manual testing  Automation testing To test any application by manual effort or manual way, there are many different methods, some of which are as follows:  Smoke Testing : A brief check to ensure basic features work. Functional Testing : Detailed testing of each function or feature. Regression Testing : Ensure older features still work after new changes. Integration Testing : Check if the software works well with other systems or services. Performance Testing : See how the software behaves under heavy use or load. Security Testing : Look for potential security risks or issues.

7. What is Defect in the Software development process and how these are identified during software testing, and how these are resolved?

8. Defect life cycle

9. On what basis defect will be fixed? Severity : Impact on functionality of the application Priority :Impact on Business

10. Conclusion:     The Software Testing Life Cycle (STLC) is a structured process that ensures software quality. This involves stages from understanding requirements, crafting test cases. A pivotal aspect of the STLC is the Defect  Life Cycle , which charts the journey of a defect from discovery to resolution, ensuring any software issues are systematically addressed.     Moreover, the creation and management of User Stories play a foundational role in the STLC. User stories define desired features in user-centric terms, providing a blueprint for both developers and testers.