1. What is a high-level system diagram called?
   • A block diagram
2. What is a detailed hardware diagram called?
   • A schematic or wiring diagram
3. What three diagrams did we use in this chapter to define our software architecture?
   • An application flowchart
   • A state diagram
   • A class diagram
4. What is it called when two classes are connected together without the use of the inheritance mechanism?
   • Composition
5. What information should be included in a test case?
   • The test case number.
   • The test case objective (why are we doing the test?)
   • Conditions that need to occur before the test is performed.
   • Input that needs to be applied to the system during testing (push a button).
   • Expected results (what should we see happen?)
   • Who did the testing? (yes, who can we blame if we discover a problem in the future?)
   • When was the test performed?
   • The software version number that the test is to be performed on.
6. How can a developer create a constant in Python?
   • There are no constants in Python so it's the same as defining a variable. A developer just needs to make sure they don't modify the constant value!
7. What line of code should a developer write to learn what addresses have slaves present on the I2C bus?
   • I2C_List = i2c.scan()
8. What can be used to catch an exception and print it out?
   • except Exception as e: print(e)

9. What statement can be written to force the application to exit?
   • sys.exit(0)
10. What type of setup can be used to fully test and validate the drivers created in an application?
    • A test suite or test harness