Task 1

1. Firstly, Software Testing is classified into 2 types.
   1) Manual Testing 2) Automation Testing
   Manual Testing : In this, test cases are written and executed by human without using any software tools.
   Automation Testing : In this, test scripts are executed with the help of software tools. Eg: Selenium
   These 2 are the basic types of testing. But once the build is ready, then developers performs Unit Testing before testers.
   Testers will perform Integration Testing, Smoke Testing, Sanity Testing, Functional Testing, End-End Testing, Regression Testing etc.
   Managers will also performs the testing to check critical functionalities. It is Exploratory Testing.
   Then Users performs User Acceptance Testing.

2. SDLC (Software Development Life Cycle) : It is used mainly to deliver high quality product with low cost and in shortest possible duration.
   There are 6 phases.
   1) Requirement Analysis and Planning : In this phase, Business Analyst will discuss with the client about the requirement of the project and do analysis and then they prepare a document.
   It is called BRS (Business requirement Specification) document.
   This document contains all the requirements of the project from client.
   Then BA will connect with the techleads and discuss about functional requirements for the project. They prepare a document.
   It is called FRS (Functional Requirement Specification) document.
   This document contains all the functional requirements. Eg : Login functionality.
   Then another document is also prepared to list the specifications required i.e., how many fields required.
   Eg: For Login functionality how many fields required.
   This document is called SRS (Software Requirement Specification) document.
   2) Designing : In this phase, overall architecture is designed.
   Eg : Where should be the logo, color of login page, where should be the Login etc.
   here two documents are prepared in this phase.
   High Level Design document(HLD) : It contains overall architecture of the project.
   It is prepared by Domain Expert in the project.
   They will also design Table and Database.
   Low Level Design document(LLD) : Here all the information in HLD is converted into low level design i.e., Detailed description.
   3) Development : In this phase, developers write the code and once the build is ready, they will give to testers.
   4) Testing : In this phase, testers executes the test cases and performs end-end testing using STLC techniques.
   5) Deployment : In this phase, after testing, once the product is ready, it is deployed to end users.
   6) Maintenance: In this phase, support team will take care of the issues raised by customers i.e., end users while using the product.

3. As an Manual Tester, firstly I have good communication skills. Apart from that I have knowledge in Software Testing Tools which is most required for a tester.
   I have thorough knowledge of SDLC and STLC as well.
   i am good at writing Test Cases.
   I have an ability to think creatively and effective time management skills.
   i am passionate to work as an Manual Tester and will be friendly with all the team members. Whenever project requires any support from my side, I will go ahead to support the team without any hesitation.

4. Waterfall Model : In this model, after completion of one phase, then only other phase will begin.
   Eg: After completion of Requirement Planning and Analysis phase only, Designing phase will begin.
   It is also called as Linear Sequential Model.
   it can be used for smaller projects and stable requirement planning projects.
   Advantages : Each phase will be clear with no high priority defects.
   Each phase is completed at a time.
   Cost and Time is calculated before the start.
   Disadvantages : Changes in the requirements is not possible throughout the project.
   Client Interaction is also not possible throughout the project.
   Agile Model : This model is also called Iterative and Incremental Model.
   In this model, each module is divided into sub-modules. After completion of 1 submodule it is released to the customers.
   No need to wait for the whole completion of module for client and customers.
   After completion of one module then another module begins.
   Eg : If there are 100 modules, then it is split into 10 modules.
   After completion of 1 module, it is released to the customers.
   Another module could begin after completion of previous module.
   Advantages : It can be used for larger projects.
   No need to wait for the Client till the completion of whole module.
   Client Interaction is possible if there are frequent changes in Requirement or Design Phase.