MétaCan
Menu
Back to cohort
Record W2004091746 · doi:10.1109/fie.2011.6142927

Providing end-to-end perspectives in software engineering

2011· article· en· W2004091746 on OpenAlexfundno aff
Michael Herold, Joe Bolinger, Rajiv Ramnath, Thomas E. Bihari, Jay Ramanathan

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Techniques and Practices
Canadian institutionsnot available
FundersCanada Excellence Research Chairs, Government of CanadaNational Science Foundation
KeywordsComputer scienceCurriculumSoftware deploymentSoftware engineeringSoftware developmentContext (archaeology)Consistency (knowledge bases)Engineering managementSoftwareProcess (computing)Social software engineeringKnowledge managementEngineeringSoftware constructionPedagogyArtificial intelligenceProgramming language

Abstract

fetched live from OpenAlex

In order to better prepare students for professional practice, we have created a software engineering curriculum that provides an end-to-end perspective that begins with the business context of software, and goes all the way to the ongoing management of software services after deployment. This paper examines how the theoretical aspects of this broad-based curriculum may be effectively delivered through a single course within a traditional computer science program. This curriculum is under a diverse set of constraints and requirements, such as the need for pedagogical consistency, faculty development, consideration of the learning style of computer science students, and a need for an effective continuous improvement process. Our approach uses “engineering-oriented” analysis frameworks such as Porter's Five Forces model for the business aspects, and attribute-driven design for software architectures, an “inverted” classroom mode of teaching where lectures are delivered on line with interactions and exercises that promote active learning reserved for the classroom, case studies developed from real projects to serve as concrete examples, open discussion boards and weekly short quizzes for concept refinement and retention, and a paper-based project where students apply the concepts learned. Faculty development and replication outside the current site are also discussed.

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 machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.013
metaresearch head score (Gemma)0.016
Version: metacan-v3-hybrid-931329e0061cValidation 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: none
Teacher disagreement score0.013
Threshold uncertainty score0.067

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0130.016
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0020.001
Science and technology studies0.0040.009
Scholarly communication0.0110.012
Open science0.0020.013
Research integrity0.0040.010
Insufficient payload (model declined to judge)0.0100.004

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.036
GPT teacher head0.249
Teacher spread0.213 · 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 source (direct Gemma or distilled Codex), 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

Citations4
Published2011
Admission routes1
Has abstractyes

Explore more

Same topicSoftware Engineering Techniques and PracticesFrench-language works237,207