"This dataset contains the application-layer measurement data underlying the comparative validation study \"XL-I2P: Cross-Layer I2P Darkweb Mapper.\" It comprises two eepsite crawl runs conducted sequentially on a single fully integrated I2P vantage node under identical infrastructure conditions: a run of the proposed XL-I2P framework and a run of the established c4i2p baseline of Mag\u00e1n-Carri\u00f3n et al. For each run, the dataset provides the recovered eepsite hyperlink graph as node and edge lists (CSV), the underlying relational tables sites, pages, links, crawl attempts, and seed provenance in both CSV and compressed SQL-dump form, and the computed summary metrics. The XL-I2P run recovered 1,400 reachable eepsites and 366,304 directed hyperlinks; the c4i2p baseline recovered 105 eepsites and 2,337 hyperlinks. The data supports reproduction of every table and figure in the associated paper, direct comparison of the two crawlers' coverage and resilience, and longitudinal extension of I2P application-layer measurement.All eepsite identifiers are I2P .b32.i2p addresses already discoverable through the public subscription feeds documented in the paper. The dataset includes page-level content metadata page titles, hyperlink anchor text, content length, word counts, and content hashes to support content-aware analysis; full page bodies are not stored. Network-layer and cross-layer observation tables are excluded from this release, as the cross-layer pipeline is implemented but not empirically evaluated in the associated study."
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.