Technology

From E-Consultation Guide
Revision as of 22:29, 8 July 2006 by Dave (talk | contribs) (Older notes, not yet included in main text)

Jump to: navigation, search

We will not attempt to list here every Information and Communication Technology (ICT) that might be used within a public consultation. Instead we will explain a way you can go about selecting appropriate technologies for e-consultation.

Older notes, not yet included in main text

  1. What are the various technologies I could use to
    1. Publicise the e-consultation. (Email campaign)
    2. Stay in contact & update participants. (Mailling list, periodic newsletter)
  1. Where can I get information on the technology and technical knowledge that I will need in order to engage in E-consultation?
Technology selection process
  • Define your needs (Why you need a consultation technology)
    • Define consultation case
      • Description: a short explanation of the consultation activity
      • Reasons: a description of the needs why this consultation activity should be taken
      • Assumptions: All the assumptions to make this consultation activity
      • Benefits: List of benefits for consulting organisation and participant
      • Cost: How much it cost to run this consultation activity
      • Investment: Can this consultation activity will be taken in future
  • Define your selection criteria (Criteria for Technology selection)
    • Vendor stability and reputation (support)
    • Wide adoption in market
    • Does it require any possible changes to meet stack holders needs
    • Secure and mature/proven technology
    • Training and documentation
    • Actual implementation of the technology
    • Technology accessibility standards
  • List of matching technologies
  • Select the best suited for you
    • Good description of technology
    • Infrastructure required (network)
    • Platforms (operating systems, hardware)
    • Architectural Integrity (Interaction with other technology, Would it possible to integrate with other technology?)
    • Fitness for purpose (Is it meeting purpose envisaged?)
    • Expertise (What knowledge should be available in-house, Maintenance and support)
    • Maturity of Standard (Is the technology mature and well-proven)
    • User needs (Does the technology satisfy the user requirements and Matching stack holders requirements)
    • Preservation needs (Is technology is appropriate for long-term preservation)
    • Budget (time, money)