-
Maintainability: What will ongoing maintenance of the tool entail? Is the software easily maintainable over time?
-
Mobile-compatible: How important is it that mobile users be able to utilize the site? How much functionality needs to be available in a mobile environment? (Rather than support all platforms, one may choose to limit supported viewports.)
-
User interface (UI): How intuitive does the UI need to be? (Rather than an elegant and intuitive UI, one may choose to allocate resources towards training once the UI is completed.)
-
Flexibility: How flexible does the application need to be to incorporate disparate data sources and map types?
-
Performance: How fast does the site need to be? How many users will the site need to support?
-
Platform: Will the site be built with proprietary software or open source software? Open source generally implies less up front or ongoing software investment but more expensive development and labor costs.
-
Transparency: How important is it that the underlying data and shapefiles be made available for viewing and downloading?
-
Modularity: Can the site be built in a modular way so that each component does not rely on the others to operate? This allows the phased addition of functionality and isolating technical concerns.
-
Extensibility: Will the software and hardware accommodate future additions to functionality and resources?
|
|
|
|
|