As shown, a method 900 begins at step 902, where setup engine 200 generates design problem geometry 330 in response to end-user interactions with GUI 214. Design problem geometry 330 represents specific boundary conditions and/or bounding geometry associated with a design problem. As the end-user modifies design space 300, where design problem geometry 330 resides, setup engine 200 updates problem specification 202 to reflect design space 300.

At step 904, analysis engine 204 associates reference geometry 400 with design problem geometry 330. In doing so, analysis engine 204 analyzes design space geometry 330 to determine potentially similar approaches to solving the design problem associated with that geometry. For example, analysis engine 204 could analyze the physical organization of boundary conditions associated with design space geometry 330 to identify (e.g., within a database) existing design solutions for similarly organized boundary conditions. Then, analysis engine 204 could generate reference geometry 400 based on those solutions, and adapt that geometry to fit within design space geometry 330.

At step 906, setup engine 200 determines a set of forces on design problem geometry 330 and/or reference geometry 400. The end-user may define the set of forces via tools provided in toolbar 310. Generally, each force in the set of forces is to be balanced by a feasible design solution. Thus, the set of forces represents one form of design objective.