Difference between revisions of "Technologists"
From E-Consultation Guide
(→Technology (***)) |
|||
| Line 73: | Line 73: | ||
** Preservation needs (Is technology is appropriate for long-term preservation) | ** Preservation needs (Is technology is appropriate for long-term preservation) | ||
** Budget (time, money) | ** Budget (time, money) | ||
| − | |||
| − | |||
| − | |||
| − | |||
== Design, planning (*) == | == Design, planning (*) == | ||
| − | + | # What technical knowledge/expertise should be available in-house? | |
| − | + | # How much time is required to implementation of the technology? | |
| − | + | # What support, documentation, help are available to implement the technology? | |
| + | # How much maintenance, training is needed for using technology? | ||
| + | # Is required to customise/change technology to meet envisage use of technology? | ||
| + | # Will it be accessible to participants and consulter? | ||
Revision as of 13:40, 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 (***)
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 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)
Design, planning (*)
- What technical knowledge/expertise should be available in-house?
- How much time is required to implementation of the technology?
- What support, documentation, help are available to implement the technology?
- How much maintenance, training is needed for using technology?
- Is required to customise/change technology to meet envisage use of technology?
- Will it be accessible to participants and consulter?
