What are common examiner traps in Modular Software Design?

Confusing the definitions of cohesion (internal module focus) and coupling (external module dependencies). Mistaking 'tight coupling' or 'high coupling' as a desirable property for module integration.

Modular Software Design

1 Qs · 2014 · 1 marks · 0.1 marks/paperStandard yield

Take topic test

In GATE CS, Modular Software Design appears as a fundamental conceptual topic testing core principles of software architecture. The questions focus on the foundational tenets of go… Guide

Type

GATE CSE 2014 Set 3Q19MCQ1 markEasyIn the context of modular software design, which one of the following combinations is desirable?

Topic guide

What does GATE test in Modular Software Design?

In GATE CS, Modular Software Design appears as a fundamental conceptual topic testing core principles of software architecture. The questions focus on the foundational tenets of good modularization, specifically the trade-offs and desired levels of module cohesion and coupling.

Core concepts

Cohesion (intra-module functional relatedness)
Coupling (inter-module dependency and interaction)
Modular design goals (High Cohesion and Low Coupling)
Maintainability and ripple effects in software modules

Recurring question patterns

Desirable Modularity Attributes (Cohesion vs Coupling)
rare · MCQ · 1 marks · 2014
Questions that evaluate the fundamental design objective for module design, testing the contrast between internal functional strength (cohesion) and inter-module interdependence (coupling).

Examiner traps in Modular Software Design

Confusing the definitions of cohesion (internal module focus) and coupling (external module dependencies).
Mistaking 'tight coupling' or 'high coupling' as a desirable property for module integration.

How questions are asked

Conceptual property selection MCQ

Paper trends

Appeared as a direct, recall-based 1-mark conceptual question focusing on standard software engineering design best practices.
2014

Difficulty notes

Easy: Direct definition recall identifying that high cohesion and low coupling is the desired combination. Medium: Identifying specific types of coupling (e.g., data, control, content) or cohesion (e.g., functional, coincidental) in brief descriptions. Hard: Analyzing code structures or architectural refactoring snippets to identify changes in coupling and cohesion.