pith. sign in

arxiv: 2605.20401 · v1 · pith:JHU7YNZJnew · submitted 2026-05-19 · 💻 cs.SE

A Semantic-Web Oriented Competency Model for Engineering Programs

Nicolas Evain (LIUPPA) , Ernesto Exposito (LIUPPA) , Philippe Arnould (LIUPPA) This is my paper

Pith reviewed 2026-05-21 06:55 UTC · model grok-4.3

classification 💻 cs.SE
keywords competency mappingBodies of Knowledgecomputing curriculasemantic wikiengineering educationcurriculum designISANUMComputing Curricula 2020
0
0 comments X

The pith

A methodology maps Bodies of Knowledge to assessable competency frameworks for computing engineering curricula.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The paper establishes a replicable methodology for translating Bodies of Knowledge into assessable competency frameworks to design computing curricula. It demonstrates the approach through the ISANUM five-year engineering program, which structures 23 competencies into five thematic blocks with explicit mappings to 494 knowledge topics drawn from 34 areas in Computing Curricula 2020. The program combines three specialized pathways in Software Engineering, Data Engineering & Data Science, and Information Technology with mandatory work-study placements to build both theoretical foundations and practical workplace skills. A sympathetic reader would care because the work supplies a concrete bridge between comprehensive knowledge documentation and coherent, professionally relevant curricula that educators can adapt and maintain collaboratively.

Core claim

The central claim is that a competency-mapping methodology bridges Bodies of Knowledge and competency frameworks for computing curricula, as shown in the ISANUM program with its 23 competencies organized in five thematic blocks, explicit mappings to 494 knowledge topics from Computing Curricula 2020, integration of three specialized pathways, and mandatory work-study programs that together develop theoretical foundations alongside practical workplace competencies, all supported by the ISANUMpedia semantic wiki infrastructure for collaborative understanding, maintenance, and evolution.

What carries the argument

The competency-mapping methodology, which translates Bodies of Knowledge into assessable frameworks and is supported by semantic wiki infrastructure for ongoing collaborative curriculum management.

If this is right

  • Computing educators receive a replicable process for converting Bodies of Knowledge into structured, assessable competency frameworks.
  • The semantic wiki infrastructure enables collaborative maintenance and evolution of the curriculum over time.
  • The five thematic blocks and three pathways ensure coverage of both theory and practical skills through integrated work-study.
  • Graduates are positioned with documented links between 494 knowledge topics and the 23 competencies for professional assessment.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • The same mapping process could be tested in non-computing engineering fields to check transferability.
  • Semantic web features might support automated detection of curriculum gaps when new knowledge topics emerge.
  • Long-term graduate outcome studies could provide direct evidence on whether the mappings improve workplace readiness.
  • The model offers a template for aligning future revisions of international curricula standards with competency requirements.

Load-bearing premise

The explicit mappings from knowledge topics to the 23 competencies will produce graduates who gain both theoretical foundations and practical, assessable workplace competencies that remain professionally relevant.

What would settle it

Follow-up data on ISANUM graduates that measures whether they demonstrate the defined competencies in actual workplace performance at rates distinguishable from graduates of programs lacking these explicit mappings.

Figures

Figures reproduced from arXiv: 2605.20401 by Ernesto Exposito (LIUPPA), Nicolas Evain (LIUPPA), Philippe Arnould (LIUPPA).

Figure 1
Figure 1. Figure 1: Competency mapping methodology Once the expected competencies of a training program have been constructed, and validated by potential employers, the training pro￾gram can be developed in a precise and detailed manner through learning activities built around learning objects and learning paths. A course or learning path can be defined through a process based on a series of stages involving interaction with … view at source ↗
Figure 2
Figure 2. Figure 2: Structure of an ISANUM competency definition [PITH_FULL_IMAGE:figures/full_fig_p004_2.png] view at source ↗
read the original abstract

Despite comprehensive Bodies of Knowledge (BoKs) documenting core knowledge across software engineering, computer science, information systems, and emerging computing fields, a critical gap persists: methodologies for integrating this knowledge into coherent competency-based curricula that prepare graduates for professional careers remain underdeveloped. This paper presents a competency-mapping methodology that bridges Bodies of Knowledge and competency frameworks to design computing curricula. We demonstrate this methodology through ISANUM, a five-year engineering degree program featuring 23 competencies organized into five thematic blocks, each with explicit mappings to 494 knowledge topics from 34 Computing Knowledge areas defined in Computing Curricula 2020. The program integrates three specialized pathways (Software Engineering, Data Engineering \& Data Science, and Information Technology) with mandatory work-study programs, ensuring graduates develop both theoretical foundations and practical workplace competencies. Our contribution provides computing educators with a replicable methodology for translating Bodies of Knowledge into assessable competency frameworks, supported by a semantic wiki infrastructure (ISANUMpedia) enabling collaborative curriculum understanding, maintenance and evolution.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

