ICT Curriculum Review/Refresh/Update - 2012

ICT Internet Stream Update - Fall 2011

Attendees for Session 1: John Selmys, Emile Ohan, Anthony Austin, Danny Abesdris (Arroway), Peter Callaghan, Mary-Lynn Manton, Ian Tipson, Peter McIntyre, Praveen Mitera, Sunny Shi, Michal Heidenreich

Attendees for session 2: Emile John Sam Fardad S Peter M Jordan A Bob B Mary-Lynn Daniel Hodgin Chris T

ULI101

• currently last 2 weeks of course is xhtml/css intro
  • consider removing web content (last 2 weeks), and not expand unix content in uli101
  • this should not affect int222 or int213

INT213

• currently legacy asp
  • no changes
  • consider changing to asp.net

INT222

• currently 1st half is xhtml/css, 2nd half is css/javascript
  • html5 replaces xhtml/javascript/css (Anthony has reservations)
  • need to manage the course depth - should not be another "killer" course
  • consider changing pre-req to IPC144 (Emile)
• propose it now be HTML5 (including Javascript/DOM/CSS3)

INT322

• currently 1st half perl, 2nd half is php with apache and mysql
  • remove perl and Apache admin and replace with more html5/ajax (not Anthony's opinion)
  • recommend perl and python as professional options
  • consider using a versioning system like git/svn (Fardad)
  • consider Python instead of PHP
• propose it now be continuation of HTML5 from INT222 + PHP + Ajax

INT422

• currently asp.net web forms and c# with intros to sql server and ajax
  • remove ajax
  • consider using a versioning system like git/svn (Fardad)

LETTERS (from faculty who could not attend)

• David Humphrey's Internet Stream Update Comments
• Timothy Mckenna's Internet Stream Update Comments
• John Samuel's additional comments

NOTES from INT REVIEW in 2010

• Here's a [link to last year's review] of our INTERNET stream.

FINAL COMMENTS

• should not be implemented in Jan 2012
• should be implemented in May 2012
• need more unix courses (Anthony, John)
• all faculty should be given cell phones and tablets (except Ian)
• all faculty should be given Mercedes (except Ian)

INT222 Outline Comments

The link below is a "version 1" proposal, listing the topics to be covered in a refreshed INT222 / BTI220 course.

I approached this task by simply listing all the topics that could be covered, without regard to sequencing, as I thought of them. Then, I grouped and sequenced them. Finally, I compared the result to the current course outlines, the comments of others, and a bit of research.

The document is available in PDF. This zenit server wouldn't permit me to upload a docx or doc file.

Proposal, version 1 - pdf

-Peter

INT222 Progress Report

The link below includes the updates received from the few verbal and written responses since the publication of "version 1" above.

Proposal, version 2 - pdf

The link below may be of interest to readers:

http://petermcintyre.com/2012/04/12/one-page-web-programming-course/

Before the next meeting, please think about the following question: What knowledge and skills should incoming students possess before starting your course? Some sample getting-started observations are below:

Coming into INT222 / BTI220

• Using software on a personal computer (which prepares them to use an editor, a browser, and a file transfer program)
• Proficiency in any code editor on any platform
• Conceptual knowledge of what a server is
• Conceptual knowledge of message-based protocols (i.e. request, response)
• Problem-solving abilities
• Good language comprehension (to be able to formulate a problem into a solution, or at least a solution approach)

Coming into INT322 / BTI320

( looking for help here... )

Coming into INT422 / BTI420

( some students know, and can do, some of these, but most couldn't, coming into Winter 2012 BTI420... )

• Conceptual knowledge of a request lifecycle
• HTTP knowledge basics
• Web site resource organization
• AuthN and AuthZ
• CSS (basics, layout, rules)
• JavaScript (anything!)
• Cookies
• Dev tools (i.e. F12, or Firebug-like tool)
• HTML (p, br, div, div, ul, li, input, etc.)
• Conceptual knowledge of page/document templates
• Server resources (request, response, file system, etc.)
• Nice-to-have - creating a navigation menu

Coming into the Web Services pro option

• Good HTTP knowledge
• Solid OO knowledge and skills