5) Cohesion is the degree of interaction within a module. If the operation's code is weakly connected or intertwined it will cause many issues. These issues have to be fixed. Maintenance is how these issues are fixed. Sometimes it is corrective maintenance, other times it will be enhancement. This need for maintenance comes from the interactions not running smoothly. Sometimes the faults are isolated and maintenance is much easier.

6) Coupling has an influence on maintenance. If the couple is tight then it is more prone to faults. That is normally because if one change is made to a module the coupled module might need to be changed as well. If they both are then everything should function correctly. But they are changed during post-maintenance. If the coupling is attended to correctly then it may not have as many effects on maintainability.

9) This can happen but the fault will be found later. The product will function but at a slower rate until the fault manifests. If a change is made to one module then it must be made to the other during post delivery maintenance in order for it to work correctly. That is if it is tightly coupled. If not then it might as well been coupled loosely.

10) Data encapsulation is when each operation has its own entry point and exit point and independent code. It is a example of separation of concerns. The data structure along with the operations to be performed on that data structure. Data encapsulation and development allows us as developers to conceptualize on higher levels. Data encapsulation and maintenance is identifying the aspects of a product likely to change. Also, design the product to minimize the effects of future changes. Abstract data types are data types together with the operations to be performed on instantiations of those data types. Abstract data types support both data abstraction and procedural abstraction. Its unlikely that the abstract data type will be changed when a product is modified. From development and maintenance point of view abstract data types useful tools for producers.

11) Abstraction is stepwise refinement. It is a way that developers can conceptualize the problem at higher levels. First step a high level design is produced. During the first step it is not necessary to know the implementation. Second step is to design lower level components based on the data structure and its operations to be implemented on that data structure. Information hiding is basically ideas for future change to a module. This concept states that a list of likely change to the implementation should be made. Then the information in one module should be hid from another module so change is localized to one module.

13) Dynamic binding is the act of connecting an object to the appropriate method. This is done at run time and not at compile time. This is what makes it dynamic and not static. A method is polymorphic when a it can be applied to objects in different classes. Because of dynamic binding it is not necessary to determine which method to invoke on a specific file. The important part is to send the message at run time and the system will determine the class and invoke the correct method. It is not easy at compilation time to determine the version of a polymorphic method will be invoked at run time. Also polymorphism and dynamic binding can have a negative effect on maintenance.

14) If we use polymorphism without dynamic binding we must determine which method is going to be invoked at run time.

15) If we use dynamic binding without polymorphism then the same method will be applied to objects in different classes.