Q1. Software design is:
(A) Process of defining software architecture
(B) Writing code only
(C) Installing hardware
(D) Testing modules
Answer: (A) Process of defining software architecture
Q2. The main goal of software design is:
(A) Develop a blueprint for implementation
(B) Delete old system
(C) Install software
(D) Test hardware
Answer: (A) Develop a blueprint for implementation
Q3. High-level design is also called:
(A) Architectural design
(B) Detailed design
(C) Coding design
(D) User interface design
Answer: (A) Architectural design
Q4. Low-level design focuses on:
(A) Module and component details
(B) Overall system architecture
(C) Deployment only
(D) Budget planning
Answer: (A) Module and component details
Q5. Modular design promotes:
(A) Reusability and maintainability
(B) Hardware efficiency
(C) Faster deployment
(D) UI colors
Answer: (A) Reusability and maintainability
Q6. Cohesion refers to:
(A) Degree to which a module performs a single task
(B) Hardware compatibility
(C) Network speed
(D) User training
Answer: (A) Degree to which a module performs a single task
Q7. Coupling refers to:
(A) Interdependence between modules
(B) Disk space
(C) CPU speed
(D) Deployment strategy
Answer: (A) Interdependence between modules
Q8. Low coupling and high cohesion are desirable because:
(A) System is easier to maintain
(B) System is slower
(C) Hardware cost increases
(D) Network usage rises
Answer: (A) System is easier to maintain
Q9. Interface design focuses on:
(A) Interaction between modules or users
(B) Hardware setup
(C) Coding speed
(D) Database installation
Answer: (A) Interaction between modules or users
Q10. Data design involves:
(A) Structuring data and database design
(B) Coding only
(C) UI design
(D) Deployment
Answer: (A) Structuring data and database design
Q11. Control design defines:
(A) Flow of control among modules
(B) Data storage
(C) Hardware setup
(D) User training
Answer: (A) Flow of control among modules
Q12. Design patterns provide:
(A) Reusable solutions to common problems
(B) Coding errors
(C) Hardware manuals
(D) Deployment scripts
Answer: (A) Reusable solutions to common problems
Q13. Architectural style defines:
(A) Overall structure of software
(B) Coding guidelines
(C) UI colors
(D) Hardware choice
Answer: (A) Overall structure of software
Q14. Layered architecture divides system into:
(A) Layers with specific responsibilities
(B) Random modules
(C) Hardware components
(D) Test cases
Answer: (A) Layers with specific responsibilities
Q15. Client-server architecture separates:
(A) Client and server modules
(B) Coding and testing
(C) UI and database
(D) Hardware and software
Answer: (A) Client and server modules
Q16. MVC stands for:
(A) Model-View-Controller
(B) Module-Version-Code
(C) Management-Validation-Control
(D) Main-View-Coding
Answer: (A) Model-View-Controller
Q17. In MVC, Model represents:
(A) Data and business logic
(B) User interface
(C) Controller
(D) Hardware layer
Answer: (A) Data and business logic
Q18. In MVC, View represents:
(A) User interface
(B) Database
(C) Code modules
(D) Network setup
Answer: (A) User interface
Q19. In MVC, Controller handles:
(A) Interaction between Model and View
(B) Hardware installation
(C) Database backup
(D) Coding errors
Answer: (A) Interaction between Model and View
Q20. Structured design uses:
(A) Data flow diagrams
(B) ER diagrams only
(C) Network diagrams
(D) Hardware layout
Answer: (A) Data flow diagrams
Q21. Object-oriented design focuses on:
(A) Objects and classes
(B) Hardware modules
(C) Coding speed
(D) Deployment process
Answer: (A) Objects and classes
Q22. UML is used for:
(A) Modeling software systems
(B) Writing code
(C) Installing OS
(D) Hardware setup
Answer: (A) Modeling software systems
Q23. Sequence diagrams represent:
(A) Interaction among objects over time
(B) Code structure
(C) UI color
(D) Database schema
Answer: (A) Interaction among objects over time
Q24. Class diagrams represent:
(A) Classes, attributes, and relationships
(B) Hardware setup
(C) Deployment plan
(D) Test cases
Answer: (A) Classes, attributes, and relationships
Q25. Component diagrams show:
(A) Software components and dependencies
(B) Coding errors
(C) User manual
(D) Database content
Answer: (A) Software components and dependencies
Q26. Package diagrams group:
(A) Classes or components
(B) Hardware modules
(C) Code files only
(D) UI pages
Answer: (A) Classes or components
Q27. Deployment diagrams show:
(A) Hardware and software deployment
(B) Code structure
(C) Test cases
(D) Database relations
Answer: (A) Hardware and software deployment
Q28. Activity diagrams represent:
(A) Workflow or process
(B) Hardware setup
(C) Code syntax
(D) Network topology
Answer: (A) Workflow or process
Q29. State diagrams model:
(A) States and transitions of an object
(B) Deployment plan
(C) Coding errors
(D) UI layout
Answer: (A) States and transitions of an object
Q30. Interaction diagrams include:
(A) Sequence and communication diagrams
(B) Deployment diagrams
(C) Hardware setup
(D) Test reports
Answer: (A) Sequence and communication diagrams
Q31. Architectural design is performed after:
(A) Requirement analysis
(B) Coding
(C) Deployment
(D) Maintenance
Answer: (A) Requirement analysis
Q32. Detailed design follows:
(A) Architectural design
(B) Coding
(C) Testing
(D) Deployment
Answer: (A) Architectural design
Q33. Black box design focuses on:
(A) Input-output behavior
(B) Internal code
(C) Hardware installation
(D) UI only
Answer: (A) Input-output behavior
Q34. White box design focuses on:
(A) Internal logic and structure
(B) Output only
(C) Deployment
(D) Testing only
Answer: (A) Internal logic and structure
Q35. Structured design emphasizes:
(A) Function decomposition
(B) Objects
(C) Hardware
(D) Deployment
Answer: (A) Function decomposition
Q36. Object-oriented design emphasizes:
(A) Objects and encapsulation
(B) Function decomposition
(C) Deployment plan
(D) Test scripts
Answer: (A) Objects and encapsulation
Q37. Encapsulation refers to:
(A) Hiding internal details of an object
(B) Hardware integration
(C) UI design
(D) Code duplication
Answer: (A) Hiding internal details of an object
Q38. Inheritance allows:
(A) Reuse of existing class features
(B) Deleting classes
(C) Hardware upgrade
(D) UI redesign
Answer: (A) Reuse of existing class features
Q39. Polymorphism allows:
(A) Same interface with different implementations
(B) Fixed code
(C) Hardware sharing
(D) Single deployment
Answer: (A) Same interface with different implementations
Q40. Abstraction means:
(A) Focusing on essential features
(B) Coding randomly
(C) Installing hardware
(D) Database backup
Answer: (A) Focusing on essential features
Q41. Design review helps:
(A) Identify defects in design
(B) Deploy hardware
(C) Install OS
(D) Write code faster
Answer: (A) Identify defects in design
Q42. Software metrics measure:
(A) Quality of design
(B) Hardware speed
(C) Network bandwidth
(D) Electricity usage
Answer: (A) Quality of design
Q43. Design verification ensures:
(A) Design meets requirements
(B) Hardware is installed
(C) Deployment is ready
(D) Code compiles
Answer: (A) Design meets requirements
Q44. Design validation ensures:
(A) Design will satisfy user needs
(B) Code runs correctly
(C) Hardware is compatible
(D) Network is fast
Answer: (A) Design will satisfy user needs
Q45. Modular design improves:
(A) Maintainability
(B) Hardware cost
(C) UI color
(D) Disk space
Answer: (A) Maintainability
Q46. Data abstraction helps in:
(A) Hiding unnecessary details
(B) Coding randomly
(C) Hardware installation
(D) Deployment speed
Answer: (A) Hiding unnecessary details
Q47. Component-based design promotes:
(A) Reuse of software components
(B) Hardware reuse
(C) Faster deployment
(D) Network efficiency
Answer: (A) Reuse of software components
Q48. Coupling should be:
(A) Low
(B) High
(C) Random
(D) Ignored
Answer: (A) Low
Q49. Cohesion should be:
(A) High
(B) Low
(C) Random
(D) Ignored
Answer: (A) High
Q50. Interface specifications help in:
(A) Module communication
(B) Hardware installation
(C) UI color
(D) Coding errors
Answer: (A) Module communicationQ51. Design constraints may include:
(A) Hardware, software, and operational limitations
(B) Coding style only
(C) UI color only
(D) Test cases only
Answer: (A) Hardware, software, and operational limitations
Q52. Architectural views provide:
(A) Different perspectives of system design
(B) Coding shortcuts
(C) Hardware setup
(D) Test scripts
Answer: (A) Different perspectives of system design
Q53. Layered architecture improves:
(A) Maintainability and separation of concerns
(B) Coding speed
(C) Hardware efficiency
(D) UI attractiveness
Answer: (A) Maintainability and separation of concerns
Q54. Pipe-and-filter architecture is suitable for:
(A) Data processing applications
(B) Hardware control
(C) UI design
(D) Coding only
Answer: (A) Data processing applications
Q55. Repository architecture centralizes:
(A) Data storage
(B) Code modules
(C) UI components
(D) Hardware devices
Answer: (A) Data storage
Q56. Event-driven architecture responds to:
(A) Events or messages
(B) Code errors
(C) Hardware signals
(D) Network failures
Answer: (A) Events or messages
Q57. Client-server design separates:
(A) Service providers and consumers
(B) Coding and testing
(C) UI and deployment
(D) Hardware and software
Answer: (A) Service providers and consumers
Q58. Peer-to-peer architecture allows:
(A) Equal nodes to communicate
(B) Central server only
(C) Hardware sharing
(D) Testing only
Answer: (A) Equal nodes to communicate
Q59. Microservices architecture emphasizes:
(A) Small, independent services
(B) Monolithic system
(C) Hardware control
(D) Single module
Answer: (A) Small, independent services
Q60. Monolithic architecture features:
(A) Single large codebase
(B) Independent services
(C) Modular components only
(D) Client-server only
Answer: (A) Single large codebase
Q61. Interface design specifies:
(A) Methods for modules to communicate
(B) Coding standards
(C) Hardware configuration
(D) Deployment scripts
Answer: (A) Methods for modules to communicate
Q62. Data design defines:
(A) Data structures and relationships
(B) UI colors
(C) Coding shortcuts
(D) Hardware setup
Answer: (A) Data structures and relationships
Q63. Control design defines:
(A) Module interactions and flow of control
(B) Data storage
(C) Network speed
(D) UI layout
Answer: (A) Module interactions and flow of control
Q64. Design patterns improve:
(A) Reusability and maintainability
(B) Coding errors
(C) Hardware usage
(D) Deployment speed
Answer: (A) Reusability and maintainability
Q65. Singleton pattern ensures:
(A) One instance of a class
(B) Multiple instances
(C) Hardware efficiency
(D) UI color
Answer: (A) One instance of a class
Q66. Factory pattern provides:
(A) Object creation mechanism
(B) Database schema
(C) Coding shortcuts
(D) UI layout
Answer: (A) Object creation mechanism
Q67. Observer pattern supports:
(A) One-to-many dependency among objects
(B) Single module
(C) Hardware setup
(D) Deployment plan
Answer: (A) One-to-many dependency among objects
Q68. Adapter pattern allows:
(A) Incompatible interfaces to work together
(B) Hardware sharing
(C) Network optimization
(D) UI redesign
Answer: (A) Incompatible interfaces to work together
Q69. MVC pattern separates:
(A) Model, View, Controller
(B) Coding, Testing, Deployment
(C) Hardware, Software, Network
(D) UI only
Answer: (A) Model, View, Controller
Q70. Layered pattern is used to:
(A) Separate concerns into layers
(B) Merge modules
(C) Install hardware
(D) Code faster
Answer: (A) Separate concerns into layers
Q71. Component diagrams show:
(A) Components and their relationships
(B) Coding errors
(C) UI layout
(D) Hardware connections
Answer: (A) Components and their relationships
Q72. Package diagrams group:
(A) Related classes or components
(B) Hardware devices
(C) Deployment scripts
(D) Test cases
Answer: (A) Related classes or components
Q73. Deployment diagrams illustrate:
(A) Physical deployment of software on hardware
(B) Data flow
(C) Code structure
(D) UI layout
Answer: (A) Physical deployment of software on hardware
Q74. Activity diagrams represent:
(A) Workflow of activities
(B) Code modules
(C) Hardware setup
(D) UI screens
Answer: (A) Workflow of activities
Q75. State diagrams model:
(A) Object states and transitions
(B) Hardware installation
(C) Deployment plan
(D) Coding style
Answer: (A) Object states and transitions
Q76. Sequence diagrams show:
(A) Interaction over time
(B) Deployment only
(C) Hardware connections
(D) Coding shortcuts
Answer: (A) Interaction over time
Q77. Communication diagrams emphasize:
(A) Object interactions
(B) UI layout
(C) Database only
(D) Coding speed
Answer: (A) Object interactions
Q78. Software design review ensures:
(A) Design correctness and quality
(B) Hardware installation
(C) UI color standards
(D) Coding shortcuts
Answer: (A) Design correctness and quality
Q79. Design documentation includes:
(A) Architectural and detailed design
(B) Coding only
(C) Hardware manuals
(D) Deployment scripts
Answer: (A) Architectural and detailed design
Q80. Design verification answers:
(A) Are we designing the system right?
(B) Are we designing the right system?
(C) Is hardware ready?
(D) Is network fast?
Answer: (A) Are we designing the system right?
Q81. Design validation answers:
(A) Are we designing the right system?
(B) Is coding correct?
(C) Hardware installed?
(D) Deployment ready?
Answer: (A) Are we designing the right system?
Q82. Interface specification defines:
(A) Inputs, outputs, and services of a module
(B) Coding standards
(C) Hardware layout
(D) UI layout
Answer: (A) Inputs, outputs, and services of a module
Q83. Design metrics measure:
(A) Quality attributes like cohesion and coupling
(B) Hardware speed
(C) Network bandwidth
(D) Disk space
Answer: (A) Quality attributes like cohesion and coupling
Q84. Modular design helps in:
(A) Reuse and maintainability
(B) Hardware deployment
(C) UI color scheme
(D) Faster installation
Answer: (A) Reuse and maintainability
Q85. High cohesion in modules leads to:
(A) Easier maintenance
(B) Complex design
(C) Hardware dependency
(D) Random errors
Answer: (A) Easier maintenance
Q86. Low coupling leads to:
(A) Independent modules
(B) Increased errors
(C) Hardware sharing
(D) Deployment failure
Answer: (A) Independent modules
Q87. Data abstraction in design hides:
(A) Unnecessary implementation details
(B) Coding shortcuts
(C) UI elements
(D) Hardware
Answer: (A) Unnecessary implementation details
Q88. Encapsulation improves:
(A) Module independence and security
(B) Hardware speed
(C) UI layout
(D) Network performance
Answer: (A) Module independence and security
Q89. Reusable components reduce:
(A) Development time and cost
(B) Hardware usage
(C) UI redesign
(D) Network load
Answer: (A) Development time and cost
Q90. Design patterns promote:
(A) Standardized solutions
(B) Random coding
(C) Hardware integration
(D) Deployment speed
Answer: (A) Standardized solutions
Q91. Singleton ensures:
(A) Only one instance of a class
(B) Multiple instances
(C) Hardware sharing
(D) Database schema
Answer: (A) Only one instance of a class
Q92. Observer pattern is used for:
(A) Event notification to multiple objects
(B) UI only
(C) Database only
(D) Coding shortcuts
Answer: (A) Event notification to multiple objects
Q93. Factory pattern helps in:
(A) Object creation without specifying exact class
(B) Database design
(C) UI layout
(D) Hardware deployment
Answer: (A) Object creation without specifying exact class
Q94. Adapter pattern allows:
(A) Incompatible interfaces to work together
(B) Coding shortcuts
(C) Hardware sharing
(D) UI redesign
Answer: (A) Incompatible interfaces to work together
Q95. Layered design separates:
(A) Concerns into layers
(B) Hardware devices
(C) UI screens only
(D) Coding files only
Answer: (A) Concerns into layers
Q96. Microservices architecture promotes:
(A) Small, independent services
(B) Monolithic design
(C) Single module
(D) Hardware sharing
Answer: (A) Small, independent services
Q97. Monolithic design is:
(A) Single large codebase
(B) Modular services
(C) Distributed system
(D) Hardware-dependent
Answer: (A) Single large codebase
Q98. Client-server design separates:
(A) Service providers and consumers
(B) UI only
(C) Coding only
(D) Database only
Answer: (A) Service providers and consumers
Q99. Peer-to-peer design allows:
(A) Equal nodes communication
(B) Central server only
(C) Monolithic system
(D) Hardware sharing
Answer: (A) Equal nodes communication
Q100. The ultimate goal of software design is:
(A) Create a blueprint for high-quality, maintainable software
(B) Install hardware
(C) Write code only
(D) Deploy network
Answer: (A) Create a blueprint for high-quality, maintainable software