Technologists

From E-Consultation Guide
Revision as of 13:39, 13 March 2006 by 143.117.75.114 (talk) (Technology (***))

Jump to: navigation, search


Time (**)

Cost (**)

Engagement (*)

Case studies (**)

Participation (**)

Skills (**)

Usability (***)

Results (*)

Benefits (***)

What is e-consultation (*)

Resources (***)

Relationships (*)

FAQ (***)

Promotion (*)

Why e-consultation ()

Guidelines (**)

Translation (***)

Stages ()

Security (***)

Process change ()

Technology, Technology matching (***)

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)

Transparency ()

Technology matching (***)

Design, planning (*)

Processes ()

Strategies ()