By Douglas C. Schmidt
part of an ongoing effort to keep you informed about our latest work, I
would like to let you know about some recently published SEI technical
reports and notes. These reports highlight the latest work of SEI
technologists in systems of systems integration from an architectural perspective, unintentional insider threat that derives from social engineering, identifying physical security gaps in international mail processing centers and similar facilities, countermeasures used by cloud service providers, the Team Software Process (TSP), and key automation and analysis techniques.
This post includes a listing of each report, author(s), and links where
the published reports can be accessed on the SEI website.
By Bill Scherlis,
Chief Technology Officer (Acting)
extent of software in Department of Defense (DoD) systems has increased
by more than an order of magnitude every decade. This is not just
because there are more systems with more software; a similar growth
pattern has been exhibited within individual, long-lived military systems. In recognition of this growing software role, the Director of Defense Research and Engineering (DDR&E, now ASD(R&E)) requested the National Research Council (NRC) to undertake a study of defense software producibility,
with the purpose of identifying the principal challenges and developing
recommendations regarding both improvement to practice and priorities
for research. The NRC appointed a committee, which I chaired, that
included many individuals well known to the SEI community, including Larry Druffel, Doug Schmidt, Robert Behler, Barry Boehm,
and others. After more than three years of effort—which included an
intensive review and revision process—we issued our final report, Critical Code: Software Producibility for Defense. In the year and a half since the report was published, I have been asked to brief it extensively to the DoD and the Networking and Information Technology Research and Development (NITRD) communities.
This blog posting, the first in a series, highlights several of the
committee’s key findings, specifically focusing on three areas of
identified improvements to practice—areas where the committee judged
that improvements both are feasible and could substantially help the DoD
to acquire, sustain, and assure software-reliant systems of all kinds.
Part 2: SEI R&D Activities Related to Sustaining Software for the DoD
By Douglas C. Schmidt,
Deputy Director, Research, and Chief Technology Officer
Software sustainment is growing in importance as the inventory of DoD systems continues to age and greater emphasis is placed on efficiency and productivity in defense spending. In part 1 of
this series, I summarized key software sustainment challenges facing
the DoD. In this blog posting, I describe some of the R&D
activities conducted by the SEI to address these challenges.