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

    Data objects are instances of classes that might come from domain-driven design, and such classes might use subtyping relationships to organize domain data. Though it reduces to classes in the end, DCI reflects a computational model dominated by object thinking rather than class thinking.

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

  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

    The objective of domain design is to satisfy as many domain requirements as possible while retaining the flexibility offered by the developed feature model. The architecture should be sufficiently flexible to satisfy all of the systems within the domain while rigid enough to provide a solid framework upon which to base the solution.

  9. Talk:Domain-driven design - Wikipedia

    en.wikipedia.org/wiki/Talk:Domain-driven_design

    ng Domain-Driven Design on WikiPedia The WikiPedia article on Domain-Driven Design needs to better reflect the core tennets of DDD. It should als welcome the critique on DDD and bring out various conflicting opinions in the community. Next actions [ ] Add sections "Strategic Design", "Tactical Design", "Ubiquitous Language"