Get documents about "Free Pink Web Templates - Excel - Excel
Description
Free Pink Web Templates document sample
Document Sample
Sitar 3-stage system for enrolling students
1 Identification of courses based on standard program templates
2 Selection of classes to produce a feasible clash-free timetable
3 Transfer of class numbers to (new) enrolment panel
Ceres Final phase of on-line enrolment process corresponding to Sitar stage 2.
Feature Sitar Ceres
Class data source Refreshed from NSS tables NSS tables
Course enrolment data source Entered in stage 1 Previous phase (ebasket)
Interaction mode (see UserModes) Mode 2 Mode 1 or 2
State tracking Via hidden data elements in page Written to ebasket or equiv
Class enrolment Pasted to new panel Enrolment request constructed + posted
Sitar/Ceres modes of user interaction
Stage 2 Class selection by timetable
Version 1.0 11-Oct-02
Sitar builds this structure for all courses that are in the e-basket. It is based on component because that is the view
Mode 1 Mode 2
Response App responds to each selection event App responds after multiple selection + submit action
Applicable System Ceres Sitar or Ceres
Advantages Provides immediate feedback to user Minimises references to cgi server + hence delays
Avoids possibility of inconsistent selection All classes for a course can be done at once
Supports other actions (e.g. expand parallel classes)
Disadvantages Possible performance impacts Increases complexity of response logic
Need for undo/back operation (single-step actions)
or confirmation for every action
based on component because that is the view
s after multiple selection + submit action
erences to cgi server + hence delays
r a course can be done at once
Component State Meaning Phase Applicable condition*
DFLT Only one available class 1 #classes(all assoc, comp) = 1
Only one available class 2 #avail(assoc, comp) = 1
Auto-enrolled from selection 2 auto-enrolled
TODO Classes need to be chosen 1, 2 #avail(assoc, comp) > 1
AUTO All classes auto-enrolled 1, 2 every class (> 1) is subject to auto-enrolment
NSOL All classes are full 1 #avail(every assoc, comp) = 0
DONE Class selection made 2 explicit selection
NONE All classes full after selection 2 #avail(assoc, comp) = 0
EXCL Component irrelevant to assoc 2 #classes(assoc, comp) = 0
Phases: 1 State established from class table
2 State established following one or more selections
Enrolment can be posted when all states are { DONE, DFLT, EXCL }
* comp: component
assoc: association established by first selected class
#avail: number of available classes
#classes: number of defined classes
Transitions to this state
fromTO_DO, AUTO
from AUTO
none
none
None: enrolment cannot proceed
from TO_DO
from TO_DO, AUTO
owing one or more selections
tablished by first selected class
Sitar component organisation
Stage 2 Class selection by timetable
Version 1.0 11-Oct-02
Sitar builds this structure for all courses that are in the e-basket. It is based on component because that is the view
presented to the user as representing the overall course structure.
Once the first selection is made, some of the information here is no longer relevant to the user (say due to choice of association).
I haven't decided whether to modify this as the selections occur, or to store all partial selection detail in the ebasket
and filter the component display accordingly.
Each course/term combination has attributes
Field Type Typical values
Term 4n 5034, 5037 etc
Course 8c COMP1011 etc
Session 2c S1, X2 etc (for info only, each course can be taken only once in a term)
Components list one or more
Each component has attributes
Field Type Typical values
Component code 3c LEC, TU1, WEB etc
Selectability enum default only one class of this component, hence no need for selection
auto all classes (> 1) are auto-enrolled from the enrolment class
selectable user can select, although may not need to if multiple associations occur
Duration n.1 1.5 maximum total duration (hrs)of meeting times for any class
Association groups list one or more
Each association group has attributes
Field Type Typical values
Association nbr 2n 1, 99
Classes list one or more
Each class has attributes
Field Type Typical values
Class nbr 5n UNSW class numbers a more applicable value is section ID, as this is displayed to the user, but the class nbr is
start at 1001 the obvious key to use for all class-related info
Sitar display framwork
Stage 2 Class selection by timetable
Version 1.0 11-Oct-02
Overall page configuration and selectable elements
1 Course summary
User must be fully aware for which course classes are currently being selected (active course )
Other course info appears on timetable where selections have been made or are defaulted
Hence need some indication of other course status
Options: (a) Show one-line summary of each course, with active course clearly highlighted
(b) Show course list (with status) on drop-down
In either case the method of changing the active course should be obvious:
(a) Radio button adjacent
(b) Drop-down is a selector
2 Component summary for active course
Gives best top-level view of selection task for students (generally one of each unless disjoint associations)
Must clearly distinguish status: defaulted/selected/to-be-selected
Acts as colour code key for components shown on T/T (see CompPres sheet)
Table with one column per component (practical max: 5 components, most 1 or 2)
Fixed number of rows to spread out info: type, status, section ID, class, selected times
3 Timetable grid
HTML table is versatile enough for this purpose
Columns are time, Mon..Fri and No TT
Rows are on half-hour boundary: all event starting times and durations quantised to this unit
Purposes:
Provides a record of all decisions made so far
Is a worksheet for active course
Heavily abbreviated cell contents to minimise confusion and clutter
Non-active course has course ID, component only, all same reserved colour
Active course has component (colour coded), multiple meeting linkage info, %free and selector button if applicable
Selectable cells contain radio buttons, initially all off
Parallel classes of the same type suppressed
Clashes shown as nested tables (border colour indicates whether acceptable or not)
Issues: How best to indicate multiple meeting times?
How to show that parallel classes exist without clutter?
Should user be able to select any parallel class, or only a timeslot?
How to show odd/even times and phantom clashes?
4 Legend
One-line summary of component codes
Submit button may be here for Mode 2 interaction
Sitar/Ceres - component presentation guidelines
Stage 2
Class selection by timetable
Version 1.0 11-Oct-02
Sitar and Ceres should present a consistent view of each possible component type
including order of presentation and colour coding
Sitar will store this internally
Ceres would probably use an NSS table as defined below
Field Type Typical
values
COMPONENT 3c see below one entry for each translate
SEQNBR 3n see below determines the component display order
NS_RGB 6c see below display colour in #RRGGBB format
Guidelines for selecting colours:
Saturation: 0.3 or less for effective contrast with black text
Brighness (val): usually maximum
Hue: Separate by at least 30 degrees (except for closely related concepts such as related components)
Component groupings (five main types):
Lectures (large groups) yellows can have LE1 + LE2
Tutorials (small groups) blues can have TU1 + TU2
Practical classes pink one of each kind at present
Other on-campus mauve rarely combined with any other component type
Off-campus activities green occasionally combined with other component types
Suggested values
Component SeqNbr RGB
LEC 020 FFFFB3 yellow large-group teaching
LE1 023 FFFFB3 yellow
LE2 024 FFEFB3 beige
TUT 050 C0E0FF blue small-group teaching
TU1 053 C0E0FF blue
TU2 054 B3FFFF turquoise
SEM 056 C0E0FF blue
LAB 100 FFD0D0 pink prac group
TLB 105 FFD0D0 pink
STD 110 FFD0D0 pink
PRJ 150 FFE0FF mauve generally on-campus
IND 160 FFE0FF mauve generally on-campus
HON 170 FFE0FF mauve generally on-campus
THE 180 FFE0FF mauve generally on-campus
DST 200 D0FFD0 green off-campus
WEB 210 D0FFD0 green off-campus
WRK 270 D0FFD0 green off-campus
FLD 280 D0FFD0 green off-campus
OTH 300 FFE0FF mauve
Colours used for screen elements besides active course:
Confirmed (posted) classes DADADA 15% grey
Unposted classes 99CCCC cyan, sat = 0.25 lum = 0.8
Screen background F0FFF0 pale green, may need to revise
T/T background FFFFE6 pale yellow
such as related components)
Sitar class organisation
Stage 2 Class selection by timetable
Version 1.0 11-Oct-02
Version 1.1 14-Oct-02 added days to meeting times
Sitar has access to a simple database that records this data in denormalised form against all classes.
Data is completely static, but will be refreshed frequently (~10 minute cycle)
Each course/term combination has attributes
Field Type Typical values
Term 4n 5034, 5037 etc
Course 8c COMP1011 etc
Class nbr 5n
Section ID 4c
Session 2c S1, X2 etc (for info only, each course can be taken only once in a term)
Association nbr 2n 1, 99
Component 3c
Enrol component? 1b Y, N true if this class is an enrolment class
Optional 1b Y, N (currently assumed to be Y, not on NSSR2922 download but available in CLASS_ASSOC)
Status 1c A, S, T, X active, stop further enrolment, tentative, cancelled
Capacity n
Free places n calculated from #Enr and #Cap
% full 4c 0%, 33%, 100%, rounded and formatted for display, calculated from #Enr and #Cap
FULL
Meeting times list one or more could be more but NSSR2922 limitted to 4, sufficient for all practical purposes
Each meeting time has attributes
Field Type Typical values
Day 3c Mon
Start time 5c (HH:MM) 09:30, 16:00
Duration n 2, 4 half-hour units
Facility descr 10c (empty), K-J17-G02 use Facility Tbl to obtain short/long descriptions and building grid.
Ignore TT clash 1b Y, N new field (not yet on NSSR2922, default N)
Association groups 1c A, E, O all weeks, even weeks, odd weeks (new field, default A)
Related docs
