Why separation of concerns

If your architecture is agnostic to technical or business logic detail then changes to implementation are less likely to require new architectural features. For example, if your main domain logic is database agnostic then supporting a new database should be as easy as swapping in a new implementation of the persistence layer. Improve this answer. I love that you made the answer firmly anchored in the financial reality. Managers have no excuse to be sloppy and ignore this fundamental concept.

RationalGeek RationalGeek 10k 7 7 gold badges 36 36 silver badges 55 55 bronze badges. Abimaran Kugathasan Abimaran Kugathasan 1, 1 1 gold badge 13 13 silver badges 23 23 bronze badges. That's one responsibility. This type of vigilance "in the wild" is highly suspect because JSX involves the full JavaScript dialect. The Team Perspective NO, if both YES, if either Everything is in the same file, causing problems for version control or productive use of modern editors.

Daniel Daniel 6 6 bronze badges. I am just pointing out that separating out concerns can take different approaches depending on the context.

This is closer to a real world situation in terns of software engineering and I am highlighting that there are different approaches you can take when working on html pages that may at first seem contradictory.

The Overflow Blog. Podcast Explaining the semiconductor shortage, and how it might end. Does ES6 make JavaScript frameworks obsolete? Featured on Meta. Now live: A fully responsive profile. Linked 1. Related 7. Hot Network Questions. Question feed. What is Separation of Concerns 1. The ability to identify, encapsulate and manipulate those s of tware artifacts which are relevant to a specific concept, task or purpose Learn more in: Modular and Systematic Interface Design for Rich Internet Applications.

The process of breaking a s of tware system into distinct pieces such that the overlaps between those pieces are as little as possible, in order to make it easier to understand, to design, to develop, to maintain, etc.

To separate the functionality modules from the target aspects, which consists of these steps, 1 identifying and specifying basic functionality components in the system; 2 specifying requirements of the target aspects; and 3 defining the crosscutting section join points of the functionality components and target aspects. A process of separating a computer program into distinct features that overlap in functionality as little as possible. Find more terms and definitions using our Dictionary Search.

Separation of Concerns appears in:. Handbook of Research on Web 2. Search inside this book for more research materials. Recommend to a Librarian Recommend to a Colleague. Looking for research materials? We always want low coupling. Cohesion : The measure of how strongly-related is the set of functions performed by a module.

We always want high cohesion. All methodologies try to reduce coupling and increase cohesion. Information Hiding reduces coupling by isolating the details of the implementation of state.

ADTs reduce coupling by defining clear and abstract interfaces. An ADT that specifies in a single definition the set of functions that can be executed on a type is certainly more cohesive than a global data structure that is modified by external functions. OOP adds another step in the reduction of coupling with the enforcement of encapsulation and the introduction of dynamic binding and polymorphism.

Inheritance allows us to increase cohesion by defining hierarchies based on generalization and specialization, in which we can separate the functionality that belongs to the superclass from its subclasses. AOP provides a solution for the problem of cross-cutting concerns, so that both the aspects and the affected methods may become more cohesive.

There are many benefits that software developers expect to obtain when making a system more modular, reducing coupling and increasing cohesion:. Maintainability : A measure of how easy it is to maintain the system. As a consequence of low coupling, there is a reduced probability that a change in one module will be propagated to other modules.

As a consequence of high cohesion, there is an increased probability that a change in the system requirements will affect only a small number of modules. Extensibility : A measure of how easily the system can be extended with new functionality. As a consequence of low coupling, it should be easier to introduce new modules, for example a new implementation for an existing interface.

As a consequence of high cohesion, it should be easier to implement new modules without being concerned with aspects that are not directly related to their functionality. Reusability : A measure of how easy it is to reuse a module in a different system. As a consequence of low coupling, it should be easier to reuse a module that was implemented in the past for a previous system, because that module should be less dependent on the rest of the system.

Accordingly, it should be easier to reuse the modules of the current system in new future systems. As a consequence of high cohesion, the functionality provided by a module should be well-defined and complete, making it more useful as a reusable component.

As software developers, after we recognize the importance of SoC, we need to apply this principle in at least two ways: Understanding the power of our programming language tools and patterns, and learning how to evaluate and compare different designs in terms of coupling and cohesion.

Tools: For each mechanism in the programming languages we use, we should understand how it can be applied to reduce coupling and increase cohesion. For example: How encapsulation, dynamic binding, polymorphism and generic types can be used to separate concerns?

Similarly, for each Design Pattern , we can analyze how it helps to make a system more modular. Designs: When evaluating and comparing our own design alternatives, it is always useful to think in terms of coupling and cohesion.