STLC & SDLC-ppt-1.pptx

Software Testing Docs

1. Software Testing Life Cycle (STLC)

2.   STLC with QA  Software Testing Life Cycle is a  sequence of activities conducted during testing process to ensure software quality goals are met.  There are 6 major phases in STLC model:                                                                                                                                 PROCESS OF STLC  MODEL Requirement Analysis Test Planning   Test Case Development Environment Setup Test Execution Test Closure

3. Requirement Analysis QA interacts with various stakeholders like Client, Business Analyst, System Analyst, Technical Lead/ Development Manager to understand the requirements in detail to develop the project. During this phase the QA takes an important decisions like what are the testing types & techniques to be performed, feasibility for automation testing implementation, etc. 

4. Test Planning It is a document which contains the plan related to all testing activities which needs to be done to deliver a quality product. Senior QA Manager determines test plan strategy along with efforts and cost estimates for the project. The focus of the is to describe: Test duration Resources What to test What cannot be tested Tools used for testing Risks and contingencies planning 

5. Test Case Development Testing team write down all test cases. Prepare test data. Test cases are reviewed by peer members or QA lead. Requirement Traceability Matrix is prepared. The RTM is an industry accepted format for tracking requirements where each test cases is mapped with the requirements using tis RTM. We can track backward and forward traceability. OOB thinking.

6. Test Environment Setup Decides the software and hardware conditions under which a work product is tested. It can be done in parallel with test case development phase. Generic thing may not repeat for every story. Needs to be discussed in sprint grooming. We can have multiple QA server.

7. Test Execution The testers will carry out the testing based on the test plans and the test cases prepared. Bugs are reported to the development team. The development team resolves the bugs and the system is retested to ensure that it is bug free and ready to go live. 

8. Test Closure Activities Test closure activities are done mostly after the product is delivered   Test closure activities mainly comprise of four types:  Ensure Test Completion  Handover Test Artifacts  Project Retrospectives  Archive Test Work Products 

9. THANK YOU presentation by Virbhadra Swami

10. Software Development Life Cycle (SDLC) Software Development Life Cycle  (SDLC) aims to produce a high-quality system that meets or exceeds customer expectations, works effectively and efficiently in the current and planned information technology infrastructure, and is inexpensive to maintain and cost-effective to enhance.

11. Detailed Explanation (What is SDLC) A process followed in software projects is SDLC. Each phase of SDLC produces  deliverables  required by the next phase in the life cycle. Requirements are translated into design. Code is produced according to the design.  Testing  should be done on a developed product based on the requirement. The deployment should be done once the testing was completed. It aims to produce a high-quality system that meets or exceeds customer expectations, works effectively and efficiently in the current and planned information technology infrastructure, and is inexpensive to maintain and cost-effective to enhance.

12. Need of SDLC The development team must determine a suitable life cycle model for a particular plan and then observe to it. Without using an exact life cycle model, the development of a software product would not be in a systematic and disciplined manner. When a team is developing a software product, there must be a clear understanding among team representative about when and what to do. Otherwise, it would point to chaos and project failure. This problem can be defined by using an example. Suppose a software development issue is divided into various parts and the parts are assigned to the team members. From then on, suppose the team representative is allowed the freedom to develop the roles assigned to them in whatever way they like. It is possible that one representative might start writing the code for his part, another might choose to prepare the test documents first, and some other engineer might begin with the design phase of the roles assigned to him. This would be one of the perfect methods for project failure.

13. SDLC Cycle SDLC Cycle represents the process of developing software. SDLC framework includes the following steps:

14. The stages of SDLC are as follows: Stage1: Planning and requirement analysis Requirement Analysis is the most important and necessary stage in SDLC. The senior members of the team perform it with inputs from all the stakeholders and domain experts or SMEs in the industry. Planning for the quality assurance requirements and identifications of the risks associated with the projects is also done at this stage. Business analyst and Project organizer set up a meeting with the client to gather all the data like what the customer wants to build, who will be the end user, what is the objective of the product. Before creating a product, a core understanding or knowledge of the product is very necessary. For Example , A client wants to have an application which concerns money transactions. In this method, the requirement has to be precise like what kind of operations will be done, how it will be done, in which currency it will be done, etc. Once the required function is done, an analysis is complete with auditing the feasibility of the growth of a product. In case of any ambiguity, a signal is set up for further discussion. Once the requirement is understood, the SRS (Software Requirement Specification) document is created. The developers should thoroughly follow this document and also should be reviewed by the customer for future reference.

15. Stage2: Defining Requirements Once the requirement analysis is done, the next stage is to certainly represent and document the software requirements and get them accepted from the project stakeholders. This is accomplished through "SRS"- Software Requirement Specification document which contains all the product requirements to be constructed and developed during the project life cycle.

16. Stage3: Designing the Software The next phase is about to bring down all the knowledge of requirements, analysis, and design of the software project. This phase is the product of the last two, like inputs from the customer and requirement gathering.

17. Stage4: Developing the project In this phase of SDLC, the actual development begins, and the programming is built. The implementation of design begins concerning writing code. Developers have to follow the coding guidelines described by their management and programming tools like compilers, interpreters, debuggers, etc. are used to develop and implement the code.

18. Stage5: Testing After the code is generated, it is tested against the requirements to make sure that the products are solving the needs addressed and gathered during the requirements stage. During this stage, unit testing, integration testing, system testing, acceptance testing are done.

19. Stage6: Deployment Once the software is certified, and no bugs or errors are stated, then it is deployed. Then based on the assessment, the software may be released as it is or with suggested enhancement in the object segment. After the software is deployed, then its maintenance begins.

20. Stage7: Maintenance Once when the client starts using the developed systems, then the real issues come up and requirements to be solved from time to time. This procedure where the care is taken for the developed product is known as maintenance.

21. Thank you presentation by Virbhadra Swami