Skip to content

Sintesi di Software tramite Rappresentazioni Intermedie Ipergrafiche in Formato NDJSON-LD: Formalizzazione di un Framework di Generazione Vincolata per Modelli Linguistici Autoregressivi

Aug 2026 · Zenodo (CERN European Organization for Nuclear Research)
Software Engineering Research

Abstract

Sintesi di Software tramite Rappresentazioni Intermedie Ipergrafiche in Formato NDJSON-LD: Formalizzazione di un Framework di Generazione Vincolata per Modelli Linguistici Autoregressivi Autore: Luigi Usai Affiliazione / Località: Quartucciu (CA), Italia Data: 29 Agosto 2026 ORCID: https://orcid.org/0009-0003-3001-717X Identificatore di Categoria (Zenodo/ACM): Computer Science – Software Engineering (cs.SE); Artificial Intelligence (cs.AI); Formal Languages (cs.FL). Abstract La generazione di software strutturato e monolitico tramite modelli linguistici di grandi dimensioni (LLM) presenta storicamente tassi elevati di allucinazione dell'interfaccia, violazioni di invarianti logici e divergenza sintattica nei contesti zero-shot non vincolati. Questo lavoro formalizza una metodologia di sintesi single-prompt a due stadi basata sull'induzione preventiva di un ipergrafo matematico $H=(V,E)$ serializzato nello standard NDJSON-LD (Newline Delimited JSON for Linked Data). Attraverso la scomposizione delle dipendenze $n$-arie tra tipi, funzioni, invarianti e canali di I/O prima dell'emissione del codice target (Python), il modello riduce drasticamente l'entropia condizionale nello spazio di decodifica autoregressiva. Il formalismo proposto converte il task da un problema di generazione a sintassi libera a una proiezione isomorfa guidata da uno schema topologico. Vengono presentati il framework matematico, la specifica della grammatica NDJSON-LD, l'architettura della pipeline di inferenza e il protocollo sperimentale di falsificazione empirica. Parole chiave: Program Synthesis, Neurosymbolic AI, Hypergraph Theory, NDJSON-LD, Prompt Engineering, Large Language Models, AST Generation, Code Reliability. 1. Introduzione e Definizione del Problema Nei modelli autoregressivi basati sull'architettura Transformer, la probabilità di emissione di una sequenza di codice sorgente $C = (c_1, c_2, \dots, c_T)$ a partire da una specifica informale in linguaggio naturale $P$ è descritta dal prodotto: $$P(C \mid P) = \prod_{t=1}^T P(c_t \mid c_{ [ V_func: PureTransformer ] | | │ | | ▼ | | [ V_inv: BoundaryCheck ] <-- [ V_type: ValidatedOutput ] | +-------------------------------------------------------------+ 3. Specificazione della Sintassi NDJSON-LD La scelta dello standard NDJSON-LD (Newline Delimited JSON-LD) garantisce tre proprietà computazionali ottimali per gli LLM: Streaming line-by-line deterministico: Ogni riga costituisce un'asserzione topologica autosufficiente, minimizzando la complessità dell'albero sintattico durante il parsing. Semantica formale esplicita (@context, @id, @type): Riduzione dell'ambiguità polisemica dei token. Compressione del footprint di contesto: Eliminazione dell'indentazione ricorsiva del JSON standard, massimizzando il throughput della context window. Schema formale di un record NDJSON-LD JSON Data format: RDF-Turtle JSON-LD JSON CSV RDF/XML Markdown RSS Atom {"@context": "https://schema.org/SoftwareSourceCode", "@id": "node:State", "@type": "TypeNode", "signature": "typing.NamedTuple", "properties": {"id": "UUID", "payload": "bytes"}} {"@context": "https://schema.org/SoftwareSourceCode", "@id": "node:Inv1", "@type": "InvariantNode", "predicate": "len(payload) <= 4096"} {"@context": "https://schema.org/SoftwareSourceCode", "@id": "edge:Transform", "@type": "HyperEdge", "sources": ["node:State"], "targets": ["node:Result"], "guards": ["node:Inv1"], "complexity": "O(N)"} 4. Architettura della Pipeline di Sintesi La pipeline di generazione si struttura su un processo deterministico a fasi sequenziali all'interno della medesima sessione di campionamento: Data format: RDF-Turtle JSON-LD JSON CSV RDF/XML Markdown RSS Atom +-------------------------------------------------------------------------+ | Prompt di Vincolo Epistemico + Requisiti Funzionali | +-------------------------------------------------------------------------+ │ ▼ +-------------------------------------------------------------------------+ | Generazione dell'Ipergrafo $H$ in NDJSON-LD | | (Allocazione di token per pianificazione topologica e contrattuale) | +-------------------------------------------------------------------------+ │ ▼ +-------------------------------------------------------------------------+ | Ordinamento Topologico degli Iperarchi | | (Risoluzione delle dipendenze $n$-arie dei nodi sorgente) | +-------------------------------------------------------------------------+ │ ▼ +-------------------------------------------------------------------------+ | Emissione del Codice Python Target | | (Implementazione di protocolli, tipi algebrici, contratti e runtime) | +-------------------------------------------------------------------------+ Regole di Traslazione $H \to \text{Python}$ Ogni $v \in V_{\text{type}}$ viene traslato in classi immutabili @dataclass(frozen=True) o typing.Protocol. Ogni $v \in V_{\text{inv}}$ viene mappato in asserzioni di runtime esplicite o clausole contrattuali (icontract / clausole di guardia). Ogni $e \in E$ viene compilato come funzione pura tipizzata staticamente con annotazioni rigorose (mypy --strict). 5. Analisi Comparativa Parametro di Valutazione Zero-Shot Diretto (P→C) Chain-of-Thought (CoT) Program Dependence Graph (PDG) NDJSON-LD Hypergraph (P→H→C) Modellazione Relazionale Implicita / Sequenziale Sequenziale informale Grafi binari ($\vert{}e\vert{}=2$) Ipergrafi $n$-ari ($\vert{}e\vert{} \ge 2$) Overhead di Parsing Assente Variabile (testo libero) Elevato (XML/DOT) Basso (NDJSON streaming) Preservazione Invarianti Bassa (Decadimento $t > 10^3$) Media Buona (strutturale) Elevata (vincolo esplicito) Allucinazione dei Tipi Elevata Media Bassa Minima (topologia chiusa) 6. Limiti Epistemologici e Protocollo di Falsificazione Per conferire al metodo validità scientifica, sono stabiliti i seguenti criteri di falsificabilità e limitazioni: Limiti intrinseci Complessità degli Iper-cicli: La presenza di dipendenze cicliche tra iperarchi $n$-ari non risolvibili genera blocchi logici che richiedono algoritmi di condensazione topologica a monte della compilazione. Consumo di Output Budget: La generazione dell'ipergrafo NDJSON-LD consuma tra il $20\%$ e il $40\%$ della finestra di generazione massima, limitando la dimensione netta del codice sintetizzabile in singolo turno. Protocollo Sperimentale di Validazione (Ablation Study) Il framework deve essere validato tramite un benchmark quantitativo strutturato come segue: Dataset di Test: SWE-bench Verified (500

