2023/10/23

11:05

The system problem statement defines why the system exists, its core purpose

Members of first SDM class

Chief system engineer for S-92

Introduced some process to semiconductor equipment companies

keeping Moore’s law alive

Concept Generation example, emergency exit on S-92

Cross functional

Structured approach removes the emotion

Cross functional team

If you don’t have a good concept, cheaper to quit

Looks interesting, reminds me of casual analysis I do when trying to make decisions on my own

essentially a scoring grid for different concepts

One idea is to generate concepts by identifying core needs and creating concepts ideas each optimized for a need

Users that are reading the product for their use cases

Can follow them to new concepts

One process

Clarify the problem

Search externally

Search internally

Explore systematically

Columbia accident as an example

How to overcome

Call out most likely, least likely

Our system will fail, how did it fail?

Essentially, anything to trigger creativity

Creativity types

Concept extraction

e.g. comparing an atom to the solar system

Connecting disparate semantic ideas through language both helps language disabled and is a basis for humor

Concept exploration

Concept induction

Change style to enable “impossible”

Specific problem -> general problem -> general solution -> specific solution

Exposes that there are many ways to solve a problem

This is the direction System Engineering is heading

Ideally, we want to find all possible forms that could satisfy the function

The trick is eliminating efficiently