2 major / 2 minor

Summary. The paper presents a competency-mapping methodology to bridge Bodies of Knowledge from Computing Curricula 2020 with competency frameworks for computing engineering curricula. It demonstrates the approach via the ISANUM five-year program, which defines 23 competencies organized into five thematic blocks, each with explicit mappings to 494 knowledge topics across 34 areas, incorporates three specialized pathways (Software Engineering, Data Engineering & Data Science, Information Technology), mandates work-study programs, and supports the model with the ISANUMpedia semantic wiki for collaborative maintenance and evolution. The central contribution is positioned as a replicable methodology for translating BoKs into assessable competency frameworks.

Significance. If the mappings prove effective and replicable, the work could supply computing educators with a concrete, semantic-web-supported process for aligning curricula with professional standards and enabling ongoing evolution. The explicit structure of thematic blocks, pathways, and the wiki infrastructure represents a practical strength for curriculum design and maintenance in software engineering education.

major comments (2)
  1. [Abstract] Abstract: The claim that the described mappings and program structure 'ensuring graduates develop both theoretical foundations and practical workplace competencies' rests on the untested premise that the specific 23 competencies and 494 topic mappings are correctly aligned and sufficient; the manuscript supplies no assessment data, graduate outcome metrics, employer validation, or replication studies to support professional relevance or assessability.
  2. [ISANUM program demonstration] ISANUM program demonstration (case study section): The detailed mappings from competencies to Computing Curricula 2020 topics are presented without any analysis of coverage completeness, justification for competency selection against industry requirements, or discussion of potential gaps, which is load-bearing for the replicability and effectiveness claims.
minor comments (2)
  1. [Tables/Figures] Consider adding a table or summary statistic showing the distribution of the 494 topics across the five thematic blocks and three pathways to improve readability of the mapping scale.
  2. [References] Verify that all references to external standards (Computing Curricula 2020 and related BoKs) include precise version citations and URLs for reader access.

Simulated Author's Rebuttal

2 responses · 0 unresolved

We thank the referee for their constructive comments, which help clarify the scope and limitations of our contribution. We respond to each major comment below.

read point-by-point responses

  1. Referee: [Abstract] Abstract: The claim that the described mappings and program structure 'ensuring graduates develop both theoretical foundations and practical workplace competencies' rests on the untested premise that the specific 23 competencies and 494 topic mappings are correctly aligned and sufficient; the manuscript supplies no assessment data, graduate outcome metrics, employer validation, or replication studies to support professional relevance or assessability.

    Authors: We agree that the manuscript presents no empirical assessment data, graduate metrics, or external validation studies. The abstract phrasing describes the intended design outcome of combining CC2020-derived knowledge with mandatory work-study integration rather than claiming proven effectiveness. We will revise the abstract to qualify the claim as design intent and add a brief limitations paragraph noting that empirical validation and replication studies remain future work. revision: yes

  2. Referee: [ISANUM program demonstration] ISANUM program demonstration (case study section): The detailed mappings from competencies to Computing Curricula 2020 topics are presented without any analysis of coverage completeness, justification for competency selection against industry requirements, or discussion of potential gaps, which is load-bearing for the replicability and effectiveness claims.

    Authors: The 23 competencies were selected to align the five thematic blocks and three pathways with the 34 CC2020 knowledge areas while supporting the five-year work-study structure. We acknowledge that the current case-study section does not explicitly analyze coverage completeness or discuss potential gaps. We will add a dedicated subsection that (a) justifies the competency selection against CC2020 and the program's industry-oriented pathways, (b) summarizes topic coverage across the 494 mappings, and (c) identifies areas where gaps may exist and how ISANUMpedia can support future refinement. revision: yes

Circularity Check

0 steps flagged

No circularity: descriptive methodology relying on external standards

full rationale

The paper presents a replicable methodology for mapping Bodies of Knowledge to competency frameworks, demonstrated via the ISANUM program with 23 competencies explicitly linked to 494 topics from the external Computing Curricula 2020 standard. No equations, fitted parameters, predictions, or self-referential definitions appear in the provided content. The central contribution is the construction of these mappings and the ISANUMpedia infrastructure as part of the case study itself, not a reduction of any claimed result back to prior inputs by construction. The work is self-contained against external benchmarks and does not invoke load-bearing self-citations or uniqueness theorems that collapse the argument.

