Software Factory

Software Framework

Our software framework enables mission requirements and optimizes mission application development.

We understand that the end users of a mission application framework are mission app developers. We are a team of mission app developers and have used that experience to develop a framework that developers want to use. Too often frameworks are complex, difficult to install and force mission app developers into product lock in. Our framework solution is thin, easy to install, and only provides capabilities that enable mission.

Our Mission App Framework is:

  • Written for App Developers by App Developers: As application developers we’ve used many frameworks, and so we understand what drives a good experience and high user adoption. Our framework test team is made up of app developers because they are ultimately the end users of an app framework.
  • Simple: Every capability is heavily vetted to ensure it provides mission value and reduces workload on app developers. Capability bloat can cause complexity and reduce user adoption, so we ensure our capability set is lean and value added.
  • Low Maintenance: We do not put framework code in between app developers and FOSS and COTS. Instead, we ensure that app developers can take advantage of new FOSS and COTS features without requiring new framework code.
  • Secure & Simple Onboarding: Our framework is easy to install and onboard applications onto. Our onboarding approach verifies application security and allows applications to take advantage of the ATO provided to the framework.
  • Automated in Test: Our framework test harness provides an easy way for app developers to verify our capabilities as well as plug in and verify additional end-to-end tests.

DevSecOps Ecosystem

The pursuit of writing better code faster.

As part of our DevSecOps approach, we’ve adopted four pillars that guide our work:

  • Deliver higher quality software, faster.
  • Keep up with rapidly evolving technology.
  • Use the right tools, not the same tools.
  • Communicate effectively.

We use DevOps Research and Assessment (DORA) metrics to measure how well our software is working. In addition to our internal goals, we know that sometimes our customers care about different metrics, so ultimately, we find ways to be flexible in making sure we are adequately measuring our own progress. Metrics we care about most when we develop software include frequency of deployments to operations, lead time, mean time to restore (MTTR), and change failure rate.

In a perfect world, we work to:

  • Increase deployment frequency.
  • Reduce lead time.
  • Reduce MTTR.
  • Reduce change failure rate.

Our DevSecOps Ecosystem supports this process by providing tools to make the development team more efficient. We aren’t creating a “software factory” that every project is mandated or required to use. We believe that the greatest value in these offerings is that it gives each team the ability to decide what is best for them. We won’t tell you how to develop software and write code; we make it easier for your team to develop software and write code faster. The people working on a project are always going to know the best tools to help and it’s our goal as a titan team to empower our developers to use the right tools for the job. Some of our current tool offerings provided by our DevSecOps ecosystem include Gitlab, Jira, Confluence, Nexus, clearml, and ArgoCD.