Coding Conventions

Question 1

explains itself without need for external documentation, like flowcharts, UML diagrams, process flow diagrams, etc.

Answer 1

Self documenting

Question 2

Coding conventions target:

Answer 2

How you write statements in the language, organize them into modules, format them in the source files

Question 3

reuse as much legacy code as possible

Answer 3

true

Question 4

The project needs to progress as fast as possible

Answer 4

true

Question 5

You have a team working on a project that will extend over a moderately long period of time. Over the course of the project, people will come and go.

Answer 5

Motivation

Question 6

Style of Working

Answer 6

• read many modules, and edit many.
• They will “factor out” duplicate code
• few modules will be able to be said to have an author

Question 7

It’s easier to integrate modules that use a common consistent naming
standard

Answer 7

true

Question 8

Comments, 3 types:

Answer 8

– File headers
– Function headers
– Explanations of variables and statements

Question 9

Statements:

Answer 9

– Organization: files, “modules,” nesting
– Format: spacing and alignment

Question 10

Divide each module into a public part and a private part.

Answer 10

• public part goes into an include (.h) file
  – private part goes into a source (.c) file

Question 11

Comments provide _____ information about the program

Answer 11

meta

Question 12

Commenting _______ is an especially good thing to do.

Answer 12

interfaces

Question 13

don’t need to be commented heavily if their interfaces are well documented.

Answer 13

Implementations

Question 14

Use simple, descriptive variable names.

Answer 14

true

Question 15

how many levels is enough for major nesting?

Answer 15

3 levels