Axiom & Free-Parameter Ledger

0 free parameters · 2 axioms · 0 invented entities

The paper rests on the domain assumption that existing Bodies of Knowledge and Computing Curricula 2020 provide a complete and appropriate foundation for competency design, plus the assumption that semantic web tools can effectively support collaborative curriculum evolution. No free parameters or invented entities are introduced.

axioms (2)
  • domain assumption Bodies of Knowledge document core knowledge across software engineering, computer science, information systems, and emerging computing fields in a usable form for curriculum design.
    Invoked in the opening sentence as the starting point for the methodology.
  • domain assumption Competency frameworks can be coherently derived from Bodies of Knowledge to prepare graduates for professional careers.
    Central premise of the bridging methodology described.

pith-pipeline@v0.9.0 · 5710 in / 1355 out tokens · 29358 ms · 2026-05-21T06:55:02.367345+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Lean theorems connected to this paper

Citations machine-checked in the Pith Canon. Every link opens the source theorem in the public Lean library.

What do these tags mean?
matches
The paper's claim is directly supported by a theorem in the formal canon.
supports
The theorem supports part of the paper's argument, but the paper may add assumptions or extra steps.
extends
The paper goes beyond the formal theorem; the theorem is a base layer rather than the whole result.
uses
The paper appears to rely on the theorem as machinery.
contradicts
The paper's claim conflicts with a theorem or certificate in the canon.
unclear
Pith found a possible connection, but the passage is too broad, indirect, or ambiguous to say the theorem truly supports the claim.

Reference graph

Works this paper leans on

