Changes

Jump to: navigation, search

Proposed ISA Program Changes

239 bytes added, 15:14, 17 March 2008
Recommended Changes
== Recommended Changes ==
# Increase the level of the courses to minimize crossover overlap with current CTY courses program and to make the program more attractive to experienced Junior- and Intermediate-Level system and /network administrators.# Require a certain basic base level of competency with basic Linux system administration tasks, including use of the command line and basic installation of Linux on a PC. For students with borderline ability in these areas, a pre-program workshop could be held.# Move Python to an early point in the scripting courses. Have the first scripting course cover some basic Bash scripting and then go into Python; have the second course cover advanced Bash scripting and then advanced Python or Perl. (The last offering of the scripting course droped PHP in favor of Python).# Schedule the program so that it can be completed by attending two days per week. Place the lecture periods for all classes on two days (for example, Monday/Tuesday) and plan the labs in such a way that they can be performed in person or remotelyand/or hold the 2nd class in each course online.# Incorporate cross-course projects where students will be working directly within the Fedora community (see below).
Note that the Fedora project is actually a collection of approximately 5800 RPMs (software groups) that are packaged, integrated, built, tested, and distributed using highly-automated tools (Koji, Mash, Revisor, Punji, etc). Within the Fedora umbrella we have a lot of latitude for many different types of student involvement.
* SCR821 Advanced Scripting
** Advanced Python
** Advanced Bash
* SRA840 Server Administration
* NAD810 Network Administration
'''Students will take their projects to the 'next level' in SYA/SEC/SCR courses (and possibly the other courses as well).''' Continuing to work with the Fedora community, students will audit their projects for security, robustness, and integration with other technologies and packages, and will deploy and test them on a variety of systems. By the end of the second semester, these projects should reach a "1.0" completion level.

Navigation menu