Evaluating partial designs
Story: engineering setting, collection of requirements, collection of component known...
Cloud created by:
Jon G. Hall
26 January 2010
As a practicing engineer, Derek designs artifacts that satisfy an identified need. The need is not stationary, nor its context: both exist in the real-world. collection of requirements, collection of component known (architecture, pieces, structures) goal, new deaign, uncertian outcome, creativity needed, external person to design process who shares risk of failure, judgement how to compile components to satisfy requirements. Ask person: yes/no
satisfactory validation of design by external. Incremental building, nothing to show in intermediate to check with external if progress is satisfactory. Use expertise to break down problem, preliminary safety analysis, ask: is there any obvious reason why this partial design won't be good enough?
Context Engineering design project
Problem: How do you know if and in which way a problem/solution is good enough to proceed?
external evaluator to project, project cannot be presented
S1: preliminary safety analysis
S2: understanding why other related project failed, trace back reasons for failure
(Academic research and other stuff at link below:)