Rev 5912 | Rev 15107 | Go to most recent revision | Details | Compare with Previous | Last modification | View Log | RSS feed
| Rev | Author | Line No. | Line |
|---|---|---|---|
| 23 | reyssat | 1 | |
| 6133 | bpr | 2 | <h2>The structure of an institution interface</h2> |
| 23 | reyssat | 3 | |
| 5912 | bpr | 4 | <a id="institution"></a> |
| 23 | reyssat | 5 | An institutional structure is a multi-level lattice of a group of virtual |
| 6 | classes. Each virtual class in the lattice is called a <em>work zone</em>, |
||
| 7 | or <em>zone</em>. |
||
| 8 | <p> |
||
| 5912 | bpr | 9 | <a id="portal"></a> |
| 23 | reyssat | 10 | The structure of an institution is built below a unique zone called |
| 11 | <em>portal</em>. This is the common entrance point, it serves also for |
||
| 12 | global management for the institution. No real teaching work should take |
||
| 13 | place in this zone. |
||
| 14 | <p> |
||
| 5912 | bpr | 15 | <a id="level"></a> |
| 23 | reyssat | 16 | Zones immediately below the portal are <em>levels</em>. A level corresponds to |
| 17 | a set of students sharing the same annual programs. |
||
| 18 | <p> |
||
| 19 | The role of levels is essentially to separate things that have no relation |
||
| 20 | between them. |
||
| 21 | Student logins are not |
||
| 22 | accepted for levels, nor teaching works. |
||
| 23 | <p> |
||
| 5912 | bpr | 24 | <a id="class"></a> |
| 23 | reyssat | 25 | <em>Classes</em> are immediately below each level. A class is a group of |
| 26 | students sharing the same teaching time table. |
||
| 27 | <p> |
||
| 28 | Students should log in to classes. Each student may have one or more classes. |
||
| 29 | <p> |
||
| 5912 | bpr | 30 | <a id="program"></a> |
| 23 | reyssat | 31 | Immediately below a level are also <em>programs</em>. Each program is a |
| 32 | gathering point of teaching resources shared by one or several classes in |
||
| 33 | the level. |
||
| 34 | <p> |
||
| 35 | Students cannot log in to programs. Teachers can log to programs (as |
||
| 36 | supervisors) in order to prepare teaching materials. |
||
| 37 | <p> |
||
| 5912 | bpr | 38 | <a id="course"></a> |
| 23 | reyssat | 39 | <em>Courses</em> are zones of lowerest level. Each course belongs to a |
| 40 | program, as well as to a class. One can think that to every pair |
||
| 41 | {program,class} may correspond a course. |
||
| 42 | <p> |
||
| 43 | Teaching resources of a program are shared by all its courses. A student in |
||
| 44 | a class can navigate between the courses of the class. Daily student works |
||
| 45 | are done in courses. |
||
| 46 | <p> |
||
| 47 | A course has a unique set of teaching resources, and a unique time table. |
||
| 48 | <p> |
||
| 5912 | bpr | 49 | <a id="icourse"></a> |
| 23 | reyssat | 50 | A program can also have <em>Interclass courses</em>. Such a course only |
| 51 | belongs to a program, and students from any class can register to an |
||
| 52 | interclass course. This can be used for optional teaching programs. |
||
| 53 | <p> |
||
| 5912 | bpr | 54 | <a id="test"></a> |
| 23 | reyssat | 55 | Each program can also have a special course, called <em>test zone</em>. |
| 56 | Teachers can prepare experimental teaching resources in the text zone, then |
||
| 57 | export them to the program when finished. Everything in the test zone is |
||
| 58 | invisible to the students. |
||
| 59 |