Skip to content
Why Software Architects Must Be Involved in the Earliest Systems Engineering Activities episode artwork

Oct 1, 2019 22 min

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

from Software Engineering Institute (SEI) Podcast Series Hosted by Dr. Sarah Sheard

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.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

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

0:00 22:07

No transcript yet.

Requests help us decide what to transcribe next.

Frequently asked questions

How long is this episode of Software Engineering Institute (SEI) Podcast Series?

This episode is 22 minutes long.

When was this Software Engineering Institute (SEI) Podcast Series episode published?

This episode was published on October 1, 2019.

Can I download this Software Engineering Institute (SEI) Podcast Series episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.