Skill UI

A comprehensive guide for authors converting an accepted research paper into its final, published camera-ready form. This checklist covers critical steps including de-anonymization, restoring author metadata (ORCIDs, DOIs), strategically utilizing extra page content, and ensuring strict production quality (IEEE templates, references, and availability statements) required for major academic proceedings.

A comprehensive guide for designing, executing, and reporting high-stakes research studies in Software Engineering (SE), tailored to meet the stringent standards of top academic conferences like ICSE. It covers best practices for evidence-claim matching, advanced statistical rigor (non-parametric tests, effect sizes), handling AI model ablations, and implementing threats-driven design to ensure findings are robust, valid, and maximally reproducible.

A detailed methodology guide for authors submitting to highly competitive software engineering venues (like ICSE). It teaches how to structure the Related Work section not as a bibliography, but as a 'delta statement' that explicitly outlines the unique differences and contributions compared to the state-of-the-art across multiple publication lanes (journals, preprints, flagship venues).

A comprehensive guide detailing the academic standards for ensuring research reproducibility at ICSE. Covers open-science policies, mandatory data availability statements, techniques for pinning provenance (especially for mining and LLMs), and best practices for maintaining verifiability while ensuring anonymity. Essential for academic submissions.

This comprehensive guide details the entire ICSE conference paper review lifecycle, from initial submission to final decision. It analyzes the four core scoring criteria—Novelty, Rigor, Relevance, and Verifiability—and maps out the Accept/Major Revision/Reject decision model. Use this to strategically plan your revisions and understand the academic publishing landscape.

A comprehensive pre-submission audit guide for ICSE conference papers. It covers mandatory deadlines, strict formatting rules (10-page limit, IEEE template), double-anonymous submission best practices, and adhering to open science policies. Use this checklist before final submission to prevent desk rejection and ensure quality.

A comprehensive guide for authors submitting to major academic conferences (e.g., ICSE). It details the strict rules for differentiating mandatory core content (the 10-page limit) from supporting evidence, such as extended proofs, scripts, and raw data, which must be placed in an anonymized supplementary package. Learn the 'summarize-and-point' discipline to ensure verifiability and maintain reviewer trust.

This guide helps software engineering researchers determine the most appropriate academic conference or journal venue for their work. It provides comprehensive fit tests based on contribution type, empirical evidence maturity, and potential impact on industry practice. Authors learn to evaluate their research against criteria like novelty, rigor, and real-world relevance, ensuring proper routing to specialized tracks (e.g., ISSTA, ASE, ICSE).

A comprehensive, single-cycle master calendar and workflow guide for major academic conferences like ICSE. It details the entire ten-month journey, covering mandatory milestones from abstract submission and full paper drafting to author response, revision sprints, and final camera-ready preparation. This guide helps research teams plan backward, mitigate timeline risks, and manage complex project dependencies.

This guide provides detailed structuring advice for writing empirical software engineering (SE) research papers for top-tier conferences like ICSE. It focuses on adopting the required academic rigor, including using Research Questions (RQs) as the core skeleton, mastering the 'Threats to Validity' section, and calibrating claims for verifiability. Learn how to structure the abstract, compress content into a 10-page limit, and address reviewer expectations in the SE community.

A comprehensive guide for auditing and positioning the novelty and eligibility of research submissions in the field of software maintenance and evolution. It teaches authors to write a 'delta-first' related work section, contrasting their contribution against key prior works and covering specialized literature lanes (e.g., MSR, ICSE, TSE) to demonstrate deep command of the academic community.

This comprehensive guide assists software engineers in determining the most appropriate venue (e.g., ICSME, ICSE, MSR) for their research paper. It clarifies the critical difference between general software engineering techniques and studies focused on the post-release lifecycle, such as maintenance, technical debt, program comprehension, and system evolution.