Difference between revisions of "Need of flexibilization of analytical tools - no overdesigned tool that provides too much features for the use"
From COST Action FP0804: FORSYS
SeanGordon (Talk | contribs) m (SeanGordon moved page Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use to [[Need of flexibilization of analytical tools - no overdesigned tool that provides too much features for the u...) |
SeanGordon (Talk | contribs) (Forsys_add_wg_subthemes.py) |
||
| Line 2: | Line 2: | ||
|ID=32 | |ID=32 | ||
|Has statement=Need flexible analytical tools - no "overdesigned" tool that provides too much features for the use | |Has statement=Need flexible analytical tools - no "overdesigned" tool that provides too much features for the use | ||
| + | |Has domain=Models and methods, User interface and outputs, User interface and outputs, User interface and outputs, User interface and outputs | ||
| + | |Has related case=Germany-Using GISCAME to test alternative land-use scenarios under climate change in the Upper Elbe Valley | ||
| + | |Has actor perspective=Developer/Architect | ||
| + | |Has working group theme=Dss development process, Models & techniques | ||
| + | |Has DSS development=Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use.Description of DSS development | ||
| + | |Has decision support techniques=Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use.Decision support techniques | ||
| + | |Has knowledge management processes=Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use.Knowledge management process | ||
| + | |Has support for social participation=Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use.Support of social participation | ||
| + | |Has researcher role= | ||
| + | |Has DSS development stage=Specification, Use | ||
|Has evidence=It was decided to develop a highly detailed system in order that it could be used in the most complex forest management planning situations encountered in Ireland. The idea was that in simpler planning cases, the components that were not needed could be ignored. However, based on the most recent feedback from the management companies, the overall complexity of the system is off-putting and managers and consultants are apprehensive about the long learning curve associated with using the system. | |Has evidence=It was decided to develop a highly detailed system in order that it could be used in the most complex forest management planning situations encountered in Ireland. The idea was that in simpler planning cases, the components that were not needed could be ignored. However, based on the most recent feedback from the management companies, the overall complexity of the system is off-putting and managers and consultants are apprehensive about the long learning curve associated with using the system. | ||
|Has consequences=It assures that a plan obtains a preliminary step on certification process | |Has consequences=It assures that a plan obtains a preliminary step on certification process | ||
|Has recommendation for action=Development of a 'light' version of the DSS, which could be used in 'simple' cases, with the option of users migrating to the detailed version as forest management problems become more complex in a maturing forest estate. | |Has recommendation for action=Development of a 'light' version of the DSS, which could be used in 'simple' cases, with the option of users migrating to the detailed version as forest management problems become more complex in a maturing forest estate. | ||
| − | |||
|Has temporal scale=Long term (strategic) | |Has temporal scale=Long term (strategic) | ||
|Has spatial context=Spatial with neighbourhood interrelations | |Has spatial context=Spatial with neighbourhood interrelations | ||
| Line 17: | Line 26: | ||
|Has related DSS=PYL | |Has related DSS=PYL | ||
|Has country=Germany | |Has country=Germany | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|Has user role= | |Has user role= | ||
|Has developer role=Architect, Project manager | |Has developer role=Architect, Project manager | ||
| Line 31: | Line 32: | ||
|Has stakeholder involvement= | |Has stakeholder involvement= | ||
|Has system testing= | |Has system testing= | ||
| − | |||
|Has justification=Hard copy of the manual only is not attractive for the user. | |Has justification=Hard copy of the manual only is not attractive for the user. | ||
|Has decision stage=organization | |Has decision stage=organization | ||
Revision as of 00:58, 9 September 2013
Lesson
| ID | 32 |
|---|---|
| Has statement | Need flexible analytical tools - no "overdesigned" tool that provides too much features for the use |
| Has evidence | It was decided to develop a highly detailed system in order that it could be used in the most complex forest management planning situations encountered in Ireland. The idea was that in simpler planning cases, the components that were not needed could be ignored. However, based on the most recent feedback from the management companies, the overall complexity of the system is off-putting and managers and consultants are apprehensive about the long learning curve associated with using the system. |
| Has consequences | It assures that a plan obtains a preliminary step on certification process |
| Has recommendation for action | Development of a 'light' version of the DSS, which could be used in 'simple' cases, with the option of users migrating to the detailed version as forest management problems become more complex in a maturing forest estate. |
| Has domain | Models and methods, User interface and outputs, User interface and outputs, User interface and outputs, User interface and outputs |
| Has DSS development stage | Specification, Use |
| Has decision stage | organization |
| Has temporal scale | Long term (strategic) |
| Has spatial context | Spatial with neighbourhood interrelations |
| Has spatial scale | Regional/national level |
| Has objectives dimension | Multiple objectives |
| Has goods and services dimension | Market services, Non-market services |
| Has decision making dimension | More than one decision maker/stakeholder |
| Has country | Germany |
| Has reference | Vacik H., Lexer M.J. and Englisch M. 2004. Einsatz des Decision Support Systems DSD v1.1 zur Unterstützung der forstlichen Beratung im Landesforstdienst. Forstarchiv 75 (5): 1-11.
Lexer, M.J., Vacik, H., Palmetzhofer, D. and Oitzinger, G. 2005. A decision support tool to improve forestry extension services for small private landowners in southern Austria. Computers and Electronics in Agriculture 49, 1: 81-102. |
| Has related DSS | PYL |
| Has related case | Germany-Using GISCAME to test alternative land-use scenarios under climate change in the Upper Elbe Valley |
| Has related lesson | |
| Has other relevant information | This requirement depends on the problem statement; some problems can be solved without neighbourhood interrelations. Some problems with neighbourhood interrelations, such as demanding a large area of interior conditions (no edge effects) tend to be large combinatorial problems. |
| Has working group theme | Dss development process, Models & techniques |
| Has DSS development | Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use.Description of DSS development |
| Has decision support techniques | Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use.Decision support techniques |
| Has knowledge management processes | Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use.Knowledge management process |
| Has support for social participation | Need of flexibilization of analytical tools - no "overdesigned" tool that provides too much features for the use.Support of social participation |
| Has actor perspective | Developer/Architect |
| Has researcher role | |
| Has user role | |
| Has developer role | Architect, Project manager |
