11:06
EM.411 meeting
System Architecture vs System Engineering
Plenty of overlap in this course
I think an important distinction is whether a system is being designed for a one off or for a repetitive process
Feels like “system” sometimes is being used like “product”
Identifying needs
Hard to avoid providing solutions when trying to define needs
Solution neutral
Operational objectives
Begins with the system problem statement
At some point when decomposing objectives you transition to functions when the objectives become measurable
Comfort -> space-> cubic feet
Concept of operations CONOPS
Sometimes visual
High level, maybe course or precise
Almost like an architectural drawing
Like a pitch for the system to the stakeholders
Operational scenarios
Cover the different operations and their contexts
Involves a system boundary
Amazon fulfillment system
Everything oriented around 2 day delivery
Guides the architectural decisions
System concept
Operational concept, context, requirements
Some process
Functional analysis
Feasibility analysis
Tradespace
Pareto front
Needs validation
How would we design a system for designing systems ?
Strange loops
Needs analysis
Make a case for the system