Skip to Main Content

Submission Guidelines

Call for Paper submissions for Arm DevSummit 2020 virtual conference are reviewed by an independent Technical Program Committee. Members of the Technical Program Committee are selected based on their industry knowledge and represent companies and technologies across the entire Arm community. Differentiation and depth of proposals are of upmost importance when submitting as we expect several hundred submissions this year!

Below are some tips that have helped previous submissions be selected. Also, be sure to check out our sample submissions page to review previous Arm DevSummit submissions that were selected.

Review and understand the submission criteria the Technical Program Committee will be using as a guideline.

The Arm DevSummit 2020 Technical Program Committee of industry experts will review all submissions based on quality, relevance, impact, and originality. Prospective authors are welcome to reference products as long as product references add to the educational value and are presented in an appropriately non-commercial fashion.

  • Quality – Proposals should be well organized and easily understood. The abstract and summary are judged as indicators of what can be expected of the session.
  • Relevance – The proposed session or panel should be highly relevant to the interests of the Arm DevSummit audience in general and the track topic in particular. Example: real-world case studies.
  • Impact – Sessions and Panels should contribute to the educational mission and technical nature of Arm DevSummit. Submissions reporting on important results, methodologies, or case studies of special significance will be considered favorably.
  • Originality – Reports on new development methodologies, case studies for innovative device designs, or other novel results contribute to the Arm DevSummit goal of providing a high-quality educational program for practicing engineers and developers.
  • Commercial content (less is best) – It is acceptable to use a product in a design case study or as a proof of concept for a design methodology. Product promotion is not permitted in the technical sessions. Proposals with blatant commercial/marketing content will be rejected (The presentation or panel’s focus should be on the development process, technology used, and/or trade-offs, not on selling a product).

Submit something that will grab the Technical Program Committee’s attention. These include presentations that are:

  • Technical sessions on implementing new functionality in software, developing low-level code on embedded systems, or designing SoCs.
  • Real-world case studies showcasing Arm-based devices incorporated in a project, innovative application, or a solution to a technical challenge in an end product, including a detailed discussion of the trade-offs and choices made (and why) during the development or design process.
  • A hands-on demonstration illustrating key technical principles that engage the audience in a creative or interactive way.

Select your topic carefully.

Things to consider:

  • Experience: The scope of your personal expertise and those of any co-speakers, moderators or panelists.
  • Timeliness of the topic: Focus on in-demand, unique or non-obvious development or design topics. Do you have a different approach to a topic that is in demand?
  • Applicability of your session: What can you impart to attendees that they can put into action the week after the conference?
  • Actionable learning objectives: What is the tangible impact of your presentation on attendees and their Arm-based system design or software development efforts?
  • Clear focus: Who would benefit the most from your presentation? Identify this specific role in your submission and provide actionable insight on real-life use cases.

Develop a unique approach to the topic to make your proposal stand-out. Recognize that your peers may be submitting on a similar topic.

  • For technical individual and co-speaker sessions, focus on in-demand, unique or non-obvious design or development topics of an Arm-based product.
  • For a panel, think outside the box. Do the proposed panelists have different opinions and backgrounds? Is there controversy around the topic? Consider whether a panel is the best choice to present this content.
  • For a demonstration, is this a new product or software that many of the attendees haven’t had a chance to experience? How can you break the demonstration down to be engaging, inspiring and fun?

Think carefully about the technical level of your proposal and matching content to your audience.

  • Beginner – Focused on introductions to technology and applicable to professionals with up to 5 years of experience.
  • Intermediate – Focused on principles and concepts that would appeal to attendees with more than 6 years of experience.
  • Advanced – Focused on advanced principles and concepts, geared toward attendees with deep subject knowledge and 11 or more years of experience.
Back To Top