Project 2 - V&V SW Analysis II

Static Code Review Analysis :

Step1: Click on Select file option in the Source menu. If asked for testbed analysis click YES.

step2: Click on RUN STATIC ANALYSIS in the Source option in the menu bar.

Step 4: Click on the test manager report under results option in the menu bar.

Step 4: Compare the results for the necessary parameters and terminology.

First window is the Code review

second window is the quality review.

Third window is the test verification data.

Fourth view is the TBrun Unit/Module Test.

Integration testing by including all the .C files available in the folder location

Integration testing:

Upon completion of unit testing, the units or modules are to be integrated which gives raise to integration testing. The purpose of integration testing is to verify the functional, performance, and reliability between the modules that are integrated.

Integration Strategies:

• Big-Bang Integration

• Top Down Integration

• Bottom Up Integration

• Hybrid Integration

Step 1: Click on Multiple files option in the source menu.

Step 2: The select/create/delete dialogue box appears. Type the name of the group/system.

Note that here if the file dependency in each other functions needs to be checked then the System option is needed to be selected. Whereas if the dependancy needs to be checked , then the group option is needed to be selected.

Click on "create" . The System is created with the entered name.

As told before we need to select which type of integration testing is needed to be performed which is as shown below.

Click on OK.

Step 4: Click on NO option when the screen asks to ren the testbed analysis. It is chosen NO because we need to change the configurations otherwise it is chosen as YES always.

Step 5: In the Configure menu choose Analysis Configuration Options. From that choose Static options...

Step 6: Click on Run Static Analysis in the Source option in the menu bar.

Step 7: To view the report click on results>> view test case report.