1) Explain in great detail the meaning of public, protected, and private modifiers with respect to inheritance with examples. Use our Object Oriented Design (OOD) notation to implement examples as opposed to code if desired.

2) Discuss developing a test plan in detail. What should be used to develop a plan. What and how should testing be accomplished. Include the specification, design, code and other pertinent information in your response.

3) Discuss decision tables and finite state automata in detail stating their advantages and disadvantages. Be sure to include how they can be used to minimize the cost of making software changes due to a changing user environment.

4) Discuss prototyping in great detail. You should include the circumstances under which prototyping is most likely to be the best software development paradigm. Include the circumstances under which prototyping is not particularly useful and what should be used. Compare and contrast prototyping, the water fall model, and the spiral model in detail. Explain in detail the circumstances under which prototyping is most likely to be the best software development paradigm. Conversely, when is it not needed and what should be used?

5) Circle the letter preceding all correct statements pertaining to major goals of OOD and OOP.

A) Minimize the expense in time, cost, and other resource requirements during original implementation.

B) Maximize re-use of the software components.

C) Minimize the cost maintenance, fixing bugs.

D) Minimize the cost of modification, responding to changes in the environment.

E) Maximize the efficiency of resource utilization.

F) Maximize the ability to optimize software with respect to the hardware/software environment while minimizing the cost of the change.

G) Allow for extension of the language by a user adding abstract data type (ADTs).

6) Circle the letter preceding all correct statements pertaining to OOD and OOP.

A) Modify the Body Only: If you modify only the body then in principle it should be possible to recompile the body and link it to the specification. This would automatically update all users without further effort.

B) Modify the Specification: The specification, body, and all user code must be recompiled and linked when data structures or functionality is added to the specification. It will not be necessary to modify any user code however unless the user code wishes to take advantage of new functionality defined in the interface. If functionality is removed from the specification, or the interface for invoking a method is modified, then the user code that exercises these features will also have to be modified.

C) Modification of User Code: Modification of user code should not affect the way objects are utilized by the rest of the system.

D) OOP Modification: Any time the specification or body of a class is modified, the specification, body, and all code utilizing the class must be recompiled and linked to prevent errors.

Briefly explain each of the following with respect to OO specification, design, and programming.