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. Event storming - Wikipedia

    en.wikipedia.org/wiki/Event_Storming

    The business process is "stormed out" as a series of domain events which are denoted as orange stickies. It was invented by Alberto Brandolini in the context of domain-driven design (DDD). Event storming can be used as a means for business process modeling and requirements engineering.

  4. 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.

  5. 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 ...

  6. 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.

  7. Data mesh - Wikipedia

    en.wikipedia.org/wiki/Data_mesh

    Data mesh is a sociotechnical approach to building a decentralized data architecture by leveraging a domain-oriented, self-serve design (in a software development perspective), and borrows Eric Evans’ theory of domain-driven design [1] and Manuel Pais’ and Matthew Skelton’s theory of team topologies. [2]

  8. Domain engineering - Wikipedia

    en.wikipedia.org/wiki/Domain_engineering

    Domain engineering is designed to improve the quality of developed software products through reuse of software artifacts. [2] Domain engineering shows that most developed software systems are not new systems but rather variants of other systems within the same field. [3]

  9. Model-driven engineering - Wikipedia

    en.wikipedia.org/wiki/Model-driven_engineering

    Hence, it highlights and aims at abstract representations of the knowledge and activities that govern a particular application domain, rather than the computing (i.e. algorithmic) concepts. MDE is a subfield of a software design approach referred as round-trip engineering. The scope of the MDE is much wider than that of the Model-Driven ...