LIVE STREAMING | TECHNOLOGY WORKSHOPS | ONLINE CHAT
Join your embedded community on the 4th of February for Embedded DevOps Summit, the first Perforce virtual user conference for the embedded software industry.
This one-day event is free for all attendees. Choose from a number of sessions on relevant categories, such as:
- Plan: Explore methodologies, tools, and practices that can help you cut costs in the planning stage of development.
- Create: Learn how to improve things like collaboration, scaling, and versioning to reduce the time it takes to create a quality product.
- Verify: Understand various practices that help you verify safety standards to reduce risk.
Stream live and pre-recorded sessions on the latest technology trends from our team of embedded experts. And connect with a broader community of programmers, engineers, developers, and more via our live chat.
Empower your organization to implement the latest innovations in embedded software.
Complete the form to save your seat!
Save Your Seat!
Explore methodologies, tools, and practices that can help you cut costs in the planning stage of development.
- Scrum, Kanban, and Gantt Scheduling in One Project – Nonsense or Necessity?
- Community vs. Enterprise Open Source – Which is Right for Your Business?
- CWE Top 25: History, Tools and Techniques
- Planning & Tracking Without Jira - Can it Be Done?
Scrum, Kanban, and Gantt Scheduling in One Project – Nonsense or Necessity?
It may seem like a strange idea to apply Gantt scheduling in an embedded DevOps context — after all, isn’t Gantt scheduling the same as Waterfall? As we will see in this presentation, there is a difference between technique (like Gantt scheduling) and mindset (Waterfall, Agile), and combining different techniques can be a very smart way to approach modern planning and tracking needs.
Learn how to combine Scrum, Gantt, and Kanban practices to optimize value delivery but keep the ability to plan around hard dependencies.
Community vs. Enterprise Open Source – Which is Right for Your Business?
New monetization models such as open core have presented questions for embedded software IT professionals. Do we stick with the freedom and agility of community releases, or do we pay for the enterprise counterparts? Explore patterns in Enterprise Edition add-ons, look at some concrete examples such as Confluent vs. Kafka, and be better prepared to decide where you spend your open source license dollars.
CWE Top 25: History, Tools and Techniques
The Common Weakness Enumeration (CWE) lists the most common and dangerous weaknesses found in software. In this talk, we will take a closer look at these top 25 weaknesses, including:
- What they are.
- How they were chosen.
- How they have changed over the years.
- Which tools and techniques can be used to identify them.
Learn how to improve things like collaboration, scaling, and versioning to reduce the time it takes to create a quality product.
- Embedded Software Development at 5G Speed
- Secure Collaboration in a Cloud-based Chip Design Environment
- Optimizing Your CI Pipeline
- Implementing a Unified HW/SW BoM to Reduce System Development
Embedded Software Development at 5G Speed
Hang Jason Dong
This talk will delve into one devops team's journey through implementing a major CI system into engineering workflow, as the project scales from the team's own needs to a service supporting thousands of global users company wide over the past 5 years. We will discuss the challenges and optimizations we worked through over the years that resulted in noticeable improvements in efficiency for our users, as well as the approaches we took to mitigate the impact on the critical perforce infrastructure we dependent on.
Secure Collaboration in a Cloud-based Chip Design Environment
As part of a large government program aimed at changing the way we design chips, we were faced with a huge challenge. Collaborating with nearly 15 companies and universities, we had to develop new game-changing technology that involves securely sharing highly valuable source code in a completely sealed cloud-based design environment. This talk will discuss the difficult requirements to this program, and how one tool was able to serve as a critical technology to enable dozens of designers to efficiently and securely work together.
Optimizing Your CI Pipeline
One of the main foundations for successful software development — including embedded as well as other types — is a continuous integration pipeline. By using a continuous integration pipeline, you are able to find an appropriate balance between quality and speed.
In general, validation tools, test suites, and review processes help to improve the quality of your software. However, these tools can add increasing amounts of time, especially if done for every check-in. This can lead to a slowdown of delivery for your project.
This talk will look at some best practices, and discuss ways to decide how you can achieve the right balance for your project.
Implementing a Unified HW/SW BoM to Reduce System Development
Managing the relationship between hardware and software during the system design process is challenging.
The hardware register definition has dependencies for embedded software designers. As a result, the software team must wait for the required information from the hardware development team. This delays the schedule. And, on top of all of that, changes are often not communicated — leading to errors and integration difficulties.
In this session, we’ll share how you can improve your system design process with a unified BoM. You’ll learn how to understand and manage hardware and software IP as atomic elements in a unified BoM. This allows IP to be built up in a hierarchical manner. And it delivers clarity and productivity to the design process that was never before possible.
Understand various practices that help you verify safety standards to reduce risk.
- CI Efficiency: How to Verify Every Developer Commit
- Role of Coding Standards in Autonomous Vehicles
- How to Improve Development with Strong Requirements Taxonomy
- Embedded Security through Coding Standards and Static Analysis
CI Efficiency: How to Verify Every Developer Commit
Fundamentally, program analysis (inter-procedural control — and data-flow static code analysis) is a computationally complex task. And with traditional computing, primitive algorithms will inevitably tend toward exponential build times.
For many years, creators of static analysis tools have optimized their algorithms to bring analysis times down to something more linear. However, as instant feedback has become a common expectation, we need to find alternative solutions to include quality, security, and compliance checks on new and changed code as part of our CI process.
Role of Coding Standards in Autonomous Vehicles
With the increased development of autonomous vehicles, it is important to consider the security aspects of software developed for these systems throughout the product development lifecycle.
Software development is the point at which many vulnerabilities are introduced, potentially leading to future performance, security, and safety issues.
This presentation will discuss the benefits of using a security-focused coding standard to ensure that these vulnerabilities are detected early in development, and that systems are safe and secure. It will consider the coding standards currently available and will compare the benefits of the guidelines.
How to Improve Development with Strong Requirements Taxonomy
One time-consuming step in embedded software development is gathering and breaking down requirements. However, without this critical step, your product direction may be unclear and could result in miscommunication and inefficiency. The later you perform rework in the development cycle, the more time and money you lose.
Avoid costly rework with some strategic organization. Learn how to define a well-structured taxonomy of requirements to help ensure your requirements capture and breakdown is considered from all necessary perspectives, and that no critical elements are skipped.
Embedded Security through Coding Standards and Static Analysis
Dr. David Long
Security vulnerabilities resulting from software defects have been studied extensively. The MITRE corporation's list of Common Vulnerabilities and Exposures (CVE) is widely used and has been maintained for almost 20 years! It turns out that weak security is often a direct result of using software language constructs and coding styles that could have been avoided. The problem is that many software developers are not aware of potential insecure features lurking in their code!
Secure coding standards provide guidelines and rules to prevent common security vulnerabilities.
Manual checking for coding standard compliance is tedious and error-prone. Static analysis tools can automate the process while also detecting violations that might be missed by other testing approaches.
This presentation highlights rules from the CERT C and MISRA C coding standards that are appropriate for a small embedded system. It will demonstrate how the Klocwork static analysis tool can apply these rules to identify and fix security vulnerabilities in a typical embedded application, written in C and running under a real-time operating system.