logo

۱۱ آذر - ۱۴ آذر ۱۴۰۴

رتبه: C (CORE2023)Offline

Asia-Pacific Software Engineering Conference

به‌روزرسانی شده: 3 days ago
0.0 (0 امتیازات)
VU1 VU1

موضوعات:

نمای کلی

The 32nd Asia-Pacific Software Engineering Conference (APSEC 2025) will be held from December 2-5, 2025, at the Wynn Palace in Macao SAR, China. This leading regional conference gathers researchers and practitioners from academia, industry, and government to exchange knowledge, best practices, and address emerging challenges in software engineering. The program includes distinguished keynote speakers, paper presentations, demos, tutorials, co-located workshops, a New Faculty Forum, and a Student Research Competition.

فراخوان مقالات

APSEC 2025: Call for Papers

The 32nd Asia-Pacific Software Engineering Conference (APSEC 2025) will be held on December 2-5, 2025, in Macao SAR, China, at the Wynn Palace.

APSEC has long been established as a leading regional conference that gathers researchers and practitioners from academia, industry, and government to exchange knowledge and best practices in software engineering, and to address emerging challenges and solutions in software engineering innovation.

APSEC 2025 will offer an extensive program of interest to academia, government, and industry. It will include several distinguished keynote speakers, conference days of paper presentations and demos. A series of exciting tutorials to develop skills in various aspects of software engineering practices is of particular interest to the industry. Co-located workshops offer forums for participants to present novel techniques and methods in specific sub-disciplines of software engineering. This year’s APSEC program also contains the New Faculty Forum and Student Research Competition, which welcome new faculties and students to participate in this exciting event.


Conference Tracks

APSEC 2025 features the following tracks, inviting diverse contributions to the field of software engineering:


Technical Track: Topics of Interest

The APSEC 2025 technical research track invites high-quality contributions describing original results in the discipline of software engineering. Solicited topics include, but are not limited to:

  • Tools and processes
    • Agile processes
    • DevOps and Container
    • Configuration Management and Deployment
    • Software Engineering Process and Standards
  • Requirements and Design
    • Service-oriented Computing
    • Component-based Software Engineering
    • Cooperative, Distributed, and Global Software Engineering
    • Software Architecture, Modeling and Design
    • Middleware, Frameworks, and APIs
    • Software Product-line Engineering
  • Testing and Analysis
    • Testing, Verification, and Validation
    • Program Analysis
    • Program Synthesis
    • Program Repairs
  • Formal Aspects of Software Engineering
    • Formal Methods
    • Model-driven and Domain-specific Engineering
  • Human Factors and Social Aspects of Software Engineering
    • Software Comprehension, Visualization, and Traceability
    • Software for Green and Sustainable Technologies
  • AI and Software Engineering
    • AI for Software Engineering
    • Software Engineering for AI
    • Search-based Software Engineering
  • Dependability, Safety, and Reliability
    • Reliability, availability, and safety
    • Performance
    • Vulnerability detection to enhance software security
  • Software Maintenance and Evolution
    • Refactoring
    • Reverse Engineering
    • Software Reuse
    • Software Project Management
    • Debugging, Defect Prediction, and Fault Localization
  • Software Repository Mining and Data Analytics

APSEC 2025 also welcomes submissions addressing topics in a variety of application domains, including mobile, cloud, blockchains, embedded, and cyber-physical systems.


Submission Guidelines

Submitted papers must have been neither previously accepted for publication nor concurrently submitted for review in another journal, book, conference, or workshop.

Technical Track Paper Requirements

  • Technical research papers must not exceed 12 pages (including references).
  • All submissions must be in English and must come in A4 paper size PDF format.
  • Submissions must conform to the IEEE Conference Proceedings Formatting Guidelines (title in 24pt font and full text in 10pt font). LaTeX users must use \documentclass[10pt,conference]{IEEEtran} without including the compsoc or compsocconf option.
  • Papers must comply with the IEEE Policy on Authorship.
  • The Chairs reserve the right to reject submissions (without reviews) that are not in compliance or out of scope for the conference.

Submission System

Papers must be submitted electronically in PDF before the due date via HotCRP: https://apsec25.hotcrp.com

Double-Blind Policy

The APSEC 2025 technical research track will use a double-blind reviewing process, which means that submissions must not reveal the authors’ identities. Authors must make every effort to honor this process by adhering to the following rules:

  • Omit authors’ names and institutions from your title page.
  • References to authors’ own related work must be in the third person. Example: Not “We build on our previous work…” but rather “We build on the work of…”.
  • If the current submission is a clear follow-up to previous work, and reviewers might associate authorship, you may anonymize the reference. For example: “based on previous results [10]” where [10] is reported as “[10] Anonymous Authors. Omitted for double blind reviewing.”. Ensure the submission is self-contained.
  • Do not include acknowledgements of people, grants, organizations, etc., that would give away your identity. These can be added in the camera-ready version.
  • Aim to reduce the risk of accidental unblinding (e.g., identifiable project names should be changed for submission, e.g., GoogleDeveloperHelper becomes DeveloperHelper).
  • Avoid revealing institutional affiliations or where the work was performed. Generalize descriptions (e.g., “The study participants consist of 200 students in an introductory CS course.”). For industrial studies, refer to the organization as “Org” or “Company”.
  • While open science is encouraged (disclosing source code/datasets), avoid linking directly to code repositories or tool deployments that can reveal your identity. Use services like zenodo.org or figshare.com for anonymous archiving, or archive.org for larger datasets. Link these archived and anonymized datasets within the paper itself.

Important Note: Submissions that allow the author to be identified may be returned for editing at short notice or may be rejected outright.

Preprint Policy

