Which fundamental software design principle advocates that a software module should have high internal operational focus while maintaining minimal direct dependencies on external modules?
Option B is correct. Good software design aims for High Cohesion (modules have strong internal focus) and Low Coupling (minimal interdependence between distinct modules).
Which type of cohesion occurs when all elements within a software module perform tasks that contribute to executing a single, well-defined function?
Option A is correct. Functional Cohesion is the strongest and most desirable form of cohesion, where all elements within a module cooperate to perform a single essential function.
Which type of cohesion exists when module tasks are grouped purely because they are executed at the same point during program execution (e.g., system initialization)?
Option B is correct. Temporal Cohesion occurs when elements of a module are grouped together because they must be processed during the same time period (e.g., initializing global variables or loading config files).
Which type of cohesion is considered the weakest and least desirable, occurring when elements are grouped together randomly without any meaningful functional or logical relationship?
Option C is correct. Coincidental Cohesion is the worst form of cohesion, where tasks are bundled together arbitrarily without any logical or functional relationship.
In software coupling hierarchy, which form of coupling is the most desirable (weakest coupling), occurring when modules communicate solely by passing scalar, primitive data items as parameters?
Option A is correct. Data Coupling is the lowest and cleanest form of coupling, where modules interact by passing simple primitive data arguments without exposing internal structures.