Technical sheet: ATutor
In this sheet the results of the evaluation are presented in a table format.
|
||||
| Functional features | ||||
| Didactics/Learning flow management | At the moment, learning paths are not available and it's not possible to implement learning activities. | |||
| Tests and assesment | Authoring tools are really easy to use and html pages can be realized without any expertise. Contents like SCORM and IMS compliant packages can be imported, moreover html pages or whatever files format can be imported and organized whitin the platform. Tests (multiple choice, true/false, open ended and range types) can be done within the system and we can choose whether scores must be assigned automatically or by the tutor. | |||
| Media formats/Authoring | SCORM and IMS contents packaging can be imported, but also whatever files format. SCORM runtime is not yet supported. One important feature (none of the systems evaluated can do the same) is the possibility to export an entire course (or a part of it) in IMS standard packaging format. Courses can be categorized in a simple folder way and contents can be annotated with keywords that are going to be used by the search engine. User data can be exported and imported in a csv format and all multimedia files format are supported. | |||
| Course monitoring | A course can be published after a predefined date; users can enroll themselves and Instructors may approve enrollments. It's possible to track a lot of informations (object, lerners, etc) and data can be even exported. | |||
| Communication | Synchronous communication is possible using chat, asynchronous communications are available through forums, emails and files (notes) exchange. All these tools are in the ACollab system, an add-on for ATutor 1.4+ but also a stand-alone collaborative work environment. | |||
| General look and feel of the system | The system makes use of stylesheets and each user can choose the prefered one changing the layout (positions) of the objects whitin the page, hiding something or simply picking up one of the available templates. Instructors can also establish a template for a set of courses. | |||
| Permissions handling | The permissions system is quite good: is not possile to define new roles but the predefined ones (Admin, Instructor, Users and Guests) are enough to satisfy whatever scenario. It's possible to create groups: all collaborative tools are based on groups. | |||
| Other features | Users can share notes but cannot annotate a particular content. At the moment more than sixteen localizations are available and it's possible to put a note at the end of the content pages to point out Intellectual Property Rights. LDAP support is not available in this version. | |||
| Maintainability | ||||
| Quality of technical documentation | There is an online a page where developers guideline are described quite well (there's only an English version). | |||
| Scalability | The system is not the most popular, but there are a lot of demo and official installations all over the world. The system is also very reliable. | |||
| Extensibility | The code is quite good and the coding conventions are almost respected, but there isn't a plug-in concept nor API are defined. Bugs and user requirements are managed within the forum and Subversion is the tool that has been adopted for the repository and the versioning control. More than six stable versions are available. | |||
| Adaptability/standard compliance | The system supports IMS packaging for import and export functionalities, and SCORM 1.2 only for import. The system is modular in the sense that functions are grouped togheter. | |||
| Usability | ||||
| User documentation | Documentation is available only in english and it's quite good for each of the actor involved in the scenario (Administrators, Instructors and Learners). There is also a help online and a very good context sensitive help. | |||
| Generating content | The instructors can easily create and modify content, and it's even possible to modify SCORM content inside the internal editor. The same for tests. | |||
| Level of expertise needed | The system is easy to use and a high level of expertise is not required: according to us, the only inconvenience is that it takes some time to view and understand all (and are really many) the functionalities available in the platform. | |||
| Other | Materials to be used in the system can be found among existing SCORM LO, IMS Courses or whatever docs and files format. The system is easy to use, customizable and the permission system is simple to understand. Furthermore, it is compliant with the accessibility specifications (W3C WAI). | |||
| Support quality | ||||
| Note | It's possible to contact the Atutor Team on the web site (there's a web page with a form to be filled) in order to get services, on the basis af a contract, regarding new development, hosting, consultation and support. The team is quite responsive and it's possible to get an answer in one day. | |||
| Total cost of ownership | ||||
| Type of users | The predominant type of users are schools and universities, but they are not the only ones: there are also small enterprieses and organizations. The number of users can be estimated in several thousands all over the world, and there is a complete list of institutions on the web site, if we want to get in contact with them. | |||
| Financial stability | The project started in 2002 and the team can be estimated in less then ten people. The core team is funded and there are a few supporters that collaborate to the project. | |||
| One time cost | There are no special hardware needs. The software requirements are: Apache, MySQL, PHP (the suggested versions are on the website). | |||
| Recurring costs | Periodical activities are the same as for all web systems: patching the OS or the tools installed. Sometime a system reboot nedds to be done. | |||
Last modified
2005-01-19 04:39 PM