Degree Completion Program Proposal

B.S. in Computer Science

with a concentration in Software Development

Computer Science Department

Proposed Software Development Program

  1. Software Development Accelerated Degree Overview
  2. Software Development Accelerated Degree Diagram
  3. Software Development Accelerated Degree Curriculum,
  4. Program Mission, Outcomes and Objectives
  5. Program Acceptance Requirements
  6. Program Assessment
  7. Proposed Software Development Course Sequence
  8. Proposed Software Development Calendar
  9. Program Workload Estimates
  10. Sample Syllabus


  1. Initially this will be an in-seat program: Except for CSC3083 Technology and Society, most or all courses will be taught in-seat. The rational is the timing of the roll-out. Most of these courses are currently taught in-seat in a traditional classroom environment. Conversion to in-seat non-traditional will be significantly less time consuming than creating online versions of the course. Online curriculum would not be ready for a fall rollout.
  2. Courses will be developed by the faculty members currently teaching the course. This will stream line the process significantly, and lead to more credible course expectations. However, to convert ALL courses over the next two years will still be extremely time consuming leading to the next assumption.
  3. After program approval, an Academic Services Specialist will be hired for the program. This is important to assist the department in the many logistical aspects of rolling out the new program.
  4. A online curriculum specialist will assist in the course conversion process. Each faculty will work in concert with this specialist to help assemble, organize, proof, and review the new curriculum.
  5. The faculty developing the course will teach it the first time. This will be a challenge. Teaching this curriculum for one cohort will consume 20 semester hours a year. But faculty are full engaged in teaching traditional, AND will be working to convert and develop the new program. This leads to the next assumption.
  6. A minimum of one FTE CS additional faculty manpower will be available prior to first course being offered. A large portion of the time will be needed to teach the traditional CS courses as existing faculty are diverted teach the new online courses just developed. It is unlikely that this much assistance can be employed through adjunct faculty, first due to availability of such a quantity of appropriately experienced individuals, but moreover, to teach traditional courses during traditional a daily schedule.
  7. Development of an online version. Once the in-seat program is running, work will commence on developing online versions of each course.
  8. Budget Creation. We will need to create a complete program budget prior to approval. This will require a collaboration of all involved parties.
  9. Mathematics Department Involvement. The mathematics department will need to create and man the Elementary Discrete Mathematics course.
  10. Creation of a placement examination process. The first two courses are considered program prerequisites, and students will not be considered in the program until these requirements are completed. A methodology and possibly a test instrument needs to be identified or created for these prerequisites.
  11. Course load calculation. Computer science lab courses require significant out of class work, and such work cannot be credibly "accelerated". It is very common for students to reach a series of impasses as they work, essentially block their work until they receive guidance. Because of this faculty help will need to be available on a ongoing basis, e.g. faculty will need to be available for voice/email/text interaction throughout the day and evening. It it is quite unlikely that an instructor load will be less for a non-traditional course.
  12. Course tutors/lab assistants. Most traditional courses with more than 10 students will have available lab assistants to help with the issue mentioned in the previous point. Having appropriate assistance could possibly mitigate additional faculty loading issues.


Goal Description Priority
Not Compromise Traditional Quality With only two faculty, sacrifices will be necessary to bring up the new program. One possible sacrifice could be to lower the quality of the existing programs. Essential
Fully start the program fall 2014   High
Not Hire a full time Employee Adding the program will add 1 FTE to departmental load. Can this be done without hiring a full time person High


Date Milestone
November 15, 2013 Completion of program proposal to present for university approval, including proposed budget
December 2013 Program Approval
January 2014 Required Position descriptions are completed, and positions announced
January 2014 Program marketing begins
March 2014 Completion of an placement process.
March-June 2014 Required personal are selected and hired
May-July 2014 Students are recruited, and placed in the first cohort
July 2014 CS A and Elementary Discrete Math curriculums are in place
September 2014 First course begins (CS A)

Possible Degree Focus:

  1. Specialization Programs - these programs are highly applied to a specific career path and job description. May appeal to the career focused individuals. Less flexible.
    • web programming
    • network engineering
    • database systems
    • server management
    • These seem to be popular at online/for profit tech schools.
  2. General computer science
    • MVNU current specialty
    • Very general degree for virtually all specializations
    • Will prepare students for graduate study
    • Very Good career advancement possibilities
    • A popular form of non-traditional or accelerated program for more traditional universities.
  3. Software Engineering
    • More applied than computer science
    • Big growth area
    • Good career advancement possibilities
    • Term is well known
    • It appears most degrees called "Software Engineering" are either traditional in seat, master's level, or part of a BS/MS accelerated program. The few non-traditional BS degrees were from quetionable schools (Univ of Phoenix, etc)
  4. Information Systems
    • Softer side of computer science (less technical)
    • Very popular for non-traditional and accelerated programs.
    • More business oriented
    • More generic, less programming
    • Focuses on using and managing rather than designing and building

Possible degree completion offering format

  1. In-seat, accelerated
  2. On-line, accelerated
  3. Blended in-seat, on-line, accelerated

Common Elements identified across accelerated programs

  • Bachelor Programs
    • Admission: 60-64 transfer credits required
    • 2-5 CS/Math courses requires for admission
    • programs consist of 13-16 courses, 3-5 courses are non-major related (core)
  • Master Programs
    • Admission: BA/BS plus 1-5 CS/Math courses required
    • 10-11 courses in program
  • Accelerated BS/MS combined programs
    • This is a very common option for many of the better schools.
    • Completion in 5 years starting with no course work
    • Generally this not a degree completion route
    • Students start in BS program, apply to combo program after first or second year



Topic attachments
I Attachment Action Size Date Who Comment
Pdfpdf AcceleratedComputerScienceStructure.pdf manage 188.0 K 2013-10-03 - 19:57 JimSkon Possible Accellerated CS Structure
Pdfpdf ComputerScience2008.pdf manage 548.5 K 2013-10-07 - 02:54 JimSkon ACM Curriculum 2008
Pdfpdf McDonald_etal-SE_EffectiveTeachingAndLearning.pdf manage 450.6 K 2013-10-17 - 03:09 JimSkon Software Engineering Accreditation in the United States
Docxdocx SoftwareDevelopment-AcceleratedProgram-Curriculum.docx manage 60.7 K 2013-11-15 - 18:24 JimSkon  
Docxdocx SoftwareEngineering-AcceleratedProgram-Curriculum.docx manage 31.8 K 2013-10-24 - 21:06 JimSkon CS Accelerated Program Curriculum
Pdfpdf cs2013-ironman-v1.0.pdf manage 3524.1 K 2013-10-08 - 15:09 JimSkon ACM Curriculum 2013
Pdfpdf parnas_seisnotcs.pdf manage 244.5 K 2013-09-25 - 19:25 UnknownUser Software Engineering Programs Are Not Computer Science Programs
Topic revision: r25 - 2013-11-25 - JimSkon
This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback