pointers and thoughts - by Martin Henz

<!--{{{-->
<link rel='alternate' type='application/rss+xml' title='RSS' href='index.xml'/>
<!--}}}-->

Background: #fff
Foreground: #000
PrimaryPale: #8cf
PrimaryLight: #18f
PrimaryMid: #04b
PrimaryDark: #014
SecondaryPale: #ffc
SecondaryLight: #fe8
SecondaryMid: #db4
SecondaryDark: #841
TertiaryPale: #eee
TertiaryLight: #ccc
TertiaryMid: #999
TertiaryDark: #666
Error: #f88

/*{{{*/
body {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}

a {color:[[ColorPalette::PrimaryMid]];}
a:hover {background-color:[[ColorPalette::PrimaryMid]]; color:[[ColorPalette::Background]];}
a img {border:0;}

h1,h2,h3,h4,h5,h6 {color:[[ColorPalette::SecondaryDark]]; background:transparent;}
h1 {border-bottom:2px solid [[ColorPalette::TertiaryLight]];}
h2,h3 {border-bottom:1px solid [[ColorPalette::TertiaryLight]];}

.button {color:[[ColorPalette::PrimaryDark]]; border:1px solid [[ColorPalette::Background]];}
.button:hover {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::SecondaryLight]]; border-color:[[ColorPalette::SecondaryMid]];}
.button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::SecondaryDark]];}

.header {background:[[ColorPalette::PrimaryMid]];}
.headerShadow {color:[[ColorPalette::Foreground]];}
.headerShadow a {font-weight:normal; color:[[ColorPalette::Foreground]];}
.headerForeground {color:[[ColorPalette::Background]];}
.headerForeground a {font-weight:normal; color:[[ColorPalette::PrimaryPale]];}

.tabSelected{color:[[ColorPalette::PrimaryDark]];
	background:[[ColorPalette::TertiaryPale]];
	border-left:1px solid [[ColorPalette::TertiaryLight]];
	border-top:1px solid [[ColorPalette::TertiaryLight]];
	border-right:1px solid [[ColorPalette::TertiaryLight]];
}
.tabUnselected {color:[[ColorPalette::Background]]; background:[[ColorPalette::TertiaryMid]];}
.tabContents {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::TertiaryPale]]; border:1px solid [[ColorPalette::TertiaryLight]];}
.tabContents .button {border:0;}

#sidebar {}
#sidebarOptions input {border:1px solid [[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel {background:[[ColorPalette::PrimaryPale]];}
#sidebarOptions .sliderPanel a {border:none;color:[[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel a:hover {color:[[ColorPalette::Background]]; background:[[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel a:active {color:[[ColorPalette::PrimaryMid]]; background:[[ColorPalette::Background]];}

.wizard {background:[[ColorPalette::PrimaryPale]]; border:1px solid [[ColorPalette::PrimaryMid]];}
.wizard h1 {color:[[ColorPalette::PrimaryDark]]; border:none;}
.wizard h2 {color:[[ColorPalette::Foreground]]; border:none;}
.wizardStep {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];
	border:1px solid [[ColorPalette::PrimaryMid]];}
.wizardStep.wizardStepDone {background:[[ColorPalette::TertiaryLight]];}
.wizardFooter {background:[[ColorPalette::PrimaryPale]];}
.wizardFooter .status {background:[[ColorPalette::PrimaryDark]]; color:[[ColorPalette::Background]];}
.wizard .button {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::SecondaryLight]]; border: 1px solid;
	border-color:[[ColorPalette::SecondaryPale]] [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryPale]];}
.wizard .button:hover {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::Background]];}
.wizard .button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::Foreground]]; border: 1px solid;
	border-color:[[ColorPalette::PrimaryDark]] [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryDark]];}

#messageArea {border:1px solid [[ColorPalette::SecondaryMid]]; background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]];}
#messageArea .button {color:[[ColorPalette::PrimaryMid]]; background:[[ColorPalette::SecondaryPale]]; border:none;}

.popupTiddler {background:[[ColorPalette::TertiaryPale]]; border:2px solid [[ColorPalette::TertiaryMid]];}

.popup {background:[[ColorPalette::TertiaryPale]]; color:[[ColorPalette::TertiaryDark]]; border-left:1px solid [[ColorPalette::TertiaryMid]]; border-top:1px solid [[ColorPalette::TertiaryMid]]; border-right:2px solid [[ColorPalette::TertiaryDark]]; border-bottom:2px solid [[ColorPalette::TertiaryDark]];}
.popup hr {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::PrimaryDark]]; border-bottom:1px;}
.popup li.disabled {color:[[ColorPalette::TertiaryMid]];}
.popup li a, .popup li a:visited {color:[[ColorPalette::Foreground]]; border: none;}
.popup li a:hover {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; border: none;}
.popup li a:active {background:[[ColorPalette::SecondaryPale]]; color:[[ColorPalette::Foreground]]; border: none;}
.popupHighlight {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
.listBreak div {border-bottom:1px solid [[ColorPalette::TertiaryDark]];}

.tiddler .defaultCommand {font-weight:bold;}

.shadow .title {color:[[ColorPalette::TertiaryDark]];}

.title {color:[[ColorPalette::SecondaryDark]];}
.subtitle {color:[[ColorPalette::TertiaryDark]];}

.toolbar {color:[[ColorPalette::PrimaryMid]];}
.toolbar a {color:[[ColorPalette::TertiaryLight]];}
.selected .toolbar a {color:[[ColorPalette::TertiaryMid]];}
.selected .toolbar a:hover {color:[[ColorPalette::Foreground]];}

.tagging, .tagged {border:1px solid [[ColorPalette::TertiaryPale]]; background-color:[[ColorPalette::TertiaryPale]];}
.selected .tagging, .selected .tagged {background-color:[[ColorPalette::TertiaryLight]]; border:1px solid [[ColorPalette::TertiaryMid]];}
.tagging .listTitle, .tagged .listTitle {color:[[ColorPalette::PrimaryDark]];}
.tagging .button, .tagged .button {border:none;}

.footer {color:[[ColorPalette::TertiaryLight]];}
.selected .footer {color:[[ColorPalette::TertiaryMid]];}

.sparkline {background:[[ColorPalette::PrimaryPale]]; border:0;}
.sparktick {background:[[ColorPalette::PrimaryDark]];}

.error, .errorButton {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::Error]];}
.warning {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::SecondaryPale]];}
.lowlight {background:[[ColorPalette::TertiaryLight]];}

.zoomer {background:none; color:[[ColorPalette::TertiaryMid]]; border:3px solid [[ColorPalette::TertiaryMid]];}

.imageLink, #displayArea .imageLink {background:transparent;}

.annotation {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; border:2px solid [[ColorPalette::SecondaryMid]];}

.viewer .listTitle {list-style-type:none; margin-left:-2em;}
.viewer .button {border:1px solid [[ColorPalette::SecondaryMid]];}
.viewer blockquote {border-left:3px solid [[ColorPalette::TertiaryDark]];}

.viewer table, table.twtable {border:2px solid [[ColorPalette::TertiaryDark]];}
.viewer th, .viewer thead td, .twtable th, .twtable thead td {background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::Background]];}
.viewer td, .viewer tr, .twtable td, .twtable tr {border:1px solid [[ColorPalette::TertiaryDark]];}

.viewer pre {border:1px solid [[ColorPalette::SecondaryLight]]; background:[[ColorPalette::SecondaryPale]];}
.viewer code {color:[[ColorPalette::SecondaryDark]];}
.viewer hr {border:0; border-top:dashed 1px [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::TertiaryDark]];}

