MétaCan
Menu
Back to cohort

Professional competencies of future software engineers in the software design: teaching techniques

2022· article· en· W4283278744 on OpenAlexaboutno aff
Andrii M. Striuk, Сергій Олексійович Семеріков

Bibliographic record

VenueJournal of Physics Conference Series · 2022
Typearticle
Languageen
FieldEngineering
TopicTechnology Assessment and Management
Canadian institutionsnot available
Fundersnot available
KeywordsSocial software engineeringSoftware developmentSoftware engineeringCompetence (human resources)Software Engineering Process GroupEngineering managementPersonal software processSoftware requirementsSoftware constructionSoftware peer reviewComputer scienceEngineeringSoftware

Abstract

fetched live from OpenAlex

Abstract The article is devoted to one of the competence components of a mobile-oriented environment for professional and practical training of future software engineers. It is shown that the introduction of higher education standard 121 “Software Engineering” for the first (bachelor) level of higher education in Ukraine has generated a number of training quality assurance problems associated primarily with the low level of detailed competencies and program learning outcomes. By solving these problems, the detailed design of the system of professional competencies for future software engineers is developed. The article deals with the approaches to developing one of the most important special professional competences of future software engineers – the ability to participate in software design, including modeling (formal description) of its structure, behavior, and processes of functioning. Based on a historical and genetic review of the software engineering training practice of future software engineers in the USA, UK, Canada, Australia, New Zealand and Singapore, recommendations for choosing forms of training organization, selection of training content, ways of students’ and teachers’ activities in software engineering, modeling and designing tools; assessment of the appropriate competence formation level are formulated. The example of organizing design training in conditions close to industrial-studio training is considered. The problems of transition from architectural to detailed design and project implementation are shown. Prospects for further development of this study are to substantiate the third (after requirements engineering and design engineering) engineering component of software engineering – the software construction.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.818
Threshold uncertainty score0.365

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
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.001
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.235
Teacher spread0.221 · 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 designOther design
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

Citations9
Published2022
Admission routes1
Has abstractyes

Explore more

Same venueJournal of Physics Conference SeriesSame topicTechnology Assessment and ManagementFrench-language works237,207