separation of concerns的意思

separation of concerns中文翻譯：

關注分離（separationofconcern的復數）

相似詞語短語

separation of───……的分開；……的分離

separation───n.分離，分開；間隔，距離；[法]分居；缺口

concerns───n.關注；關注點；關注者（concern的復數形式）；v.使關心（concern的三單形式）；涉及；關系到…

separation of powers───分權；三權分立；[法] 分權，權力的分立

enhancement separation───增強分離

raise concerns───引起關注

disqualifying separation───不合格離職

mounting concerns───越來越多的關注

voluntary separation───自愿分居

雙語使用場景

Separation of concerns.───關注的分離。

MVC is all about proper separation of concerns.───MVC最重要的就是合理的分離關注點。

no layering and no separation of concerns.───各種關系之間沒有任何分層和分離。

When you're aiming for separation of concerns, transparency, and flexibility, aspect-oriented programming (AOP) is often the right answer.───如果目的是分離關注點、透明性和靈活性，那么面向方面的編程（AOP）通常就是正確的答案。

The code that handles the UI and the business is all mixed together, without any separation of concerns at all.───處理UI以及業務的代碼全部混在一起，根本沒有任何關系分離。

Each piece of the MVC architecture is well defined and self-contained, which is referred to as the separation of concerns.───MVC體系結構的每一部分都是定義良好和自包含的，這稱為關系分離。

Use the concept of layers to maximize separation of concerns, and to improve reuse and maintainability for your mobile application.───利用層的概念來最大化地分離考慮的因素，并且提高移動應用的可重用性和可維護性。

Introducing Ajax into a Java EE Web application has implications for separation of concerns (and therefore separation of developer roles).───把Ajax引入JavaEEWeb應用程序對于問題的隔離（以及開發人員角色的隔離）是有意義的。

What the MVC-for-the-Web crowd is really trying to achieve is a clear separation of concerns.───MVC-for-the-Web實際上試圖完成的是關注點的明確分離。

英語使用場景

OST and OSML encourage data-driven development of applications and services while promoting a clear separation of concerns between markup and programming logic.

One important design guideline used in the design of components and interfaces in SOA (in fact, in any IT architecture) is separation of concerns [ SoC1, SoC2].

Data access technologies should be amenable to this separation of concerns.

Separation of concerns is fundamental to well-structured code, because it encapsulates responsibilities and dependencies.

This design principle is very similar to agile design principles (separation of concerns, avoid waste etc.) that are often used in software development.

This logic was often interspersed with presentational information, meaning that there was no clear separation of concerns within the architecture, further restricting flexibility.

Keeping the templates for transforming machine-readable entries is good programming practice, as is separation of concerns in general.

MVC's several advantages include separation of concerns and decreased redundant code.