Forgot your password?
KN Fast Folders
Technical sheet: Dokeos
In this sheet the results of the evaluation are presented in a table format.
|
||||
| Functional features | ||||
| Didactics/Learning flow management | Dokeos allows to create learning paths for the classroom. Each learning path can be done creating one or more modules, each of them may contain a set of the resources available in the course. Once the modules are choosen, we can set up the order and the dependences among the modules and among the included items. | |||
| Tests and assesment | Tests cannot be imported but they can be created within the system. The following types of questions are available: with single and multiple choice, with matching answers and with blank fields to be filled in. It's possible to track navigation and to view tests statistiscs. For each object (e.g. available tool) statistics data can be seen. The same statistics are available for each user. | |||
| Media formats/Authoring | Contents can be created within the system (viewed as html file), and imported in whatever format (pdb, doc, txt, html, etc). SCORM modules are also supported, even with runtime environment (result can be viewed in a statistics way). Contents can be organized in folder. | |||
| Course monitoring | Users can be enrolled by the the teacher/admin or can enroll by themselves. It's possible to track a lot of information (particular objects, particular lerners or access time) and data is presented in tables. | |||
| Communication | For synchronous communications chat and audio/video conferencing are available, for asynchronous communications internal email, forums and notes/files sharing can be used. Email can be sent to external addresses. | |||
| General look and feel of the system | The system makes use of css and it's possible to personalize almost everything, but customizations are at platform level (users cannot choose a different style or change it). | |||
| Permissions handling | Permissions are handled in a role based style. There are 4 predefined roles: administrator, teacher, user and guest. It' not possible to modify these roles or to create a new one (in an easy way). Users can be organized into groups. | |||
| Other features | There are a lot of localizations (more then thirty) and LDAP is supported with an extra module. Users can share notes. | |||
| Maintainability | ||||
| Quality of technical documentation | Only one document for developers (in English) is available. The document is a kind of manual dealing with issues regarding architecture, database structure, work method, code conventions, and so on. We appreciate the effort, but the manual should be more extended. | |||
| Scalability | There are a lot of institutions and universities that are using Dokeos. We can estimate that for each istallation more than 5 thousands users and 150 courses can be supported, but it's not clear if the system can grow horizontally. The system is very reliable. | |||
| Extensibility | The code is quite clear and code conventions are normally respected; at the moment, no APIs have been defined and there isn't a plug-in concept available (we would prefer a separation between the php code and the GUI in html). User requirements and bugs are handled within the forum and there is a public CVS system. There are 3 stable versions released. | |||
| Adaptability/standard compliance | The system is SCORM 1.2 compliant even for the runtime environment. | |||
| Usability | ||||
| User documentation | Documentation is available for authors (in a multilingual format), administrators (only in English), but not for users. | |||
| Generating content | The system is really easy to use and it possible to create test and content within the environment, and to modify what we have done. | |||
| Level of expertise needed | All the system operations, at any level, do not require special expertise. Everything can be done in a simple way and without any training. | |||
| Other | The system is easy to navigate, and customizations are possible at platform level. Contents and data available in the Internet, like SCORM modules, Can be used in whatever type of document and HTML pages. The permission system is not really flexible but it's easy to understand. | |||
| Support quality | ||||
| Note | It's possible to get a lot support for training, consulting, hosting migration and programming customisations (all information is on the website). The team is always responsive and it's possible to get a lot of information in the forum. | |||
| Total cost of ownership | ||||
| Type of users | Schools and Universities are the most predominant users, but also public administrations and companies. The list on the web site includes only the organisations that are using the Dokeos commercial services and the number of users is quite big (many thousands). | |||
| Financial stability | The project started in 2003 by a fork in the Claroline story, and the core team is composed of about 7 members but there are a few developers all around the world. The team is founded. | |||
| One time cost | There are no special hardware needs. The software requirements are: Apache, MySQL, PHP and some php module (mysql, zlib, preg, xml). To set up a running system it's needed less than one day. | |||
| Recurring costs | Periodical activities are the same as for all web systems: patching the OS or the tools installed. Sometime a system reboot should be done. | |||
Last modified
2005-01-19 04:42 PM
