chapter 7

Question 1

When does a system have a good design?

Answer 1

Low coupling, high cohesion, well-defined interface.

Question 2

What are some programming guidelines?

Answer 2

1. easy to read code
2. build program from modular blocks
3. not too specific and not too general
4. use comments
5. make dependencies among components visible

Question 3

What are some guidelines for algorithms?

Answer 3

performance (big O)

tradeoff of efficiency.

Question 4

What are data structures used for?

Answer 4

To make the code simpler and keep data organized.

Question 5

What is pseudo code used for?

Answer 5

Revising code and algorithms to prevent patching code.

Question 6

What is necessary for component reuse?

Answer 6

1. component functions well for the task required.
2. less modification than building from scratch.
3. is it well-documented?
4. a record of the component’s test and revision history.

Question 7

What is internal documentation?

Answer 7

1. header block comment
2. good variable names and statement labels
3. general program comments
4. proper formatting
5. document data

Question 8

What is external documentation?

Answer 8

1. describe the program
2. describe the algorithm
3. describe the data

Question 9

What information should be in the header block of a program (internal documentation)?

Answer 9

1. component name
2. author
3. components role in the system
4. date written and revised
5. purpose
6. how it uses data structures, algorithms, and control

Question 10

What is extreme programming?

Answer 10

customers define the features with stories, describe tests and assign priorities.
programmers implement the stories.

Question 11

What is pair programming?

Answer 11

Driver or pilot: controlling computer and writing the code.

Navigator: reviewing the driver’s code and providing feedback.

Question 12

What is whither programming?

Answer 12

documentation is essential in agile-methods.

1. for roadmaps
2. abstraction and system boundaries
3. better communications.