KUFA UNIVERSITY

Department ofComputer Science

22/04/23

Fundamentals of Software Engineering

Presented ByPresented ByNeamah HassanNeamah Hassan

Presented ByPresented ByNeamah HassanNeamah Hassan

22/04/23

Code reviewCode review

Code review Code review

-Code review is undertaken after the module successfully Code review is undertaken after the module successfully compiles and all the syntax error have been eliminated from compiles and all the syntax error have been eliminated from the module the module

-Code review are cost – effective strategies for eliminating Code review are cost – effective strategies for eliminating coding error and for producing high quality code coding error and for producing high quality code

-Code review directly detect the error Code review directly detect the error

22/04/23

Coding standards and guidelinesCoding standards and guidelines

Coding guidelines Coding guidelines

-Is provides general suggestions regarding the coding Is provides general suggestions regarding the coding stylestyle

-Leave the actual implementation of these guidelines to Leave the actual implementation of these guidelines to the discretion of the individual developers the discretion of the individual developers

22/04/23

Type of code reviewType of code review

1- Code walkthrough 1- Code walkthrough -Is an informal code analysis technique Is an informal code analysis technique

-A few members of the development team are given the code for a A few members of the development team are given the code for a couple days before the walkthrough meeting couple days before the walkthrough meeting

-Each member selects some test cases of code to hand runEach member selects some test cases of code to hand run

- the main objective of Code walkthrough is to discover the logical the main objective of Code walkthrough is to discover the logical error in the code error in the code

-Even though Code walkthrough is an informal analysis technique but Even though Code walkthrough is an informal analysis technique but have several guidelines over the years have several guidelines over the years

22/04/23

some Code walkthroughsome Code walkthrough guidelines guidelines

1- the team that performing Code walkthrough should not be 1- the team that performing Code walkthrough should not be either too big or too small , it should consist between three to either too big or too small , it should consist between three to seven member seven member

2- discussions should focus on discovery of errors and avoid 2- discussions should focus on discovery of errors and avoid how to fix the discovered error how to fix the discovered error

3- mangers should not attend to foster cooperation among the 3- mangers should not attend to foster cooperation among the engineers engineers

22/04/23

ContCont .. ..

2- Code inspection 2- Code inspection

- The aim of Code inspection is to check for the presence of - The aim of Code inspection is to check for the presence of some types of errors that usually creep in to code bcz the some types of errors that usually creep in to code bcz the programmer oversight and to check whether coding standards programmer oversight and to check whether coding standards

Have been adhered to Have been adhered to

- Good s/w companies collect statistics regarding different type - Good s/w companies collect statistics regarding different type of error commonly committed by engineers and identify the of error commonly committed by engineers and identify the types of error most frequently committed , such a list of types of error most frequently committed , such a list of commonly committed errors can be used as a check list during commonly committed errors can be used as a check list during Code inspection to look out for possible errors Code inspection to look out for possible errors

22/04/23

some classical programming error checked during code inspectionsome classical programming error checked during code inspection

22/04/23

1- use uninitialized variable 1- use uninitialized variable

2- non terminating loop 2- non terminating loop

3- incompatible assignments 3- incompatible assignments

4- array indices out of bound 4- array indices out of bound

5- use incorrect logical operators or incorrect precedence 5- use incorrect logical operators or incorrect precedence among operators among operators

6- mismatch between actual and formal parameter in 6- mismatch between actual and formal parameter in procedure calls procedure calls

Next lecture Next lecture

Testing phaseTesting phase

Basic approach of testingBasic approach of testing

Verification and validation Verification and validation

22/04/23