| |
Technical sheet |
Evaluation date:
2004/10/30 |
|
| Functional features |
| Didactics/Learning flow management |
Paths are not available and it is not possible to
link activities |
| Tests and assesment |
No specific tool is provided to create tests. |
| Media formats/Authoring |
The system allows the upload of any kind of files,
but no tool is provided to create learning modules. All the documents
or any subset of them can be exported. |
| Course monitoring |
Course management is very simple: users can enroll on
a course, but no tools are available to monitor or track their
actions. |
| Communication |
The system provides a chat tool for synchronous
communication. For asynchronous ones, it uses forums and mailing
lists. |
| General look and feel of the system |
A few parts of the application can be customized and
it's possible for users to change the skin used. |
| Permissions handling |
The permission system is easy to use: it uses ACL and
groups to handle access to objects. The author of a resource can
decide whether he grants acces to his object and he also can accept
or reject enrollment for this object. |
| Other features |
No other feature |
| Maintainability |
| Quality of technical documentation |
There is a very good developer documentation (in
English) |
| Scalability |
The system is very reliable. |
| Extensibility |
The code of the application is good and respects the
coding conventions of the project. It is fully object oriented and
supports a plugin system and offers an API for developers. A CVS
server is available for the project, which uses Sourceforge standard
tools to handle bug reports and feature requests. 1 stable version
has been released. |
| Adaptability/standard compliance |
The system is fully modularized but doesn't support
any elearning standard |
| Usability |
| User documentation |
The documentation for administrators is available in
English and is very good. For end-users, the documentation is only
available in German. |
| Generating content |
There's no tool to generate content or tests in the
system, but they can be uploaded. |
| Level of expertise needed |
The system is quite easy to use and doesn't require a
high level of expertise. |
| Other |
The system is easy to navigate. It can be customized
by the institution running it, but it takes some time. The permission
system, while not as flexible as it could be, is easy to understand
and to learn. No standard for accessibility is supported. |
| Support quality |
| Note |
Discussions are possible through the project forums
in various languages. It is also possible to buy support from several
companies (listed on
http://openuss.sourceforge.net/openuss/commercial.html) |
| Total cost of ownership |
| Type of users |
The system is mainly used in unversities |
| Financial stability |
The project is supported by university of
Muenster. |
| One time cost |
No special hardware required. |
| Recurring costs |
Periodical activities are standard for large java web
applications. |
Forgot your password?
KN Fast Folders