.highlight, .marked {background:[[ColorPalette::SecondaryLight]];}

.editor input {border:1px solid [[ColorPalette::PrimaryMid]];}
.editor textarea {border:1px solid [[ColorPalette::PrimaryMid]]; width:100%;}
.editorFooter {color:[[ColorPalette::TertiaryMid]];}

#backstageArea {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::TertiaryMid]];}
#backstageArea a {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::Background]]; border:none;}
#backstageArea a:hover {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; }
#backstageArea a.backstageSelTab {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
#backstageButton a {background:none; color:[[ColorPalette::Background]]; border:none;}
#backstageButton a:hover {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::Background]]; border:none;}
#backstagePanel {background:[[ColorPalette::Background]]; border-color: [[ColorPalette::Background]] [[ColorPalette::TertiaryDark]] [[ColorPalette::TertiaryDark]] [[ColorPalette::TertiaryDark]];}
.backstagePanelFooter .button {border:none; color:[[ColorPalette::Background]];}
.backstagePanelFooter .button:hover {color:[[ColorPalette::Foreground]];}
#backstageCloak {background:[[ColorPalette::Foreground]]; opacity:0.6; filter:'alpha(opacity:60)';}
/*}}}*/

/*{{{*/
* html .tiddler {height:1%;}

body {font-size:.75em; font-family:arial,helvetica; margin:0; padding:0;}

h1,h2,h3,h4,h5,h6 {font-weight:bold; text-decoration:none;}
h1,h2,h3 {padding-bottom:1px; margin-top:1.2em;margin-bottom:0.3em;}
h4,h5,h6 {margin-top:1em;}
h1 {font-size:1.35em;}
h2 {font-size:1.25em;}
h3 {font-size:1.1em;}
h4 {font-size:1em;}
h5 {font-size:.9em;}

hr {height:1px;}

a {text-decoration:none;}

dt {font-weight:bold;}

ol {list-style-type:decimal;}
ol ol {list-style-type:lower-alpha;}
ol ol ol {list-style-type:lower-roman;}
ol ol ol ol {list-style-type:decimal;}
ol ol ol ol ol {list-style-type:lower-alpha;}
ol ol ol ol ol ol {list-style-type:lower-roman;}
ol ol ol ol ol ol ol {list-style-type:decimal;}

.txtOptionInput {width:11em;}

#contentWrapper .chkOptionInput {border:0;}

.externalLink {text-decoration:underline;}

.indent {margin-left:3em;}
.outdent {margin-left:3em; text-indent:-3em;}
code.escaped {white-space:nowrap;}

.tiddlyLinkExisting {font-weight:bold;}
.tiddlyLinkNonExisting {font-style:italic;}

/* the 'a' is required for IE, otherwise it renders the whole tiddler in bold */
a.tiddlyLinkNonExisting.shadow {font-weight:bold;}

#mainMenu .tiddlyLinkExisting,
	#mainMenu .tiddlyLinkNonExisting,
	#sidebarTabs .tiddlyLinkNonExisting {font-weight:normal; font-style:normal;}
#sidebarTabs .tiddlyLinkExisting {font-weight:bold; font-style:normal;}

.header {position:relative;}
.header a:hover {background:transparent;}
.headerShadow {position:relative; padding:4.5em 0em 1em 1em; left:-1px; top:-1px;}
.headerForeground {position:absolute; padding:4.5em 0em 1em 1em; left:0px; top:0px;}

.siteTitle {font-size:3em;}
.siteSubtitle {font-size:1.2em;}

#mainMenu {position:absolute; left:0; width:10em; text-align:right; line-height:1.6em; padding:1.5em 0.5em 0.5em 0.5em; font-size:1.1em;}

#sidebar {position:absolute; right:3px; width:16em; font-size:.9em;}
#sidebarOptions {padding-top:0.3em;}
#sidebarOptions a {margin:0em 0.2em; padding:0.2em 0.3em; display:block;}
#sidebarOptions input {margin:0.4em 0.5em;}
#sidebarOptions .sliderPanel {margin-left:1em; padding:0.5em; font-size:.85em;}
#sidebarOptions .sliderPanel a {font-weight:bold; display:inline; padding:0;}
#sidebarOptions .sliderPanel input {margin:0 0 .3em 0;}
#sidebarTabs .tabContents {width:15em; overflow:hidden;}

.wizard {padding:0.1em 1em 0em 2em;}
.wizard h1 {font-size:2em; font-weight:bold; background:none; padding:0em 0em 0em 0em; margin:0.4em 0em 0.2em 0em;}
.wizard h2 {font-size:1.2em; font-weight:bold; background:none; padding:0em 0em 0em 0em; margin:0.4em 0em 0.2em 0em;}
.wizardStep {padding:1em 1em 1em 1em;}
.wizard .button {margin:0.5em 0em 0em 0em; font-size:1.2em;}
.wizardFooter {padding:0.8em 0.4em 0.8em 0em;}
.wizardFooter .status {padding:0em 0.4em 0em 0.4em; margin-left:1em;}
.wizard .button {padding:0.1em 0.2em 0.1em 0.2em;}

#messageArea {position:fixed; top:2em; right:0em; margin:0.5em; padding:0.5em; z-index:2000; _position:absolute;}
.messageToolbar {display:block; text-align:right; padding:0.2em 0.2em 0.2em 0.2em;}
#messageArea a {text-decoration:underline;}

.tiddlerPopupButton {padding:0.2em 0.2em 0.2em 0.2em;}
.popupTiddler {position: absolute; z-index:300; padding:1em 1em 1em 1em; margin:0;}

.popup {position:absolute; z-index:300; font-size:.9em; padding:0; list-style:none; margin:0;}
.popup .popupMessage {padding:0.4em;}
.popup hr {display:block; height:1px; width:auto; padding:0; margin:0.2em 0em;}
.popup li.disabled {padding:0.4em;}
.popup li a {display:block; padding:0.4em; font-weight:normal; cursor:pointer;}
.listBreak {font-size:1px; line-height:1px;}
.listBreak div {margin:2px 0;}

.tabset {padding:1em 0em 0em 0.5em;}
.tab {margin:0em 0em 0em 0.25em; padding:2px;}
.tabContents {padding:0.5em;}
.tabContents ul, .tabContents ol {margin:0; padding:0;}
.txtMainTab .tabContents li {list-style:none;}
.tabContents li.listLink { margin-left:.75em;}

#contentWrapper {display:block;}
#splashScreen {display:none;}

#displayArea {margin:1em 17em 0em 14em;}

.toolbar {text-align:right; font-size:.9em;}

.tiddler {padding:1em 1em 0em 1em;}

.missing .viewer,.missing .title {font-style:italic;}

.title {font-size:1.6em; font-weight:bold;}

.missing .subtitle {display:none;}
.subtitle {font-size:1.1em;}

.tiddler .button {padding:0.2em 0.4em;}

.tagging {margin:0.5em 0.5em 0.5em 0; float:left; display:none;}
.isTag .tagging {display:block;}
.tagged {margin:0.5em; float:right;}
.tagging, .tagged {font-size:0.9em; padding:0.25em;}
.tagging ul, .tagged ul {list-style:none; margin:0.25em; padding:0;}
.tagClear {clear:both;}

.footer {font-size:.9em;}
.footer li {display:inline;}

