SEI Webcasts
Are you confused about what should be in your Software Acquisition Pathway program’s Capability Needs Statement (CNS)? You are not alone! One of the most frequent requests we receive is for a sample CNS. If only it was that easy! Never fear; our recently released Tactical Guide called will provide you with the practical insight you need to develop a CNS that will be effective for your program. We’ll also talk about the Cracking the CNS Code’s complementary supplement called What Will Attendees Learn? ...
info_outlineSEI Webcasts
Software management is too frequently ignored or addressed piecemeal in systems. Cyber threat actors take advantage of gaps and errors in their attacks, which they can accomplish throughout the lifecycle. Exploiting these gaps and errors allows them to compromise processes, practices, and procedures that touch a system’s design, component development, and supply chain to bypass controls and leverage available vulnerabilities. Key software assurance activities must be embedded within the acquisition lifecycle to effectively combat these threat actors. What Will Attendees Learn? How software...
info_outlineSEI Webcasts
AI is transforming both the threat landscape and our defensive capabilities. What does cyber mission readiness mean in this new environment? A researcher from the CERT Division of Carnegie Mellon University's (CMU’s) Software Engineering Institute (SEI) describes the current challenges and emerging solutions that individuals and teams can use to build and sustain their cyber and AI-readiness. The webcast showcases Crucible, an open source framework that integrates learning management, hands-on labs, team exercises, competitions, threat sharing, and AI models into a unified cyber readiness...
info_outlineSEI Webcasts
Is your program really ready to adopt the SWP? Next in the Software Acquisition Go Bag series, we’ll walk you through our new Tactical Guide called SWP: Ready, Set, Go! This guide provides proven techniques to assess the project’s readiness to adopt the SWP; identify any shortfalls; and obtain the resources, information, and support needed for success. What Will Attendees Learn? • How to know if your acquisition program is really ready to adopt the SWP • What “Instill an Agile Culture” actually means for your program • How programs enter or transition to the SWP • A dispelled...
info_outlineSEI Webcasts
Many organizations practicing DevSecOps have collapsed under the weight of their own tooling. These organizations tried to solve delivery problems by stacking Kubernetes, Helm, GitOps controllers, scanners, and templating systems until no one can explain their own deployment path. This webcast cuts through that complexity and shows how right-sizing DevSecOps—reproducible environments, deterministic builds, type-safe configuration, and small iterative releases—restores velocity and reliability. We focus on what high-stakes teams actually need, not what vendors or compliance frameworks...
info_outlineSEI Webcasts
This webcast offers a solution to the problem of poorly defined requirements in system design that can lead to software flaws, cost and time overruns, and stakeholder dissatisfaction. We will tell you how to use a structured process called the ATAM (architectural tradeoffs analysis method) to develop a system design by eliciting requirements, scenarios, and priorities from stakeholders. Then, we will explain how to measure compliance with those requirements during testing using DevSecOps principles and tools, such as the SEI’s Silent Sentinel. What Will Attendees Learn? What software...
info_outlineSEI Webcasts
The SEI contributed its expertise to the development of the Software Acquisition Pathway (SWP), which the Department of Defense (DoD) issued in 2020 as DoD Instruction 5000.87. Since the SWP’s issuance, SEI researchers have collaborated with DoD program teams and policy owners to effectively implement the pathway in different program contexts, identify barriers and challenges, and monitor outcomes. Throughout that work, we’ve identified common questions and stumbling blocks that programs encounter as they adopt the SWP. Answering these questions often warrants additional tools and...
info_outlineSEI Webcasts
Experts agree that quantum computing will likely become powerful enough to break modern-day encryption within the next 10–15 years on “Q Day.” Once encryption is defeated, the computing world will never be the same. Organizations need to identify the correct courses of action to take today so that the sudden onset of quantum computing does not threaten their critical assets. In this webcast, Brett Tucker, Dan Justice, and Matthew Butkovic discuss the challenges expected with the realization of quantum computing capabilities. Furthermore, the group will provide possible responses to...
info_outlineSEI Webcasts
Finding and fixing weaknesses and vulnerabilities in source code has been an ongoing challenge. There is a lot of excitement about the ability of large language models (LLMs, e.g., GenAI) to produce and evaluate programs. One question related to this ability is: Do these systems help in practice? We ran experiments with various LLMs to see if they could correctly identify problems with source code or determine that there were no problems. This webcast will provide background on our methods and a summary of our results. What Will Attendees Learn? • how well LLMs can evaluate source code •...
info_outlineSEI Webcasts
Often, agile implementations are a struggle. Dedicated agile teams focus hard and deliver value on a regular cadence. But when results are tallied, the value teams produce may not fit neatly into the expectations of senior stakeholders. Why? In this webcast, Peter Capell addresses the importance of a practical vision to express outcomes, so that the program's “target picture” is clear to all parties involved. Peter highlights the value of tools such as Model-Based Systems Engineering (MBSE) in engineering processes, and how the combination of architecture and MBSE can anchor the...
info_outlineThis webcast offers a solution to the problem of poorly defined requirements in system design that can lead to software flaws, cost and time overruns, and stakeholder dissatisfaction. We will tell you how to use a structured process called the ATAM (architectural tradeoffs analysis method) to develop a system design by eliciting requirements, scenarios, and priorities from stakeholders. Then, we will explain how to measure compliance with those requirements during testing using DevSecOps principles and tools, such as the SEI’s Silent Sentinel.
What Will Attendees Learn?
- What software quality attributes are and why they are important
- How to prioritize competing requirements
- How to ensure architectural requirements are satisfied during development in a DevSecOps toolchain