Tutorials and WorkshopsISEC 2027

Accepted Workshop

Call for Papers(Workshop): GenAI&SE – Co-Pilots to Actors

Generative AI and Software Engineering (GenAI&SE) – Co-Pilots to Actors

We propose a full-day workshop on Generative AI and Software Engineering, marking the fourth edition of the series. This edition expands the focus from Generative AI as a copilot to Generative AI as an actor. An actor is an AI system that can independently plan, decide, and act within real-world software systems under human oversight.

The workshop will bring together three related areas:

· Proven software engineering practices for deploying Generative AI

· The use of large language models and AI agents throughout the software development life cycle

· New challenges and research questions arising from greater AI autonomy

The workshop will offer a forum for the community to explore how these systems can be built, operated, and trusted in enterprise environments.

More details and updates are available on the workshop website:

Visit the workshop website

Location: ISEC 2027 will be held at Bharatiya Vidyarthi Bhavan’s Sardar Patel Institute of Technology, Mumbai, India. Address: Bhavan’s Campus, Old D N Nagar, Munshi Nagar, Andheri West, Mumbai, Maharashtra 400058

The Microsoft CMT service was used for managing the peer-reviewing process for this conference. This service was provided for free by Microsoft and they bore all expenses, including costs for Azure cloud services as well as for software development and support.

Organizers

Call for Workshop Proposals

ISEC 2027 invites proposals for workshops to be held on the first day of the conference (Thursday, 18th February 2027). We seek half-day and full-day proposals on established or emerging research topics related to the field of software engineering for the audiences who come from both academia and industry. A half-day workshop should be for 3 hours whereas a full-day workshop should be for 6 hours. Focus areas include all areas of software engineering (To get a better idea, please refer to the list in the call-for-papers under the Research Papers track available at https://conf.researchr.org/track/isec-2027/isec-2027-research-papers).

The workshops at the Innovations in Software Engineering Conference (ISEC) provide a forum for groups of 20-50 participants that share a particular research agenda to discuss topics in software engineering research and practice. They also provide opportunities for researchers to exchange, and discuss scientific and engineering ideas, and provide future research directions.

A workshop is primarily intended to consist of talks related to the topic(s) of interest. This could either be brought in through submissions solicited by individual workshop call for papers (CFPs) and/or through a pre-decided list of eminent invitees. In case of the former (talks invited through workshop CFPs), the organizers would call for submissions and select the good ones (if needed, through a program committee).

Submissions

All proposals must not exceed 5 pages (following the formatting guidelines for the main track), including proposal text, references, appendices, and figures.

Proposals should include:

1. Proposed Title.

2. Abstract (upto 250 words) for website

3. Topic/Area (refer to the suggestive list of topics/areas of the main conference).

4. Duration (half day or full day).

5. Number of attendants in previous version(s) of the workshop (if any).

6. Contact Information for all workshop organizers, including the main contact person. A short biography for each organizer, including selected relevant publications in the proposed area, if any). Relevant past experience in organizing conferences and workshops may also be included.

7. Target audience and prerequisite knowledge of the audience.

8. Motivation and Objectives of the Workshop : a. Relevance of the workshop, b. Anticipated goals and expected outcomes for students, academia and Industry

9. The proposed structure shall include information about whether the workshop includes a call for paper submissions, and selection by the organizers from these submissions for presentation at the workshop (include draft call-for-papers and proposed program committee). Information about whether there are invited talks (include names of proposed speakers), panel discussions (include information about proposed panellists), etc. A breakup of the time in case the workshop includes more than one kind of component. For workshop with separate CFPs, additional guidelines are given in subsequent section.

10. Special resource/equipment requirements for organizing the workshop, if any.

Email your proposal to Workshops Chairs Sheikh Umar Farooq (suf.cs@uok.edu.in) and Anant Nimkar (anant_nimkar@spit.ac.in) on or before the deadline(s).

The proposals would be reviewed based on their ability to garner interest from the audience, relevance and importance of the topic in the context of the current lines of research in software engineering, experience of organizers, depth of the submitted plan/structure, and a fit with the entire program of ISEC 2027.

Review Criteria

ISEC welcomes workshops which are relevant, timely, engaging and foster actionable discussions.

