Skip to Content
You are currently on the new version of our website. Access the old version .
  • Indexed in
    Scopus
  • 22 days
    Submission to First Decision
  • 5 days
    Acceptance to Publication

Software

Software is an international, peer-reviewed, open access journal on all aspects of software engineering published quarterly online by MDPI.
  • Open Access— free for readers, with article processing charges (APC) paid by authors or their institutions.
  • High Visibility: indexed within Scopus, Ei Compendex, and other databases.
  • Rapid Publication: manuscripts are peer-reviewed and a first decision is provided to authors approximately 21.3 days after submission; acceptance to publication is undertaken in 4.9 days (median values for papers published in this journal in the first half of 2026).
  • Recognition of Reviewers: Reviewers whose reports are timely and of high quality receive an APC discount voucher for a future publication in an MDPI journal. Become a reviewer.
  • Software is a companion journal of Electronics.

Get Alerted

Add your email address to receive forthcoming issues of this journal.

All Articles (158)

  • Article
  • Open Access

Software developed using modern agile practices delivers a stream of software versions that require continuous regression testing rather than testing once close to the delivery or maintenance phase, as assumed by classical regression-testing theory. In this work, we formalize the phenomenon of continuous or near-continuous regression testing using successive ‘builds’ as a time-ordered chain, where each build contains the program, requirements, and the accompanying tests. We also formalize the regression test window between any two builds, which captures the limited time budget available for regression testing. As the time limit is set to infinity and the chain is closed to two builds, the model degenerates to retest-all, thereby preserving semantics for the classical two-version case. The formalization is validated by directly representing two state-of-the-art agile regression testing algorithms in terms of build-tuple operations without requiring auxiliary assumptions, followed by proof of the soundness and completeness of our formalization.

Software

16 November 2026

Candidate Set for Regression Testing.
  • Article
  • Open Access

From Executable to Demonstrable: Synthesizing API Usage Showcases for Research Repositories

  • Davide Evangelista,
  • Mathieu Linty and
  • Alexander Tormasov
  • + 4 authors

A script that runs a research repository is not the same as a script that shows how to use it. Test generation targets structural coverage, and work on executability targets whether a repository can be made to run. Neither yields what a new user of a research library needs, which is a worked example. We define demonstrativeness by three explicit predicates: in-process contact with a public non-driver symbol, use of a constructed argument, and output that depends on the returned value. We record these static predicates separately from environment construction and trial execution, preventing dependency-blocked repositories from being labelled runtime successes or failures. Reaching a library’s interface requires a target model that entry-point selection cannot express; we derive symbol-level targets by Horn clauses over signatures, exports, docstrings, and documentation references. Generated scripts are read back after every successful execution, and a vacuous script can be repaired without discarding the best executable fallback. In a paired, single-run evaluation on 90 repositories, of which 24 had buildable environments, the full configuration produced 11 passing showcases against 2 for an entry-point-only configuration and made static API contact in 15 buildable environments against 7, while both retained Tier-1 success on the same 21; exact McNemar tests on the per-repository records give p=0.012 and p=0.008. Corpus-wide, the entry-point-only configuration attempted generation on 24 repositories and the full configuration on 89, with API contact in 7 and 70; that contrast is largely by design, since only the full configuration has a generation path in a dependency-blocked environment. Because the full configuration bundles API targets, read-back, and vacuity repair, these figures establish a system-level contrast, not the isolated causal effect of any component.

Software

12 November 2026

Both configurations on the same corpus repository, karpathy/nanoGPT, abridged from the generated scripts. Both terminate with exit status zero, so an executability criterion cannot tell them apart. (a) locates a script, prints the command a user would type, and launches nothing in process, so no repository symbol is credited. (b) imports the model module, constructs a configuration and a model, and prints shapes and parameter counts that depend on what each call returned. The difference is what this paper measures.
  • Article
  • Open Access

A novel application of function hooking is presented, allowing software that runs on Windows and uses MFC, wxWidgets, or the Win32 API to have its user interfaces translated without modification of the original application or access to source code. A launcher is used to run the target executable, loading it into the launcher’s address space and allowing the launcher to hook into functions that display text in the user interface. These functions then transparently replace original text with the translated version and call the original function. The method is effective, with minimal to no measurable runtime overhead (3% in the worst case), but visual imperfections remain due to differing lengths of text and potential numerical translations.

Software

3 November 2026

Traditional methods of translating/localising an executable for French and Italian.
  • Article
  • Open Access

The European Digital Identity Wallet (EUDI Wallet) is reshaping how citizens across Europe access, manage, and share verifiable credentials. Peer-reviewed work explains wallet protocols, trust frameworks, and adoption barriers, but it rarely links those mechanisms to a measured national rollout. This paper presents an explanatory case study of the Italian digital identity wallet (IT-Wallet), an early implementation of Regulation (EU) 2024/1183, organised around which design and governance decisions co-occur with the national activation path, which trade-offs are visible in the evidence, and which findings depend on the Italian setting. The analysis pattern-matches a priori propositions to legal and technical primary materials, to adoption series supplied by the State Mint and Polygraphic Institute (IPZS), and to a GDPR-compliant telemetry pipeline in the IO application. Between 23 October 2024 and 27 June 2026, more than 12 million wallet instances were issued, including renewals, which is a cumulative total rather than the number of instances still active on the last day of the window. The case reads national wallet adoption through the way the software was released, by setting the embedding in IO, the staged opening, and the reuse of existing infrastructures next to the issuance series, without estimating a cause.

Software

30 October 2026

Reference EUDI Wallet actor model: issuer, wallet, verifier, and trust infrastructure.

Highly Accessed Articles

News & Conferences

Latest Issues

Open for Submission

Journal Sections

XFacebookLinkedIn
Software - ISSN 2674-113X