Computer Science

2024-2025 - UG - Minor Program Adjustment

completed

What can I do next?

View the Proposal

  • View changes to the proposal by clicking the Discussion tab and selecting "Show current with markup" on the User Tracking dropdown.
  • View current comments concerning this proposal by clicking the Discussion tab.
  • View the history of the proposal by clicking the Workflow Status tab.
  • View the signatures the proposal has collected by clicking the Signatures tab.
  • View the files associated with the proposal by clicking the Files tab.
  • Compare the proposal with related proposal by clicking the Proposal Lookup tab.
(A) Proposal summary
  • STEP 1 - Complete the proposal summary information
  • Home faculty*
    Choose your faculty from the list of available options.
  • Content type*
    Choose the type of content imported from the calendar. Contact ciqe@ontariotechu.ca if you require assistance.
  • Summary of proposed changes*
    • Addition of 2 new courses for first year students: CSCI 1062U - Accelerated Programming Workshop, and CSCI 1063U - Computer Programming Project
    • Changes to prerequisites for courses requiring CSCI 1060U (replacing with CSCI 1061U / CSCI 1062U)
    • Change to Program Map to add CSCI 1062-1063
    Include a brief summary of the changes included in this proposal. for pathways, please include details on the specific or unspecified transfer credits students will receive, if applicable).
  • Is a new course associated with this proposal?*
    Select 'yes' only if you are adding a brand new course to the calendar copy in this proposal.
  • If applicable, list new course codes, course titles and include hyperlinks to course proposals in Curriculog in the 'new courses' field below. To hyperlink, open a new window and search for the new course proposal in Curriculog. Copy the url from your web browser, return to this form and select the hyper link icon. Paste the url into the url field and save.

  • New courses

    CSCI 1062 - Accelerated Programming Workshop

    CSCI 1063 - Computer Programming Project

  • Are you modifying a pathways (Bridge/Advanced Entry) program?*
  • STEP 2 - Attach supporting documents, if applicable
  • Visit the files section of the toolbox on the right-hand side of the form to attach any supporting documentation.

  • Are you attaching any supporting documents?*
(B) Program information
  • STEP 3 - Complete program adjustments in Section B
  • Program or shared core name*
    Computer Science
    Computer Science
    This is the title of the program or shared core in the calendar. Program names should not be changed through this form. Contact ciqe@ontariotechu.ca for more information.
  • Program type
  • Degree type
  • Note: If the program or shared core description does not import into the field below, it is captured in the calendar copy. In this case, do not add content to the program or shared core description field as it will import to the calendar.

  • Program or shared core description
  • Calendar copy*
  • Note: Program learning outcomes will not import from the calendar. If you are making changes to this field, please enter the current information now and make changes only after you have validated and launched the proposal.

    If you do not have a recent version of your programs learning outcomes, or would like to make a modification to them, please contact ciqe@ontariotechu.ca

  • Program learning outcomes
(C) Pathways programs
  • STEP 4 - Complete Section C
  • Complete this section only if you are modifying a pathways program.

  • Proposed transfer credit block
    Please include details on the specific or unspecified transfer credits students will receive.
(D) Detailed proposal information
  • STEP 5 - Complete Section D
  • Enhanced academic opportunities*

    As Ontario Tech grows, we are seeing a noticeable increase in the quality of our incoming students, as evidenced by the attached data about the increasing high school entrance averages. It is necessary to update our program to account for the fact that many first year computer science students already have experience in programming and are not the intended audience for the introductory programming topics taught in CSCI 1060U. The majority of the top ranking Computer Science programs at Canadian universities offer multiple pathways for new students based on their level of competence. This program adjustment is aimed to help with retention of students who have a higher existing knowledge level of programming upon arriving at Ontario Tech. 

    By offering two paths for incoming computer science students, we will continue to support incoming students who do not have any programming experience, preparing them to meet the learning outcomes in CSCI 1061U that are necessary for upper year courses.  For students with prior programming experience, they may find the CSCI 1062U -> CSCI 1063U path to be more appropriate for their level of competence while still receiving two semesters of practical programming courses. A diagnostic test offered in the first week of CSCI 1062U will help students correctly assess whether or not they should transfer into the less challenging CSCI 1060U -> CSCI 1061U path.

    Description of the ways in which the proposed change will enhance the program and/or academic opportunities for students.
  • Financial/ resource implications*

    Because this program adjustment is intended to filter students out of CSCI 1060U and CSCI 1061 into CSCI 1062U and CSCI 1063U, the reduced number of sections needed for those courses should mean there is not a significant resource change to offering sections for the alternate course path.

    Offering CSCI 1062U as a retention course in the Spring/Summer will support students who fail CSCI 1061U in Winter. It will also provide an option for students who enter the program outside of the Fall intake and are looking to acquire a necessary prerequisite for second year Computer Science courses, without waiting until the following year’s offering of CSCI 1061U in Winter.

    Provide an analysis of the financial and resourcing implications.
  • Enrolment implications*

    None

    Provide an analysis of the enrolment implications.
  • Transition plan*

    This option provides new options to the existing program map, and students beyond first year will still be able to use their CSCI 1060U and CSCI 1061U credits towards graduation and for their course prerequisites.

    Semester (e.g., Fall 2020) for the implementation of the proposed changes; include a plan for all current students in the program, by year level. If this change impacts students that are not new and/or 1st year students as of the start date, then a transition plan is required.
  • Additional supporting information, if applicable
    Describe any additional information needed to support the proposal.
  • Calendar start date*
    Choose when the change should appear in the Academic Calendar.
  • Registration start date*
    Specify the first active term (e.g. Fall 2021).
