What is the purpose of code review or program inspection?

• a) To improve code quality

• b) To create a clear hierarchy of packages

• c) To manage relationships among software components

• d) To discover and fix errors

What is reviewed and inspected as part of code review activities?

• a) Design

• b) Software product

• c) Documentation

• d) All of the above

What are the objectives of code review?

• a) To improve code quality

• b) To make source code easier to understand

• c) To make software easier to maintain

• d) All of the above

What is the high-level focus of code review?

• a) Code architecture

• b) Specific code

• c) Package/folder structure

• d) Managing relationships among software components

What is the low-level focus of code review?

• a) Code architecture

• b) Specific code

• c) Package/folder structure

• d) Managing relationships among software components

How can the organization of a software project be improved?

• a) Create a clear hierarchy of packages and resources folders

• b) Put relevant classes in the same package

• c) Put relevant resources in the same folder

• d) All of the above

What is coupling between object classes?

• a) The measure of how many other classes rely on the class and vice versa

• b) The depth of inheritance tree

• c) The number of methods per class

• d) The method fan-in/fan-out

What is the recommended size for classes?

• a) Small

• b) Large

• c) Medium

• d) Varies based on requirements

What does depth of inheritance tree measure?

• a) The measure of how many other classes rely on the class and vice versa

• b) The depth of inheritance tree

• c) The number of methods per class

• d) The method fan-in/fan-out

What does the number of methods per class indicate?

• a) The measure of how many other classes rely on the class and vice versa

• b) The depth of inheritance tree

• c) The number of methods per class

• d) The method fan-in/fan-out