A well-designed computer engineering curriculum must connect theory with practical capability. That challenge is relevant beyond universities: industrial automation teams also depend on professionals who can understand hardware, software and the interfaces between them. A 2012 University of Florida program self-study offers a detailed example of how an engineering program organized its curriculum, monitored student progress and used stakeholder feedback to guide improvement.
The report describes a joint computer engineering program administered by the university’s Computer and Information Science and Engineering (CISE) and Electrical and Computer Engineering (ECE) departments. Its processes are specific to that program and period, but several principles are broadly useful to technical decision-makers: define the capabilities graduates should develop, align coursework to those goals, and review evidence systematically.
Designing a computer engineering curriculum around connected disciplines
The program’s central educational idea was to prepare students to work across computer hardware and software. Its stated philosophy covered a complete system, from circuits through operating systems to application programs, with engineering analysis, design and implementation connecting those layers.
Students selected one of two tracks:
- Hardware: emphasized areas such as electronic circuits, digital devices and communications.
- Software: included areas such as networks, databases and algorithms.
Both tracks shared a core intended to provide a foundation in computer engineering. This structure reflects a practical curriculum-design question: which competencies should every graduate share, and where should specialization begin? The report’s proposed redesign aimed to establish a clearer common core while allowing more flexible specialization through certificate options. At the time of the self-study, that redesign was still under consideration, not yet implemented.
For automation organizations, the parallel is not that every engineer needs identical expertise. Rather, teams benefit when core knowledge is explicit and specialist skills are developed on top of it. In a multidisciplinary environment, shared foundations can help people communicate across system boundaries.
Linking educational objectives to measurable student outcomes
The self-study distinguished between program educational objectives and student outcomes. Educational objectives described what graduates were expected to achieve three to five years after graduation: career success in computer engineering, continued learning, effectiveness in diverse professional environments, and leadership with professional integrity. Student outcomes, by contrast, addressed the capabilities students should develop during the program.
This distinction helps make improvement work actionable. Long-term objectives express the broader purpose of a program; student outcomes translate that purpose into capabilities that can be examined during a student’s education. A curriculum can then be reviewed to see whether courses provide opportunities to develop those capabilities.
The report also described changes made after the previous general ABET review. Examples included changing the instructional language in a data structures and algorithms course, adding laboratory time to an introductory course, and adding Java threading and synchronization topics to an operating systems course. These are examples of course-level adjustments, not claims that any one change produced a particular result. Their value lies in showing how a program can respond to perceived needs by revisiting specific content and learning experiences.
Using assessment as a continuous improvement loop
Assessment is useful when it informs decisions, rather than simply producing documentation. The report organized continuous improvement around defined objectives and outcomes, assessment processes, expected levels of attainment, analysis of results, and records of decisions. This creates a loop: establish what should be learned, gather evidence, evaluate the findings and decide whether changes are warranted.
In technical training or workforce development, a similar cycle can clarify whether instruction is preparing people for the work they must perform. Teams can identify essential capabilities, determine where those capabilities are taught or practiced, review available evidence and revise the learning plan where needed. The source does not prescribe a particular assessment tool, so the method should be chosen to fit the program and the skills being evaluated.
Making stakeholder feedback part of program governance
The program identified faculty, alumni and employers as important constituencies. Its Industrial Advisory Board included representatives from companies employing graduates, and the board met twice a year to discuss the program and provide feedback. Alumni surveys also contributed information about graduates’ progress and the relevance of the program’s objectives.
Feedback had a defined route into decision-making. Recommendations could be directed to curriculum or administrative committees, considered by the computer engineering faculty, and submitted for college approval where required. The program also described communicating changes back to the advisory board. This governance process matters: collecting opinions is not the same as showing how those opinions are considered.
Industrial organizations can apply the same principle to skills planning. Input from operations, engineering, maintenance and leadership is more useful when responsibilities for reviewing it and acting on it are clear. A structured process helps connect changing technical needs to decisions about training, role development and technical education.
Supporting progression through advising and prerequisites
The report also shows how curriculum quality depends on more than course content. Students were monitored through degree audits and advising, while prerequisite controls helped ensure that students completed required preparation before advancing. Students who fell behind received additional advising, and academic progress was reviewed each semester.
These mechanisms address progression: learners need a coherent sequence of experiences and timely guidance when they encounter barriers. In industrial settings, a skills pathway similarly needs defined prerequisites and visibility into whether employees are ready to move to more advanced responsibilities. The specific tools will differ, but the underlying goal is to make expectations and progression understandable.
Practical lessons for technical decision-makers
The University of Florida self-study presents a program-level example, not a universal template. Still, it highlights several useful practices for organizations responsible for technical capability:
- Define shared core competencies before organizing specialist pathways.
- Connect broad objectives to observable, teachable outcomes.
- Review course or training content when technical needs change.
- Gather feedback from people who teach, learn and use the resulting skills.
- Assign a clear process for evaluating feedback and documenting decisions.
- Support progression with prerequisites, advising and regular progress checks.
For automation engineers, system integrators and plant leaders, the central implication is that capability development works best as a coordinated system. Curriculum, assessment, stakeholder input and learner support should reinforce one another. When these elements are connected, organizations can make skill expectations clearer and base improvement decisions on an ongoing review of needs and results.