dqmh:documentation:dqmh_better_practices
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| dqmh:documentation:dqmh_better_practices [2023/06/30 04:28] – created joerghampel | dqmh:documentation:dqmh_better_practices [2023/06/30 04:35] (current) – joerghampel | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| - Model the different DQMH Modules to be created for the application and the events in between them before starting to code. This model can be a simple bubble diagram showing the events as arrows in between the bubbles or a more formal model like an UML Sequence diagram. | - Model the different DQMH Modules to be created for the application and the events in between them before starting to code. This model can be a simple bubble diagram showing the events as arrows in between the bubbles or a more formal model like an UML Sequence diagram. | ||
| - Avoid circular dependencies. If the modules are going to be built into different packages or are going to be used by themselves in other packages, do not have Module A calling Requests for Module B and Module B calling Requests for Module A. Instead consider using broadcast events for one of the two communication paths. | - Avoid circular dependencies. If the modules are going to be built into different packages or are going to be used by themselves in other packages, do not have Module A calling Requests for Module B and Module B calling Requests for Module A. Instead consider using broadcast events for one of the two communication paths. | ||
| + | |||
| + | See also: | ||
| + | |||
| + | * https:// | ||
| + | * https:// | ||
| ===== Deciding where to call “Start Module” ===== | ===== Deciding where to call “Start Module” ===== | ||
/home/dqmh/www/wiki/data/attic/dqmh/documentation/dqmh_better_practices.1688113723.txt.gz · Last modified: 2023/06/30 04:28 by joerghampel