4. Outcome (c) assessment

 

Outcome (c): An ability to design, implement, and evaluate a computer-based system, process, component, or program to meet desired needs

Assessment of Outcome (c) were assessed at the Advanced Level in CS 151 in all sections taught (Sections 1 and 2).

Data Collected 

 

Conclusive analysis

Overall, the students did well in the Program Outcomes assessed. However, there are three areas of concern.

26.6% of the students did not achieve at least a satisfactory level in Performance Indicator 1 of Outcome B.

33.3% of the students did not achieve at least a satisfactory level in Performance Indicator 2 of Outcome B.

33.3% of the students did not achieve at least a satisfactory level in Performance Indicator 2 of Outcome C.

For Performance Indicator 2 of Outcome C, the instructor notes that this rubric was assessed through the midterm which was done right after the concept was introduced. Students needed more practice for applying patterns correctly to solve a problem. When the rubric was assessed through the team project, which was done at the end of the semester, their performance was improved greatly. Here is the data collected from the team project.

 

Recommendation

The instructor interviewed every student who participated in the project in order to assess their ability to use the MVC pattern. The students who belong to the exemplary group exactly articulated the roles of model, view, and controller, and also correctly knew the application of the MVC model to the project.

In this semester, the instructor notes that students studied 2 to 3 examples per pattern in class, and solved 5 to 6 exam questions regarding patterns. Also, 2 programming assignments and 1 project involving the use of MVC and Strategy patterns were assigned. Students understood a pattern more concretely when they actually implemented it in their program, by the time the final assessment was done. The recommendation is to continue this practice.