Student or educator? Sign up with your school email and get 6 months of Pro free.
Cited by 472

The DOI matches its Crossref record; 40 of the 40 references it cites were found in a registry or an index.

What Competencies Should Undergraduate Engineering Programs Emphasize? A Systematic Review

Passow, Honor J., Passow, Christian H.·2017·Journal of Engineering Education

Abstract

Background: Under Washington Accord or ABET accreditation requirements, faculty must envision, collectively articulate, and prioritize the competencies that students should gain from their educational program to prepare for life and myriad career paths. Purpose: When faculty create specifications for designing a curriculum, they need to answer questions, including “Among generic engineering competencies, what is the relative importance for professional practice across disciplines and work contexts?” Scope/Method: A search identified the intersection of four concepts (competence, engineering, practice, and importance) in engineering and education databases (8,232 reports, 1990–2012). This review integrates a quantitative synthesis inspired by meta‐analytic techniques (27 studies, 14,429 participants) and a qualitative thematic analysis (25 studies, 2,174 participants plus 36,100 job postings) to establish a comprehensive list of generic engineering competencies, their relative importance, and rich descriptions highlighting interrelationships. Conclusions: Engineers' technical work is inseparably intertwined with team‐player collaboration. The most crucial skill is coordinating multiple competencies to accomplish a goal. Sixteen generic competencies important for engineering practice are defined. Compared with Washington Accord graduate attributes, the evidence‐based competencies re‐envision “teamwork” as coordinate efforts, split “life‐long learning” into gather information and expand skills, broaden “ethics” to take responsibility, expand “design experiments” to measure accurately and separate it from interpret data, apply “contemporary issues” and “impacts” in define constraints, modify “manage projects” to devise process,and add important competencies (take initiative,think creatively, and make decisions). Definitions are refined for communicate effectively,design solutions,apply knowledge, apply skills,and solve problems. Problem solving is the core of engineering practice.

Overview

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1002/jee.20171

Cites

40 of 40 references verified0 citation errors · 0 not checkable

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.

A few free checks a day · papers already verified open instantly · results are public

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cites

Cited by

See all 472

Metadata

Authors
Passow, H. J., & Passow, C. H.
Venue
Journal of Engineering Education
Publisher
Wiley
Published
2017-07-19
Volume
106
Issue
3
Pages
475-526
ISSN
  • 1069-4730 (ISSN-L)
  • 2168-9830
OpenAlex
W2739098987
Cited by
472
References
40
FWCI
12.22
Type
journal article
Language
en
Open access
closed

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.