Table I.

Top table: overall workflow evaluation, separately for the original (“orig.”) and adaptive (“adapt.”) design tasks including average ratings (“Av.”). Bottom table: General evaluation of acceptance and important aspects for design automation and optimization applications. Scale: –2 (absolutely no), –1 (rather no), 0 (neutral), +1 (rather yes), +2 (absolutely yes)

QuestionDesignEvaluationAv.
Overall evaluation
Does it make sense?Orig.1010.67
 Adapt.1121.33
Do you think it works?Orig.1111.00
 Adapt.1211.33
Would you use it?Orig.1010.67
 Adapt.1211.33
Optimization
Would you use it?Orig.–1–10–0.67
 Adapt.1010.67
Would you rather draw the pathOrig.2211.67
manually?Adapt.2111.33
Would you trust it?Orig.1111.00
 Adapt.1111.00
Would you use the proposed solutions?Orig.1–110.33
 Adapt.1211.33
Does run-time need to be instant?Orig.2111.33
 Adapt.2–100.33
Interaction
In general?Orig.2121.67
 Adapt.2222.00
For moving access points and obstacles?Orig.1111.00
 Adapt.1221.67
Pulling lines?Orig.2222.00
 Adapt.2222.00
With the optimizer?Orig.0110.67
 Adapt.1211.33
Selecting from several solutions?Orig.2111.33
 Adapt.2222.00
Seamlessness
Is the integration of optimization andOrig.1111.00
ACC-Design important?Adapt.1221.67
Does this workflow increase the value ofOrig.2111.33
ACC-Design?Adapt.2111.33
QuestionEvaluationAv.
Acceptance
Practical relevance2222121.83
Stepwise introduction10–10000.00
Stepwise integration of users1211111.17
See/test prototype10–10100.17
Trust/understand solution1122211.50
Influence solution finding2222121.83
Aspects
Functionality2111121.33
Usability2111221.50
Comprehensibility/traceability0021110.83
Seamlessness2000110.67

or Create an Account

Close Modal
Close Modal