Start learning →

Changing one module should ideally not force changes in others; this is achieved by keeping:

Acoupling low
Bboth coupling and cohesion high
Ccohesion low
Dthe SRS short
Answer & Solution
Correct answer: A. coupling low
Keeping coupling low localises the impact of changes, so editing one module rarely affects others.
Practise this question with Quill — B.Tech CSE →

Keep practising Software Engineering

Browse all Software Engineering questions for B.Tech CSE, or explore more Computer Science topics.

Start a Software Engineering lesson →
Related questions
Cyclomatic complexity is a metric that measures:A UML use-case diagram primarily captures:In the V-model, each development phase is associated with a corresponding:A good modular software design aims for:Testing the interactions between combined modules is called:The Agile approach to software development emphasises:White-box testing focuses on:Black-box testing focuses on: