This document is for quality management purposes.
Distribution List:
Mailing list user@Skolelinux.de and Teachers in Germany
Changelog
Authors: Volker Eckert, Hans-Georg Terlecki, Maximilian Wilhelm / 2003-11-21
Checked: Jürgen Leibner / 2003-11-21
Released: Kurt Gramlich / 2003-11-21
Valid from: 2003-11-22
New document
Replaces version from:
This document contains the requirements for the skolelinux school server from teacher's point of view. These requirements should be outlined in a comprehensive way. Based on this work statement the product requirement specifications will be made. The work statement was compiled by members of the German Skolelinux mailing list.
...means that the input to be types in is reduced to only the really necessary. Hardware detection and Installation on the hard drive (partitioning, formatting, installation) should as automatically as possible. An administrator should be able to install an uninterruptable power supply (UPS) easily.
For advanced users, it should be possible to install Skolelinux manually, for instance to integrate Skolelinux in an existing network.
Every user should get an account. Every user should get only the needed rights. The principle of the minimum user rights should be followed.
The user-rights have at least to be differentiated between administrator, teacher and pupils.
A further differentiation into project leader, project groups and subject teacher through the user administration has to be possible.
Userdata from every popular school administration program should be importable.
Administration of user accounts should be customized to the special requirements of the school-types. All users should be able to change their own password. Privileged teachers should be able to change pupils passwords.
The account data should be easily updateable at every new school year.
When removing user accounts, it should be possible to save the user data for a limited time.
It should be possible to get an clear overview of the used disk space.
It should be possible to specify which user may access which printer. The selection of several printers should be possible. It should be possible to assign one user the right to disable and enable printers, as well as stopping and deleting printer jobs. Each user should be able to delete its own printing jobs. It should be possible to configure that the printing jobs of a user are removed when logging off.
During examinations / tests, it should be possible to easily prevent any communication between pupils.
It should be possible to install the newest security-updates into the entire system easily and fast.
Easy installation and removal of software must be ensured. Updating of single packages should also be possible.
All administration should be possible to do remotely using a secure connection.
Upgrading to a new version should be possible to do safely and without any interruption.
The administrative tasks should be delegateable through the rights- system.
All sensitive data (authentication) should only be exchanged encrypted.
The use of the preconfigured services should be configureable for each user.
It should be possible to allow and disallow access to the Internet based on the room, PC or user.
Access to unwanted websites should be deniable. Maintainance of the filters should be easy.
During classes, it should be possible to monitor the active surfing. It should also be possible to log all surfing activity.
The local web-server should let all users present static and dynamic web-pages. After the responsible teacher has checked the individual web-pages, it should be possible to make them publicly available.
It should be possible to upload specified web-pages to an external web-server using a encrypted connection.
The email-server should provide local and external email. The rights should be configureable through the user administration. It should be possible to integrate a virus scanner. For use in the German speaking parts of the world, an interface to the Winshuttle service should exist.
A local news-server should provide selected news groups. The write- and read-access should be configureable through the user administration.
Every user should get their own directory. The size of the directories should be configureable through the user administration.
It should be possible to create directories for exchanging files related to classes, rooms and projects. The maximum size should be configurealbe.
Here teachers, course- and project-leaders should be able to place data for being picked up. Pupils should only have read-access to this directory.
Here pupils should be able to deliver finished documents or files. This directory should not be readable by other pupils. Teachers should easily be able to fetch and move these documents and files.
A print server should manage the printing jobs, and it should provide a way to limit and account the number of pages printed. Prints should be relateable to the user.
For communication within groups, for email-projects and for newsletters from the point of parents representatives, pupil representatives, school management, working groups and projects, a mailinglist-server should be available.
Documentation customized for the intended audience is required indeed and is divided in an admin, a user manual and accompanying material.
The administration manual is about installation of the base system, configuration of server-services, user administration, maintenance and ensuring ongoing operation, updating and upgrading of the system, and a FAQ.