Project 2 - V&V SW Analysis II

                        ********************  RAJU.MANGALWADE   **************

1. Static Code Review Analysis: 

The static code verification/static code analysis involves finding fatal run-time errors without executing the code. It is done on the software which is already compiled. It is independent of the compiler. The initial process of software testing for finding out the run-time issues includes a manual code review. But for Larger systems, it is laborious. It needs experienced engineers to review it. The absence of runtime errors is a more complex operation that is not manageable by code review.

Bugs identified in static code: 

Out of Bound Array Index(OBAI), Division by Zero (ZDV), Uninitialised data variables(NIV/NIVL), Illegal Dereferenced pointers(IDP),Integer Overflows(OVFL)

 Testrain.c

i) Open Testrain.c in the LDRA tool. Goto Source and click "Single file". Then click "Testrain.c file".

ii)Create a New sequence, give a proper name and select "Code Coverage".

iii)Run static analysis from Source  in the menu

iv)Then take the test manager report from the Results option after static analysis is done.

v)In the LDRA report: One can see code review, quality review and TBrun Unit/Module Test is present. We can know it is a PASS or FAIL.

2. Integration Testing

It is analysing multiple files or single files and analysing dependencies between the subfunctions in the file. It is also the testing of combining building blocks implemented in any of the software languages. Approaches in Integration Testing: Top-Down Testing and Bottom-up Testing are done.

Top-Down Testing: It is the process of breaking down the complex system into small sections.

Bottom-Up Testing: Basic blocks from greater components that give rise to complex systems.

Cashregister.c

i) Select Source and Multiple files. After selecting multiple files, a window appears asking to select/create a set. We have to enter a name and press create.

ii) Then LDRA with question appears, in that select system. The system is selected to take the dependencies between the subfunctions.

iii) A window showing add option appears, click on it, then ok pressed

iv) Cashregister.c file appears, select it and add it

v) We have to configure then only Testbed is run.

vi) Select configure, click static options from analysis configuration options

vii) Click on Find/create from the Static Analysis options.

viii) Click on Select with a default file name

ix) Run the static analysis to check any bugs in the code without actually building and running.

x) Select Test Manager Report from Results and LDRA tool with code review and quality review appearing having percentages of completion.