Program Outcomes
|
Outcomes are statements that describe what students are expected to know and be able to do by the time of graduation.
At the time of graduation, all students will have demonstrated the ability to:
CS/SE1 Understand professional and ethical responsibilities.
CE/SE2 Work with clients and co-workers, have tact and see things from other perspectives
CS/SE3 Identify and evaluate technical alternatives
CS/SE4 Identify and evaluate non-technical alternatives.
CS/SE5 Apply oral and written skills effectively
SE6 Use the techniques and tools of modern software engineering practice.
CS6 Use the techniques and tools of modern computing and software development
CS/SE7 Work effectively in multidisciplinary teams
CS/SE8 Understand the need for professional development and historical perspective
CS/SE9 Learn new technologies independently
CS/SE10 See a multistage project/task through to completion
CS/SE11 See the essence of the problem and design a solution
CS/SE12 Stay current with respect to societal issues relating to computer technology
CS/SE13 Apply quantitative methods to software development
SE14 Be able to apply skills gained in math science engineering and business
CS14 Be able to apply skills gained in math science and logic
CS/SE15 Be technically proficient and perform all phases of software development
CS/SE16 Work effectively in one or more significant application domains.
SE17 Observe, use, reflect on, and refine software development and business processes
CS17 Observe use reflect on and refine software development processes and computing infrastructure
At the end of this document is the correspondence between these program outcomes and the courses in the SE curriculum that address these outcomes.
|
|
Assessment & Evaluation of Program Outcomes:
Assessment exams (E):
Give exams at the beginning of the courses CS 2546 (to assess the freshman year), CS 3326 (to assess up to the sophomore year), CS 4526 (to assess the up to junior year), and in SE 4920W/CS4946 at the end of the senior year (to assess the entire program). The first three tests will be 50 minutes long and will be given in the second class period. The exit exam will be two hours long and given as the final for SE 4920W/CS4946. The exams will primarily be multiple choice. Students will not be given grades for these exams.
The exams to assess the freshman and sophomore years will be the same for the CS and SE programs. The exams to assess the junior year and the entire program will be customized for the two programs.
The assessment exam results as they relate to program outcomes will be publicly available. By making the results of these exams openly available we show our commitment to improving our program. (Making these results publicly available will also motivate the students to take the exam seriously.) For all assessment exams, the public exam results will include program outcomes and aggregated percentages of students that got the question correct.
These exams will not be linked to individual students. The exam answers may be reviewed in the class where the exam was taken, but the exams will not be given to the students. Personal results for exams taken will be available to students upon request but the students are not allowed to copy the exam or take it from the room.
Instructors for each course will generate a pool of questions for the assessment exams. The questions will be related to the program outcomes for each course that contributes to or covers the program outcome. Each year the assessment exams will be made by randomly picking questions from the question pool for that year’s exam.
The first exam will be made up of an equal percentage of the questions from the courses being assessed. The second exam will be weighted with 80% from second year material and 20% from first year material. The third exam will be weighted with 70% from third year material, 20% from the second year material and 10% from the first year material. The final exit exam will be weighted 40/30/20/10 across the four years.
There will be two sections for the written and oral assessments: a section of common criteria used for assessment and a section of assignment specific criteria used for grading. The specific criteria are written by the instructor and do not appear on the standardized forms on the web. |
Written evaluations (W):
Evaluate all papers with a standard form (standardized written assessment form). These evaluations will be used to assess all written assignments. A limited number of writing assignments will be targeted to appear in the final evaluation portfolio. The specific topics and courses for these assignments are given in the table below. |
| Course |
Targeted Assignments |
| SE 1000/CS 1006 |
Copyright or a related issue |
| CS 2656 |
Information stewardship and computer technology |
| CS 3406 |
Operating system research topic |
| SE 3250W |
Software development or software metrics |
| SE 3260 |
Globalization or professionalism |
For an assignment that appears in the evaluation portfolio, all writing evaluations will be provided and the good, average and poor of the graded assignments will be identified and the graded paper will be included.
Oral presentation evaluation (O):
Presentations will be assessed, using the standardized oral assessment form, in the same way that written assignments are except that the evaluation portfolio will not include actual transcripts of the presentations. Targeted assignments include:
| Course |
Targeted Assignments |
| CS 2656 |
Database application presentation to outside clients |
| CS 3406 |
Operating system research topic |
| SE 3250W |
Software development or software metrics |
| SE 3260 |
Globalization or professionalism |
| CS 4406 |
Computer presentation of a system not covered in class |
Additional presentations will come from include internships and senior design projects.
Development process evaluation (D):
All student programs will be assessed, using the standardized development process assessment form, in the same way that written assignments are assessed. Targeted assignments include:
| Course |
Targeted Assignments |
| CS 2116 |
An assignment |
| CS 2546 |
Final project |
| CS 3326 |
A graph programming assignment |
| CS 3356 |
An assignment |
| CS 4526 |
Multi-threaded client or server assignment |
Reflection papers (R):
To evaluate CS/SE2, CS/SE7, CS/SE9, CS/SE10 and CS/SE16 we will do the following:
Students in the courses CS 2656, SE 3250W, SE 3260, SE 4920W, CS4916 work on multi-stage project for outside clients. Students in these courses will write a reflection paper to answer the following questions:
How did we work as a team? (CS/SE2)
How did we work with the clients? (CS/SE7)
What things could we do better next time?
What is the process that I have to use to quickly get up to speed in the application domain of the clients? (CS/SE16)
What new technologies did you need to learn to accomplish this project? (CS/SE9)
What techniques did you use to learn the new technology that you used in the project? (CS/SE9)
Project evaluation complete by the clients to determine the following:
How satisfied are you with the finished product? How well do you expect the finished product meet you needs? (CS/SE10)
Did the students appear to be effective as a team? (CS/SE7)
Were the students responsive to your needs? (CS/SE2)
Evaluation:
When the educational objectives and objectives assessment process are evaluated every two years, we will also evaluate program outcomes and the outcomes assessment process. Program outcomes will be evaluated and modified by the assessment committee. Program outcomes and the outcomes assessment process will remain constant for the intervening two years.
Ownership of assessment components:
Instructors own (1) course outcomes, (2) course to program outcomes mappings in the matrix, (3) catalog descriptions, and (4) course outcome review and evaluation (CORE) documents.
The assessment committee will own the educational objectives and program outcomes.
The CORE documents are completed by the instructor for every course offering. The first portion of the form is completed before the semester begins and the final portion is completed after the course is completed. The purpose of these CORE documents is to review and evaluate the course outcomes, course mapping to program outcomes and catalog description. The completed documents are publicly available.
|