QA is a process within software development in which software is verified for correctness, quality, and performance. Software testing is used to guarantee that probable business systems and product features performsuitably as expected. The strategies planned or implemented tor QA caller QA Strategies.
The benefits of QA will save time and money of organization by reducing software development and maintenance costs. QA ensures that a feature is working as expected and users are not encountering bugs.
If any new feature has to implemented, so the development time on new features is reduced by specifying a set of test cases that the new feature must match to be considered complete and deliverable. This gives developers a fixed target to work towards enabling more accurate timeline estimates and lowering the occurrence of new bug. Once the Strategy is in place the overall maintenance costs are lowered. QA Strategy have pillars as Requirement Analysis and Test Planning.Benefits:
Requirements analysis is the process of shaping user prospects for a novel or adapted product. These features must be quantifiable, relevant and detailed. In software development, such requirements are often called functional specifications. Requirements analysis is ansignificant aspect of project management.
Requirement Analysis is process of defining user expectations for a new software being built or modified. It encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholdersscrutinizing, recording, authenticating and handling software or system requirements.Why we need Requirement Analysis:
Requirement analysis involves the task that determines the initial need of the software, which mainly includes complaints and requirements of various clients. It is a major key in the development cycle of software and is the starting step of the project.Activities:
Identify customer's needs.
Evaluate system for feasibility.
Perform economic and technical analysis.
Establish schedule and constraints.
Create system definitions.
Test planning is concerned with the application of test strategy for each test level or all the levels of testing. It is a technical planning which details a systematic approach to testing a specific system such as a device or software. Ideally there is a test plan that spans all levels of testing and ensures that sufficient amount of testing occurs for a particular test level. In addition to the master test plan that spans across all level of testing test planning also befalls at each test level.
The test plan comprises a thorough understanding of the workflow and functions of the system and documents how each of those will be tested in order to locate if the system works according to its design, to detect bugs, and to regulate its real limitations. It is most important activity to ensure that there is initially a list of tasks and milestones in plan to track the progress of the project.