11:08

I tend to ignore the note granular, complicated, step by step processes that professors outlines

For better or worse

The “V” model of system engineering

Is all cost actually cost in human well-being ?

Verification, validation, integration, testing

Verification vs validation

Verification

Meeting requirements

Validation

Satisfying customer needs

Integration

Put the parts together to make sure things work together

Includes the expected operating environment

Autonomous vehicles testers on public streets

Integration readiness level

How easy is it to integrate things

A stepping stone to System Readiness Level

Now what the heck is system readiness level? So

Seems important

The story of F35 software development

The kind of thing I think I could help do

Went from extreme slow iteration cycles to much more rapid testing

This seems like the process could be quite different for first time, one off systems vs repeated builds

We’re really talking about first delivery, QA is different (if probably a subset)

The core idea is cost of change goes up over time

Testing

Functional or non functional

Models

The cost pressure is to do model based engineering and simulation

Models need maintenance and testing as well

Thinking about the technological change 11.325

Are technologies and systems isomorphic ?

Maybe technologies are a type of system

Both seem to be defined by fulfilling a function

All this essentially means we need to build a system to deliver the system

This level of detail seems excessive for such abstract out flexible guidelines

I’m guessing this is mostly about exposure to different options for processes

I guess I oscillate between thinking about building the product vs building the process that delivers the product at scale

Both are systems that need to be built

Similarly

We seem to be talking about a system that needs to be built to deliver another system

A system to deliver a system

A system to design a system

A system to build the systems to design and deliver a system