A: Product-Driven Information Systems
The car in your driveway has 20,000 components, and the plane on the tarmac has a million. The development of modern products begins with thousands or millions of requirements, all of which must be managed through the stages of the product lifecycle.
This lecture briefly discusses early-stage requirements management using the Vee-model, SysML, and RFLP, as well as later-stage information structures known as Digital Twins and Threads.
Here are some links to technology vendors videos on some of the topics (under 4 min). I don't promote any one over another, but they provide some context.
B: How do we fix Systems Engineering? (by Mike Griffin)
Dr. Michael Griffin was Nasa administrator, Undersecretary of Defense in Research in Engineering, and had a long history in the US Space program. The following is from a speech given in 2010, and is assigned reading for the course. A video of Dr. Griffin's speech is below.
C: How do we fix Systems Engineering? (by Pat Hillberg)
Decomposing problems into small manageable pieces inevitably leads to dysfunction, which in turn leads to either scandalous products, or a failure to innovate. Our Systems Engineering tools are not capable of modeling the economic and cultural aspects of the organizations responsible for the products. We need Systems Thinking.
Discusses other project management techniques as a lead-in to Scrum, and then posits that its true value is as a means to encourage Collective Learning.
Optional: Mike Griffin Video
In the following video (optional for the course) Griffin gives this talk at the Stevens Institute of Technology. (It runs a little under an hour.)