Edit Software: PEB.Software

Jump to: navigation, search

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.


Software

Responsible organisation (name of the detail wiki page): Name of the organisation with the lead responsibility
Institutional framework: Institutional framework regarding the tool development and main utilization
Contact person for the DSS:
Contact e-mail for the DSS:
Status: Development status of the system
Accessibility: How accessible is the system from the licensing point of view
Commercial product: Is the tool commercial or not? If yes, indicate the price
Deployment cost: Ready-to-use costs, based on an average computer (hardware, software) considering the target user group, inclusive installation costs when performed by a specialist
Installation requirements: List of the software and hardware requirements for installing and using the tool. Mention specific hardware like sensors, GPS, PDA
Computational limitations: Describe the system limitations: e.g. number of management units, number of vehicles, time horizon; address the ability to control computational performance
User support organization (name of the detail wiki page): Organisation in charge of the support
Support team size: Number of people involved in the support
Maintenance organization (name of the detail wiki page): Organisation in charge of the maintenance
Input data requirements: Nature of the input data required by the tool (can have more than one)
Format of the input data: Format of the input data (can have more than one)
Data validation: Methods implemented for validating the data placed by the user, if any
Format of the output data: Format of the output data (can have more than one)
Internal data management: Format of the internal data (can have more than one)
Database: Product name of the database integrated, if any
GIS integration: Product name of the GIS integrated, if any
Data mining: Data mining algorithms included/supported by the system
Spatial analysis: integrated capabilities vs. facilitates links to GIS (wizards, etc.)? Provides standard data import/export formats? Includes GIS editing interfaces? Allows spatial analysis (e.g. topology overlays (e.g. multi layering of different maps, selection of objects based on selection criteria, aggregation by attributes (e.g. areas of similar characteristics), Linking by logical means, Statistics by area, analysis with digital terrain model)
User access control: Does it require prior user registry and authentication?
Parameterised GUI: Existence of GUI parameterised by the user
User-friendliness of GUI: How is the user-friendliness of the graphical user interface (GUI) ensured? Which of the mentioned attributes are followed in the interface?
Map interface: Can the planning results be browsed in a 2D map interface
GUI technology: Product name of the GUI implemented, if any
System type: Type of system
Application architecture: overview of the tool's application architecture. List the modular components; identify equipment needed
Communication architecture: Characterize the network requirements and the communication architecture. Is it peer-to-peer or layered architecture? What protocols are required?
Operating system: Type of Operating system used
Programming language: Name of the programming language adopted
Scalability: Is the tool easily evolved to new modules and new functionalities or does it works like a "black box"
Interoperability: If there is more than one user profile, how interoperability among the users is assured?
Integration with other systems: Describe the solution adopted for integrating with other user's systems, and the communications protocols in use, if any
+ +++Has price+++:

Price of the system

Price:

Free text: Free text with wiki-syntax. Use the following tag to list up references used in this document: "<references/>"


Cancel