Jasper User Group 2022

Abstract Submissions

Ready to share and discuss the latest design and verification best practices with your peers from around the world?

It’s time for our annual Jasper™ User Group Conference. This interactive, in-depth technical conference connects designers, verification engineers, and engineering managers from around the world to share the latest design and verification practices based on Cadence’s® Jasper™ formal verification technologies and methodologies. This year, the conference will be held live and in-person, for the first time since 2019. The Jasper User Group Conference has become the premier industry event for formal experts and beginners alike to learn from each other how to effectively accelerate their design and validation processes by applying formal methods.

Conference highlights include:

• User presentations on core technologies, applications, and flows
• Roadmap discussions
• New technology demos
• Executive keynotes
• Best presentation awards
• Networking Reception

Submit an Abstract

User presentations typically make up at least three-quarters of the conference agenda. We’re seeking your unique perspectives on improving your design and validation methods using Jasper technologies.  These presentations exhibit a combination of technical depth and real-life experiences, of both benefits achieved and lessons learned, that make the Jasper User Group Conference the unique event it is.

If your presentation is accepted, you can:

• Increase industry visibility for you and your team’s field of expertise
• Improve and fine-tune your methods with insights from colleagues across the industry
• Earn wide acclaim with a Best Presentation Award nomination

Accepted authors will be expected to travel to the conference and present in-person. Please submit your abstract for consideration by 5:00pm (PDT) on Monday, August 15, 2022.

Hot Topics for 2022

• Best practices to achieve formal signoff
• Algorithmic and datapath verification
• Safety and security verification
• Sequential equivalence checking
• Deep deadlock and bug hunting
• Machine learning for performance and convergence gains
• Formal regressions and optimizing compute resources
• Complex proofs, abstraction, and reduction techniques
• Processor ISA verification
• Protocol verification with assertion-based VIP
• Blending formal and dynamic verification flows
• Driving broader adoption of formal methods
• Formal verification for design teams
• Novel applications for formal verification

Important Dates

Contact Organizers

Abstract Guidelines

• Prepare your abstract for a 35-minute session, not counting audience Q&A.
• Set up the problem/need your session will  address. (1 – 2 sentences)
• How will your session solve this problem/meet this need? Mention the main points/topics your session will cover. (1 – 3 sentences)
• What technologies, services, or methodologies were employed to meet this need? (1 – 2 sentences)
• What case study(ies) will be cited as examples of success? (1 – 2 sentences)
• How will your session help attendees or their customers? Will they save time to market? Reduce overhead? Increase      productivity? Quantify the big benefit. Example: Saved 6 – 8 weeks. (1 – 2 sentences)
• 2,500-character limit (including spaces).

Content Tips

Please note that rating of abstracts will be based upon — and should also include information regarding—the following criteria for the final presentation:

• Quality—The abstract should be well organized and easily understood. The abstract and summary are good indicators of what can be expected of the prospective authors for a full-length presentation.
• Relevance—The abstract should be highly relevant to the interests of a user group audience, and to the track topic in particular.
• Impact—Submissions reporting on important results, methodologies, or case studies of special significance will be considered favorably.
• Originality—New design methodologies or a case study for an innovative design have great educational value.
• Commercial content—It is acceptable to use a product in a design case study or as a proof of concept for a design      methodology, and many of the abstracts a user group views most favorably do just that. However, we also know that the audience responds negatively to anything that comes across as a product pitch. A good case study that uses a real product in an appropriate manner to demonstrate feasibility or illustrate a concept will be considered favorably.

Questions? Email us