ABET accreditation is more than a review of course lists. It asks engineering programs to show how educational objectives are defined, how student outcomes are assessed and how assessment results lead to improvement. A 2012 self-study by the University of California, Riverside (UCR) Electrical Engineering program offers a concrete example: earlier accreditation findings prompted changes to course requirements, outcome documentation and the design project sequence.
For industrial automation engineers, system integrators and plant leaders, the report is relevant as a case study in how engineering education translates broad expectations into defined requirements and evidence. It describes an academic process, not an evaluation of automation operations, but its emphasis on traceability, technical depth and documented results will be familiar to organizations that rely on disciplined engineering practices.
What ABET accreditation asks programs to demonstrate
The report describes accreditation criteria that connect a program’s educational objectives with the needs of its constituencies, including faculty, alumni and employers. Programs must also assess student outcomes and use the results to improve the curriculum. In other words, stating that a subject is taught is not enough: a program needs a way to show what students can do and how that capability is evaluated.
UCR’s self-study recounts four weaknesses identified in a draft review following a 2006 site visit. They concerned educational objectives, student-outcome assessment, the professional component of the curriculum and electrical engineering program criteria. The report documents how the department responded and how the accreditation body later resolved the identified weaknesses.
Turning accreditation findings into curriculum changes
Make student outcomes observable
One finding concerned insufficient evidence that students achieved several outcomes, including designing and conducting experiments, working on multidisciplinary teams, understanding professional and ethical responsibility, and recognizing the broader impacts of engineering solutions. The department said that some of these topics were already covered in its senior design sequence, but that coverage was not adequately documented.
In response, the program revised the EE175A/B senior design syllabus to identify relevant outcomes and connect them to assignments and assessment. It also used EE/CSE 120A/B to address multidisciplinary teamwork. This distinction matters: curriculum content and evidence of learning are related, but they are not interchangeable. An assessment process needs identifiable work that can be reviewed against the intended outcome.
Specify engineering constraints and standards
The review also questioned whether all senior design projects demonstrated the use of engineering standards and realistic constraints. The department revised the design specification requirements so that these elements were explicitly included in project documentation.
For engineering teams, the parallel is straightforward: requirements need to be clear enough that reviewers can verify them. In the academic setting described here, the project brief and final work provide evidence. In industrial settings, teams likewise benefit from making design constraints, applicable standards and acceptance criteria explicit within their own engineering processes—but the report itself makes claims only about the university program.
Ensure both breadth and depth
Another finding focused on the balance of breadth and depth in the electrical engineering curriculum. Under the previous elective rules, a student could potentially take introductory courses across several areas without completing a coherent advanced sequence. The program changed its catalog requirements to require at least three electrical engineering courses in a coherent sequence, giving students depth in one area.
The department also replaced a general probability and statistics requirement with a new electrical engineering course covering probability, random variables and random processes in applications specific to the discipline. These changes tied mathematical preparation more directly to electrical engineering practice while clarifying the expected scope of technical study.
Close the loop with stakeholder feedback
The report’s account of educational objectives highlights the importance of connecting review processes to stakeholder input. In response to an earlier finding, the department described a process for gathering feedback from faculty, alumni and industry or employers, and proposed revised objectives developed in consultation with these constituencies. It also reported examples of changes made through the process, including the introduction of a programming course.
This is the substance of continuous improvement in engineering education: collect relevant feedback, define what should change, implement the change and retain evidence that it took place. A process is more credible when the path from feedback to action can be followed rather than inferred.
Why documentation is part of engineering quality
Across the findings, a recurring issue was not simply whether the program addressed a topic, but whether it could demonstrate that the requirement was met. The department’s responses used concrete mechanisms: revised syllabi, assignments linked to outcomes, a required course, and a more prescriptive elective sequence. Such documentation made expectations easier to inspect and assessment easier to connect to learning activities.
For technical decision-makers, the broader takeaway is not that accreditation and industrial project governance are identical. Rather, the report illustrates a useful principle: requirements, implementation and evidence should align. When they do, reviewers can assess whether a program—or a defined engineering process—has delivered what it set out to deliver.
Conclusion
UCR’s 2012 self-study shows how ABET findings can prompt specific and verifiable changes: clearer outcome assessment, explicit senior design constraints, discipline-focused coursework and greater depth in technical electives. The practical implication is that continuous improvement depends on more than identifying gaps. It requires translating findings into defined actions and retaining evidence of implementation. That approach offers a useful reference for anyone concerned with the preparation and evaluation of engineering capability.