Tag: separation-of-concerns


Found 60 results for 'separation-of-concerns'.


1) wpf - Add complex customization to form or create two forms?
2) c# - How to separate the ViewModel from the Model, yet associate them with each other based on the Model?
3) c# - Avoid type checking but preserve separation of concerns
4) design-patterns - Does it break SRP to have concerns of data handling and object mapping inside a single class, as part of the DataMapper pattern?
5) database - Should Data Access Layer mirror my Database Configuration?
6) design - Separate domain entity in small ones
7) c# - Proper design for models
8) design - Email service or simply abstract email out and call from?
9) c# - Is this a good practice or not?
10) architecture - Architecting project into multiple source control repositories
11) architecture - What layer generates commands for dependent services?
12) php - In which layer should I load views on a Clean(ish) architecture?
13) language-agnostic - Is there ever a reason to do all an object's work in a constructor?
14) php - How to explain to my manager the importance of separation of concerns?
15) design-patterns - Is there a design pattern that describes the separation of a Form from a Model
16) asp.net-mvc - Why is using named routes for generating outbound URLs a violation of Separation of Concerns?
17) architecture - Separation of concerns SOAP Services
18) javascript - Why Have People Started Deeming it Necessary to Separate JS hooks from CSS hooks in HTML?
19) c# - What kind of abstraction/SoC should I use here?
20) domain-driven-design - Complex fetching of Domain Objects
21) object-oriented - How do you explain Separation of Concerns to others?
22) design - Separating save logic from WinForm to make it reusable
23) design-patterns - When can a design pattern make your software worse?
24) object-oriented-design - Separation of concerns between objects
25) productivity - Third Party web controls and tight coupling
26) object-oriented - Why is SRP using the class construct to contain a responsibility opposed to using any other OOP entity?
27) design - What is meant by, "A user shouldn't decide whether it is an Admin or not. The Privileges or Security system should."
28) object-oriented - Single responsibility: how does this code cause problems?
29) architecture - Put functionality in same executable with command-line flag, or put it in a separate executable?
30) java - What are the steps to grouping related classes into packages
31) business-logic - Do stored procedures violate three-tier separation?
32) c# - Database transaction and separation of concerns
33) php - Separation of concern. Accessor methods and data sanitisation.
34) language-agnostic - Do higher order functions violate the separation of data and code principle?
35) c# - Is it possible to keep logging code completely outside the business logic?
36) design - How does one choose where to place logic which converts data between two formats/representations?
37) design - Class design dilemma: Encapsulation vs Single Responsibility/Separation of Concerns
38) c# - Segregating interfaces/concerns to a tree
39) object-oriented - How do you achieve encapsulation while "separating view and business logic"?
40) design-patterns - Extracting domain logic from the forms to which they are coupled?
41) architecture - Architecturally speaking, does a database abstraction layer, such as Microsoft's Entity Framework, void the need for a separate Data Access Layer?
42) domain-driven-design - Separation of concerns
43) object-oriented - Does Exception Handling Violates "Program to Abstraction"?
44) design - Designing functions with separation of concern in mind
45) design - Did Dijkstra intend for code modularization, when he wrote about separation of concerns?
46) single-responsibility - Separation of concerns: When is it "too much" separation?
47) domain-model - Separate presentation layer from data entities
48) gui - Should a State Machine or Processing Engine be abstracted away from the UI?
49) java - What are the steps to grouping related classes into packages
50) separation-of-concerns - Rx stream resulting in lots of one-off objects