Difference between revisions of "Technology"
From E-Consultation Guide
Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
+ | |||
+ | |||
+ | # What are the various technologies I could use to | ||
+ | ## Publicise the e-consultation. | ||
+ | ## Stay in contact & update participants. | ||
+ | ## Get theie views. | ||
+ | ## Collective writing. | ||
+ | ## Conduct a survey. | ||
+ | ## Organise meetings. | ||
+ | ## Consult over long distnaces. | ||
+ | # What are the various technologies & what are they used for? | ||
+ | # 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) |
Revision as of 16:31, 23 March 2006
- What are the various technologies I could use to
- Publicise the e-consultation.
- Stay in contact & update participants.
- Get theie views.
- Collective writing.
- Conduct a survey.
- Organise meetings.
- Consult over long distnaces.
- What are the various technologies & what are they used for?
- 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 consultation case
- 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)