2023/10/16

11:06

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

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

Needs validation

How would we design a system for designing systems ?

Needs analysis

Make a case for the system