View source

Similar papers

#computer vision Open access Jun 2016

Software Development in Startup Companies: The Greenfield Startup Model

Software startups are newly created companies with no operating history and oriented towards producing cutting-edge products. However, despite the increasing importance of startups in the economy, few scientific studies attempt to address software engineering issues, especially for early-stage startups. If anything, startups need engineering practices of the same level or better than those of larger companies, as their time and resources are more scarce, and one failed project can put them out of business. In this study we aim to improve understanding of the software development strategies employed by startups. We performed this state-of-practice investigation using a grounded theory approach. We packaged the results in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible. This strategy allows startups to verify product and market fit, and to adjust the product trajectory according to early collected user feedback. The need to shorten time-to-market, by speeding up the development through low-precision engineering activities, is counterbalanced by the need to restructure the product before targeting further growth. The resulting implications of the GSM outline challenges and gaps, pointing out opportunities for future research to develop and validate engineering practices in the startup context.

Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al. · 179 citations · ⚡14
#computer vision Open access Oct 2016

Software Startups - A Research Agenda

Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models. Software startup ...

M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al. · 157 citations · ⚡17
#machine learning Review Open access Oct 2016

“Failures” to be celebrated: an analysis of major pivots of software startups

In the context of software startups, project failure is embraced actively and considered crucial to obtain validated learning that can lead to pivots. A pivot is the strategic change of a business concept, product or the different elements of a business model. A better understanding is needed on different types of pivots and different factors that lead to failures and trigger pivots, for software entrepreneurial teams to make better decisions under chaotic and unpredictable environment. Due to the nascent nature of the topic, the existing research and knowledge on the pivots of software startups are very limited. In this study, we aimed at identifying the major types of pivots that software startups make during their startup processes, and highlighting the factors that fail software projects and trigger pivots. To achieve this, we conducted a case survey study based on the secondary data of the major pivots happened in 49 software startups. 10 pivot types and 14 triggering factors were identified. The findings show that customer need pivot is the most common among all pivot types. Together with customer segment pivot, they are common market related pivots. The major product related pivots are zoom-in and technology pivots. Several new pivot types were identified, including market zoom-in, complete and side project pivots. Our study also demonstrates that negative customer reaction and flawed business model are the most common factors that trigger pivots in software startups. Our study extends the research knowledge on software startup pivot types and pivot triggering factors. Meanwhile it provides practical knowledge to software startups, which they can utilize to guide their effective decisions on pivoting.

Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al. · 127 citations · ⚡15
#computer vision Review Open access May 2015

