Contents
What is the main idea behind separation of concern?
At its essence, Separation of concerns is about order. The overall goal of separation of concerns is to establish a well-organized system where each part fulfills a meaningful and intuitive role while maximizing its ability to adapt to change.
What are the three main principles of object oriented programming?
Use of encapsulation alone (i.e., defining and using classes, but making no use of either inheritance or polymorphism) is often called object-based programming. To be truly practicing object-oriented programming, you must be using all three of the “pillars”, i.e., encapsulation, inheritance, and polymorphism.
Why do we separate software into different layers?
The same is true of complex enterprise applications. Separating the various concerns into different systems or layers makes code easier to navigate and maintain. When changes are made, the impacts and regressions on other areas are minimized, and a healthier and more adaptable program evolves.
What does separation of concerns mean in programming?
Separation of concerns results in more degrees of freedom for some aspect of the program’s design, deployment, or usage. Common among these is increased freedom for simplification and maintenance of code.
Why are modules a form of separation of concerns?
Modules can also expose different versions of an interface, which increases the freedom to upgrade a complex system in piecemeal fashion without interim loss of functionality. Separation of concerns is a form of abstraction.
How does a multi-dimensional separation of concerns work?
Multi-dimensional Separation of Concerns allows the analysis and composition of concerns to be manipulated as a multi-dimensional “matrix” in which each concern provides a dimension in which different points of choice are enumerated, with the cells of the matrix occupied by the appropriate software artifacts.