The software development process of Delft-FEWS is fed by several important sources:
developments in the framework of new implementations
new ideas from existing Delft-FEWS users
new features initiated by the Deltares development team
necessary improvements of the base code and refactoring
New ideas are shared among the community and are picked up jointly and where possible Deltares optimises available resources in the community.
The following diagram shows systematically how the developments eventually become part of the newest release (click and show graph below)
Click on one of the elements for more information
The responsibility of the Delft-FEWS Steering Commity is to guard the basic principles of the Delft-FEWS code base. It decides if and how new features will be implemented and determines which resources are needed to do so. All refactoring activities and fundamental changes to the code base also have to be approved by the Steering Commity. In case of complex new features or refactoring activities a design session will be organised to determine the approach.
The Deltares development team -hydrologists, software developers, ICT experts, etc.- generates ideas for improvements or refactoring of the code base of Delft-FEWS. These suggestions are placed on a longlist. Depending on the urgency and the availability of resourcess these will be picked up in the next release of Delft-FEWS.
When an organisation has selected Delft-FEWS as the basis for their operational system this generates ideas for adjusting Delft-FEWS to the end user's needs. When applicable new developments are suggested to meet those ideas and requirements. These new features are developed in close collaboration between the end-users of the system and the Deltares team.
The existing user community - consisting of a wide range of (inter)national organizations and government agencies – contributes to the developments by bringing in their ideas for improvements and enhancements within the Delft-FEWS code base. In a number of cases their Support & Maintenance contract contains a reserved budget to accommodate this or separate projects are defined.
Delft-FEWS is released in two stable versions each year. Working towards these releases several activities take place in a returning cycle. Testing forms a crucial part of this cycle.