Proposals for new workshops should carefully consider existing workshops and co-located events to avoid duplication or significant overlaps as these may be desk-rejected. You can visit ISEC website (https://conf.researchr.org/series/isec) and see the pages for previous editions of ISEC and co-located workshops.

All proposals that meet the basic requirements identified in the call will be evaluated by the workshop chairs and any additional reviewers the chairs may consider fit to review a proposal.

Workshops Chairs will facilitate the following

• Evaluation of the proposals.
• Link a web page for each accepted submission on the ISEC website. For this purpose, the organizers must provide a clear description of the workshop after accepting their proposal.
• Coordinate with other chairs for conducting the workshop as planned.
• Coordinate with general and publication chairs to publish the accepted workshop papers.

Responsibilities of accepted organizers

• Create required publicity for their workshop through websites and other social media.
• Identify speakers and other participants (if applicable, through CFPs).
• Coordinate with workshop chairs for organizing the workshop.
• Provide a summary write-up about the organized workshop for inclusion in the conference proceedings, by

Guidelines for the workshops that intend to issue an independent Call for Papers (CFP) and publish accepted papers as part of the ISEC 2027 Proceedings

1. Peer Review: Every workshop paper must undergo a formal peer-review process involving at least two independent reviewers. The review timeline should provide sufficient time to ensure a rigorous and high-quality evaluation.

2. Program Committee (PC) Structure: To avoid potential conflicts of interest, workshop organizers should not serve as Program Committee (PC) members for their own workshops. Their primary role should be to coordinate and manage the workshop.

3. Appointment of PC Chairs: The Program Committee Chair(s) for each workshop should be appointed in consultation with the General Chairs (GCs) and Research Track Program Chairs (PCs). The appointed PC Chair(s) will then constitute the remaining Program Committee.

4. Workshop Papers: Accepted workshop papers should be limited to 4 pages.

5. Poster Papers: Workshop organizers may also invite poster submissions. Poster papers should be limited to 2 pages. The organizing committee may decide whether to publish individual poster papers or combine multiple poster abstracts into a single proceedings document, as done in previous editions.

6. Author Affiliations and APC: Authors should be informed that eligibility for ONOS coverage depends on their institutional affiliation. If an affiliation is not covered under ONOS, the corresponding Article Processing Charges (APC) must be borne by the authors.

7. Registration and APC Policy: Workshop proposals should clearly specify the registration policy and any applicable APC-related charges so that prospective authors are fully informed before submitting their papers.

8. Submission System: Paper submissions and the peer-review process shall be managed through an established online submission system, such as EasyChair, OpenReview, Microsoft CMT, or HotCRP. The system shall facilitate paper submission, reviewer assignment, review collection, and communication with authors, ensuring an efficient, transparent, and well-organized review process.

Call for Proposals: Tutorials and Technical Briefings

A. Technical Briefings

A focused 90-minute session. Proposals should indicate which of the following types applies.

1. Topic briefings. An introduction to a specific or emerging area of software engineering, optionally with initial research results, or a point-of-view talk on where research and practice are heading, or a report on an innovation that emerged while solving a real world engineering problem.
2. Cross-community briefings.A researcher from an adjacent community, such as machine learning, human computer interaction, programming languages, formal methods, information retrieval, systems, statistics, or security, teaches the foundations of their area to a software engineering audience and indicates where those foundations may apply. Software engineering results are not expected.
3. Hands-on briefings. A session in which participants work directly with tools, datasets, or notebooks.

B. Tutorials

A session on a specific topic focusing on the current state of the art, taught in enough depth that attendees can begin reading and working in the area afterwards. Tutorials may include a hands-on component, and proposals that do should say so. 90 or 180 minutes.

Topics of Interest

Proposals are welcome on all aspects of software engineering. Please refer to the ISEC 2027 Research Papers call for papers for the list of topics.

Submission Requirements

Proposals should be no longer than 3 pages and should include the following.

1. Title
2. Category and requested duration, being a Technical Briefing (indicating type A1, A2, or A3) at 90 minutes, or a Tutorial at 90 or 180 minutes, with a justification if 180 minutes is requested
3. A summary paragraph suitable for publication in the ISEC 2027 program
4. Objective
5. Learning objectives, being what an attendee should be able to do or understand at the end of the session
6. Relevance and motivation
7. Target audience
8. Outline
9. Names and short biographies of the speakers, including evidence of expertise in the area and of experience in teaching it
10. Logistical requirements, including whether participants need laptops, and any software, dataset, or network dependencies. For a session with a hands-on component, please add one page describing the exercises and what participants need to prepare beforehand.
11. Any other relevant information, for example past experience

Please also attach 3 to 10 slides showing material that will actually be used in the session. These do not count towards the page limit.

Submit the proposal as a single PDF by email to the track chairs before the deadline below.

Not Eligible

Proposals on very narrow topics with limited audience appeal, commercial presentations centred on a specific product or service, and marketing material will be desk-rejected.

Review and Selection

Proposals will be reviewed by the track chairs, with additional reviewers where appropriate. We will consider the relevance and importance of the topic to the ISEC community, the experience of the presenters, the extent to which the outline and sample material support the stated objective, and the fit of the session with the overall ISEC 2027 program.

For Accepted Sessions

Accepted sessions will be held on the first day of the conference. The complete slide deck must be submitted to the track chairs at least two weeks before the conference.

Presenters of each accepted session will also be asked to provide a short video of one to two minutes describing the topic, which will be posted on the ISEC 2027 website for publicity.

Call for Papers(Workshop):RELIABLE-SE 2027

Engineering Reliable and Trustworthy LLM-Based Software Development

Co-located with ISEC 2027 | Mumbai, India

Can we trust AI to build software?

As Large Language Models (LLMs) and autonomous coding agents transform software development, how can we ensure reliability, security, correctness, and trustworthiness?

RELIABLE-SE 2027 invites researchers, academics, students, and industry practitioners to contribute original research, empirical studies, experience reports, demonstrations, innovative ideas, and position papers.

📄 Submission Categories

Workshop Papers (4 Pages) | Poster Papers (2 Pages)

💡 Topics of Interest

• Reliable LLM-Based Software Engineering: Reliability, trustworthiness, robustness, consistency, uncertainty estimation, and reliability metrics.

• Coding Agents & Agentic Development: Autonomous software development, multi-agent systems, repository-level agents, planning, execution, and agent evaluation.

• Hallucination & Error Management: Code/API hallucinations, requirement misunderstanding, incorrect reasoning, semantic inconsistencies, and error propagation.

• Evaluation & Benchmarking: Coding-agent benchmarks, real-world datasets, automated and human-centred evaluation, generalization, and reproducibility.

• Prompt, Context & Retrieval Engineering: Prompt engineering and testing, prompt robustness, context engineering, RAG, repository-aware LLMs, and long-context software engineering.

• Verification & Validation: Static/dynamic analysis, symbolic execution, formal verification, execution-grounded LLMs, automated test generation, and patch verification.

• Security: Secure code generation, LLM-induced vulnerabilities, AI-assisted threat modelling, security requirements, vulnerability detection, and automated security repair.

• Human–AI Collaboration: Human-in-the-loop development, developer trust, appropriate reliance, explainable AI, human oversight, and responsible deployment.

• Reproducibility & Responsible AI-SE: Model/version sensitivity, prompt and benchmark reproducibility, open evaluation frameworks, and reporting guidelines.

• Broader Software Engineering: Requirements engineering, software architecture and design, software development tools and processes, software quality assurance, maintenance and evolution, DevOps/DevSecOps, and empirical software engineering.

🚀 Be Part of the Conversation!

Join us for peer-reviewed research presentations, invited keynotes, a hands-on Reliability Challenge, an interactive panel, and a research roundtable to shape the future of trustworthy AI-assisted software engineering.

📨 Submission link: https://reliablese2026.hotcrp.com/

✨ Move beyond “Can AI code?” to “Can we trust the software AI builds?”

About

The tutorials track at ISEC 2027 is aimed to provide an opportunity for conference participants to learn, explore and gain knowledge, including hands-on and working sessions, on topics ranging from theoretical foundations to practical techniques in the broad area of software engineering. The track serves as an opportunity for researchers and industry experts to present advances in the field of software engineering, providing insights for young students and researchers to get an overview of a research area and to further pursue research.

Sessions run for 90 minutes by default. A tutorial may be proposed as a 180-minute session delivered in two 90-minute modules where the material genuinely requires it, with a justification and an outline showing what the second module adds. A session may have one or more presenters.