PLAY PODCASTS
Why Software Architects Must Be Involved in the Earliest Systems Engineering Activities

Why Software Architects Must Be Involved in the Earliest Systems Engineering Activities

Software Engineering Institute (SEI) Podcast Series · Dr. Sarah Sheard

October 1, 201922m 7s

Audio is streamed directly from the publisher (traffic.libsyn.com) as published in their RSS feed. Play Podcasts does not host this file. Rights-holders can request removal through the copyright & takedown page.

Show Notes

Today's major defense systems rely heavily on software-enabled capabilities. However, many defense programs acquiring new systems first determine the physical items to develop, assuming the contractors for those items will provide all needed software for the capability. But software by its nature spans physical items: it provides the inter-system communication that has a direct influence on most capabilities, and thus must be architected intelligently, especially when pieces are built by different contractors. As Dr. Sarah Sheard discusses in this SEI Podcast, if this architecture step is not done properly, a software-reliant project can be set up to fail from the first architectural decision.