enow.com Web Search

Search results

  1. Results from the WOW.Com Content Network
  2. Domain-driven design - Wikipedia

    en.wikipedia.org/wiki/Domain-driven_design

    Domain-driven design (DDD) is a major software design approach, [1] focusing on modeling software to match a domain according to input from that domain's experts. [2] DDD is against the idea of having a single unified model; instead it divides a large system into bounded contexts, each of which have their own model.

  3. Data, context and interaction - Wikipedia

    en.wikipedia.org/wiki/Data,_context_and_interaction

    The data design is usually coded up as conventional classes that represent the basic domain structure of the system. These classes are barely smart data, [1] [2] and they explicitly lack the functionality that is peculiar to support of any particular use case. These classes commonly encapsulate the physical storage of the data.

  4. Naked objects - Wikipedia

    en.wikipedia.org/wiki/Naked_objects

    Domain-driven design is the idea that an evolving domain (object) model should be used as a mechanism to help explore requirements rather than vice versa. The fact that a naked object system forces direct correspondence between the user interface and the domain model makes it easier to attempt domain-driven design, and makes the benefits more ...

  5. Specification pattern - Wikipedia

    en.wikipedia.org/wiki/Specification_pattern

    In computer programming, the specification pattern is a particular software design pattern, whereby business rules can be recombined by chaining the business rules together using boolean logic. The pattern is frequently used in the context of domain-driven design.

  6. Multitier architecture - Wikipedia

    en.wikipedia.org/wiki/Multitier_architecture

    The book Domain Driven Design describes some common uses for the above four layers, although its primary focus is the domain layer. [ 11 ] If the application architecture has no explicit distinction between the business layer and the presentation layer (i.e., the presentation layer is considered part of the business layer), then a traditional ...

  7. List of software development philosophies - Wikipedia

    en.wikipedia.org/wiki/List_of_software...

    This is a list of approaches, styles, methodologies, and philosophies in software development and engineering. It also contains programming paradigms, software development methodologies, software development processes, and single practices, principles, and laws.

  8. Data-driven programming - Wikipedia

    en.wikipedia.org/wiki/Data-driven_programming

    While data-driven design does prevent coupling of data and functionality, in some cases, data-driven programming has been argued to lead to bad object-oriented design, especially when dealing with more abstract data. This is because a purely data-driven object or entity is defined by the way it is represented. Any attempt to change the ...

  9. Anemic domain model - Wikipedia

    en.wikipedia.org/wiki/Anemic_domain_model

    The anemic domain model is described as a programming anti-pattern where the domain objects contain little or no business logic like validations, calculations, rules, and so forth. The business logic is thus baked into the architecture of the program itself, making refactoring and maintenance more difficult and time-consuming.