27 extracted references · 27 canonical work pages

  1. [1]

    Joel C. Adams. 2020. Computing Continues to Dominate STEM Career Opportuni- ties. https://cacm.acm.org/blogcacm/computing-continues-to-dominate-stem- career-opportunities Posted Jan 4, 2020. Accessed: 2025-11-03

    work page 2020

  2. [2]

    SEBoK Editorial Board. 2024. The Guide to the Systems Engineering Body of Knowledge (SEBoK). The Trustees of the Stevens Institute of Technology. https: //www.sebokwiki.org

    work page 2024

  3. [3]

    Bourque and eds R.E

    P. Bourque and eds R.E. Fairley. 2014. Guide to the Software Engineering Body of Knowledge, Version 3.0. Technical Report. https://www.computer.org/education/ bodies-of-knowledge/software-engineering

    work page 2014

  4. [4]

    Adcock et al. 2009. Curriculum Guidelines for Graduate Degree Programs in Software Engineering. Technical Report. New York, NY, USA. doi:10.1145/2593248

    work page doi:10.1145/2593248 2009

  5. [5]

    Cassel et al. 2008. Computer Science Curriculum 2008: An Interim Revision of CS

    work page 2008

  6. [7]

    May, 2024

    Evain et al. May, 2024. Ontology-driven approach for competency-oriented and student-centered engineering education. (May, 2024). doi:10.1109/EDUCON60312. 2024.10578793

    work page doi:10.1109/educon60312 2024

  7. [8]

    Kumar et al. 2024. Computer Science Curricula 2023 . Association for Computing Machinery, New York, NY, USA. doi:10.1145/3664191

    work page doi:10.1145/3664191 2024

  8. [9]

    Lunt et al. 2008. Curriculum Guidelines for Undergraduate Degree Programs in Information Technology. Technical Report. New York, NY, USA. doi:10.1145/ 2593311

    work page 2008

  9. [10]

    Topi et al. 2010. IS2010: Curriculum Guidelines for Undergraduate Degree Programs in Information Systems . Technical Report. New York, NY, USA. doi:10.1145/ 2593310

    work page 2010

  10. [11]

    2017.MSIS 2016: Global Competency Model for Graduate Degree Programs in Information Systems

    Topi et al. 2017.MSIS 2016: Global Competency Model for Graduate Degree Programs in Information Systems . Technical Report. New York, NY, USA. doi:10.1145/ 3129538

    work page 2017

  11. [12]

    ACM Data Science Task Force. 2021. Computing competencies for undergraduate data science curricula . Association for Computing Machinery, New York, NY, USA. doi:10.1145/3453538

    work page doi:10.1145/3453538 2021

  12. [13]

    CC2020 Task Force. 2020. Computing Curricula 2020: Paradigms for Global Com- puting Education. Association for Computing Machinery, New York, NY, USA. doi:10.1145/3467967

    work page doi:10.1145/3467967 2020

  13. [14]

    The Joint ACM/AIS IS2020 Task Force, Paul Leidig, and Hannu Salmela. 2021. A Competency Model for Undergraduate Programs in Information Systems . Associa- tion for Computing Machinery, New York, NY, USA. doi:10.1145/3460863

    work page doi:10.1145/3460863 2021

  14. [15]

    Washizaki

    eds H. Washizaki. 2024. Guide to the Software Engineering Body of Knowledge (SWEBOK Guide), Version 4.0 . IEEE Computer Society. https://ieeecs-media. computer.org/media/education/swebok/swebok-v4.pdf

    work page 2024

  15. [16]

    Sarah Harris and David Harris. 2015. Digital Design and Computer Architecture: ARM Edition (1st ed.). Morgan Kaufmann Publishers Inc., San Francisco, CA, USA. doi:10.5555/2815529

    work page doi:10.5555/2815529 2015

  16. [17]

    DR Krathwohl. 2002. A Revision Bloom’s Taxonomy: An Overview. Theory into Practice (2002)

    work page 2002

  17. [18]

    2021.The Cyber Security Body of Knowledge v1.1.0, 2021

    Andrew Martin, Awais Rashid, Howard Chivers, George Danezis, Steve Schneider, and Emil Lupu. 2021.The Cyber Security Body of Knowledge v1.1.0, 2021. University of Bristol. https://www.cybok.org/

    work page 2021

  18. [19]

    Bureau of Labor Statistics

    U.S. Bureau of Labor Statistics. 2025.Table 1.2: Occupational projections, 2024–2034, and worker characteristics . https://www.bls.gov/emp/tables/occupational- projections-and-characteristics.htm Accessed: 2025-11-03

    work page 2025

  19. [20]

    2016.Curriculum Guidelines for Undergraduate Degree Programs in Computer Engineering

    Joint Task Force on Computer Engineering Curricula. 2016.Curriculum Guidelines for Undergraduate Degree Programs in Computer Engineering . Technical Report. New York, NY, USA. doi:10.1145/3025098

    work page doi:10.1145/3025098 2016

  20. [21]

    Joint Task Force on Computing Curricula. 2013. Computer Science Curricula 2013: Curriculum Guidelines for Undergraduate Degree Programs in Computer Science . Association for Computing Machinery and IEEE Computer Society, New York, NY, USA. doi:10.1145/253486

    work page doi:10.1145/253486 2013

  21. [22]

    The Joint Task Force on Computing Curricula. 2004. Curriculum Guide- lines for Undergraduate Degree Programs in Computer Engineering . Techni- cal Report. https://www.acm.org/binaries/content/assets/education/curricula- recommendations/ce-final-report.pdf

    work page 2004

  22. [23]

    The Joint Task Force on Computing Curricula. 2004. Curriculum Guidelines for Undergraduate Degree Programs in Software Engineering . Technical Report. New York, NY, USA. doi:10.1145/2594168

    work page doi:10.1145/2594168 2004

  23. [24]

    The Joint Task Force on Computing Curricula. 2015. Curriculum Guidelines for Undergraduate Degree Programs in Software Engineering . Technical Report. New York, NY, USA. doi:10.1145/2965631

    work page doi:10.1145/2965631 2015

  24. [25]

    Joint Task Force on Cybersecurity Education. 2018. Cybersecurity Curricula 2017: Curriculum Guidelines for Post-Secondary Degree Programs in Cybersecurity . Association for Computing Machinery, New York, NY, USA. doi:10.1145/3184594

    work page doi:10.1145/3184594 2018

  25. [26]

    Task Group on Information Technology Curricula. 2017. Information Technology Curricula 2017: Curriculum Guidelines for Baccalaureate Degree Programs in Infor- mation Technology. Association for Computing Machinery, New York, NY, USA. doi:10.1145/3173161

    work page doi:10.1145/3173161 2017

  26. [27]

    IEEE Computer Society. 2025. Enterprise Integration Technical Body of Knowledge (EITBOK). http://eitbokwiki.org/Main_Page Accessed: 2025-11-03

    work page 2025

  27. [28]

    France Travail. 2025. Labour Needs Survey – Number of Recruitment Projects in 2025 - France. https://statistiques.francetravail.org/bmo/bmo?graph=5&fg=JZ& la=0&va=0&pp=2025&ss=1 Accessed: 2025-11-03. Received 3 October 2025; accepted 3 December 2025

    work page 2025