Treffer: Patterns in software design.

In the past 30 years I have worked in various agencies conducting research and developing software in application fields dealing with radiative transfer modelling in the ocean, atmosphere, and vegetation; meteorology; atmospheric chemistry; marine oil spill and fish stock monitoring; cancer risk assessment; satellite sensor design and extraction and assessment of environmental information from remote sensing data. The software Fragstats (McGarigal and Marks [5]), seen by many as a game changer for the advance and acceptance of landscape ecology, is a prime example for the importance of software as a reference, communication and assessment tool. The same process occurred in the case of my software, where additional image analysis modules for different purposes were developed and grouped into thematic application fields of landscape ecology, such as pattern, fragmentation, connectivity, distance, and cost/restoration. This question is directly related to the cost/effort of development, choice of programming language, the potential re-use of already existing modules, and the development of software installer packages and software maintenance. [Extracted from the article]

Copyright of Landscape Ecology is the property of Springer Nature and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)