By Derrick H. Karimi
Member of the Technical Staff
Emerging Technology Center
This blog post is co-authored by Eric Werner.
In an era of sequestration and austerity,
the federal government is seeking software reuse strategies that will
allow them to move away from stove-piped development toward open,
reusable architectures. The government is also motivated to explore
reusable architectures for purposes beyond fiscal constraints: to
leverage existing technology, curtail wasted effort, and increase
capabilities rather than reinventing them. An open architecture in a
software system adopts open standards that support a modular, loosely
coupled, and highly cohesive system structure that includes the
publication of key interfaces within the system and full design
disclosure. One area where the Department of Defense (DoD) is
concentrating on the development of service-oriented architectures and
common technical frameworks is in the intelligence community,
specifically the Defense Intelligence Information Enterprise (DI2E). As this blog post details, a team of researchers at the SEI Emerging Technology Center (ETC) and the Secure Coding Initiative in the SEI’s CERT Division,
are working to help the government navigate these challenges in
building the DI2E framework, which promotes reuse in building defense
To view a video of this blog post in its entirety, please click here.
By Douglas C. Schmidt
To view a video of the introduction, please click here.
The Better Buying Power 2.0
initiative is a concerted effort by the United States Department of
Defense to achieve greater efficiencies in the development, sustainment,
and recompetition of major defense acquisition programs through cost
control, elimination of unproductive processes and bureaucracy, and
promotion of open competition. This SEI blog posting describes how the
Navy is operationalizing Better Buying Power in the context of their Open Systems Architecture and Business Innovation initiatives. This posting also presents the results from a recent online war game
that underscore the importance of automated testing in these
initiatives to help avoid common traps and pitfalls of earlier cost
By Douglas C. Schmidt
deliver enhanced integrated warfighting capability at lower cost across
the enterprise and over the lifecycle, the Department of Defense (DoD)
must move away from stove-piped solutions and towards a limited number of technical reference frameworks
based on reusable hardware and software components and services. There
have been previous efforts in this direction, but in an era of sequestration and austerity,
the DoD has reinvigorated its efforts to identify effective methods of
creating more affordable acquisition choices and reducing the cycle time
for initial acquisition and new technology insertion. This blog
posting is part of an ongoing series on how acquisition professionals and system integrators can apply Open Systems Architecture (OSA)
practices to decompose large monolithic business and technical designs
into manageable, capability-oriented frameworks that can integrate
innovation more rapidly and lower total ownership costs. The focus of
this posting is on the evolution of DoD combat systems from ad hoc
stovepipes to more modular and layered architectures.
By Douglas C. Schmidt
Department of Defense (DoD) program managers and associated acquisition professionals are increasingly called upon to steward the development of complex, software-reliant combat systems. In today’s environment of expanded threats and constrained resources (e.g., sequestration), their focus is on minimizing the cost and schedule of combat-system acquisition, while simultaneously ensuring interoperability and innovation. A promising approach for meeting these challenging goals is Open Systems Architecture (OSA), which combines (1) technical practices designed to reduce the cycle time needed to acquire new systems and insert new technology into legacy systems and (2) business models for creating a more competitive marketplace and a more effective strategy for managing intellectual property rights in DoD acquisition programs. This blog posting expands upon our earlier coverage of how acquisition professionals and system integrators can apply OSA practices to decompose large monolithic business and technical designs into manageable, capability-oriented frameworks that can integrate innovation more rapidly and lower total ownership costs.
By Douglas C. Schmidt,
agile methods have become popular in commercial software development
organizations, the engineering disciplines needed to apply agility to
mission-critical, software-reliant systems are not as well defined or
practiced. To help bridge this gap, the SEI recently hosted the Agile Research Forum.
The event brought together researchers and practitioners from around
the world to discuss when and how to best apply agile methods in
mission-critical environments found in government and many industries.
This blog posting, the fifth and final installment in a multi-part
series highlighting research presented during the forum, summarizes a
presentation I gave on the importance of applying agile methods to common operating platform environments (COPEs) that have become increasingly important for the Department of Defense (DoD).