.annotation {padding:0.5em; margin:0.5em;}

* html .viewer pre {width:99%; padding:0 0 1em 0;}
.viewer {line-height:1.4em; padding-top:0.5em;}
.viewer .button {margin:0em 0.25em; padding:0em 0.25em;}
.viewer blockquote {line-height:1.5em; padding-left:0.8em;margin-left:2.5em;}
.viewer ul, .viewer ol {margin-left:0.5em; padding-left:1.5em;}

.viewer table, table.twtable {border-collapse:collapse; margin:0.8em 1.0em;}
.viewer th, .viewer td, .viewer tr,.viewer caption,.twtable th, .twtable td, .twtable tr,.twtable caption {padding:3px;}
table.listView {font-size:0.85em; margin:0.8em 1.0em;}
table.listView th, table.listView td, table.listView tr {padding:0px 3px 0px 3px;}

.viewer pre {padding:0.5em; margin-left:0.5em; font-size:1.2em; line-height:1.4em; overflow:auto;}
.viewer code {font-size:1.2em; line-height:1.4em;}

.editor {font-size:1.1em;}
.editor input, .editor textarea {display:block; width:100%; font:inherit;}
.editorFooter {padding:0.25em 0em; font-size:.9em;}
.editorFooter .button {padding-top:0px; padding-bottom:0px;}

.fieldsetFix {border:0; padding:0; margin:1px 0px 1px 0px;}

.sparkline {line-height:1em;}
.sparktick {outline:0;}

.zoomer {font-size:1.1em; position:absolute; overflow:hidden;}
.zoomer div {padding:1em;}

* html #backstage {width:99%;}
* html #backstageArea {width:99%;}
#backstageArea {display:none; position:relative; overflow: hidden; z-index:150; padding:0.3em 0.5em 0.3em 0.5em;}
#backstageToolbar {position:relative;}
#backstageArea a {font-weight:bold; margin-left:0.5em; padding:0.3em 0.5em 0.3em 0.5em;}
#backstageButton {display:none; position:absolute; z-index:175; top:0em; right:0em;}
#backstageButton a {padding:0.1em 0.4em 0.1em 0.4em; margin:0.1em 0.1em 0.1em 0.1em;}
#backstage {position:relative; width:100%; z-index:50;}
#backstagePanel {display:none; z-index:100; position:absolute; margin:0em 3em 0em 3em; padding:1em 1em 1em 1em;}
.backstagePanelFooter {padding-top:0.2em; float:right;}
.backstagePanelFooter a {padding:0.2em 0.4em 0.2em 0.4em;}
#backstageCloak {display:none; z-index:20; position:absolute; width:100%; height:100px;}

.whenBackstage {display:none;}
.backstageVisible .whenBackstage {display:block;}
/*}}}*/

/***
StyleSheet for use when a translation requires any css style changes.
This StyleSheet can be used directly by languages such as Chinese, Japanese and Korean which need larger font sizes.
***/
/*{{{*/
body {font-size:0.8em;}
#sidebarOptions {font-size:1.05em;}
#sidebarOptions a {font-style:normal;}
#sidebarOptions .sliderPanel {font-size:0.95em;}
.subtitle {font-size:0.8em;}
.viewer table.listView {font-size:0.95em;}
/*}}}*/

/*{{{*/
@media print {
#mainMenu, #sidebar, #messageArea, .toolbar, #backstageButton, #backstageArea {display: none ! important;}
#displayArea {margin: 1em 1em 0em 1em;}
/* Fixes a feature in Firefox 1.5.0.2 where print preview displays the noscript content */
noscript {display:none;}
}
/*}}}*/

<!--{{{-->
<div class='header' macro='gradient vert [[ColorPalette::PrimaryLight]] [[ColorPalette::PrimaryMid]]'>
<div class='headerShadow'>
<span class='siteTitle' refresh='content' tiddler='SiteTitle'></span>&nbsp;
<span class='siteSubtitle' refresh='content' tiddler='SiteSubtitle'></span>
</div>
<div class='headerForeground'>
<span class='siteTitle' refresh='content' tiddler='SiteTitle'></span>&nbsp;
<span class='siteSubtitle' refresh='content' tiddler='SiteSubtitle'></span>
</div>
</div>
<div id='mainMenu' refresh='content' tiddler='MainMenu'></div>
<div id='sidebar'>
<div id='sidebarOptions' refresh='content' tiddler='SideBarOptions'></div>
<div id='sidebarTabs' refresh='content' force='true' tiddler='SideBarTabs'></div>
</div>
<div id='displayArea'>
<div id='messageArea'></div>
<div id='tiddlerDisplay'></div>
</div>
<!--}}}-->

<!--{{{-->
<div class='toolbar' macro='toolbar closeTiddler closeOthers +editTiddler > fields syncing permalink references jump'></div>
<div class='title' macro='view title'></div>
<div class='subtitle'><span macro='view modifier link'></span>, <span macro='view modified date'></span> (<span macro='message views.wikified.createdPrompt'></span> <span macro='view created date'></span>)</div>
<div class='tagging' macro='tagging'></div>
<div class='tagged' macro='tags'></div>
<div class='viewer' macro='view text wikified'></div>
<div class='tagClear'></div>
<!--}}}-->

<!--{{{-->
<div class='toolbar' macro='toolbar +saveTiddler -cancelTiddler deleteTiddler'></div>
<div class='title' macro='view title'></div>
<div class='editor' macro='edit title'></div>
<div macro='annotations'></div>
<div class='editor' macro='edit text'></div>
<div class='editor' macro='edit tags'></div><div class='editorFooter'><span macro='message views.editor.tagPrompt'></span><span macro='tagChooser'></span></div>
<!--}}}-->

To get started with this blank TiddlyWiki, you'll need to modify the following tiddlers:
* SiteTitle & SiteSubtitle: The title and subtitle of the site, as shown above (after saving, they will also appear in the browser title bar)
* MainMenu: The menu (usually on the left)
* DefaultTiddlers: Contains the names of the tiddlers that you want to appear when the TiddlyWiki is opened
You'll also need to enter your username for signing your edits: <<option txtUserName>>

These InterfaceOptions for customising TiddlyWiki are saved in your browser

Your username for signing your edits. Write it as a WikiWord (eg JoeBloggs)

<<option txtUserName>>
<<option chkSaveBackups>> SaveBackups
<<option chkAutoSave>> AutoSave
<<option chkRegExpSearch>> RegExpSearch
<<option chkCaseSensitiveSearch>> CaseSensitiveSearch
<<option chkAnimate>> EnableAnimations

----
Also see AdvancedOptions

<<importTiddlers>>

* Graduate modules sometimes pose informal non-overlap constraints. For example, grad students taking ~CS5341 Comp. Photography would also be interested in ~CS5245 Vision and Graphics for Special Effects. There is currently no workflow to capture such constraints. Need to take this up to ~SoC grad office. Wee Kheng suggests to organize the modules into "bags" which represent non-overlap constraints. Raymond would take these bags into account during timetabling.

Modules are assigned to academic staff (as [[coordinators|Module Coordinator of CS Department]] and lecturers) in an annual exercise in April/May before each academic year. Prior to the module assignment, the [[Teaching Coordinator of CS Department]] identifies the modules to be mounted, see [[Module Offering and Mounting of CS Department]].

