Which is an example of a design principle, and what is its purpose?

Which is an example of a design principle, and what is its purpose?

• A. A company policy about user login times.
• B. A guiding rule such as Modularity to enable substitution and scalability.
• C. A regulatory compliance requirement.
• D. A specific technology stack requirement.

Answer: (B)

Design principles are high-level guidelines that shape how a system is organized and how its parts interact over time, independent of specific technologies. Modularity fits this idea as a guiding rule: it encourages building the system as distinct modules with clear interfaces. This structure makes it possible to substitute one module for another without impacting the rest, and to scale the system by adding or replacing modules as needs grow. The purpose is to make the architecture more maintainable, adaptable, and extensible, so changes can be made safely and efficiently. Other options describe concrete policies or constraints rather than structural guidance. A policy about user login times is about operational rules for users, not about how the system should be built. A regulatory compliance requirement is a rule you must follow, not a design approach. A specific technology stack requirement is a concrete implementation choice, not a principle that guides the overall design.

Design principles are high-level guidelines that shape how a system is organized and how its parts interact over time, independent of specific technologies. Modularity fits this idea as a guiding rule: it encourages building the system as distinct modules with clear interfaces. This structure makes it possible to substitute one module for another without impacting the rest, and to scale the system by adding or replacing modules as needs grow. The purpose is to make the architecture more maintainable, adaptable, and extensible, so changes can be made safely and efficiently.

Other options describe concrete policies or constraints rather than structural guidance. A policy about user login times is about operational rules for users, not about how the system should be built. A regulatory compliance requirement is a rule you must follow, not a design approach. A specific technology stack requirement is a concrete implementation choice, not a principle that guides the overall design.