A survey study on major technical barriers affecting the decision to adopt cloud services

In the context of cloud computing, risks associated with underlying technologies, risks involving service models and outsourcing, and enterprise readiness have been recognized as potential barriers for the adoption. To accelerate cloud adoption, the concrete barriers negatively influencing the adoption decision need to be identified. Our study aims at understanding the impact of technical and security-related barriers on the organizational decision to adopt the cloud. We analyzed data collected through a web survey of 352 individuals working for enterprises consisting of decision makers as well as employees from other levels within an organization. The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability. The result from our logistic regression analysis confirms the criticality of the security concern, which results in an up to 26-fold increase in the non-adoption likelihood. Our study underlines the importance of the technical and security perspectives for research investigating the adoption of technology.

Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al. · 111 citations · ⚡8
#computer vision Conference Open access Dec 2013

Affordable and Energy-Efficient Cloud Computing Clusters: The Bolzano Raspberry Pi Cloud Cluster Experiment

We present our ongoing work building a Raspberry Pi cluster consisting of 300 nodes. The unique characteristics of this single board computer pose several challenges, but also offer a number of interesting opportunities. On the one hand, a single Raspberry Pi can be purchased cheaply and has a low power consumption, which makes it possible to create an affordable and energy-efficient cluster. On the other hand, it lacks in computing power, which makes it difficult to run computationally intensive software on it. Nevertheless, by combining a large number of Raspberries into a cluster, this drawback can be (partially) offset. Here we report on the first important steps of creating our cluster: how to set up and configure the hardware and the system software, and how to monitor and maintain the system. We also discuss potential use cases for our cluster, the two most important being an inexpensive and green test bed for cloud computing research and a robust and mobile data center for operating in adverse environments.

P. Abrahamsson, S. Helmer, Nattakarn Phaphoom et al. · 110 citations · ⚡7
#computer vision Book Open access Mar 2017

On the Unhappiness of Software Developers

The happy-productive worker thesis states that happy workers are more productive. Recent research in software engineering supports the thesis, and the ideal of flourishing happiness among software developers is often expressed among industry practitioners. However, the literature suggests that a cost-effective way to foster happiness and productivity among workers could be to limit unhappiness. Psychological disorders such as job burnout and anxiety could also be reduced by limiting the negative experiences of software developers. Simultaneously, a baseline assessment of (un)happiness and knowledge about how developers experience it are missing. In this paper, we broaden the understanding of unhappiness among software developers in terms of (1) the software developer population distribution of (un)happiness, and (2) the causes of unhappiness while developing software. We conducted a large-scale quantitative and qualitative survey, incorporating a psychometrically validated instrument for measuring (un)happiness, with 2 220 developers, yielding a rich and balanced sample of 1318 complete responses. Our results indicate that software developers are a slightly happy population, but the need for limiting the unhappiness of developers remains. We also identified 219 factors representing causes of unhappiness while developing software. Our results, which are available as open data, can act as guidelines for practitioners in management positions and developers in general for fostering happiness on the job. We suggest considering happiness in future studies of both human and technical aspects in software engineering.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 84 citations · ⚡6

Related blog posts