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

INTEGRATING UCD WITHIN AN AGILE SOFTWARE DEVELOPMENT PROCESS IN AN EDUCATIONAL SETTING

2015· article· en· W1953210639 on OpenAlexaffvenueabout
Olga Ormandjieva, Kristina Pitula, Cherifa Mansura

Bibliographic record

VenueProceedings of the Canadian Engineering Education Association (CEEA) · 2015
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsConcordia University
Fundersnot available
KeywordsAgile software developmentComputer scienceContext (archaeology)Agile usability engineeringSoftware engineeringAccreditationAgile Unified ProcessEngineering managementProcess (computing)Engineering design processSoftwareSoftware development processSoftware developmentEngineeringMedical education

Abstract

fetched live from OpenAlex

The Canadian Engineering Accreditation Boardhas defined 12 attributes that an institution must demonstrategraduates of its engineering program possess. We are inpursuit of the attribute "Design” dealing with the students’ability to select candidate engineering design solutions fordevelopment, with three indicators relating to how candidatesolutions are selected. Our approach to teaching “Design” isbased on “learning outcomes” rather than “teaching inputs”.In this paper, we describe the learning outcomes of teaching anewly proposed Integrated User Centered Design (UCD)-Agile Process in the context of a one term project coursewherein teams of undergraduate students apply what theyhave learnt about Agile software development and UserInterface (UI) design in the context of a real-world projectwith actual clients. The Integrated UCD-Agile Processincludes upfront design of the UI in parallel with developmentof the functionalities, UI design specialists for each sprint andusability testing of all UI design decisions

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.001
metaresearch head score (Gemma)0.003
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.226
Threshold uncertainty score0.663

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.003
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.002
Open science0.0010.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.015
GPT teacher head0.260
Teacher spread0.245 · 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 designObservational
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

Citations1
Published2015
Admission routes3
Has abstractyes

Explore more

Same venueProceedings of the Canadian Engineering Education Association (CEEA)Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207