PyQdeck LogoPyQdeckSubjectsSyllabusBlog
Back to the 2025 paper

Module 3: Software Design & Metrics

20252m

Which of the following is not a characteristic of good software design?

(i) Low coupling
(ii) High cohesion
(iii) High complexity
(iv) Modularity

Search GoogleAsk AI
Worked SolutionAI Assisted

Answer: (iii) High complexity

Good software design aims to produce a system that is maintainable, understandable, and extensible. Its hallmarks are:

  • (i) Low coupling — modules depend on each other as little as possible (good),
  • (ii) High cohesion — related responsibilities stay together in a module (good),
  • (iv) Modularity — the system is broken into independent, manageable modules (good).

High complexity is the opposite of good design — it makes software hard to understand, test, and maintain, and increases defect rates. Therefore "high complexity" is the one that is not a characteristic of good software design — option (iii).

Similar questions

Software EngineeringWhich combination generally represents desirable modular design? (i) High coupling and low cohesion (ii) Low coupling and high cohesion (iii) High coupling and high cohesion (iv) Low coupling and low cohesion20262mSoftware EngineeringTo achieve a good design, modules should have (i) Weak cohesion Low coupling (ii) Weak cohesion High coupling (iii) Strong cohesion Low coupling (iv) Strong cohesion High coupling20242mSoftware EngineeringTo achieve a good design, modules should have a) Weak cohesion and low coupling b) Weak cohesion and high coupling c) Strong cohesion and low coupling d) Strong cohesion and high coupling20232mSoftware Engineering______ is a measure of the degree of interdependence between modules. (i) Cohesion (ii) Coupling (iii) None of the mentioned (iv) All of the mentioned20212m
PreviousThe main purpose of an SRS (Software Requirements Specification) document is to: (i) Describe coding standards (ii) Provide a user manual (iii) Serve as a contract between client and developer (iv) Define the software test casesNextIn a Data Flow Diagram (DFD), which symbol represents an external entity? (i) Circle (ii) Arrow (iii) Open rectangle (iv) Double line
Official AppAndroid App

PYQDeck for Android

Solve BEU previous-year exam papers anywhere, anytime. Fast search, offline paper viewing, and step-by-step solutions designed specifically for your phone.

Get on Google Play