DevSecOps Support
Abstract
Continue development and support for DevSecOps infrastructure, platform, software development pipeline, and joint F-35 organizational connections. Continue to develop a transition plan to stand-up a team consisting of industry and government software development in support of software modernization and DevSecOps Cloud transition. Establish initial capabilities and expand existing software development efforts with the goal of transitioning dispersed and separated software development environments into model-based systems engineering and a fully collaborative requirements to development environment. Capabilities include software development environment for Maintenance Systems ODIN, ALIS to ODIN migration, Combat Data System's Mission Planning, Propulsion's Offboard Management System, and Air Vehicle Mission System domains. Additional goals of delivering flight-worthy rapid prototyping of capability, virtual test capability, and transitioning workloads to lower cost software sustainment efforts. New requirements from PMOs are expected. Prepare environment for on-boarding, as well as transitioning the PMOs from separate pillars to a centralized JPO-managed cloud environment. Includes software licensing for PMO tool sets and associated applications. Major cost drivers include requirements tool, and collaboration tools, authentication tools - supporting Single Sign On, Multi-Factor Authentication and development tools. For software tooling efforts, working towards an eventual consolidation of tools across the PMOs (i.e., application rationalization) with an end goal of a standardized compiler tool sets and Cybersecurity compliance. Accordingly, talent/consumption (hardware and software to run the environment) contracts must be renewed and expanded. Cybersecurity requirements must also be met, meaning additional resources for security processes, monitoring, scanning, vulnerability identification plus mitigation, and meeting all requirements for DoD compliance to obtain ongoing/continuous Authority to Operate (ATO) and continuous Authority to Operate (cATO).
Document Details
- Document Type
- Accomplishment
- Publication Date
- Oct 01, 2024
- Source ID
- 57ea9d1f819f70feafbfb2695edf44eb
Related Documents
- Root: F-35 C2D2