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