Left hand side:As said earlier, lef

Left hand side:

As said earlier, left hand side are the activities from development activities from. Bình thường We feel, what can chúng by testing in the development phase, but this is the beauty of this model demonstrates mà mà testing can be done in all phases of development activities from as well.

Requirement analysis : In this phase the requirements are Collected, analyzed and studied. Here is how the system thực, but is not Important, what the system is supposed to do, is Important. Brain storming sessions / walkthroughs, interviews are done to have the Objectives clear.

Verification Activities : Requirements reviews.
Validation Activities : Creation of UAT ( User Acceptance Test ) Test Cases
Produced Artifacts : Requirements document understanding, UAT Test Cases.
System requirements / High level design : In this phase a high level design of the software is build. The team investigates and studies on how the requirements thể thực. The technical requirements of the Feasibility cũng is studied. The team cũng That Comes up with the modules would be created / dependencies, Hardware / software needs

Verification Activities : Design Remixer
Validation Activities : Creation of System test plan and Cases, Creation of traceability metrics
Artifacts Produced : System Test Cases, Feasibility reports, System test plan, Hardware software requirements, and modules to be created etc.
Architectural design: In this phase, based on the high level design , software architecture is created. The modules, ask for their relationships and dependencies, architectural diagrams, database tables, technology all details are finalized in this phase.

Verification Activities : Design Remixer
Validation Activities : Integration test plan and test Cases.
Produced Artifacts : Design documents, test plan and test Cases Integration, Database table designs etc.
Module design / Low Level Design: In this phase each and every module or the software components are individually kế. Methods, classes, interfaces, data types etc are all finalized in this phase.

Verification Activities : Design Remixer
Validation Activities : Creation and review of unit test Cases.
Artifacts Produced : Unit Test Cases,
Implementation / Code : In this phase, the Actual coding is done.

Verification Activities : Code review, review test Cases
Validation Activities : Creation of functional test Cases.
Produced Artifacts : Test Cases, review checklist.
Right Hand Side:

------------



Right hand side or demonstrates the testing activities from the Validation Phase. We will start from the bottom.

Unit Testing : In this phase all the unit test case, created in the Low level design phase are executed.

* Unit testing is a white box testing technique, where a piece of code invokes a method mà Is Written (or any other piece of code) to test the code snippet is forwarded giving the expected output or not. This testing is Basically Performed by the development team. In case of any anomaly, defects are logged and tracked.

Artifacts Produced : Unit test execution results

Integration Testing : In this phase the integration tests are executed mà Cases Were created in the Architectural design phase. In case of any anomalies, defects are logged and tracked.

* Integration Testing: Integration testing is a technique where the modules are integrated unit Tested Tested and forwarded the modules are integrated rendering the expected results. In simpler words, It validates forwarded the components of the application work together as expected.

Artifacts Produced : Integration test results.

Systems testing : In this phase the system test all Cases, functional and nonfunctional Test Cases Test Cases are executed. In other words, the full fledge thật and testing of the application takes place here. Defects are logged and tracked for the its closure. Progress reporting is am also a major part in this phase. The traceability metrics are updated to check the coverage and Risk mitigated.

Produced Artifacts : Test results, test logs, defect reports, test summary report and updated traceability matrices.

User Acceptance Testing : Acceptance testing is related to the business requirements Basically testing. Here testing is done to validate business requirements are met rằng in the user environment. Compatibility testing and sometimes nonfunctional testing ( Load, stress and volume ) cũng testing done in this phase.

Artifacts Produced : UAT results, Updated Business coverage matrices.