Design Patterns

Example of the Model View Controller design pattern

The model-view-controller (MVC) design pattern specifies that an application consists of a data model, presentation information, and control information. The pattern requires that each of these be separated into different objects.

Most applications today follow this pattern, many with slight variations. For example, some applications combine the view and the controller into one class because they are tightly coupled. All of the variations strongly encourage the separation of data and its presentation. This not only makes the structure of an application simpler but also enables code reuse. For more information read the page of IBM about Design Patterns.

Next demos to watch

All Dragon1 (Software and EA Method) texts and visualizations on this website are originals and copyrighted material and are intellectual property of Dragon1 BV. This website is the official source for these materials. Copying, modifying, and/or using (parts of) this content in other media, or technology is prohibited, unless prior written consent is obtained. Any person, AI agent, or software reusing (parts) of Dragon1 material must show a clear, visible referral link to this website, dragon1.com.