Difference between revisions of "Technologists"

From E-Consultation Guide
Jump to: navigation, search
(Security (***))
(Translation (***))
Line 34: Line 34:
  
 
== Translation (***) ==
 
== Translation (***) ==
 +
 +
# What are aim/purpose/objectives of the consultation?
 +
# What sort of the activities will be taken place during the consultation?
 +
# How/when each activity will be used in consultation? (Is there any assumptions in activity?)
 +
# What is stack holders envisage role in activity?
 +
# Are these activities integrated with each other or any other consultation? How?
 +
# List of the matching technology for each activities of the consultation?
 +
# Is there any single technology or many technology required for consultation?
 +
# How the technology overall will be useful in meet consultation aim/purpose/objectives?
  
 
== Stages () ==
 
== Stages () ==

Revision as of 14:25, 13 March 2006


Time (**)

Cost (**)

Engagement (*)

Case studies (**)

Participation (**)

Skills (**)

Usability (***)

Results (*)

Benefits (***)

What is e-consultation (*)

Resources (***)

Relationships (*)

FAQ (***)

Promotion (*)

Why e-consultation ()

Guidelines (**)

Translation (***)

  1. What are aim/purpose/objectives of the consultation?
  2. What sort of the activities will be taken place during the consultation?
  3. How/when each activity will be used in consultation? (Is there any assumptions in activity?)
  4. What is stack holders envisage role in activity?
  5. Are these activities integrated with each other or any other consultation? How?
  6. List of the matching technology for each activities of the consultation?
  7. Is there any single technology or many technology required for consultation?
  8. How the technology overall will be useful in meet consultation aim/purpose/objectives?

Stages ()

Security (***)

  • Define security issues for consultation technology.
    • User management
    • Authentication
    • Authorization
    • Data protection
    • Data validation
  • Conduct security test and planning
  • Know common source of security error/violation/attack for web sites, web technologies.
  • Are you collecting personnel information on the website/technology?
    • Do you have your privacy policy and terms of use available for users?
    • How this personnel information will be treated?
  • Who will be having access to data colleted with consultation technology?
  • What will happen at end of consultation? How would you archive consultation responses?
  • Security policy/backup for any unlikely event for technology fails.

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)

Design, planning (*)

  1. What technical knowledge/expertise should be available in-house?
  2. How much time is required to implementation of the technology?
  3. What support, documentation, help are available to implement the technology?
  4. How much maintenance, training is needed for using technology?
  5. Is required to customise/change technology to meet envisage use of technology?
  6. Will it be accessible to participants and consulter?