Academic Degree Program Assessment

School of Computing and Software Engineering

Use of Results Report

CS - BA Computer Science: 2007 - 2008

While there are currently no majors in the B.A. in Computer Science program, the Computer Science content portion of the program is a subset of the B.S. in Computer Science program, and the courses and program outcomes (which are identical) are evaluated within those courses.  The following discussion and uses of the program outcomes was carried out for the B.S. program:

 

1. Please list the Program Outcomes which were met and briefly discuss these.

1. Convey the understanding of, and ability to solve, problems through artifacts of computing such as specifications, code and other written documents.
2. Demonstrate and apply their knowledge of fundamental data structures and algorithms to solve problems.
3. Describe and explain the major concepts in the areas of operating systems, programming languages, architecture, and distributed computing.
4. Demonstrate an ability to work effectively in teams on computing related projects.
5. Demonstrate an ability to effectively communicate technical information.
6. Demonstrate an understanding of social, professional and ethical issues related to computing.
7. Obtain the skills and knowledge to be employable in positions that utilize their computing education.

All of the program outcomes for the BSCS program are listed above, and have been met.  They are measured through the overall EPAN results on the different courses contributing to those outcomes or on EEMU results if EPAN results were not available.  When the EPAN summaries are averaged for all the courses, it is clear that the desired threshold (of 2 out of 3) was exceeded for all the above outcomes.

2. If any program outcomes were not met, please list these and discuss these in more detail.

While the following outcomes were met, a concern was indicated by the results on the following outcomes:

2.  Demonstrate and apply their knowledge of fundamental data structures and algorithms to solve problems.

3.  Describe and explain the major concepts in the areas of operating systems, programming languages, architecture, and distributed computing.

7.  Obtain the skills and knowledge to be employable in positions that utilize their computing education.

On #2, the concern was in the Data Structures course the overall EPAN measurement was 1.9, not quite at the threshold of 2.  Outcome #3 had a deficiency in the Programming Languages area, however that may be because only one offering of the course was measured.  This course should be re-examined for the next few offerings.  For outcome #7 we are unsure that the outcome has been adequately measured in the capstone course with the data that was available.

3. Chair:

A. Please discuss how you think that or anticipate that these results might be used.

 

The following suggestions for improvement have been made and will be considered for implementation:

1. More detailed information concerning assessment sources and methodology needs to be applied to the capstone course as it is central to all program outcomes.
2. The Programming Languages course CS 3123 needs more examination for meeting program outcomes in the next few offerings.
3. Suggestions from CSE 4990 need a methodology for feeding student suggestions back into the department.

 

B. Please note below when you are tentatively planning to discuss these results and the use of these results with your faculty and with others.

 

These results have been discussed at the August 22 meeting and a prioritization is in progress by the respective subcommittees for implementation purposes.  At the next department meeting, scheduled for September 12, this process will be completed and steps for implementation will be taken.

 

It was also agreed that the program objectives and outcomes should be better aligned with ABET definitions.

 

4. Dates of Meetings: Please list below the dates of meetings at which the use of assessment results was discussed and also briefly summarize the discussions and decisions.

In the meeting of August 12, it was decided to call an Assessment Retreat on August 22 to complete the work.  Several subcommittees were formed to cover different programs.  It was also agreed that the Assessment Retreat should be an annual event, generally scheduled on the fourth Friday of each Fall semester, and that FCARs will be due by the second Friday of each semester for the courses taught the previous semester.  (The best time to complete them is perhaps when the grades are submitted to the Registrar.)

 

In the meeting of August 22, four subcommittees met and discussed the various programs as follows:

• Undergraduate CS programs subcommittee
• MSCS subcommittee
• Graduate Certificates in CS subcommittee
• Software Engineering programs subcommittee

 

Each subcommittee studied the FCARs related to the programs it covered, summarized whether each outcome is met or not, and identified a prioritized list of improvements for further discussion and implementation.

 

The EPAN vector reflects the number of students that passed the course whose proficiency for that outcome was rated Exemplary, Proficient, Apprentice, or Novice.

 

Academic Degree Program Assessment (CSE)

Planning and Assessment Homepage