File: structure.phtml

package info (click to toggle)
wims 2%3A4.29a%2Bdfsg1-3
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 185,704 kB
  • sloc: xml: 366,687; javascript: 120,570; ansic: 62,341; java: 62,170; sh: 7,744; perl: 3,937; yacc: 3,217; cpp: 1,915; lex: 1,805; makefile: 1,084; lisp: 914; pascal: 601; python: 520; php: 318; asm: 7
file content (60 lines) | stat: -rw-r--r-- 2,358 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60

<h2>The structure of an institution interface</h2>

<a id="institution"></a>
An institutional structure is a multi-level lattice of a group of virtual
classes. Each virtual class in the lattice is called a <em>work zone</em>,
or <em>zone</em>.
<p>
<a id="portal"></a>
The structure of an institution is built below a unique zone called
<em>portal</em>. This is the common entrance point, it serves also for
global management for the institution. No real teaching work should take
place in this zone.
</p><p>
<a id="level"></a>
Zones immediately below the portal are <em>levels</em>. A level corresponds to
a set of students sharing the same annual programs.
</p><p>
The role of levels is essentially to separate things that have no relation
between them.
Student logins are not
accepted for levels, nor teaching works.
</p><p>
<a id="class"></a>
<em>Classes</em> are immediately below each level. A class is a group of
students sharing the same teaching time table.
</p><p>
Students should log in to classes. Each student may have one or more classes.
</p><p>
<a id="program"></a>
Immediately below a level are also <em>programs</em>. Each program is a
gathering point of teaching resources shared by one or several classes in
the level.
</p>
</p><p>
Students cannot log in to programs. Teachers can log to programs (as
supervisors) in order to prepare teaching materials.
</p><p>
<a id="course"></a>
<em>Courses</em> are zones of lowerest level. Each course belongs to a
program, as well as to a class. One can think that to every pair
{program,class} may correspond a course.
</p><p>
Teaching resources of a program are shared by all its courses. A student in
a class can navigate between the courses of the class. Daily student works
are done in courses.
</p><p>
A course has a unique set of teaching resources, and a unique time table.
</p><p>
<a id="icourse"></a>
A program can also have <em>Interclass courses</em>. Such a course only
belongs to a program, and students from any class can register to an
interclass course. This can be used for optional teaching programs.
</p><p>
<a id="test"></a>
Each program can also have a special course, called <em>test zone</em>.
Teachers can prepare experimental teaching resources in the text zone, then
export them to the program when finished. Everything in the test zone is
invisible to the students.
</p>