COMP - 3300 - Application Development I

Z2022-2023 Undergraduate New Course Request

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.
Introduction
Next

  • Welcome to the University of West Georgia's curriculum management system. 

    Please TURN ON the help text before starting this proposal by clicking  next to the print icon directly above this message. 

    Your PIN is required to complete this process. For help on accessing your PIN, please visit here.

    The link to the shared governance procedures provides updates on how things are routed through the committees. Please visit  UWG Shared Governance Procedures for Modifications to Academic Degrees and Programs for more information.

    If you have any questions, please email curriculog@westga.edu.

  • Desired Effective Semester*
    Scroll to the bottom of the list and choose either Fall, Spring, or Summer.
    Desired Effective Year*
Routing Information
Next

  • Routes cannot be changed after a proposal is launched.

    Please be sure all fields are filled out correctly prior to launch. If a routing error is made it can result in the proposal being rejected and a new proposal will be required. 

    Please refer to this document for additional information: UWG Shared Governance Procedures for Modifications to Academic Degrees and Programs.

    If there are any questions or concerns regarding the routing of your proposal please contact curriculog@westga.edu.

  • College - School/ Department*
  • Is this a School of Nursing or School of Communication, Film and Media course?*
    Is this a College of Education course?*
  • Is this an Honors College course?*
  • Is the addition/change related to core, honors, or XIDS courses?*
Course Information
Next
  • Course Prefix*
    Course Number*
    3300
    3300
  • Course Title*
    Application Development I
    Application Development I
    Must be 30 characters or less including spaces
  • Long Course Title
  • Course Type*
  • Catalog Course Description*
    This course introduces students to the effective practices, principles, and patterns of software development and testing.
    Description as you wish for it to appear in the catalog.

  • Please indicate in the boxes below the credit hour distribution for this course. If the course will be variable in credit please be sure to include minimum and maximum values in each box. 

  • Is this a variable credit hour course?*
  • Lec Hrs*
    2
    2
  • Lab Hrs*
    2
    2
  • Credit Hrs*
    3
    3
  • Can a student take this course multiple times, each attempt counting separately toward graduation?*
    If yes, indicate maximum number of credit hours counted toward graduation.*
    N/A
    N/A

  • For definitions of prerequiste, concurrent prerequisite, and corequisite, please see the Curriculog Terminology/Icon Guide.

  • Prerequisites
    COMP 2320 OR CS 1302
    COMP 2320 OR CS 1302
    Please only list courses (prefix and number).
  • Concurrent Prerequisites
  • Corequisites
    Please only list courses (prefix and number).
  • Cross-listing
    Please only list courses (prefix and number).
  • Restrictions
    COMP 2320 minimum grade of C OR CS 1302 minimum grade of C
    This could include test scores, classifications, TE admission, major declaration, etc.
  • Is this a General Education course?*
  • If yes, which area(s) (check all that apply):
  • Status*
    Select Active-Visible unless the Registrar’s Office has notified you to do otherwise.
  • Type of Delivery (Select all that apply)*
  • Frequency - How many semesters per year will this course be offered?
    Grading*
Justification and Assessment
Next
  • Rationale*
    This is a new course in support of the newly proposed program, Bachelor of Science in Computing. The Bachelor of Science in Computing will give students a broad understanding of the ever changing field of Computing. Students will deepen their knowledge and sharpen their skills in one or more in-depth areas of specialization. Upon graduation, students will find employment in high-demand careers in areas such as cybersecurity, information technology, web or mobile development, and gaming.
  • Student Learning Outcomes - Please provide these in a numbered list format. *
    1. Apply current best practices in the construction of a software system consisting of several classes/modules.
    2. Demonstrate the ability to use IDEs, including debuggers, unit testing frameworks, distributed version control, and other tools in the design, development, and testing of a software system.
    3. Apply an iterative, incremental development process in the life cycle of a software program.

  • REQUIRED ATTACHMENTS

    ATTACH any required files (e.g. syllabi, other supporting documentation) by navigating to the Proposal Toolbox and clicking  in the top right corner.

    1.) Syllabus

    Please ensure it’s the correct syllabus (e.g., correct course prefix and number, course title, learning objectives/outcomes and includes link to the Common Language for Course Syllabi: http://www.westga.edu/UWGSyllabusPolicies/

  • Syllabus*
Resources and Funding
Next
  • Planning Info*
  • Present or Projected Annual Enrollment*
    80
    80
  • Will this course have special fees or tuition required?*
    If yes, what will the fee be?*
    N/A
    N/A
  • Fee Justification

  • LAUNCH proposal by clicking  in the top left corner. DO NOT implement proposed changes before the proposal has been completely approved through the faculty governance process. 

  • FINAL TASK: After launching the proposal, you must make a decision on your proposal. Select the select.png icon in the Proposal Toolbox to make your decision.

  • 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}