Home_intro

intro story DELWAQ

DELWAQ

DELWAQ is the engine of the D-Water Quality and D-Ecology programmes of the Delft3D suite. It is based on a rich library from which relevant substances and processes can be selected to quickly put water and sediment quality models together.

The processes library covers many aspects of water quality and ecology, from basic tracers, dissolved oxygen, nutrients, organic matter, inorganic suspended matter, heavy metals, bacteria and organic micro-pollutants, to complex algae and macrophyte dynamics. High performance solvers enable the simulation of long periods, often required to capture the full cycles of the processes being modelled.

The finite volume approach underlying DELWAQ allows it to be coupled to both the structured grid hydrodynamics of the current Delft3D-FLOW engine and the upcoming D-Flow Flexible Mesh engine (1D-2D-3D) of the Delft3D Flexible Mesh Suite (or even other models such as TELEMAC).

'DELWAQ in open source' is our invitation to all leading experts to collaborate in further development and research in the field of water quality, ecology and morphology using Delft3D. Feel free to post your DELWAQ related questions or comments in this dedicated forum space. If you are new to DELWAQ, the tutorial (in the user manual) is a good place to start. A list of DELWAQ related publications is available here.

** PLEASE TAG YOUR POST! **

 

 

Sub groups
D-Flow Flexible Mesh
DELWAQ

Cohesive sediments & muddy systems

 


Message Boards

Specification by example is also called as living documentation

LT
Leanpitch Tech, modified 1 Month ago.

Specification by example is also called as living documentation

Jedi Master Posts: 380 Join Date: 10/1/20 Recent Posts
Specification by example is also called as living documentationBehavior driven development aka BDD is an efficient way to test the functionality of the product without worrying much on the user interface. Automation is done for the specific feature and its Behavior rather than the complete UI/functional flow. Automating everything up front helps in saving time for other types of testing like exploratory testing and non-functional testing. BDD helps you eliminating more documents related to testing, even test cases. Specification by example is also called as living documentation because the examples and automation code are glued together. Updating the examples with behavioural changes needs changes in automation code as well. So, at any point of time, the key examples and the automation code will always be in sync and hence living documentation.There are variety of testing types available and there is more non-functional testing to be done. As much as quality should be ingrained on to the product, all these testing needs to be done in a very limited timeframe. The Agile test quadrant explains what type of testing is technical, functional, helps team, helps business, when to do what, which type of testing should be automated, which type of testing should be done manually, which type of testing uses tools etc.  Product Prototyping