In April, the module coordinator invites the academic staff to state their preferences for teaching by using the [[Module Preference|https://mysoc.nus.edu.sg/~teachadm/lecturer/lect_pref_1.php]] component of the Teaching Admin System. After that, the [[Teaching Coordinator of CS Department]] assigns the modules to the academic staff, considering the teaching needs of the School and the workload and preferences of the academic staff. 

The teaching assignment is then published in the [[Schedule of Classes|http://www.comp.nus.edu.sg/~online/course_list/courses.html]] (for Semester III and IV, click on "Semesters III & IV" at the top).

After that, the [[Timetable Coordinator]] of the School manages the timetabling (assignment of lecture times and venues), in coordination with Registrars Office, around May for Semesters 1 and 2 of the following Academic Year. The final timetable is also published in the [[Schedule of Classes|http://www.comp.nus.edu.sg/~online/course_list/courses.html]].

Request by module coord:  anita jagannadhan <meet_janita5@yahoo.co.in> as lab TA

Request from EE student De Silva Ransi Nilaksha <ransidesilva@nus.edu.sg> to be TA. Asked Sun Teck if he needs him.

Sun Teck says:   I think he is fine as he had done it last semester
and we did not receive any negative feedback from students.
Yes. It is not easy to get TAs to teach C++.
   Can we have Anshul Nigham for cs1102C this semester. He
had done a good job last semester. I am not sure if Ye Nan
will be around, if yes, he is also very good for cs1102C.
   Also, as I am doing two modules (cs1102y and cs1102C)
this semester, please do not assign any tutorial session
to me as what was done last semester.

Assigned Anshul Nigham anshulni@comp.nus.edu.sg

12 groups

Lectures and tutorials provided by Math department. 
Contact: Zhu Chengbo, Prof and Deputy Head, mailto:matzhucb@nus.edu.sg

Razvan wants TAs for all tutorials, see [[CS3211]]

Razvan wants to teach all tutorials, see [[CS2104]]

Module entails discussion groups. Martin asked MC Tan Chuan Hoo mailto:tanch@comp.nus.edu.sg who would be suitable. Chuan Hoo answered that he needs the TAs Tan Wee Kek and Tong Yu, who have already started working on the module.

Helpdesk students:  we can make do with
four: Yang Zhenbin (U065315H), Ho Zhi Wei (U057081E), Ng Chee Pheng
Samuel (U065230U), and Wang Deliang (U047057M)

Requires experienced TA; some preparation work before the semester; overhead for learning CS3215 for each new TA to be considered in the assignment process.

Tentative assignment for Sem 2 2007/2008: TA Beatrice Luca mailto:lucabeat@comp.nus.edu.sg

DONE: Assigned Beatrice

Module requires special qualifications from TA, which are met by a candidate identified by the module coordinator. The candidate will be offered a [[Part-time Tutor II]] position. Module coordinator Ben confirmed the number of hours as follows:
*  Grading of assignment 1 (27 submissions): 15 hours
*  Grading of assignment 2 (18 submissions): 10 hours
*  Grading of assignment 3 (18 submissions): 10 hours
*  Course admin: 13 hours (est 1 hour per week)
*  Preparation of course material/assignments : 20 hours
*  Meeting with project teams (est 18 teams, fortnightly for 6 weeks) = 3 x 18 = 54 hours
*  Grading of project proposals (18 submissions): 10 hours
*  Total requested = 15+10+10+13+20+54 +10 = 132.

The module may need a tutor, depending on the number of students; quota issue. Martin asked Ashraf for name of suitable grad student

This is a required module in the curriculum of the 4-year programmes of the School of Computing for students of the 2004 and earlier regular intake, and the 2005 and earlier poly intake. The exception to this is the Computational Biology programme, which ''does not'' require CS4102.

The aim of this module is to provide students with practical technical and management experience, in the environment of academic learning. Students will get the opportunities to manage computer laboratories, as well as conduct and manage practical sessions and tutorial groups.

This module is assigned upon allocation of Honours project (~CS4101) or Head's approval. The CS4102 requirements are met if the assigned teaching is conducted adequately in one semester, as confirmed by the respective module coordinator.

The Module Coordinator for CS4102 is always the [[School of Computing Teaching Coordinator]].
----
Students can meet their [[CS4102]] requirement by serving as [[Undergraduate Discussion Leader]].

MC Klarissa Chang mailto:changtt@comp.nus.edu.sg asked for 30 discussion groups. Martin asked her for names of suitable grad students.

Klarissa: grad student Xu Lingling (unix id: xuling0)

Status: DONE
Xu Lingling as sole tutor assigned.

!! Sem 2 2007/2008
Dean is module coordinator; Martin asked him in late 2007 whether to go ahead with the module, given the fact that Dean is exempted from teaching. Dean asked to go ahead with the module, and move it to Wednesday (done).

Instructor TOK Wee Hyong will assist in the labs (database administration) and marking. Martin asked Dean how many hours to allocate for Wee Hyong per week.

Current estimate of workload by MC:
could be around 4x 7 weeks +  marking of programming assignments
(more like testing them on oracle -- the assignment is yet to be
assigned)

Status: DONE
Wee Hyong assigned

The Department Teaching Coordinators handle the following activities:
* Module Offering and Mounting
* Assigning Modules to Academic Staff
* Hiring Teaching Assistants
* Handling Teaching Track Applications
* Coordinating the [[Overseas Graduate Scholarships
----
The [[Teaching Coordinator of CS Department]] is Associate Professor [[Martin Henz|mailto:henz@comp.nus.edu.sg]], and the Teaching Coordinator for the Department of Information Systems is Associate Professor [[Teo Hock Hai|mailto:teohh@comp.nus.edu.sg]].

The [[Teaching Coordinator of CS Department]] assists the Office of HR of the School by reviewing applications, shortlisting candidates and chairing interview sessions. The Interview Committee consists of:
* [[Teaching Coordinator of CS Department]] (chair)
* Tan Tiow Seng
* Tan Tuck Choy, Aaron
The process is supported by the HR Office of the School of Computing through Nasila D/O Samuvallu and Lim Pei Ying. All payment matters are handled by the Head of Department through Heads Meeting.

The [[Teaching Coordinator of CS Department]] coordinates the hiring of Teaching Assistants. Together with his colleagues in the Committee for hiring Teaching Assistants, he reviews the applications, shortlists candidates and chairs the interview sessions. The Interview Committee currently consists of:
* [[Teaching Coordinator of CS Department]] Martin Henz (chair)
* Teo Yong Meng
* Tan Tuck Choy, Aaron
The process is supported by the HR Office of the School of Computing through Nasila D/O Samuvallu and Lim Pei Ying. All payment matters are handled by the Head of Department through Heads Meeting.

TA Sathish is requested by module coordinator (co-author of textbook)

Sent Hung Pheng a list of students to choose from in addition to TA Sathish

Hung Pheng says:

Thank you very much for your support.  The figure stands at 221 now and it
looks like I need 11 tutorial classes at the moment.  However, it depends
very much on tonight's figure after today's bidding.
I don't know any of the students listed by you.  Moreover, I do not know how
many hours the Ph D students can help although I know for HY students it is
only 2 hours per week (i.e. max. take care of two tutorial classes). Based
on qualification and experience, of course I would prefer to hire the
graduate student.
There is one student on the list who prefers marking.  As I will need
marking support also (for assignments as well as term test), perhaps you can
reserve him for me if possible.  Last semester with about the same
enrollment, I have four HY students assisting my marking.

Hung Pheng says:

The final count is 220 and I am planning 11 classes (or if there are
sufficient dropouts like we experienced before, I may cut one to fit team
formation within classes).
I don't know if you have any TA to spare?  A TA taking 5 classes (and
Sathish another 5) will leave just one for myself to take care.

Dear Colleagues,

staff members are expected on average to teach a series of lectures 
and take 2 tutorial classes. 

For core/lower level modules, full-time TAs will be provided to
assist in the tutorials. For others, parttime TAs will be used if needed.

In addition to the lectures and tutorials, staff members are required to
handle up to 40 hours of grading (~150 scripts) of assignments, quizzes,
tests, and exams.  You may request for additional support if you envisage
marking beyond that. The enrolment figures will be firmed up after 13th 
August.
 
Please email me with the following info in the template shown if you need 
support, so that I can gauge the amount and budget required.
 
(example)
cs1111   enrolment 75
activity      %tage   no. of scripts   marked by:
--------      -----   --------------   ---------
final exam    50%     75 scripts      lecturer (20 hours)
quiz 1        15%     75 scripts      lecturer (10 hours)
quiz 2        15%     75 scripts      lecturer (10 hours)
assignment 1  10%     75 scripts      parttime (8 hours)
assignment 2  10%     75 scripts      parttime (8 hours)

It would be helpful if you could provide me with the name of the Ph.D
student you have in mind for the support.


regards,

Martin Henz
Teaching Coordinator

!! External Staff
See
https://mysoc.nus.edu.sg/~teachadm/admin/edit_ext_tutor_1.php?tutor_id=wangqiuh
The drop-down does not include all the teaching staff classes that we agreed on. Can you update.

Status: Open
!! CA/Exam for ~CS1102S
Martin has trouble entering CA/Exam info for ~CS1102S and asks Philip for help. Philip answers with clarification on how to use the system. Martin suggests changes in wording. Philip updates. Martin asks about the workflow if CA is above 60%. Philip says that he will build an email notification for Mun Bak and Agnes for CA above 60%.

Status: Open
!! ~CS4102 Prerequisite
Martin asked Philip (cc to Siau Cheng) whether the ~CS4102 prerequisite "Upon allocation of Honours project (~CS4101) or Head's approval" is implemented.

Status: Open
!! Access Rights to System
Martin asked Philip who has access to the component "Part-Time/Honors Tutors". Philip answers that all undergrad and postgrad students have access as long as they have an ~SoC ID.

Status: Closed on 2/1/08
!! ~CS1102S not Shown
~CS1102S is not listed in "Tutor Preference".

Status: Closed by bug fix by Philip on 2/1/08
!! Outdated Descriptions of Modules
The page https://mysoc.nus.edu.sg/~teachadm/lecturer/offering_1.php contains a link to https://mysoc.nus.edu.sg/~teachadm/announcement/description.html which is outdated.

Philip says the proper module info is at:
http://www.nus.edu.sg/nusbulletin/ and
http://www.comp.nus.edu.sg/~online/course_list/

Martin asked Philip to remove the link. Philip replaces the link by a link to the NUS Bulletin, as well as ~SoC module descriptions.

Status: Closed on 2/1/08
!! Obsolete Module Quota Feature
Coordinator -> Module -> Modules Quota
Martin asked Philip about the feature. Philip says it is outdated. Martin asked Philip to remove the feature.

Status: Closed by Philip by removing the feature on 2/1/08
!! Postdoc Fellow: Access to Lecturer Features
Martin asks Philip to add Post-doc as an option for "Create External Teaching Staff". Philip adds the feature. Martin asks whether the such added people have access to the Lecturer features. This will be needed when post-docs teach more, as is planned. Philip answers with [[Staff With Teaching Credentials]]. Martin asks him to add the LKY Fellows to the list.

Status: Closed by Philip 3/1/08
!! Renamings
Teaching Admin System, menu on the left:
"Lecturer" -> "Module Coordinator" (Lecturer is a designation, but we are dealing with a role
here).
In the menu on the right, can you rename
"Lecture Preference" to "Module Preference".
Also do the renaming in the target page.
Philip does renaming, but "Lecture Preference" is still there. Also to be done:
View Lecture Preference -> View Module Preference
Modules Mounting -> Module Mounting
"Part-Time/Honors Tutor" to "Teaching Support Student"

The description under Teaching Preference should read:

This system allows you to apply for the position of Teaching Support Student to
meet the requirements for CS4102 and/or to gain teaching
experience. The position is paid at an hourly rate.

Please fill up as many fields...

Status: Closed by Philip on 3/1/08
!! Do we need UDL separate from Other Activities?
Martin proposed to merge the Lab, Tut Preference form with the UDL preference form. Proposal to Aaron. Aaron points out that UDL is managed by [[Module Coordinator of CS Department]]. Martin updates the workflow accordingly.

Status: Closed by Aaron on 4/1/08.
!! ~CS1102 Missing
How come
~CS1102
is not included in
http://www.comp.nus.edu.sg/~online/course_list/courses.html ?

It is mounted and assigned a module coordinator. Philip says it is not in RO database. Martin asks Mui Kiat to check with RO. This led to a discussion with Siau Cheng and others on the modules ~CS1102X, ~CS1102Y, etc. Siau Cheng will bring this to the Curriculum Committee to decide for AY 2008/2009. For AY 2007/2008, things remain as they are.

Status: Closed by Siau Cheng on 4/1/08
!! ~CA-Exam Weightage Feature
Martin asked Philip about the workflow for this feature. Philip referred to Mun Bak and Mui Kiat. Martin asked Mun Bak and Mui Kiat about the workflow.

The workflow needs to be documented in these pages.

Status: Closed by Martin on 4/1/08 by documenting weightage assignment.
!! Student Preferences List All Modules
The page at
https://mysoc.nus.edu.sg/~teachadm/rs/teach_req_1.php
lists all modules, not just the ones in the working semester. Martin asked Philip to change this so that only modules actually offered in the working semester are displayed. Philip informs Martin about Teaching Support Student Vacancies component.

Status: Closed by Philip on 4/1/08
!! Canceling of exams when CA is 100%
Agnes sent reminder to Raymond to remove final exam. Martin asks Agnes about the workflow. Agnes explains and martin updates documentation.

Status: Closed by Agnes on 7/1/08 by explaining workflow to martin.
!! Announcements
Martin asks Philip how announcements are made for https://mysoc.nus.edu.sg/~teachadm/ Philip says that this feature does no work any longer. Martin asks Philip to remove the obsolete announcements in the page. Philip does that and updates "Policies". Martin asks him to remove a couple of entries under policies.

Status: Closed by Philip by removing the items on 7/1/08.

The module coordinator is typically also the main lecturer of the module.
Modules with more than two [[teaching activities|Teaching Activities]] in addition to the lecture are typically supported by additional [[teaching staff|Staff With Teaching Credentials]],  [[Teaching Assistants of SoC]] or [[Student Teaching Support]]. The allocation of [[teaching support activities|Teaching Activities]], except [[UDL|Undergraduate Discussion Leader]], is handled by the [[School of Computing Teaching Coordinator]] of the School. The allocation of [[UDL|Undergraduate Discussion Leader]]s is done by the module coordinator of the modules that use ~UDLs. The workflow for all other teaching support activities is as follows:
* Until 10 days (Friday) before start of Week 1 of the semester, the module coordinator states the kind of teaching support required for the module through the [[Manpower Request|https://mysoc.nus.edu.sg/~teachadm/lecturer/mpreq_1.php]] form of the Teaching Admin System. The [[School of Computing Teaching Coordinator]] sends a [[reminder|Reminder for Manpower Request]] to mailto:academic-l@comp.nus.edu.sg a few days before this deadline.
* The [[School of Computing Teaching Coordinator]] removes modules that are not suitable for student teaching support, or that are already allocated to students from the available choices using the [[Teaching Support Students Vacancies|https://mysoc.nus.edu.sg/~teachadm/admin/ptta_alloc_1.php]] module of the [[Teaching Administration System]] (only accessible by the [[School of Computing Teaching Coordinator]] and the [[Department Teaching Coordinator]]s).
* Until 3 days (Friday) before start of Week 1 of the semester, the [[Teaching Assistants of SoC]] and students involved in [[Student Teaching Support]] state their preferences through the [[Tutorial Preference form for Teaching Assistants|https://mysoc.nus.edu.sg/~teachadm/tutor/tut_pref_1.php]] and the [[Tutorial Preference form for students involved in Student Teaching Support|https://mysoc.nus.edu.sg/~teachadm/rs/teach_req_1.php]]. The [[School of Computing Teaching Coordinator]] sends a [[reminder|Reminder for Student Preferences]] to {{{comp3-l, comp4-l, cec3-l, cec4-l, postgrad-l}}} and a [[reminder|Reminder for TA Preferences]] to {{{ta-cs-l, ta-is-l}}} a few days before this deadline.
* The [[School of Computing Teaching Coordinator]] inquires the Administrative Officer in charge of the [[CS4102]] requirement (currently [[Pamela Lim|mailto:plimmf@comp.nus.edu.sg]]) for the list of [[UDL|Undergraduate Discussion Leader]]s, so that they are not allocated to any other duties. [Note that students can meet their [[CS4102]] requirement using UDL.] The [[School of Computing Teaching Coordinator]] also requests a list of students that need to meet their [[CS4102]] requirement in the coming semester in order to graduate.
* After enrollment figures are stabilized, the [[School of Computing Teaching Coordinator]] assigns Teaching Assistants and students to the [[teaching support activities|Teaching Activities]].
* At the end of Week 1, the [[School of Computing Teaching Coordinator]] asks the module coordinators to request for grading support in an [[email|Invitation for Requesting Grading Support]] to mailto:academic-l@comp.nus.edu.sg.

!! Remuneration
The respective module coordinator is in charge of budgeting for these teaching activities. For all students, except  [[Teaching Assistants of SoC]], the remuneration proceeds as follows. At the end of the semester, the student submits a claims form to the module coordinator, which he endorses and passes to the School for approval. 

Reimbursement is done by the NUS Office of Finance. Undergraduate students are reimbursed through the Undergraduate Office of the School (current contact: [[Shanika Lakmali|mailto:shanika@comp.nus.edu.sg]]), and graduate students through the Graduate Programme of the School (current contact: [[Loo Line Fong|mailto:loolf@comp.nus.edu.sg]]). Claims need to be submitted to Shanika (undergrad) and Line Fong (grad) within one week from the last lesson (unless valid reason given).
!! Part-time Tutors
The processes above also apply to people hired as [[Part-time Tutor II]].

[img[Martin Henz|http://www.comp.nus.edu.sg/~henz/henz.jpg]]
Yes, that's me. Or more accurately, a rather old photo of me. Am not getting prettier, so why bother taking a new photo?

Module coordinators get assigned to modules by the [[Teaching Coordinator of CS Department]], see [[Assigning Modules to Academic Staff of CS Department]]. The administrative tasks of the module coordinators includes the following:
* Declaring the percentage of CA for the module. This declaration is done using the [[CA/Exam Weightage|https://mysoc.nus.edu.sg/~teachadm/lecturer/ca_wt_1.php]] component of the [[Teaching Administration System]]. An administrator at Undergraduate Office (currently   [[Low Mun Bak|mailto:lowmb@comp.nus.edu.sg]]) sends out a [[reminder|Reminder for CA Exam Weightage]] about 1 month prior to the semester, also on behalf of an administrator, Graduate Division (currently [[Agnes Ang|mailto:aang@comp.nus.edu.sg]]). After the deadline, Agnes and Mun Bak inform Registrar's office about modules with 100% CA (no need for exam).
* Declaring the required teaching support for the module until 10 days (Friday) before the start of Week 1 of the semester through the [[Manpower Request|https://mysoc.nus.edu.sg/~teachadm/lecturer/mpreq_1.php]] form of the Teaching Admin System.
* Budgeting the remuneration of student teaching support (details coming soon).
* Reviewing and approving claims of student teaching support (details coming soon).
----
The work of the [[Module Coordinator of CS Department]] is supported by the [[Teaching Administration System]]. All [[Staff With Teaching Credentials]] can access the system with role [[Module Coordinator of CS Department]].
----
When special qualifications are required for teaching support staff that cannot be met by existing students and staff, the module coordinator may request for the hiring of a [[Part-time Tutor II]].

!! Module Offering and Proposals
Undergrad modules are offered by the CS Department as part of the undergrad or graduate curriculum, managed by the [[School Curriculum Committee|http://www.comp.nus.edu.sg/undergradprog/committee.htm]]. Graduate modules are part of the graduate programs, managed by [[Academic Affairs/Graduate Studies|http://www.comp.nus.edu.sg/aboutsoc/deanery.htm]]. To propose a new module, contact the curriculum committee (for undergrad modules) or Graduate Studies (for graduate modules).
!! Module Mounting
Once offered, the modules get published in the NUS Bulletin, which is available [[online|http://www.nus.edu.sg/registrar/nusbulletin/faculty.html]] (click on Computing on the right, and then on the blue year). Modules may be mounted in any one of the four official semesters, see [[NUS Academic Calendar|http://www.nus.edu.sg/registrar/calendar.html]]. Not every module is mounted in every academic year. Mounting of CS modules is done by the [[Teaching Coordinator of CS Department]] in coordination with the curriculum committee and Graduate Studies. To see the modules mounted in the academic year that includes next April, see [[Teaching Admin System|https://mysoc.nus.edu.sg/~teachadm/lecturer/offering_1.php]].
!! Mounting Request
In order to request or comment on the mounting of a module offered by CS Department for the academic year after next April, please use the [[Modules Mounting Request|https://mysoc.nus.edu.sg/~teachadm/lecturer/offering_2.php]] interface. The [[Teaching Coordinator of CS Department]] will attend to your request or comment.
!! Workflow
* Before annual teaching assignment, [[Teaching Coordinator of CS Department]] needs to send a reminder to fill up mounting requests to teaching staff. A separate reminder needs to go to [[Research Staff of CS Department]] in order to invite them to teach in the next academic year. Once response received, check with supervisor regarding suitability.

NUS is offering scholarships to Singaporean and PR students to pursue a doctoral degree overseas. To this end, the NUS Office of Human Resources sends a call for nominations at the beginning of each year to the Heads of Department. The Heads forward this email to the CS academic staff (mailto:acad_cs@comp.nus.edu.sg to ask for nominations, cc to the [[Teaching Coordinator of CS Department]]. The [[Teaching Coordinator of CS Department]] assists in the management of the programme by: 
* Reviewing applications for submission to NUS OHR (deadline for submission to Head: 31 January)
* Reviewing annual progress reports sent by OGS scholars and recommending continuation/termination.
More information on OGS is given at [[NUS website on OGS|http://www.nus.edu.sg/ohr/OGS_OPF/]], including [[application instructions|http://www.nus.edu.sg/ohr/OGS_OPF/NUS-OGS_ApplInstr.htm]]. Deadline for submission by Department to OHR: 14 March.
!! Current Scholars
* Low Kian Hsiang at CMU, last report August 2006-July 2007, reviewed on 17/9/07

!! Part-time Tutor II
NUS allows the hiring of people with at least an Honour's degree as part-timers paid at an hourly rate between 30 and 60 dollars, with a max of 400 hours per AY, and a monthly max of 2000 dollars. Requests for such tutors needs to be done by the module coordinator via email to his respective [[Department Teaching Coordinator]] well ahead of the semester (1 month), so that HR has enough time to process the hiring. 

# Atleast an honours degree, with relevant working experience.
** $30-60 per hour, up to a maximum of 400 hours per academic year, or
# Exceptions may be allowed where the appointee has a basic degree plus expertise and/or industrial experience relevant to the course.
** a monthly honorarium of up to $2,000/-

Resources:
* Appointment scheme: https://wws.nus.edu.sg/staff/ohr/acad/apt/other_appts/PTTAppointments_Scheme.doc
* Criteria: https://wws.nus.edu.sg/staff/ohr/acad/apt/other_appts/Annex.pdf
* Recommendation form: https://wws.nus.edu.sg/staff/ohr/acad/apt/other_appts/Recommendation%20for%20ApptRe-appt%20of%20part-time%20staff.doc
!! Part-time Tutor I
Similar, but:
# Atleast a master's degree with several years of relevant working experience.
** S$60-120 per hour, up to a maximum of 200 hours per academic year or
# Exception may be allowed where appointee has a basic degree plus expertise and/or industrial experience highly relevant to the course.
** a monthly honorarium of up to $2,000/-
** part-time tutor I appointed to conduct language courses may be appointed for up to a maximum of 300 hours per academic year or paid a monthly honorarium of up to $3,000/-.

Dear Lecturers,

If you wish to change the CA weightage for the module you are teaching for Semester 2, ~AY2007-08, please submit your request through the Teaching Admin System.

https://mysoc.nus.edu.sg/~teachadm >  Lecturer > Misc > ~CA-Exam Weightage

(a) Any changes for CA of up to 60%, the system will automatically update the change.
(b) For CA higher than 60%, the request will be forwarded to the Head and

Dean for approval before the change is updated into the system.

Please provide the breakdown (eg: Midterm=35%, tutorials=5%, assignments=30% etc) and write a short paragraph to justify the change.

Deadline: Friday, 21 Dec 2007

Thank you.

regards,

Mun Bak and Agnes
UG and PG offices

Subject: Manpower Request for Teaching Support

Dear Module Coordinators for Modules of Semester 2, AY 2007/2008:

After enrollment numbers are settled, I am going to assign teaching support to your modules for tutorials, lab supervision, recitals, discussion groups.

The process of assignment is explained in detail at
http://www.comp.nus.edu.sg/~henz/teachingadmin.html#%5B%5BManaging%20Teaching%20Support%5D%5D
It considers your requests (see below) and preferences stated by full-time TAs and teaching support students. Would you please take a look at your modules in the Teaching Admin System at
https://mysoc.nus.edu.sg/~teachadm/lecturer/mpreq_1.php
* First check that all modules are listed that you are going to coordinate in the coming semester. If a module is missing, let me know.
* Click on each module and:
  * Ignore "Lecture Hours"
  * Tick the box for each kind of activity for which you anticipate the need of support 
    from TAs and teaching support students. [Note that support for grading is managed
    separately; look out for corresponding emails.]

Thanks and best regards,

Martin Henz
Teaching Coordinator

Dear Students,

this is for those eligible to take CS4102 for this coming academic year
07/08. 

Please indicate your preference for your Semester 2 modules at

MySoc > MySoc Academic > Teaching Admin System > Part Time/Honors Tutors >
Teaching Preference

We are looking especially for students with expertise for the following
courses, so please indicate with higher priority if you do:

You are required to conduct lab sessions, mark assignments, consultation
etc, up to a maximum of 33 hours per semester. 

Modules with vacancies in tutorials are limited, however you can still
indicate your availability.

Please make your choices by Friday, January 11.

Martin Henz
Teaching Coordinator

Dear All,

Please indicate your teaching preference for semester 1 in 

MySoc -> Teaching Admin System -> Teaching Assistant -> Tutorial
Preference

For the list of modules available, please see 

SoC home page > Current Students > Course Info > Course Schedule

Please note we are looking for someone who can teach cs3266 (java and
.net). Please email me if you can help in this course.

Would appreciate it very much if you could do this by end of July.


Best regards,
Martin Henz
Teaching Coordinator

All CS staff members with a ~PhD are allowed to teach modules and tutorials. After all, the "D" in "~PhD" stands for "doctor", which is the Latin word for teacher.

Staff members on a research contract such as Research Fellows, Post-doctoral fellows, and LKY fellows may not have any contractual obligation to teach at the School. However, the School encourages all these staff members to engage in teaching in order to enrich the School's offering of modules, and in turn be enriched by the experience of interacting with our students and gain teaching experience.

If you are a research staff member interested in teaching, please contact the [[Teaching Coordinator of CS Department]] to identify a suitable module for you.

The ~SoC Teaching Coordinator is involved in the following activities within the School of Computing:
* [[Managing Teaching Support]]
All other teaching coordination activities are handled by the [[Department Teaching Coordinator]]s.
----
Since late 2007, the Teaching Coordinator of the School of Computing is Associate Professor [[Martin Henz|http://www.comp.nus.edu.sg/~henz]].
----
The work of the teaching coordinators is supported by the [[Teaching Administration System]]. The [[School of Computing Teaching Coordinator]] maintains this system, and coordinates the maintenance with the [[Department Teaching Coordinator]]s.
----
For your entertainment, see the definition of "coordinator" at [[wikipedia|http://en.wikipedia.org/wiki/Cosmic_Era_human_enhancements#Coordinators]].

The [[Teaching Administration System]] maintains a list of staff with teaching credentials, which as of 3/1/08 contains the following designations:

|!~APPT_T                    |!                        ~APPT2_T|
|ADJUNCT ASSOCIATE PROFESSOR      |                  ADJ A/P|
|ADJUNCT FELLOW                           |          ADJ F|
|ADJUNCT PROFESSOR                     |             ADJ PROF|
|ASSISTANT PROFESSOR                  |              a/p|
|ASSOCIATE PROFESSOR                 |               A/P|
|ASSOCIATE PROFESSORIAL FELLOW|                      A/PF|
|EOM RESEARCH FELLOW       |                         EOM RF|
|FELLOW                              |               F|
|INSTRUCTOR                     |                    INSTR|
|KITHCT CHAIR PROFESSOR|                             PROF|
|LECTURER               |                            L|
|PROFESSOR             |                             PROF|
|SENIOR FELLOW      |                                SF|
|SENIOR LECTURER |                                   SL|
|SENIOR TUTOR     |                                  ST|
|SHAW PROFESSOR                                    | SHAW PROF|
|VISITING ASSOCIATE PROFESSOR              |         V A/P|
|VISITING FELLOW                                   | V F|
|VISITING PROFESSOR                             |    V PROF|
|VISITING SENIOR FELLOW                      |       VSF|
|LKY ~POST-DOCTORAL FELLOW                    |         LKY PD F|

This list is maintained by the [[Appn Team from IT Unit|mailto:teachadm@comp.edu.sg]]. These people all have access to the module coordinator role of the [[Teaching Administration System]].

The authentication is handled by ~mySoC. So users can either use NUSNET or mySoC ~IDs to log in. Both will let users through if they are valid.

Students are assigned to [[teaching activities|Teaching Activities]] (tutorials, lab supervision, discussion groups) by the [[School of Computing Teaching Coordinator]]. The [[School of Computing Teaching Coordinator]] takes the preferences of the students into account. For stating preferences, the students use the [[Tutorial Preference|https://mysoc.nus.edu.sg/~teachadm/rs/teach_req_1.php]] form in the Teaching Admin System. The process is described in [[Managing Teaching Support]].

The following student groups are involved in teaching:
* Undergraduate students taking [[CS4102]]<html>&#8212;</html>Technical and Management Training<html>&#8212;</html>to satisfy degree requirements
* Other undergraduate students 
* Graduate students who are [[Teaching Assistants|Teaching Assistants of SoC]]
* Other graduate students

The School of Computing uses the following types of teaching activities:
* Lectures: Frontal instruction in 1, 2 or 3 hour slots. Lectures are conducted by teaching staff, see [[Staff With Teaching Credentials]].
* Tutorials: Interactive sessions in 1 hour slots with class sizes up to 25 students. Tutorials are scheduled in rooms equipped with tables for students. Tutorial activities may include preparation of assignment and the grading of assignments. Tutorials are conducted by Teaching Assistants or graduate [[students serving as teaching support|Student Teaching Support]]. Undergraduate [[teaching support students|Student Teaching Support]] in the their final year of their 4-year programme may also teach tutorials for first-year modules, if they have sufficiently good grades and qualifications.
* Laboratory sessions: Interactive sessions in 1 or 2 hour slots with class sizes up to 25 students. Lab sessions are scheduled in rooms equipped with a PC for each student, and are supervised by a Teaching Assistant or a [[teaching support student|Student Teaching Support]].
* Discussion groups (not UDL): Weekly interactive 2-hour sessions, led by a discussion leader. These discussion groups are led by Full-time Teaching Assistants or graduate [[students serving as teaching support|Student Teaching Support]].
* Discussion group led by UDL: Weekly Interactive 2-hour sessions, led by an [[Undergraduate Discussion Leader]] (UDL). 
* Recitations: Frontal sessions involving a medium number of students, conducted by [[teaching staff|Staff With Teaching Credentials]] or [[Teaching Assistants|Teaching Assistants of SoC]].
All activities other than lectures are called teaching support activities. All teaching support activities except [[UDL|Undergraduate Discussion Leader]] are allocated by the [[School of Computing Teaching Coordinator]].
----
Undergraduate students meet their requirements for the module [[CS4102]] by supervising laboratory sessions and serving as UDL.

The Teaching Administration System supports the activities of coordinating teaching activities, including:
* Management of module information,
* Mounting of modules,
* Assignment of modules to module coordinators,
* Allocation of teaching support by TAs and students.
The system is available at:
https://mysoc.nus.edu.sg/~teachadm/
The site asks you to log on with your Soc/NUS user ID and password. Depending on your credentials, you will see a link for one or more of the following roles on the left:
* Module Coordinator: Access rights to this component have [[all staff with teaching credentials|Staff With Teaching Credentials]].
* [[Teaching Assistants of SoC]] 
* [[Teaching Support Student|Student Teaching Support]] (all students of ~SoC with ~SoC account have access)
* Admin (Mun Bak, Mui Kiat, Pamela, Pei Pei)
* Teaching Coordinator (~SoC and Department)
The technical staff maintaining the system is the [[Appn Team from IT Unit|mailto:teachadm@comp.edu.sg]]. Direct more general questions about the system to the [[School of Computing Teaching Coordinator]].
----
The [[School of Computing Teaching Coordinator]] maintains a list of [[Issues Regarding Teaching Administration System]].

Teaching Assistants of SoC are assigned to [[teaching activities|Teaching Activities]] (tutorials, lab supervision, recitations etc) by the [[School of Computing Teaching Coordinator]]. The [[School of Computing Teaching Coordinator]] takes the preferences of the Teaching Assistants into account. For stating preferences, the Teaching Assistants use the [[Tutorial Preference|https://mysoc.nus.edu.sg/~teachadm/tutor/tut_pref_1.php]] form in the Teaching Admin System. The process is described in [[Managing Teaching Support]].
----
There is a variety of arrangements with respect to teaching hours for Teaching Assistants, ranging from 5 to 15 hours per week. Teaching Assistants are paid a monthly salary.

The Teaching Coordinator for the Department of Computer Science is involved in the following activities:
* [[Module Offering and Mounting of CS Department]] 
* [[Assigning Modules to Academic Staff of CS Department]] 
* [[Hiring Teaching Assistants of CS Department]] 
* [[Handling Teaching Track Applications for CS Department]] 
* Coordinating the [[Overseas Graduate Scholarships for CS Department]]
The [[Teaching Coordinator of CS Department]] is Associate Professor [[Martin Henz|mailto:henz@comp.nus.edu.sg]].
----
See [[Timeline for CS Teaching Coordinator]] for chronological overview of the tasks of the [[Teaching Coordinator of CS Department]].

Early April: Invite [[Research Staff of CS Department]] to propose modules, see Workflow in [[Module Offering and Mounting of CS Department]]
Early April: Invite teaching staff to request mounting, see Workflow in [[Module Offering and Mounting of CS Department]].
...to be completed...

Person in charge of timetabling activities of the School of Computing. 

Currently Raymond Tan, mailto:rtan@comp.nus.edu.sg

Undergraduate Discssion Leaders are students selected by the [[Module Coordinator]]s of certain modules (e.g. ~CS1101) to lead discussions. See [[More details on UDL|http://www.comp.nus.edu.sg/undergradprog/UDLnew.html]].
----
The Module Coordinator of modules that use ~UDLs invite all undergraduate students to apply for a UDL position using the [[Undergraduate Discussion Leader Application|https://mysoc.nus.edu.sg/~teachadm/rs/udl_req_1.php]] component of the [[Teaching Administration System]]. He then conducts interviews and selects suitable students. He communicates the selected students to the Administrative Officer in charge of the [[CS4102]] requirement (currently [[Pamela Lim|mailto:plimmf@comp.nus.edu.sg]]). Before allocation of [[teaching support|Managing Teaching Support]], the [[Teaching Coordinator]] asks the Administrative Officer for the list of UDL students, so that they are not allocated to any other duties.
----
Students can meet their [[CS4102]] requirement using UDL.

[[School of Computing Teaching Coordinator]]

Teaching coordination  at ~SoC:
[[Managing TAs|Managing Teaching Support]]
Teaching coordination at CS:
[[Module Offering|Module Offering and Mounting of CS Department]]
[[Assigning Modules|Assigning Modules to Academic Staff of CS Department]]
[[Hiring TAs|Hiring Teaching Assistants of CS Department]]
[[OGS|Overseas Graduate Scholarships for CS Department]]
----
Information for:
[[CS Coordinators|Module Coordinator of CS Department]]
[[CS Research Staff|Research Staff of CS Department]]
[[SoC TAs|Teaching Assistants of SoC]]
[[SoC Students|Student Teaching Support]]
----
[[Areas of Improvement]]

information for teaching staff at the School of Computing

Teaching Administration

http://www.comp.nus.edu.sg/~henz/teachingadmin.html

* teachingMainMenu
* teachingSiteTitle
* teachingSiteSubtitle

* too much...