These requirements are from the project proposal.

Functional Requirements

• WFS client read/write support, to allow direct editing of data exposed via transaction web feature servers
• WMS support, to allow viewing of background data published via WMS
• Styled Layer Descriptor (SLD) support, to allow the client-directed dynamic re-styling of WMS layers
• Web Registry Server support, for quick location of available CGDI layers
• Printing support, to allow users to create standard and large format cartography from their desktops using CGDI data sources
• Standard GID file format support, to allow users to directly open, overlay, and edit local Shape and GeoTiff files with CGDI online data.
• Coordinate porjection support, to transparently intergrate remote layers in the cline tapplication where necessary.
• Database access support, to allow users to directly open, overlay and edit data stored in PostGIS, OracleSpatial, ArcSDE, and MySQL.
• Cross-platform support, using Java as an implementation language, and providing one-click setup files for Windows, OS/X, and Linux.
• Multi-lingual design, allowing easy internationalization of the interface, with French and English translations of the interface completed initially.
• Customizability and modularity, to allow third party developers to add new capabilities, or strip out existing capabilities as necessary when intergrating the application with existing enterprise infrastructures.

Non Functional Requirements

• Well-Rounded Framework, built on standard and best-of-breed libraries to offer a sustainable, competitive advantage to uDig developers.
  • Plug-in Deployment Model, with versioning and plug-in management to ease the cost of deployment, upgrading and installation.
  • Integration/Extension, maintain common appearance, workflow, framework and persistence mechanisms between built-in editing and third-party modules.
  • Logs, make use of logging standards and libraries.
• Open Development Process, capture developer interest and third party contributions.
• Marketing
• Release Management, stable and development releases.
• Product Development and Branding, continued use of JUMP branding.
• Licensing Model and Business Model
  • Application License Model, open-source license to allow distribution and extension without incurring multiple licensing fees, commercial support allows for a business model.
  • Extension License Model, open-source Framework API allows GPL or Commercial extension.
• Usability, use industry standard user-interface constructs and terminology to reduce training time.
  • Configuration and Preferences, make use of sensible defaults, use context where possible.
  • Installation, allow installation with sensible defaults and little user input.
  • Professional Appearance, integrate with existing installation base.
  • Quick Response, provide immediate feedback.
• Performance
  • Data Access Performance, ESRI Shapefile access is a significant measure of application performance and must be more then competitive.
  • Operative Performance, application must be sufficiently responsive so that an operator can maintain concentration.
• Security, considered where applicable: database passwords will not be stored with project file; the OWS infrastructure lacks a strong security model.

Next [Source License]