Difference between revisions of "OPS"

From CDOT Wiki
Jump to: navigation, search
 
(43 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
'''OPS STREAM'''
 
−
 
 
= OPS Stream Discussion =
 
= OPS Stream Discussion =
  
 
== Overview ==
 
== Overview ==
  
−
This WIKI is a collection of curriculum discussions held in May 1024 and January 6, 2015, as well as discussion from PAC committee meetings have been held several times during 2014. The term '''PAC''' stands for '''Program Advisory Committee'''. This committee consists of management, faculty, industry professionals, and former CNS/CTY students that meet to review and discuss the current curriculum and recommend or advise any changes that may need to be made. It is the intension of this WIKI to provide a collection point for ideas and collaboration between courses for the OPS Stream to assist in future curriculum development as a result of these PAC meetings.
+
This WIKI is a collection of curriculum discussions held in May 2014 and January 6, 2015, as well as discussion from PAC committee meetings have been held several times during 2014. The term '''PAC''' stands for '''Program Advisory Committee'''. This committee consists of management, faculty, industry professionals, and former CNS/CTY students that meet to review and discuss the current curriculum and recommend or advise any changes that may need to be made. It is the intension of this WIKI to provide a collection point for ideas and collaboration between courses for the OPS Stream to assist in future curriculum development as a result of these PAC meetings.
−
 
 
−
 
 
−
'''Curriculum Discussion for each course in OPS Stream:'''
 
−
 
 
−
* [ [[ULI101 - Curriculum Discussion |ULI101 - Curriculum Discussion]] ]
 
−
* [ [[OPS235 - Curriculum Discussion |OPS235 - Curriculum Discussion]] ]
 
−
* [ [[OPS335 - Curriculum Discussion |OPS335 - Curriculum Discussion]] ]
 
−
* [ [[OPS435 - Curriculum Discussion |OPS435 - Curriculum Discussion]] ]
 
−
* [ [[OPS535 - Curriculum Discussion |OPS535 - Curriculum Discussion]] ]
 
−
 
 
−
 
 
−
'''Recommendations From Recent PAC Meetings (based on discussion notes [[CNS/CTY Curriculum: Discussion Transcript]] ):'''
 
  
−
The following rough program maps were discussed in the January Startup Meeting (Jan 6, 2015):
 
  
−
:'''The curriculum discussions for the CNS/CTY programs have drawn attention to several key areas:'''<br>(Note current and proposed CNS/CTY curriculum maps display below)
+
==Curriculum Discussion for each course in OPS Stream==
  
−
:*'''Create an identical skill base for both CNS and CTY programs for the first four semesters'''
+
:* [ [[ULI101 - Curriculum Discussion |ULI101 - Curriculum Discussion]] ]
−
:::Students in the CTY program (after completing co-op) sometimes want to graduate with CNS and fail to see the point of taking an additional 2 semesters. The problem is that when students are enrolled in the CTY program, the CTY program requires them to complete the 6 semesters. A number of students will accept employment without having completed the CTY diploma certificate (this affects the perception of student success and retention). Creating an identical skill base for both CNS and CTY programs will offer employers with a minimum level of employee competence and provide a conduit for students to "upgrade" to CTY.
+
:* [ [[OPS235 - Curriculum Discussion |OPS235 - Curriculum Discussion]] ]
−
+
:* [ [[OPS335 - Curriculum Discussion |OPS335 - Curriculum Discussion]] ]
−
:*'''Increase retention of CTY students by offering career-oriented capstone projects with IT industries in the fifth and sixth semesters'''
+
:* [ [[OPS435 - Curriculum Discussion |OPS435 - Curriculum Discussion]] ]
−
:::With identical core requirements for the first four semesters of the CNS/CTY programs, the fifth and sixth semester of the CTY program can roll-out or tweak courses to have students develop a better understanding of the IT industry by working on a solving a real IT industry-related task. A "capstone project" can match a CTY student with industry. By allowing students to with an industry partner, the student is encouraged to complete the CTY program and prevent them from being "stagnant" after completing the CNS program and waiting for employement.
+
:* [ [[OPS535 - Curriculum Discussion |OPS535 - Curriculum Discussion]] ]
 +
:* [ [[OPS635 - Curriculum Discussion |OPS635 - Curriculum Discussion]] ]
  
−
:*'''Promote student success by channeling them to one year, lower credential diplomas (with the option of re-applying to CNS/CTY upon successful completion)'''
 
  
−
:::There has been discussion in curriculum meetings to channel students that are unsuccessful in their first semester in the CNS/CTY programs to a One Year, reduced credit Diploma certificate. This course would provide essential skills for students to apply to more basic job categories in the IT industry. Students that successfully complete this program may be allow to re-apply to the CNS/CTY program.
+
==General Findings from OPS Stream Discussion / Curriculum Review / Analysis==
  
−
:*'''Align hardware concepts to reflect data servers (eg. data centers) as well as desktop (client-server) models'''
+
: '''Key issues have been immediately identified''' (See each course "Curriculum Discussion" for detail):
  
−
:::Subject matter experts in the CDOT applied research division have indicated gaps from what students learn and what is currently adopted in the IT industry. One example would be students, although having skills to create Ethernet cables for workstations, lack the subtle skill to wire a server rack. In an effort to eliminate this discrepancy, newer course will be introduced to deal with these issues including infrastructure, advanced data communications, advanced firewalls, and security. In addition, a course in project management should be considered.
+
:# Tighten up wording of Learning Outcomes. There are considerably more learning outcomes for OPS235 course outline compared to OPS335, OPS435 course outlines
 +
:# Check that learning outcomes apply to course delivery
 +
:# Missing central repository for all courses for consistent "cover-off" of materials, techniques, better supporting AODA, course start-up check-lists, etc.
 +
:# Tighten up overview or description of course to meet all learning outcomes
 +
:# How newer CPU implementation will affect delivery of courses like OPS235, OPS335, OPS535
 +
:# How will "Visualization" affect OPS Stream course delivery, and if so, when (eg. target dates)
 +
:# Students should be exposed to and reinforced shell scripting throughout stream from the beginning and add additional scripting skills throughout program duration
 +
:# Students should incorporate Linux commands in the form of a standardized reference sheet and that resource for be permitted in addition to lab logbook for evaluation in courses such as: OPS235, OPS335, OPS435, OPS535
  
−
{|cellpadding="15" width="40%"
 
  
−
|-
+
==This WIKI's Approach==
  
−
|[[Image:cns.png|thumb|400px| ]]
 
−
 
−
|[[Image:cty.png|thumb|400px| ]]
 
−
 
−
|}
 
−
 
−
 
−
'''The Challenge:'''
 
−
 
−
:Curriculum development can seem like a daunting task! On one hand, it is important for curriculum to grow and develop in order to take advantage of changing trends and help to better train our students for industry. On the other hand, '''great care must be taken to not make changes in course curriculum without considering the impact on other courses''', and to make certain that '''content and learning skills are maintained in the learning outcomes for courses until a major curriculum review and possible curriculum revisions are warranted'''. Other challenges include limited time frames for all faculty to meet at the same time to discuss curriculum issues.
 
−
 
−
 
−
'''This WIKI's Approach:'''
 
  
 
:This WIKI hopes to encourage on-line repository of OPS stream course discussions to provide to help view all courses and to foster communication between faculty members. Faculty members can simply view and contribute freely to the the curriculum discussion.  To help keep the discussion on track, a '''Triage framework''' has will be used to prioritize suggested improvements into '''short-term''', '''long-term''', and '''wish-list''' categories. In this way, faculty can sort out easy to perform changes or "tweaks" to courses and foster discussion among courses in the OPS stream.  It is hoped that this method allows for transparency, and allows for an encouraging and welcoming area for faculty to make suggestions / improvements to course curriculum.
 
:This WIKI hopes to encourage on-line repository of OPS stream course discussions to provide to help view all courses and to foster communication between faculty members. Faculty members can simply view and contribute freely to the the curriculum discussion.  To help keep the discussion on track, a '''Triage framework''' has will be used to prioritize suggested improvements into '''short-term''', '''long-term''', and '''wish-list''' categories. In this way, faculty can sort out easy to perform changes or "tweaks" to courses and foster discussion among courses in the OPS stream.  It is hoped that this method allows for transparency, and allows for an encouraging and welcoming area for faculty to make suggestions / improvements to course curriculum.
Line 60: Line 38:
  
  
−
'''General Definitions (Purpose) of OPS Streams:'''
 
  
−
There are two basic diploma programs at Seneca College that utilize the OPS stream:
+
== Additional Resources / Navigation ==
  
−
: '''CNS (Computer Networking and Technical Support)'''
+
:* [[CNS / CTY Curriculum Development]]
−
:: This program places emphasis on practical subjects and "hands-on" training delivered in specialty labs. These dedicated labs are configured for various environments such as Linux, Microsoft Windows, networking, OC hardware, Internet, AS/400, and RS/6000. Through these labs, students have access to stand-alone, clustered and networked PC's along with a host of LAN servers and mid-range computers.
 
−
 
 
−
: '''CTY (Computer System Technology Overview)'''
 
−
:: Similar in certain respects to CNS program, but contains 2 additional semesters to allow students to specialize in areas such as: '''Security''', '''Data Communications''', and '''Network Administration'''.
 
−
 
 
−
 
 
−
 
 
−
== Additional Resources / Navigation ==
 
  
−
:* [ [[OPS Stream Meeting (November 13, 2013)]] ]
 
−
:* Meeting Minutes for CNS/CTY PAC Committee Meetings
 
  
−
[[Category:Curriculum, OPS Stream]]
+
[[Category:Curriculum, OPS, CNS / CTY Curriculum Development]]

Latest revision as of 19:19, 11 April 2016

OPS Stream Discussion

Overview

This WIKI is a collection of curriculum discussions held in May 2014 and January 6, 2015, as well as discussion from PAC committee meetings have been held several times during 2014. The term PAC stands for Program Advisory Committee. This committee consists of management, faculty, industry professionals, and former CNS/CTY students that meet to review and discuss the current curriculum and recommend or advise any changes that may need to be made. It is the intension of this WIKI to provide a collection point for ideas and collaboration between courses for the OPS Stream to assist in future curriculum development as a result of these PAC meetings.


Curriculum Discussion for each course in OPS Stream


General Findings from OPS Stream Discussion / Curriculum Review / Analysis

Key issues have been immediately identified (See each course "Curriculum Discussion" for detail):
  1. Tighten up wording of Learning Outcomes. There are considerably more learning outcomes for OPS235 course outline compared to OPS335, OPS435 course outlines
  2. Check that learning outcomes apply to course delivery
  3. Missing central repository for all courses for consistent "cover-off" of materials, techniques, better supporting AODA, course start-up check-lists, etc.
  4. Tighten up overview or description of course to meet all learning outcomes
  5. How newer CPU implementation will affect delivery of courses like OPS235, OPS335, OPS535
  6. How will "Visualization" affect OPS Stream course delivery, and if so, when (eg. target dates)
  7. Students should be exposed to and reinforced shell scripting throughout stream from the beginning and add additional scripting skills throughout program duration
  8. Students should incorporate Linux commands in the form of a standardized reference sheet and that resource for be permitted in addition to lab logbook for evaluation in courses such as: OPS235, OPS335, OPS435, OPS535


This WIKI's Approach

This WIKI hopes to encourage on-line repository of OPS stream course discussions to provide to help view all courses and to foster communication between faculty members. Faculty members can simply view and contribute freely to the the curriculum discussion. To help keep the discussion on track, a Triage framework has will be used to prioritize suggested improvements into short-term, long-term, and wish-list categories. In this way, faculty can sort out easy to perform changes or "tweaks" to courses and foster discussion among courses in the OPS stream. It is hoped that this method allows for transparency, and allows for an encouraging and welcoming area for faculty to make suggestions / improvements to course curriculum.
Faculty members (new hires and existing) can be directed to this site when teaching these courses for the first time to help gain the fundamental importance of the course curriculum, to note the importance of flow between the streaming courses, and to perhaps integrate this knowledge into their course delivery to provide students with forward linkages (i.e. a "heads-up") of why the current course content topics are essential to their success in the CNS/CTY programs.


Additional Resources / Navigation

Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=OPS&oldid=117021"