To ensure a fair and unbiased double-blind review process, authors submitting papers must comply with guidelines regarding non-anonymized versions. A non-anonymized version is any publicly available document (e.g., on arXiv) with essentially the same scientific content as the submitted paper, even if it differs in minor ways such as the title, paper structure or organization, length or formatting.

Preprints Posted Before the Anonymity Period

Authors are permitted to make a non-anonymized version publicly available before the anonymity period. The anonymity period starts one month before the submission deadline and ends when the paper is accepted, rejected, or withdrawn. However, authors are responsible for minimizing the risk of trivial linking between the submitted paper and a public version. Specifically, authors must:

  • Prevent the submitted manuscript from being associated with the non-anonymized version.
  • Not make the non-anonymized version easily discoverable via search engines by reusing distinctive phrases (e.g., title, keywords).
  • Not update the non-anonymized version during the anonymity period.
  • Not actively promote the non-anonymized version (e.g., via social media, blogs, or mailing lists).
  • Not reference, cite, or link to any non-anonymized version within the submitted manuscript.

Post-Publication Preprint Policy According to IEEE Guidelines

Upon acceptance and publication by IEEE, authors must update any publicly available non-anonymized version of the paper by:

  1. Replacing it with the full IEEE citation, including the Digital Object Identifier (DOI), OR
  2. Posting the accepted version of the paper (i.e., the author’s final version prior to IEEE formatting), along with the DOI. The IEEE-published version must not be posted.

IEEE will provide each author with a preprint version including the DOI and IEEE copyright notice. Authors may post this preprint version in accordance with IEEE’s posting guidelines. For more details: https://conferences.ieeeauthorcenter.ieee.org/get-published/post-your-paper/


Important Dates (AoE UTC-12h)

WhenTrackWhat
Sun 13 Jul 2025Technical TrackAbstract Deadline (Optional)
Sun 20 Jul 2025Technical TrackPaper Deadline
Wed 23 Jul 2025Early Research Achievements (ERA)Submission Deadline
Thu 7 Aug 2025Software Engineering in Practices (SEIP)Submission Deadline
Fri 15 Aug 2025Journal-First TrackSubmission deadline
Sat 23 Aug 2025TutorialsSubmission deadline
Fri 5 Sep 2025WorkshopsWorkshop Proposal Submission
Sat 13 Sep 2025Early Research Achievements (ERA)Author Notification
Sat 13 Sep 2025Journal-First TrackAuthor notification
Sun 14 Sep 2025Tool DemonstrationAbstract Deadline
Wed 17 Sep 2025Doctoral SymposiumSubmission Deadline
Sat 20 Sep 2025Technical TrackAuthor Notification
Sun 21 Sep 2025Tool DemonstrationSubmission Deadline
Sun 21 Sep 2025Student Research CompetitionSubmission Deadline
Thu 25 Sep 2025TutorialsNotification
Fri 26 Sep 2025Software Engineering in Practices (SEIP)Author Notification
Sun 28 Sep 2025Doctoral SymposiumAcceptance Notification
Fri 17 Oct 2025Tool DemonstrationAcceptance Notification
Fri 17 Oct 2025Student Research CompetitionAcceptance Notification
Sun 19 Oct 2025WorkshopsNotification
Mon 20 Oct 2025Technical TrackCamera Ready Deadline
Mon 20 Oct 2025Early Research Achievements (ERA)Camera Ready Deadline
Thu 23 Oct 2025Software Engineering in Practices (SEIP)Camera Ready Deadline
Fri 31 Oct 2025Tool DemonstrationCamera Ready
Fri 31 Oct 2025Student Research CompetitionCamera Ready
Tue 2 - Fri 5 Dec 2025Journal-First TrackConference

Publication

All accepted papers will be included in the IEEE Digital Library as the APSEC 2025 conference proceedings. Accepted papers will not be permitted any additional page of content. After acceptance, the list of paper authors cannot be changed under any circumstances, and the list of authors on camera-ready papers must be identical to those on submitted papers. After acceptance, paper titles cannot be changed except by permission of the Program Co-Chairs, and only when referees recommend a change for clarity or accuracy with paper content.

Conference Attendance Expectation

If a submission is accepted, at least one author of the paper must register for APSEC 2025 and present the paper at the conference. If an accepted paper is not presented, the paper will be removed from the proceedings.


Contact Information

Jacky Keung and Eunjong Choi
APSEC 2025 Program Co-Chairs
Contact form: https://conf.researchr.org/contact/apsec-2025

تاریخ‌های مهم

تاریخ‌های کنفرانس

Conference Date

۱۱ آذر ۱۴۰۴۱۴ آذر ۱۴۰۴

ارسال مقاله

(Technical Track) Abstract Deadline (Optional)

۲۲ تیر ۱۴۰۴

(Technical Track) Paper Deadline

۲۹ تیر ۱۴۰۴

(Early Research Achievements (ERA)) Submission Deadline

۱ مرداد ۱۴۰۴

اعلان

(Early Research Achievements (ERA)) Author Notification

۲۲ شهریور ۱۴۰۴

(Journal-First Track) Author notification

۲۲ شهریور ۱۴۰۴

(Technical Track) Author Notification

۲۹ شهریور ۱۴۰۴

نسخه نهایی

(Early Research Achievements (ERA)) Camera Ready Deadline

۲۸ مهر ۱۴۰۴

(Technical Track) Camera Ready Deadline

۲۸ مهر ۱۴۰۴

(Software Engineering in Practices (SEIP)) Camera Ready Deadline

۱ آبان ۱۴۰۴

تاریخ‌های دیگر

(Journal-First Track) Conference

۱۱ آذر ۱۴۰۴۱۴ آذر ۱۴۰۴

رتبه منبع

منبع: CORE2023

رتبه: C

حوزه پژوهشی: Software engineering

نقشه

Loading feedback section...