(E) Impact and consultation
  • STEP 6 - Complete Section E
  • We have consulted with all impacted areas*
    By selecting 'yes', you agree that you have consulted with all affected areas prior to beginning this proposal. Select 'N/A' only if the change(s) do not involve students, staff and faculty from other programs or courses.
  • Consultation*

    The Computer Science group was involved in the change

    Process of consultation with other units if the change(s) involve(s) students, staff, and/or faculty from other programs or courses).
  • Are there any considerations for the principles of equity, diversity, inclusion or decolonization included with this program change?*
  • Please explain:*

    n/a

    Does the program contain concepts, materials or resources from scholars/professionals who are part of one or more historically marginalized groups? Are multiple perspectives represented in the program, such as those offered by those who are Indigenous, Black, Persons of Colour and/or 2SLGBTQIA+? How has accessibility been considered? More specifically, have the needs of students with disabilities been integrated into the program design (e.g., the ways that students are asked to demonstrate their learning)? Will this program provide space to allow for the discussion of other viewpoints outside the dominant, Western narrative? Have the principles of Universal Design been considered?
  • Indigenous Content and Consultation
  • Does this change include any Indigenous content?*
  • For more information on how Indigenous content is defined at Ontario Tech University and how to consult with the Indigenous Education Advisory Circle, please refer to the Protocol for Consultation with the Indigenous Education Advisory Circle.

  • Has the IEAC been contacted?
  • If Yes, when?
  • What was the advice you received from the IEAC? And, how has it been included in your proposal?
  • Did the IEAC ask you to return the proposal to them for review?
    If Yes, have they completed their review?
(F) Routing
  • STEP 7 - Enter routing information
  • Important note: it is imperative that you choose the correct routing path as it cannot be changed once a proposal has been launched. If you have made a routing error after launching the proposal, the proposal will be cancelled and a new proposal will be required. If you require assistance with routing, please contact ciqe@ontariotechu.ca.

    Please note that changes to joint or collaborative programs do require approval at Faculty Council of each faculty involved in the program. You do not need to include other faculties in the routing, however, consultation with other faculties should be noted and any required approval by other Faculty Councils (and date of approval) should be noted in the comments section as approval is logged on the home Faculty Council step.

  • Should this proposal be routed to the Program Approval step prior to Curriculum Committee?*
    If your curriculum committee is organized by program, or if program-level approval prior to curriculum committee is not required, select 'no'.
  • Faculty or program-level group*
    Choose your faculty or program-level group from the list of options. If your faculty has program-level committees, choose the corresponding program group from the list. Otherwise, choose the home faculty. You may choose more than one option, but please note that your proposal will go to the committees of all options selected. The proposal will not move on to the next step until all faculties have approved at their respective committees. Note: If you are making a change for a Bachelor of Engineering program in FESNS, you must select both the Faculty of Energy Systems and Nuclear Science, and the Faculty of Engineering and Applied Science from the list of options.
  • Is this change for a Bachelor of Engineering program or program which requires Engineering Curriculum Committee approval?*
  • Are there departments associated with your faculty?*
(G) End of proposal
  • STEP 8 - Save and ensure all required fields are complete
  • STEP 9 - Validate and launch proposal
  • STEP 10 - Review program adjustments
  • To view the proposal with mark-up, navigate to the discussion section of the toolbox on the right-hand side of the form and change the User-Tracking setting to Show current with mark-up. To view the calendar copy with mark-up, click the Preview Curriculum icon and then the red pencil icon.

  • STEP 11 - Approve proposal
  • As the originator, you must approve the proposal to send it on to the next step. To approve, navigate to the decisions section of the toolbox on the right-hand side of the form.

(H) CIQE use only
  • Code
  • Program or shared core OID
    16760
    16760
  • User Tracking

    Help: Show Original: This option displays the proposal as it appeared at launch. No markup will be visible on the form. There will be no differentiation between fields that contain imported content and content that was created or selected by the originator by hand.

    Help: Show Current: This option displays the proposal as it appears currently. No markup will be visible on the form. There will be no differentiation between fields that contain imported content and content that was created or selected by the originator by hand.

    Help: Show Current with Markup: This option displays the proposal with all of its current content marked to show different editors. Text fields that include imported content are indicated by a blue highlight, and may also include additional changes within, indicated by each editor’s unique color. Fields containing selects, checkboxes, radio buttons, or widgets (such as the curriculum) provide an activity log above the field, indicating each editor’s selection and unique color.

    Comments

    You have not saved your changes to all the assessment fields you edited. You have the following options:

    • Click "Save All Changes" now to save every change you made
    • Click "Abandon Changes" to destroy all unsaved changes
    • Click "Cancel" to continue working on assessments and save each field individually

    What would you like to do?

      You must be logged in, in order to approve.

      Please upload the form that you just printed and signed.

      This will be used as your signature to sign this proposal upon approval.


      Listed below are the symbols and colors utilized in Curriculum:

      • = has not made a decision
      • = approved
      • = rejected
      • = held
      • = suspended
      • = cancelled
      • = multiple decisions
      • = task
      • = mine
      • = stuck
      • = urgent, out of date import source
      x

      #{title}

      #{text}

      x
      warning

      #{title}

      #{text}

      x
      warning

      #{title}

      #{text}