MétaCan
Menu
Back to cohort
Record W2603486877 · doi:10.24908/pceea.v0i0.6495

USING META-CASES FOR CAPSTONE LEARNING

2017· article· en· W2603486877 on OpenAlexaffvenue
Stephen L. James, Douglas Ruth

Bibliographic record

VenueProceedings of the Canadian Engineering Education Association (CEEA) · 2017
Typearticle
Languageen
FieldEngineering
TopicEngineering Education and Curriculum Development
Canadian institutionsUniversity of Manitoba
Fundersnot available
KeywordsCapstoneExperiential learningEngineering educationProject-based learningComputer scienceEngineering managementEngineering ethicsEngineeringMathematics educationPsychology

Abstract

fetched live from OpenAlex

The purpose of capstone courses and projects in engineering is to provide a learning experience that effectively and reliably solidifies earlier acquired understandings. It provides a culminating exercise that lies just beyond a student’s existing ability so that learning is furthered while motivation is preserved. Historically, individual engineering projects, practicums, and internships have been heavily used to provide that culminating experience; however, with often disappointing results. This has been particularly the case in attempting to cap off programs in systems engineering where the learning ideal would be to have a student experience a real-world complex multi-disciplinary engineering and program environment. Given the limitation, this paper proposes using a term-long, class-based, repeatable meta-case as the capstone learning venue, particularly in support of systems engineering programs where securing meaningful experiential learning is difficult. Case teaching is a classic approach in law, medicine and business faculties where the need to develop higher cognitive abilities—analyzing, synthesizing and judging—inside high ambiguity and across multi-disciplines is paramount. A meta-case, as opposed to other case types, is characterized by the use of a very complex, multi-factor (engineering) real-world challenge with a long, multi-stage solution scenario. In proposing the use of a capstone meta-case, the paper presents its use in an aerospace systems engineering environment where development timelines are very long, and where the engineering requirements and solutions are many and highly interdependent. It specifically discusses the course design structure and considerations associated with a meta-case based on the development of the Airbus A400 military transport aircraft. The paper is based on a year-long study into the use of the case method for teaching aerospace systems engineering.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.308
Threshold uncertainty score0.761

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.032
GPT teacher head0.256
Teacher spread0.223 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2017
Admission routes2
Has abstractyes

Explore more

Same venueProceedings of the Canadian Engineering Education Association (CEEA)Same topicEngineering Education and Curriculum DevelopmentFrench-language works237,207