Good system design characteristics: which option best captures a core, desirable property of a well-engineered information system?
-
AConversion (deployment) as the sole focus
-
BLong discussions without formal artifacts
-
CProper documentation
-
DModular approach
-
ENone of the above
Answer
Correct Answer: Modular approach
Explanation
Introduction / Context:Quality system design emphasizes maintainability, scalability, and clarity. Modularity—decomposing a system into cohesive, loosely-coupled components—is foundational to achieving these outcomes.
Given Data / Assumptions:
- We seek a core design trait, not a process step.
- Choices include documentation and deployment, which are important but not architectural qualities.
Concept / Approach:A modular approach isolates responsibilities, enabling independent development, testing, and scaling. It reduces ripple effects from changes, improves reuse, and clarifies ownership.
Step-by-Step Solution:
Identify which option speaks to architecture rather than administration.Select modular approach as the core design characteristic.Acknowledge that documentation is supportive but not the design's intrinsic structure.Verification / Alternative check:Design reviews rate cohesion/coupling as primary evaluation criteria, both improved by modularity.
Why Other Options Are Wrong:“Conversion” is a deployment phase activity; “long discussions” without artifacts do not ensure quality; documentation is necessary but does not replace modular architecture.
Common Pitfalls:Creating modules that are too granular or too coupled; neglecting clear interfaces and contracts.
Final Answer:Modular approach