ABET accreditation is more than a periodic review of an engineering curriculum. It requires a program to show how it defines the capabilities graduates should develop, measures student learning, and uses evidence to improve. A 2018 self-study by Saint Louis University’s Computer Engineering Program offers a useful example of how those elements can be connected—and why assessment design matters to programs preparing engineers for complex technical work.
ABET accreditation depends on a connected assessment process
A central challenge in engineering program assessment is tracing the path from individual student work to program-level conclusions. Course grades alone do not automatically show whether students have achieved a broader outcome. Programs need a documented method that links assignments and other evidence to specific skills, then interprets that evidence consistently.
In its 2012 review, the computer engineering program received a weakness related to continuous improvement. The assessment process was described as thorough, but the connection between course-level data and the evaluation of student outcomes was not sufficiently clear. Some outcomes also included several distinct characteristics that had not been separated for assessment. Without that detail, it was difficult to determine precisely which parts of an outcome students had achieved.
The issue is relevant well beyond accreditation. In engineering education, broad statements such as the ability to design a solution or work effectively on a team must be translated into observable elements. Otherwise, educators and program leaders may collect substantial amounts of information without being able to identify where learning is strong or where changes are needed.
Make outcomes measurable at the level of student work
The program’s response included a more structured assessment approach. Its self-study describes a course assessment matrix, an assessment schedule, indicators for student outcomes, and rubrics for evaluating performance. Together, these tools provide a framework for connecting learning activities to program expectations.
An outcome indicator makes a broad capability more specific. A rubric then describes how student work will be evaluated against that indicator. This approach helps faculty distinguish between different elements of performance rather than assigning a single, general judgment to a complex outcome. It also gives a program a clearer basis for comparing evidence collected across courses and assessment periods.
For engineering programs, the practical sequence is:
- Define the outcome: State what students should be able to demonstrate.
- Break it into assessable elements: Identify the component skills or behaviors that can be observed in student work.
- Choose evidence: Map relevant assignments or course activities to those elements.
- Apply a rubric: Use stated criteria to evaluate performance consistently.
- Review results: Interpret the evidence and decide whether program changes are warranted.
This is not simply a documentation exercise. The value lies in making findings actionable: if results reveal a gap, faculty can investigate where the relevant knowledge or practice appears in the curriculum and consider whether instruction, course sequencing, or assessment needs adjustment.
Use stakeholder feedback for the right questions
Student outcomes and program educational objectives are related, but they describe different stages. Student outcomes concern what students demonstrate by the time they complete the program. Program educational objectives describe what graduates are expected to attain within a few years after graduation. Assessment sources should reflect that distinction.
The 2012 review identified a concern with relying on feedback from current students—such as course surveys, self-evaluations, and senior exit surveys—to judge objectives focused on graduates’ later careers. Those tools can provide useful information about the educational experience, but they do not directly show what graduates attain after entering professional practice.
The program’s documented assessment sources included alumni surveys and input from its Industry Advisory Board, alongside feedback from graduating students and course-level assessment. These sources serve different purposes. Course evidence can help evaluate learning before graduation; graduating-student feedback can describe students’ perceptions at program completion; alumni and industry input can inform consideration of longer-term objectives and professional relevance.
For technical programs, this distinction supports better decisions. A curriculum team can use direct student work to identify learning needs, while graduate and employer perspectives can help test whether program objectives remain appropriate. No single source answers every question, so the evidence needs to be matched to the question being asked.
Close the loop with documented action
Assessment becomes continuous improvement only when findings lead to review and, where appropriate, action. The self-study reports that computer engineering faculty redefined the program educational objectives, sought feedback from the Industry Advisory Board, and developed a roadmap to address the assessment process. The roadmap was implemented over the following three years. The report states that ABET removed the two identified weaknesses and one concern in an August 2013 statement.
The self-study also describes a separate institutional-support concern: budget reductions had affected access to technical journal subscriptions. The university amended the library budget in response. This example shows that program quality depends not only on course design but also on resources that support teaching and learning.
For engineering leaders, the useful lesson is to preserve a clear record of the improvement cycle: what evidence was reviewed, what the review indicated, what action was taken, and how the program will evaluate whether the response was appropriate. A scheduled assessment plan helps distribute the work over time rather than concentrating it around an accreditation visit.
Practical implications for engineering programs
The computer engineering self-study presents accreditation as an ongoing management process built on evidence and feedback. Programs can strengthen that process by ensuring that:
- Each student outcome is linked to specific, assessable evidence.
- Rubrics address the component skills within complex outcomes.
- Assessment sources are appropriate to the timescale of the question.
- Course-level findings are reviewed in relation to program-level expectations.
- Improvement actions and their follow-up are documented.
- Facilities and information resources are considered as part of program support.
For industrial automation and other engineering fields, graduates must apply technical knowledge in systems where multiple components and disciplines interact. Programs that assess specific capabilities and respond to evidence can better understand how their curriculum supports that preparation. The practical value of ABET accreditation, then, lies not only in demonstrating compliance, but in maintaining a disciplined feedback loop that helps keep educational objectives, student learning, and program resources aligned.