a. design space navigation framework object...

Appendix A 109

A. Design Space Navigation Framework Object Models

A.1 General Organization

NAV_SolutionSpace

NAV_ProblemSpace

NAV_Solution

NAV_Problem

NAV_DesignSpace NAV_Marker

derived_solutions

parent_solution

versions

base_version

problem_space

current_problemproblems

current_solutionsolutions

solution_space

problem

problemsubproblems

superproblem

marksnode:NAV_Node*

Appendix A 110

A.2 Design Space

NAV_Dimensions:enum

eDimP=0eDimQeDimReDimRheDimSeDimT

NAV_SolutionNAV_Problem

NAV_Node

#NAV_Node

NAV_DesignSpace

+NAV_DesignSpace()+~NAV_DesignSpace()#nextNode(np:NAV_Node*,dim:NAV_Dimensions,forward:bool=TRUE):NAV_Node*#addNode(np:NAV_Node*,ref:NAV_Node*,dim:NAV_Dimensions):NAV_Node*#removeNode(np:NAV_Node*):NAV_Node*+GoToNode(np:NAV_Node*):NAV_Node*+GoToMarker(mk:NAV_Marker*):NAV_Node*+ParentProblemNode(np:NAV_Node*):NAV_Node*+FirstChildProblemNode(np:NAV_Node*):NAV_Node*+PrevSiblingProblemNode(np:NAV_Node*):NAV_Node*+NextSiblingProblemNode(np:NAV_Node*):NAV_Node*+PrevRevisionNode(np:NAV_Node*):NAV_Node*+NextRevisionNode(np:NAV_Node*):NAV_Node*+PrevSiblingVersionNode(np:NAV_Node*):NAV_Node*+NextSiblingVersionNode(np:NAV_Node*):NAV_Node*+ParentSolutionNode(np:NAV_Node*):NAV_Node*+FirstDerivedSolutionNode(np:NAV_Node*):NAV_Node*+PrevSiblingSolutionNode(np:NAV_Node*):NAV_Node*+NextSiblingSolutionNode(np:NAV_Node*):NAV_Node*+AddChildProblem(np:NAV_Node*,ref:NAV_Node*):NAV_Node*+AddSiblingProblem(np:NAV_Node*,ref:NAV_Node*):NAV_Node*+AddRevision(np:NAV_Node*,ref:NAV_Node*):NAV_Node*+AddDerivedSolution(np:NAV_Node*,ref:NAV_Node*):NAV_Node*+AddSiblingSolution(np:NAV_Node*,ref:NAV_Node*):NAV_Node*+AddProblem(np:NAV_Node*):NAV_Node*+AddSolution(np:NAV_Node*,ref:NAV_Node*):NAV_Node*+DeleteProblem(np:NAV_Node*):bool+DeleteSolution(np:NAV_Node*):bool+GetCurrentNode():NAV_Node*+GetCurrentProblem():NAV_Problem*+SetCurrentProblem(np:NAV_Problem*):void+GetCurrentSolution():NAV_Solution*+SetCurrentSolution(sp:NAV_Solution*):void+MakeProblemsIter():Iterator*+FindNodes(target:Object*):SeqCollection*+MarkNode(np:NAV_Node*,mp:NAV_Marker*):void+UnmarkNode(np:NAV_Node*,mp:NAV_Marker*):NAV_Marker*+GetMarkers():SeqCollection*+GetMarkers(np:NAV_Node*):SeqCollection*#getMarkers(np:NAV_Node*):Collection*#makeMarkerColl(np:NAV_Node*):Collection*#destroyMarkerColl(np:NAV_Node*):void

Appendix A 111

A.3 Problem

NAV_ProblemSpace

+NAV_ProblemSpace()+~NAV_ProblemSpace()-%NAV_DesignSpace::#nextNode(np:NAV_Node*,dim:NAV_Dimensions,forward:bool=TRUE):NAV_Node*#addNode(np:NAV_Node*,ref:NAV_Node*,dim:NAV_Dimensions):NAV_Node*#removeNode(np:NAV_Node*):NAV_Node*#findNode(np:NAV_Node*):NAV_Node*#addNode0(np:NAV_Node*):NAV_Node*#addNode0(np:NAV_Node*,ref:NAV_Node*):NAV_Node*+GetCurrentNode():NAV_Node*+SetCurrentNode(np:NAV_Node*):void+GetCurrentSolution():NAV_Solution*+MakeTopLevelProblemsIter():Iterator*+FindNodes(target:Object*):SeqCollection*

NAV_Problem

#NAV_Problem#~NAV_Problem-%NAV_ProblemSpace::+GetParentProblem:NAV_Problem*+GetSiblingProblem(after:bool=TRUE):NAV_Problem*+GetFirstChildProblem:NAV_Problem*+MakeChildProblemsIter(forward:bool=TRUE):Iterator*+GetRevision(next:bool=TRUE):NAV_Problem*+GetSiblingVersion(after:bool=TRUE):NAV_Problem*+MakeRevisionsIter(forward:bool=TRUE):Iterator*+GetNextSolution(np:NAV_Node*,dim:NAV_Dimensions,forward:bool):NAV_Node*+GetCurrentSolution:NAV_Solution*+SetCurrentSolution(np:NAV_Solution*):void+MakeSolutionsIter:Iterator*#findRevision(target:NAV_Problem*):NAV_Problem*#findChildProblem(target:NAV_Problem*):NAV_Problem*#findProblem(target:NAV_Problem*):NAV_Problem*#removeNode(np:NAV_Node*):NAV_Node*#addChildProblem(np:NAV_Problem*):NAV_Problem*#addRevision(np:NAV_Problem*):NAV_Problem*#addRootLevelSolution(np:NAV_Solution*):NAV_Solution*#setParentProblem(np:NAV_Problem*):void+FindNodes(target:Object*):SeqCollection*+FindChildProblems(target:Object*):SeqCollection*+FindRevisions(target:Object*):SeqCollection*+FindSolutions(target:Object*):SeqCollection*#satisfiesTarget(target:Object*):bool

Appendix A 112

A.4 Solution

A.5 Marker

A.6 Implementation-specific Information

NAV_SolutionSpace

+NAV_SolutionSpace(lp:NAV_Problem*)+~NAV_SolutionSpace()-%NAV_Problem::-%NAV_ProblemSpace::#nextNode(np:NAV_Node*,dim:NAV_Dimensions,forward:bool=TRUE):NAV_Node*#addNode(np:NAV_Node*,ref:NAV_Node*,dim:NAV_Dimensions):NAV_Node*#removeNode(np:NAV_Node*):NAV_Node*#findNode(np:NAV_Node*):NAV_Node*#addNode0(np:NAV_Node*):NAV_Node*+GetCurrentNode():NAV_Node*+SetCurrentNode(np:NAV_Node*):void+MakeTopLevelSolutionsIter():Iterator*+FindNodes(target:Object*):SeqCollection*

NAV_Solution

#NAV_Solution#~NAV_Solution-%NAV_SolutionSpace::+GetProblem:NAV_Problem*+GetParentSolution:NAV_Solution*+GetSiblingSolution(after:bool=TRUE):NAV_Solution*+GetFirstDerivedSolution:NAV_Solution*+MakeDerivedSolutionsIter(forward:bool=TRUE):Iterator*#findSolution(target:NAV_Solution*):NAV_Solution*#removeNode(np:NAV_Node*):NAV_Node*#addDerivedSolution(np:NAV_Solution*):NAV_Solution*+FindNodes(target:Object*):SeqCollection*+FindSolutions(target:Object*):SeqCollection*#satisfiesTarget(target:Object*):bool

NAV_NodeNAV_Marker

#label[250]:char

#NAV_Marker(l:char*)+~NAV_Marker()+GetNode:NAV_Node*-%NAV_DesignSpace::+SetLabel(l:char*):void+GetLabel:char*+SetIcon(:Bitmap*):void+GetIcon:Bitmap*

node

NAV_DesignSpaceNAV_Node

Object:imported

NAV_ProblemSpace NAV_SolutionSpace

Object:imported

NAV_Marker

Object:imported

0:include

ET++.hDictionary.h

Appendix B 113

B. SEED-Layout Navigation Utility Object Models

B.1 Problem Hook Classes

NAV_Problem:imported

0:include

DesignSpace.hxxLayoutProblem.hxx

LayoutProblem:imported

NAV_SLProblemImpl

+NAV_SLProblemImpl(lp:LayoutProblem*)+~NAV_SLProblemImpl()#UpdateStructures:void#initInstance(lp:LayoutProblem*):void+DoObserve(id:int,part:int,vp:void*,op:Object*):void#addChildProblem(lp:NAV_SLProblemImpl*):NAV_SLProblemImpl*+GetName():char*+GetActiveLayout():SL_Layout*+FindAdaptorOf(lp:LayoutProblem*):NAV_SLProblemImpl*+FindAdaptorOf(lp:SL_Layout*):NAV_Solution*+GetLayoutProblem:LayoutProblem*

adaptee

NAV_SLProblemImpl

VObject:imported

Rectangle:imported

Ink:imported

NAV_SLProblemShape

+NAV_SLProblemShape(p:NAV_SLProblemImpl*)+~NAV_SLProblemShape#initInstance:void+Draw(r:Rectangle):void+DoObserve(id:int,part:int,vp:void*,op:Object*):void+GetProblem:NAV_SLProblemImpl*+SetBackgroundColor(c:Ink*):void+UnsetBackgroundColor():void+SetOrigin(at:Point):void+Center():Point

problem

bbox

bgcolor

Appendix B 114

B.2 Solution Hook Classes

NAV_Solution:imported

SL_Layout:imported

1:include

DesignSpace.hxxLayout.hxxSLProblemImpl.hxx

NAV_SLSolutionImpl

+NAV_SLSolutionImpl(pp:NAV_SLProblemImpl*,lp:SL_Layout*)+~NAV_SLSolutionImpl()#UpdateStructures:void#initInstance(pp:NAV_SLProblemImpl*,lp:SL_Layout*):void+DoObserve(id:int,part:int,vp:void*,op:Object*):void#NAV_SLSolutionImpl(pp:NAV_SLProblemImpl*,node:HSTreeNode*)#initInstance0(pp:NAV_SLProblemImpl*,node:HSTreeNode*):void#updateStructures0(node:HSTreeNode*):void+GetName():char*+GetShortName():char*+GetDesignUnits():SeqCollection*+GetWalls():SeqCollection*+GetEnclosure():DesignUnit*+GetSubsolutions:SeqCollection*+GetSupersolution:NAV_SLSolutionImpl*+FindAdaptorOf(lp:SL_Layout*):NAV_SLSolutionImpl*+IsAdaptorOf(lp:SL_Layout*):bool+GetLayout:SL_Layout*

adaptee

VObject:imported

NAV_SLSolutionImpl

2:include

VObject.h

Ink:imported

Rectangle:imported

NAV_SLSolutionShape

#size:int

+NAV_SLSolutionShape(sp:NAV_SLSolutionImpl*)+~NAV_SLSolutionShape()#initInstance:void+Draw(r:Rectangle):void+GetSolution:NAV_SLSolutionImpl*+DrawInner(r:Rectangle,highlight:bool=FALSE):void+DrawHighlight(r:Rectangle):void+SetBackgroundColor(c:Ink*):void+UnsetBackgroundColor():void+DoObserve(id:int,part:int,vp:void*,op:Object*):void+SetOrigin(at:Point):void+Center():Point

solution

bgcolor

lines bbox

Appendix B 115

B.3 Marker Hook Classes

0:include

DesignSpace.hxx

NAV_Marker:imported

Bitmap:importedNAV_SLMarkerImpl

+NAV_SLMarkerImpl(vop:Bitmap*,l:char*)+~NAV_SLMarkerImpl()#initInstance(vop:Bitmap*):void+SetIcon(vop:Bitmap*):void+GetIcon():Bitmap*

icon

ImageItem:imported

1:include

ImageItem.h

NAV_SLMarkerImpl NAV_SLSimpleMarkerView

+NAV_SLSimpleMarkerView(m:NAV_SLMarkerImpl*)#initInstance:void+DoObserve(id:int,part:int,vp:void*,op:Object*):void+GetMarker:NAV_SLMarkerImpl*+~NAV_SLSimpleMarkerView()

marker

HBox:imported

NAV_SLMarkerImpl

2:include

Box.h

NAV_SLMarkerView

#markerShared:bool

+NAV_SLMarkerView(m:NAV_SLMarkerImpl*)+~NAV_SLMarkerView()+initInstance():void+DoObserve(id:int,part:int,vp:void*,op:Object*):void+GetMarker:NAV_SLMarkerImpl*+SetMarkerShared():void+IsMarkerShared:bool

marker

Appendix B 116

B.4 Navigation Utility Menu

2:include

ImageItem.h

Ink:imported

ImageItem:imported

NAV_DSNavIconImage

+NAV_DSNavIconImage(bmp:Bitmap*,c:Ink*)+NAV_DSNavIconImage(id:int,bmp:Bitmap*,c:Ink*)+~NAV_DSNavIconImage()+SetColor(c:Ink*):void+Draw(r:Rectangle):void#initInstance:void

color

PopupButton:imported

:global

-$_gMarkersMenu:Menu*

TextField:imported

1:include

Dialog.hPopupItem.hFields.h

NAV_DSNavMarkerInput

#text:char*

+NAV_DSNavMarkerInput(l:char*)+~NAV_DSNavMarkerInput()+MakeButtons():VObject*+DoMakeContent():VObject*+GetIcon():Bitmap*+GetLabel():char*#makeIconMenuItem(i:int,b:Bitmap*):VObject*

Dialog:imported

ib

lt

Dialog:imported

NAV_Marker:imported

VObject:imported

ActionButton:imported

NAV_DSNavMarkerEdit

+NAV_DSNavMarkerEdit(mkrs:SeqCollection*)+~NAV_DSNavMarkerEdit()+Control(i:int,part:int,vp:void*):void+DoMakeContent():VObject*#makeMarkersView:VObject*+MakeButtons():VObject*+GetRemovedMarkers():SeqCollection*+DoSetDefaults():void

CollectionView:imported

3:include

CollView.h

markers

selections

mview

removeButton

Appendix B 117

B.5 2D Tree View Tool

1:include

DesignSpace.hxx

NAV_DSNav2DWindow

NAV_DS2DViewNAV_DesignSpace:imported

design_space ds_view

0:include

Dialog.hDesignWin.hxx

Dialog:imported :global

-__gSimpleView:bool

NAV_DSNav2DWindow

-simple:bool=TRUE

+NAV_DSNav2DWindow(ds:NAV_DesignSpace*,s:bool=TRUE)+~NAV_DSNav2DWindow()#initInstance:void#makeCommandBar:VObject*+DoMakeContent():VObject*+DoMakeMenuBar():MenuBar*+GetInitialWindowSize():Point+Control(id:int,part:int,vp:void*):void+DoSetupMenu(m:Menu*):void+DoMenuCommand(cmd:int):Command*+DoObserve(id:int,part:int,vp:void*,op:Object*):void+SetDesignSpace(ds:NAV_DesignSpace*):void+DoMarkNode():void+DoUnmarkNode():void+$MakeSimple2DView(ds:NAV_DesignSpace*):NAV_DSNav2DWindow*+$MakeEnhanced2DView(ds:NAV_DesignSpace*):NAV_DSNav2DWindow*

TreeView:imported 0:include

TreeView.h

NAV_DesignSpace:imported

Menu:imported

NAV_DS2DView

#versionHidden:bool=FALSE#solutionHidden:bool=FALSE

+NAV_DS2DView(dp:EvtHandler*,ds:NAV_DesignSpace*)+~NAV_DS2DView()#initInstance:void+InstallTree(root:Object*):void+BuildTree(op:Object*):VObject*+NodeAsVObject(op:Object*):VObject*+MakeTreeNode(id:int,items:SeqCollection*):TreeNode*+MakeChildrenIter(op:Object*):Iterator*+IsVersionHidden:bool+IsSolutionHidden:bool+ToggleVersionDisplay():void+ToggleSolutionDisplay():void#showVersions(on:bool,fromnode:TreeNode*):void#showSolutions(on:bool,fromnode:TreeNode*):void+GetMenu:Menu*+DoSetupMenu(m:Menu*):void+FindTreeNode(vop:VObject*):TreeNode*+SetSelection(vop:VObject*):void

design_space

popup

Appendix B 118

TextItem:imported

1:include

ImageItem.hTextItem.hSLProblemImpl.hxxSLSolutionImpl.hxx

NAV_SLProblemImpl:imported NAV_SLSolutionImpl:imported

NAV_DS2DPNode

+NAV_DS2DPNode(np:NAV_SLProblemImpl*,a:bool)+~NAV_DS2DPNode()#initInstance(a:bool):void+DoObserve(id:int,part:int,vp:void*,op:Object*):void

NAV_DS2DSNode

+NAV_DS2DSNode(sp:NAV_SLSolutionImpl*,a:bool)+~NAV_DS2DSNode()#initInstance(a:bool):void+DoObserve(id:int,part:int,vp:void*,op:Object*):void

NAV_DS2DRSNode

+NAV_DS2DRSNode+Draw(:Rectangle):void#initInstance:void

NAV_DS2DPSNode

+NAV_DS2DPSNode+Draw(:Rectangle):void#initInstance:void

NAV_DS2DSSNode

+NAV_DS2DSSNode+Draw(:Rectangle):void#initInstance:void

ImageItem:imported

problem solution

NAV_SLSolutionShape:imported

NAV_DS2DSShapeNode

#$curcolor:Ink*

+NAV_DS2DSShapeNode(sp:NAV_SLSolutionImpl*,a:bool)+~NAV_DS2DSShapeNode()#initInstance(a:bool):void+DoObserve(id:int,part:int,vp:void*,op:Object*):void

HBox:imported

NAV_DS2DMNode

+NAV_DS2DMNode(:VObject*,:VObject*)+~NAV_DS2DMNode()#initInstance:void+Highlight(:HighlightState):void

Appendix B 119

B.6 Multi-layer Tool

1:include

DesignSpace.hxx

ToggleButton:imported

Box:importedSeqCollection:imported

NAV_DSNavMLWindow

NAV_DSMLViewNAV_DesignSpace:imported

design_spacelayer_controls

problem_controlpcontrol_list

ds_view

Dialog:imported

2:include

Dialog.h

NAV_DSNavMLWindow

+NAV_DSNavMLWindow(ds:NAV_DesignSpace*)+~NAV_DSNavMLWindow()#initInstance:void#makeCommandBar:VObject*#makeLayerControls:VObject*#updateLayerControls:void#makeProblemControls:VObject*#updateProblemControls():void#resetProblemControls:void+DoMakeContent():VObject*+DoMakeMenuBar():MenuBar*+GetInitialWindowSize():Point+Control(id:int,part:int,vp:void*):void+DoSetDefaults():void+DoSetupMenu(m:Menu*):void+DoMenuCommand(cmd:int):Command*+DoObserve(id:int,part:int,vp:void*,op:Object*):void+IsLayerOn(layer:int):bool+SetDesignSpace(ds:NAV_DesignSpace*):void

3:include

Shape.hxxSLSolutionImpl.hxxDialogView.h

NAV_SLSolutionVObject

NAV_DesignSpace:importedSLUI_Shape:imported

CompositeVObject:imported

NAV_SLSolutionImpl:imported

DialogView:imported

Menu:imported

NAV_DSMLView

focused_solution

root_solution

design_space

shapes

solution

list

menu

Appendix B 120

:global

-cDSNavLayerOn:const int=2001-cDSNavLayerOff:const int=2002

NAV_SLSolutionVObject

#layer:int#hide:bool

+NAV_SLSolutionVObject(l:int,sp:NAV_SLSolutionImpl*,cp:SeqCollection*,active:bool)+~NAV_SLSolutionVObject()#initInstance(active:bool):void+Draw(r:Rectangle):void+GetMinSize():Metric+DoObserve(id:int,part:int,vp:void*,op:Object*):void+GetLayer:int+GetSolution:NAV_SLSolutionImpl*+StopObserving(op:Object*):void+Focus():void+Unfocus():void+GetProblemsOfLayer(l:int):SeqCollection*+GetSolutionsOfLayer(l:int):SeqCollection*+ContainsPoint(p:Point):bool+IsHidden:bool+FindSubsolutionUnderMouse(p:Point):NAV_SLSolutionImpl*

NAV_DSMLView

#view_layers:int#focused_layer:int

+NAV_DSMLView(eh:EvtHandler*,ds:NAV_DesignSpace*)+~NAV_DSMLView()#initInstance:void+SetRootSolution(s:NAV_SLSolutionVObject*):void+SetDesignSpace(ds:NAV_DesignSpace*):void+BuildSubsolutionLayer(op:NAV_SLSolutionImpl*,layer:int):NAV_SLSolutionVObject*+MakeSolutionVObject(id:int,sp:NAV_SLSolutionImpl*,items:SeqCollection*):NAV_SLSolutionVObject*#buildLayers(ds:NAV_DesignSpace*):NAV_SLSolutionVObject*+GetLayers:int+SetLayerOn(l:int):void+SetLayerOff(l:int):void+GetFocusedLayer:int+UpdateLayers(fromnode:NAV_SLSolutionVObject*,focus:bool):void+GetProblemsOfFocusedLayer():SeqCollection*+GetSolutionsOfFocusedLayer():SeqCollection*+DoLeftButtonDownCommand(p:Point,t:Token,clicks:int):Command*+DispatchEvents(lp:Point,t:Token&,vf:Clipper*):Command*+GetMenu():Menu*

SLUI_InactiveDUView:imported5:include

DUView.hxx

NAV_DSMLInactiveDUView

+NAV_DSMLInactiveDUView(dup:DesignUnit*)+Draw(r:Rectangle):void

Appendix B 121

B.7 Entity-Relationship Diagraming Tool

NAV_DSERView

ActionButton:imported

NAV_DSMarkerCollView


Zoomer:imported

NAV_DSNavERWindow1:include

DesignSpace.hxxZoomer.h

design_space

ds_view

marker_view

put_button

zoomer

Dialog:imported

2:include

Dialog.h

NAV_DSNavERWindow

+NAV_DSNavERWindow(ds:NAV_DesignSpace*)+~NAV_DSNavERWindow()+DoMakeContent():VObject*+DoMakeMenuBar():MenuBar*+GetInitialWindowSize():Point+Control(id:int,part:int,vp:void*):void+DoSetupMenu(m:Menu*):void+DoMenuCommand(cmd:int):Command*+DoObserve(id:int,part:int,vp:void*,op:Object*):void+SetDesignSpace(ds:NAV_DesignSpace*):void#initInstance:void+MarkersInView():SeqCollection*

View:imported

3:include

SLMarkerImpl.hxx

NAV_SLMarkerImpl:imported



NAV_DSERView

+NAV_DSERView(:EvtHandler*,:Point)+~NAV_DSERView()+DoLeftButtonDownCommand(:Point,:Token,:int):Command*#initInstance:void+Draw(:Rectangle):void+AddMarker(:NAV_SLMarkerImpl*):void+GetMarkers:SeqCollection*+DispatchEvents(:Point,:Token&,:Clipper*):Command*+AddConnection(:VObject*):void+RemoveConnection(:VObject*):VObject*+FindShape(:Point):VObject*+DoObserve(:int,:int,:void*,:Object*):void+RemoveMarkerView(:VObject*):void

markers

marker_shapes

connections

Appendix B 122

CollectionView:imported


4:include

CollView.hOrdColl.h

Menu:imported

NAV_DSMarkerCollView

+NAV_DSMarkerCollView(eh:EvtHandler*,ds:NAV_DesignSpace*)+~NAV_DSMarkerCollView()+SetDesignSpace(ds:NAV_DesignSpace*):void#initInstance:void+GetSelectedMarkerView():VObject*+RemoveMarkerView(vop:VObject*):void+GetMenu():Menu*+HasSelection():bool

design_space

menu

VBox:imported

NAV_SLMarkerShape

+NAV_SLMarkerShape(mk:NAV_SLMarkerImpl*)+~NAV_SLMarkerShape()#initInstance:void+Draw(r:Rectangle):void+GetMarker:NAV_SLMarkerImpl*+DoLeftButtonDownCommand(p:Point,t:Token,clicks:int):Command*+Center():Point+DoObserve(id:int,part:int,vp:void*,op:Object*):void+ContainsPoint(p:Point):bool

TextView:importedText:importedCompositeVObject:imported

NAV_SLMarkerImpl:imported

5:include

Text.hTextView.h

NAV_SLMarkerConnection

+NAV_SLMarkerConnection(sh:NAV_SLMarkerShape*,eh:NAV_SLMarkerShape*)+~NAV_SLMarkerConnection()#initInstance:void+Draw(r:Rectangle):void+DoObserve(id:int,part:int,vp:void*,op:Object*):void+UpdatePoints():void+Init(vp:View*):void+SetLabel(t:Text*):void+SetOrigin(at:Point):void+GetMinSize():Metric+Center:Point

startShape endShape

textviewtx

marker

Appendix B 123

Command:imported

NAV_DSERView NAV_SLMarkerShape

NAV_SLMarkerConnection

NAV_SLMarkerConnectCommand

+NAV_SLMarkerConnectCommand(:NAV_DSERView*,:NAV_SLMarkerShape*)+~NAV_SLMarkerConnectCommand()+DoIt():void+UndoIt():void+Commit():void+TrackFeedback(:Point,:Point,:bool)+TrackMouse(:TrackPhase,:Point,:Point,:Point):Command*#initInstance:void

view start end

newconnection

Appendix B 124

Appendix C 125

C. Navigation Support: Specifications and Design

This document records the software engineering process of a software environment thatprovides support of information navigation in generative design systems. This softwareengineering process is developed based on the Use Case Approach of the Object-OrientedSoftware Engineering (OOSE) method by Jacobson1. A formal usability evaluation methodGOMS model2 is introduced into the software engineering process to enhance theevaluation phase of the process.

C.1 OrganizationTo support information navigation in generative design systems, there are five basicoperations: show location, mark, go to, step and search (or find). These basic operationsare formulated as use cases which describe scenarios of possible uses of the softwareenvironment from the user’s perspective. The design and implementation of the softwareenvironment follow specifications described in each use case. Therefore, the reportdocuments the software engineering process use case-by-use case. Each use case contains4 parts:

1. the use case description that specifies interactions between a user and the system;2. an interaction diagram that briefly describes the system design in terms of interactions

between objects (different parts of the system or actors);3. the user interface implementation to demonstrate the use of the system; and4. the GOMS model based on the user interface implementation.

C.2 NotationsGenerally, notations used in this document follow those described in the OOSE andGOMS methods. For convenient references, the notations are briefly explained below.

1. See Jacobson, I., M. Christerson, P. Jonesson and G. Övergaard, Object-Oriented SoftwareEngineering: A Use Case Driven Approach, Addison-Wesley, 1992.

2. GOMS is a modeling method to describe user’s cognitive structure through Goals, Operators,Methods for achieving the goals and Selection rules for choosing among competing methods forgoals. For an introduction of GOMS analysis, see Kieras, D.E., “Towards a practical GOMS modelmethodology for user interface design,” in Handbook of Human-Computer Interaction, M. Helander(ed.), Elsevier Science Publishers B.V., 1988 (pp. 135-157). For further readings, see John, B.E. andD.E. Kieras, “The GOMS family of analysis techniques: tools for design and evaluation,” TechnicalReport, CMU-CS-94-181, School of Computer Science, Carnegie Mellon University, 1994.

Appendix C 126

Interaction diagrams use notations illustrated in Figure C-1. In some diagrams (as well asin the illustration in Figure C-1) throughout this document, a solid-color rectangle arearepresents a system, such as a generative design system, which can communicate but isindependent from the navigation software environment. Readers should note that thisparticular notation is not a standard notation used in OOSE methods, but used here tosimplify the presentation of interaction diagrams.

The user interface sections describe step-by-step user interactions with the system toachieve use case goals. Most interactions are performed through mouse movements andbutton clicks or keyboard strokes. These are called keystrokes. In user interface sections,keystrokes are presented in angle-brackets with bold typeface, such as <Control-Key> and<Left-Mouse-Button>.

GOMS models encode user interactions in terms of goals, operators, methods andselection rules. Figure C-2 illustrates these terms.

Figure C-1: Interaction diagram

Figure C-2: GOMS model

GenerativeDesignSystem

DesignSpaceView Solution

Designer request the search for solutions

System prompts thedesigner to input search

criteria

System prompts thedesigner to select a

solution (if multipleavailable)

SearchView SearchEngine

activate_solution

highlight

set_active_solution

System objects

System boundary

Other system

Communication

Optional communication

user activity

Object in activation

GOAL: LOCATE-ACTIVE-NODE-IN-DESIGN-SPACE-VIEW. GOAL: OPEN-DESIGN-SPACE-VIEW. . [select:. . GOAL: OPEN-2DTREE-VIEW ...if desired 2D tree view. . . MOVE-POINTER-TO-MENU. . . CLICK-LEFT-MOUSE-BUTTON. . GOAL: OPEN-MULTILAYER-VIEW ...if desired multi-layer view. . . MOVE-POINTER-TO-MENU. . . CLICK-LEFT-MOUSE-BUTTON. . ]. GOAL: ADJUST-VIEW ...repeat until active node is in view

Goal statement

Operator

Selection rule

Method

Appendix C 127

C.3 Use CasesThe remaining of this document describes specifications and design according to thefollowing five groups of use cases:

1. Show Location

• Show Location of Active Node

2. Mark

• Mark a Node

• Go To Marked Node

3. Go To

• Go To Node

• Go To Specific Solution

• Go To Specific Problem

4. Step

• Step To Parent, Child, Sibling Solution

• Step To Parent, Child, Sibling Problem

• Step To Previous, Next Problem Revision

5. Find

• Find Solution

• Find Problem

Appendix C 128

Show Location of Active Node

Brief Description The system displays a design space view and highlights the active node.

Flow of Events 1. The designer requests display of a design space view.

2. The system displays a design space view with the active node highlighted.

Comments A node represents a problem or a solution. There may be more than one activenode in a design space, i.e., an active problem and its associated active solution.A design space view does not necessarily display a complete view of all nodesin the design space; it may be a partial view, e.g. a view of problemdecomposition hierarchy only. The highlighting mechanism may employ visualcues in addition to the color change method (e.g. reverse video display)commonly used.

Interaction Diagram

DesignSpaceView DesignSpaceNodeDesigner requests display of the design space get_active_node

highlight

Appendix C 129

User Interface (Alternative 1) 1. The designer selects the 2D Tree View option from the Navigation Tool menu.

2. The system brings up a 2D tree view displaying the design space with the active problem and solution highlighted (for examples, see Figure 1 and Figure 2 below).

Figure 1. A simple 2D tree view of a design space

Active problem

Active solution

Figure 2. An enhanced 2D tree view of a design space

Active problem

Active solution

Appendix C 130

User Interface (Alternative 2) 1. The designer selects the Multilayer View option from the Navigation Tool menu.

2. The system brings up a multi-layer view displaying the design space with the active solution highlighted (see Figure 3).

Figure 3. A multi-layer view of a partial design space (showing solutions)

Active solution

Appendix C 131

GOMS ModelFor user interface (Alternative 1) and (Alternative 2):GOAL: LOCATE-ACTIVE-NODE-IN-DESIGN-SPACE-VIEW. GOAL: OPEN-DESIGN-SPACE-VIEW. . [select:. . GOAL: OPEN-2DTREE-VIEW. . . MOVE-POINTER-TO-MENU. . . CLICK-LEFT-MOUSE-BUTTON. . GOAL: OPEN-MULTILAYER-VIEW. . . MOVE-POINTER-TO-MENU. . . CLICK-LEFT-MOUSE-BUTTON. . ]. GOAL: ADJUST-VIEW ...repeat until active node is in view. . [select:. . GOAL: PAN-VIEW. . . [select:. . . GOAL: DO-PAN-THROUGH-SCROLLER. . . . MOVE-POINTER-TO-SCROLLER-HANDLE. . . . PRESS-LEFT-MOUSE-BUTTON. . . . MOVE-MOUSE-TO-NEW-POSITION. . . . RELEASE-MOUSE-BUTTON. . . GOAL: DO-PAN-THROUGH-MITTEN. . . . MOVE-POINTER-TO-VIEW-AREA. . . . PRESS-MIDDLE-MOUSE-BUTTON. . . . MOVE-MOUSE-TO-NEW-POSITION. . . . RELEASE-MOUSE-BUTTON. . . ]. . GOAL: ZOOM-VIEW. . . [select:. . . GOAL: DO-ZOOM-THROUGH-MENU. . . . MOVE-POINTER-TO-VIEW-MENU. . . . PRESS-LEFT-MOUSE-BUTTON. . . . MOVE-MOUSE-TO-ZOOMOUT-OPTION. . . . VERIFY-HIGHLIGHT. . . . RELEASE-MOUSE-BUTTON. . . GOAL: DO-ZOOM-THROUGH-SHORTCUT. . . . MOVE-POINTER-TO-VIEW-AREA. . . . SHIFT-LESSTHAN(<)-KEY. . . ]. . GOAL: RESIZE-WINDOW. . . MOVE-POINTER-TO-WINDOW-FRAME. . . PRESS-LEFT-MOUSE-BUTTON. . . MOVE-MOUSE-TO-NEW-POSITION. . . RELEASE-MOUSE-BUTTON. . ]. . VERIFY-ACTIVE-NODE

Appendix C 132

Mark a Node

Brief Description The system marks a node selected by the designer.

Flow of Events 1. The designer selects a node in a design space view and asks the system to mark it.

2. The system prompts the designer to input a marker label.

3. The system tags the selected node with the marker label.

Comments A marker label may contain texts and/or images (such as an icon). A user should be able to distinguish active nodes, marked nodes, and active-and-marked nodes (active nodes that have associated markers).

Interaction Diagram

DesignSpaceView DesignSpaceNode

Designer requests marking of the selected node

get_selected_node

MarkerList

Designer selects a nodeset_selection

System prompts thedesigner to input a

marker label mark_node

display_markers

Appendix C 133

User Interface 1. The designer selects (i.e. clicks the <Left-Mouse-Button> on) a node in a 2D tree design space view; the system highlights the selected node.

2. The designer presses down the <Right-Mouse-Button> on the selected node.

3. The system brings up a pop-up operation menu (see Figure 4).

4. The designer selects (i.e. releases the <Right-Mouse-Button> on) the Mark option.

5. The system brings up the marker label dialog (for example, see Figure 5); the designer selects a marker icon and enters a marker label, then clicks COMMIT or CANCEL.

6. If the designer selects CANCEL, the system withdraws the dialog and leaves the state of the session unaltered.

7. If the designer selects COMMIT, the system records the marker and refreshes the design space view (for example, see Figure 4).

Figure 4. Marked nodes and pop-up operation menu

Marked node

Pop-up operation menu

Figure 5. Marker label dialog

Appendix C 134

GOMS ModelGOAL: MARK-NODE. GOAL: SELECT-NODE. . MOVE-POINTER-TO-NODE. . CLICK-LEFT-MOUSE-BUTTON. . VERIFY-SELECTION. GOAL: ISSUE-MARK-COMMAND. . MOVE-POINTER-TO-SELECTED-NODE. . PRESS-RIGHT-MOUSE-BUTTON. . MOVE-MOUSE-TO-MARK. . VERIFY-HIGHLIGHT. . RELEASE-MOUSE-BUTTON. GOAL: INPUT-MARKER. . GOAL: SELECT-ICON. . . [selection:. . . GOAL: ACCEPT-DEFAULT-ICON. . . . VERIFY-ICON. . . GOAL: CHANGE-ICON. . . . MOVE-POINTER-TO-ICON-BUTTON. . . . PRESS-LEFT-MOUSE-BUTTON. . . . MOVE-MOUSE-TO-NEW-ICON. . . . VERIFY-ICON. . . . RELEASE-MOUSE-BUTTON. . . ]. . GOAL: INPUT-LABEL. . . [selection:. . . GOAL: ACCEPT-DEFAULT-LABEL. . . . VERIFY-LABEL. . . GOAL: CHANGE-LABEL. . . . MOVE-POINTER-TO-LABEL. . . . INPUT-N-CHARACTERS. . . . VERIFY-LABEL. . . ]. . GOAL: CONFIRM-INPUT. . . [selection:. . . GOAL: CONFIRM-THROUGH-KEYBOARD. . . . HIT-RETURN-KEY. . . GOAL: CONFIRM-THROUGH-POINTER. . . . MOVE-POINTER-TO-COMMIT. . . . CLICK-LEFT-MOUSE-BUTTON. . . ]. VERIFY-MARKED-NODE

Appendix C 135

Go To Marked Node

Brief Description The system activates and displays a node selected by the designer from among those that are marked.

Flow of Events 1. The designer selects a marker from a design space view and requests its activation.

2. The system activates the node associated with the selected marker.

3. If the node is a solution, the system activates and displays the solution and its associated problem. If the node is a problem, the system activates and displays the problem and its last active solution.

Interaction Diagram

DesignSpaceView Marker

Designer selects a marker

get_selected_marker

get_solution

Designer requests activation of the selected marker

activate_problem

Generative

get_problem

activate_solution

set_marker_selection

DesignSpaceNodeDesignSystem

set_active_node

highlight

Appendix C 136

User Interface 1. The designer selects (i.e. clicks the <Left-Mouse-Button> on) a marker in a design space view; the system highlights the selected marker (for example, see Figure 6).

2. The designer presses down the <Right-Mouse-Button> on the selected marker.

3. The system brings up a pop-up operation menu.

4. The designer selects (i.e. releases the <Right-Mouse-Button> on) the Go To option.

5. The SEED-Layout system updates the DW with the proper layout; if necessary, it refreshes the PSW with the information of the associated problem specification, and properly refreshes the PHW and DSW to display active problem specification and layout.

GOMS ModelGOAL: GO-TO-MARKED-NODE. GOAL: SELECT-MARKER. . MOVE-POINTER-TO-MARKER. . CLICK-LEFT-MOUSE-BUTTON. . VERIFY-SELECTION. GOAL: ISSUE-GO-TO-COMMAND. . MOVE-POINTER-TO-SELECTED-MARKER. . PRESS-RIGHT-MOUSE-BUTTON. . MOVE-MOUSE-TO-GO-TO. . VERIFY-HIGHLIGHT. . RELEASE-MOUSE-BUTTON. VERIFY-DISPLAYS

Figure 6. A design space view that shows marked nodes and markers

Selected marker

Appendix C 137

Go To Node

Brief Description The system activates and displays a node selected by the designer.

Flow of Events 1. The designer selects a node in a design space view and requests its activation.

2. The system activates and displays the solution or problem that defines this node.

Interaction Diagram

DesignSpaceView DesignSpaceNode

Designer selects a node

get_selected_node

get_problem

set_selection

Designer requests activation of the selected node

set_active_node


activate_problem

get_solution

activate_solution

highlight

Appendix C 138

User Interface 1. The designer selects (i.e. clicks the <Left-Mouse-Button> on) a node in a design space view.

2. The designer presses down the <Right-Mouse-Button> on the selected node.

3. The system brings up a pop-up operation menu (see Figure 7).

4. The designer selects (i.e. releases the <Right-Mouse-Button> on) the Go To option.

5. The system updates the design space view: it highlights the new active node and de-highlights the previously active node.


GOMS ModelGOAL: GO-TO-NODE. GOAL: SELECT-NODE. . MOVE-POINTER-TO-NODE. . CLICK-LEFT-MOUSE-BUTTON. . VERIFY-SELECTION. GOAL: ISSUE-GO-TO-COMMAND. . MOVE-POINTER-TO-SELECTED-NODE. . PRESS-RIGHT-MOUSE-BUTTON. . MOVE-MOUSE-TO-GO-TO. . VERIFY-HIGHLIGHT. . RELEASE-MOUSE-BUTTON. VERIFY-DISPLAYS

Figure 7. A selected node with pop-up operation menu

Pop-up operation menu

Appendix C 139

Go To Specific Solution

Brief Description The system activates and displays a solution selected by the designer in a design space view.

Flow of Events 1. The designer selects a solution in a design space view and requests its activation.

2. The system activates and displays the selected solution.

Interaction Diagram


Designer selects a solution

get_selected_node

get_problem

set_selection

Designer requests activation of the selected solution

set_active_node


activate_problem

activate_solution

highlight

Appendix C 140

User Interface (Alternative 1) See the User Interface section of use case “Go To Node” (when selected node represents a solution).

User Interface (Alternative 2) 1. The designer selects a layout radio button from a multi-layer view window.

2. The system updates the view with the new active layout highlighted and de-highlights the previously active layout.

3. The SEED-Layout system updates the DW with the proper layout, and if necessary, refreshes the PSW with the information of the associated problem specification; it properly refreshes the PHW and DSW to display active problem specification and layout.

Figure 8. Go to specific layout through layout radio buttons

Layout radio buttons

Appendix C 141

User Interface (Alternative 3) 1. To go to a sublayout, the designer holds the <Control-Key> and clicks the <Left-Mouse-Button> on a design unit in a multi-layer design space view.

2. The system updates the view with the new active layout highlighted and de-highlights the previously active layout (for examples, see Figure 9).


Figure 9. Go to a sublayout

Previously active solution

New active solution

(before the go to command)

(after the command)

Appendix C 142

GOMS Model

For user interface (Alternative 1), see the GOMS Model section of use case “Go To Node”.

For user interface (Alternative 2):

GOAL: GO-TO-LAYOUT. MOVE-POINTER-TO-LAYOUT-RADIO-BUTTON. CLICK-LEFT-MOUSE-BUTTON. VERIFY-DISPLAYS

For user interface (Alternative 3):

GOAL: GO-TO-SUBLAYOUT. MOVE-POINTER-TO-DESIGN-UNIT. CONTROL-CLICK-LEFT-MOUSE-BUTTON. VERIFY-DISPLAYS

Appendix C 143

Go To Specific Problem

Brief Description The system activates and displays a problem selected by the designer in a design space view.

Flow of Events 1. The designer selects a problem in a design space view and requests its activation.

2. The system activates and displays this problem.

3. The system activates and displays the last active solution of the selected problem.

Comments The last active solution is made active if the problem to be activated has led to more than one (partial) solution because it suggests to the designer that work can continue at the point where it was left off the last time.

Interaction Diagram

User Interface See the User Interface section of use case “Go To Node” (when selected node represents a problem).

GOMS Model See the GOMS Model section of use case “Go To Node”.

DesignSpaceView Problem

Designer selects a problem

get_selected_node

get_solution

set_selection

Designer requests activation of the selected problem

set_active_node

Generative

activate_problem

activate_solution

highlight

SolutionDesignSystem

highlight

Appendix C 144

Step To Parent, Child, Sibling Solution

Brief Description The system activates and displays the parent, child, or sibling solution of the currently active solution.

Flow of Events 1. The designer requests activation of the parent/child/sibling solution.

2. The system activates and displays it.

Comments This is a stepping navigation in the solution hierarchy.

Interaction Diagram


get_active_solutionDesigner requests activation of the parent/child/previous sibling/next sibling solution


highlight

set_active_solution

get_parent, get_first_child, get_next_sibling, get_prev_sibling

activate_solution

Appendix C 145

User Interface 1. The designer presses down the <Right-Mouse-Button> in a multi-layer design space view.

2. The system brings up a pop-up navigation menu (see Figure 10).

3. The designer selects (i.e. releases the <Right-Mouse-Button> on) one of the four navigation buttons:

• : go to parent solution • : go to child solution

• : go to previous sibling solution • : go to next sibling solution

4. The system updates the design space with the new active solution.

5. The system displays a message if a solution does not exist.

GOMS ModelGOAL: STEP-TO-PARENT/CHILD/SIBLING-SOLUTION. MOVE-POINTER-TO-VIEW. PRESS-RIGHT-MOUSE-BUTTON. MOVE-MOUSE-TO-STEP-ICON. VERIFY-HIGHLIGHT. RELEASE-MOUSE-BUTTON. VERIFY-DISPLAYS

Figure 10. Pop-up navigation buttons and results of Step to Parent Solution

Pop-up navigation buttons

Previously active solution(before step command)

new active solution(after step to parent)

Appendix C 146

Step To Parent, Child, Sibling Problem

Brief Description The system activates and displays the parent, child, or sibling problem of the currently active problem.

Flow of Events 1. The designer requests activation of the parent/child/sibling problem.

2. The system responds as specified in the Flow of Events section of use case “Go To Specific Problem”.

Comments This is a stepping navigation in the problem decomposition hierarchy.

Interaction Diagram


get_active_problem

get_solution

Designer requests activation of parent/child/previous sibling/next sibling problem

set_active_problem

Generative

activate_problem

activate_solution

highlight


highlight

get_parent, get_first_child, get_prev_sibling, get_next_sibling

Appendix C 147

User Interface (Step to Parent Problem)

1. To step to the parent problem, the designer holds the <Control-Key> and clicks the <Left-Mouse-Button> on a point outside the active layout in a multi-layer design space view.

2. The system updates the view with the new active layout (of the new active problem) highlighted and de-highlights the previously active layout (for examples, see Figure 11).

3. The SEED-Layout system updates the DW with the proper layout; if necessary, it refreshes the PSW with the information of the associated problem specification and properly refreshes the PHW and DSW to display active problem specification and layout.

GOMS ModelFor user interface (Step to Parent Problem):

GOAL: STEP-TO-PARENT-PROBLEM. MOVE-POINTER-TO-VIEW. VERIFY-POSITION-NOT-ON-ACTIVE-LAYOUT. CONTROL-CLICK-LEFT-MOUSE-BUTTON. VERIFY-DISPLAYS

Figure 11. Step to parent problem

Solution of previously active problem

Solution of new active problem

(before the step command)

(after the command)

Appendix C 148

Step To Previous, Next Problem Revision

Brief Description The system activates and displays the previous or next version of the currently active problem.

Flow of Events 1. The designer requests activation of the previous/next problem revision.

2. The system responds as specified in the Flow of Events section of use case “Go To Specific Problem”.

Comments This is a stepping navigation in the problem revision history.

Interaction Diagram

User Interface No implementation available explicitly for stepping navigation in the problem revision history.

For an alternative operation, see the User Interface section of use case “Go ToSpecific Problem”.

GOMS Model Not available.

For analysis of an alternative operation, see the GOMS Model section of use case“Go To Specific Problem”.


get_active_problem

get_solution

Designer requests activation of previous/next problem revision

set_active_problem

Generative

activate_problem

activate_solution

highlight


highlight

get_previous_revision, get_next_revision

Appendix C 149

Find Solution

Brief Description The system finds a solution that satisfies search criteria or indices specified by the designer, activates and displays it.

Flow of Events 1. Upon the designer’s request, the system displays a find solution dialog view.

2. The designer inputs the solution search criteria and search scope (local to the current solution hierarchy or globally in the design space), and confirms the request.

3. The flow of events after the search request depends on the search result:

If none of the solutions in memory satisfies the search criteria, thesystem notifies the designer and returns the system state to what iswas before this operation.

If only one solution satisfies the search criteria, the system activatesand displays it.

If two or more solutions satisfy the search criteria, the system displaysthem and notifies the designer. The designer selects a solution; thesystem activates and displays it.

Comments The search mechanism is a research issue that is out of the context of this research scope.

Interaction Diagram



Designer request the search for solutions

System prompts the designerto input search criteria

System prompts the designerto select a solution (if

multiple available)


activate_solution

highlight

set_active_solution

Appendix C 150

User Interface No implementation available.

Interface design suggestions for the case of multiple search results:

1. Create a new window displaying the list of solutions to allow the designer to examine and select a solution from the display.

2. Update the design space view (if there is one) to highlight (by using visual cues or hiding other nodes) solutions that are the search results so that the designer can examine and select a solution from the view (i.e. in this case, the find command acts as a filtering utility).

3. Mark the search results with special markers (if a marker utility is available) to allow the designer to examine and select a solution from the list of marked solutions.

GOMS ModelGoal level model (based on the use case description and interaction diagram):

GOAL: FIND-SOLUTION. GOAL: INVOKE-FIND-SOLUTION-OPERATION. GOAL: INPUT-SEARCH-CRITERION ...repeat until all criteria entered. GOAL: ISSUE-FIND-COMMAND. [select:. . GOAL: COMFIRM-SYSTEM-NOTIFICATION ...if no solutions found. . GOAL: GO-TO-A-SOLUTION ...if multiple solutions found. ]. VERIFY-DISPLAYS

Appendix C 151

Find Problem

Brief Description The system finds a problem that satisfies the criteria specified by the designer, activates and displays it.

Flow of Events 1. Upon the designer’s request, the system displays a find problem dialog view.

2. The designer inputs the problem search criteria and search scope (local to the current problem decomposition hierarchy or revision history, or globally in the design space), and confirms the request.

3. The flow of events after the search request depends on the search result:

If none of the problems satisfies the search criteria, the system notifiesthe designer and returns the system state to what is was before thisoperation.

If only one problem satisfies the search criteria, the system responds asspecified in the Flow of Events section of use case “Go To SpecificProblem”.

If two or more problems satisfy the search criteria, the system displaysthem and notifies the designer. The designer selects a problem; thesystem responds as specified in the Flow of Events section of use case“Go To Specific Problem”.

Comments Refer to the Comments section of use case “Find Solution”.

Interaction Diagram



Designer request the search for problems

System prompts the designerto input search criteria

System prompts the designerto select a problem (if

multiple available)


activate_problem

highlight

set_active_problem

Appendix C 152

User Interface No implementation available.

For interface design suggestions to handle multiple search results, see the UserInterface section of use case “Find Solution”.

GOMS ModelGoal level model (based on the use case description and interaction diagram):

GOAL: FIND-PROBLEM. GOAL: INVOKE-FIND-PROBLEM-OPERATION. GOAL: INPUT-SEARCH-CRITERION ...repeat until all criteria entered. GOAL: ISSUE-FIND-COMMAND. [select:. . GOAL: COMFIRM-SYSTEM-NOTIFICATION ...if no problems found. . GOAL: GO-TO-A-PROBLEM ...if multiple problems found. ]. VERIFY-DISPLAYS

Appendix D 153

D. Task Descriptions and Instructions for Control Treatment

Appendix D 154

Appendix D 155

Appendix D 156

Appendix D 157

Appendix D 158

Appendix E 159

E. Task Descriptions and Instructions for Map-and-Notepad Treatment

Appendix E 160

Appendix E 161

Appendix E 162

Appendix E 163

Appendix E 164

Appendix E 165

Appendix E 166

Appendix F 167

F. Task Descriptions and Instructions for Map Treatment

Appendix F 168

Appendix F 169

Appendix F 170

Appendix F 171

Appendix F 172

Appendix F 173

Appendix F 174

Appendix G 175

G. Task Descriptions and Instructions for View Treatment

Appendix G 176

Appendix G 177

Appendix G 178

Appendix G 179

Appendix G 180

Appendix G 181

Appendix G 182

Appendix H 183

H. Processed Keystroke Data and Post-task Interview Notes

Appendix H 184

Control Treatment Processed Keystroke Data: B2

Window Action Time delta elapsed-t Notes

Design [ FIRESTATION ] // experiment setup 884896328

Design [ adm_wing ] cSLUIIdLPGoToParentProblem 884896627 299 0’00" // begin

Design [ FIRESTATION ] cSLUIIdLPGoToParentProblem 884896635 8 0’08"

Design [ FIRESTATION ] // window manipulation 884896637 2 0’10"

Design [ FIRESTATION ] cSLUIIdDWOpenLPW 884896658 21 0’31"

Layout Problem [ FIRESTATION ] cCLOSE 884896663 5 0’36"

Design [ FIRESTATION ] cSLUIIdDWOpenPHW 884896666 3 0’39"



Design [ FIRESTATION ] SLUIIdDWOpenDSW 884896676 5 0’49"





Design [ FIRESTATION ] cSLUIIdDWOpenLPW 884896700 19 1’13"

Layout Problem [ FIRESTATION ] cCLOSE 884896713 13 1’26"

Design Space [ FIRESTATION ] // window manipulation 884896713 0 1’26"



Design [ FIRESTATION ] cSLUIIdDWOpenLPM 884896759 46 2’12"














Design Space [ FIRESTATION ] cSLUI_StateOpen 884896835 16 3’28" // locate Firestation

Design [ FIRESTATION ] // window manipulation 884896838 3 3’31" // confirm Firestation




Design [ FIRESTATION ] // DU selection 884896916 74 4’49"

Design [ FIRESTATION ] cSLUIIdDWExpandDU 884896918 2 4’51"



Design Space [ FIRESTATION ] cSLUI_StateOpen 884896945 3 5’18" ***

Design [ FIRESTATION ] // window manipulation 884896947 2 5’20" *** confused layout

Design [ FIRESTATION ] // window manipulation 884896947 0 5’20" *** derivation hierarchy

Design Space [ FIRESTATION ] // window manipulation 884896950 3 5’23" *** with problem

Design Space [ FIRESTATION ] cSLUI_StateOpen 884896953 3 5’26" *** hierarchy

Design [ FIRESTATION ] // window manipulation 884896954 1 5’27" ***

Design [ FIRESTATION ] // window manipulation 884896958 4 5’31" *** wondering between

Design [ FIRESTATION ] // window manipulation 884896958 0 5’31" *** problems

Design Space [ FIRESTATION ] // window manipulation 884896981 23 5’54" ***

Design Space [ FIRESTATION ] // window manipulation 884896981 0 5’54" ***

Design Space [ FIRESTATION ] cSLUI_StateOpen 884896982 1 5’55" ***



Design [ FIRESTATION ] cSLUIIdLPGoToChildProblem 884896995 11 6’08" ***

Design Space [ adm_wing ] // window manipulation 884897022 27 6’35" ***

Design [ adm_wing ] cSLUIIdDWOpenLPM 884897025 3 6’38" ***



Design [ adm_wing ] cSLUIIdLPGoToPrevSibProblem 884897076 49 7’29" ***

Design [ dorm_wing ] // window manipulation 884897084 8 7’37" ***

Design Space [ dorm_wing ] // window manipulation 884897109 25 8’02" ***

Design [ dorm_wing ] cSLUIIdDWOpenLPM 884897118 9 8’11" ***






Design [ dorm_wing ] cSLUIIdDWOpenLPM 884897145 11 8’38" ***



Appendix H 185








LayoutProblem Manager cSLUIIdLPMActivate 884897191 36 9’24"

Design [ dorZ_1 ] // DU selection 884897194 3 9’27"

Design [ dorZ_1 ] // window manipulation 884897195 1 9’28"

Design [ dorZ_1 ] cZOOMIN 884897206 11 9’39"

Design [ dorZ_1 ] cZOOMIN 884897209 3 9’42"

Design [ dorZ_1 ] cSLUIIdDWShowSuperlayout 884897233 24 10’06"

Design [ dorZ_1 ] cSLUIIdDWShowSuperlayout 884897239 6 10’12"

Design Space [ dorZ_1 ] // window manipulation 884897252 13 10’25"




Design Space [ dorZ_1 ] cSLUI_StateOpen 884897255 3 10’28" // locate dorZ

Design [ dorZ_1 ] // window manipulation 884897257 2 10’30" // confirm dorZ


Design Space [ batZ_1 ] // window manipulation 884897281 3 10’54"

Design [ batZ_1 ] cSLUIIdDWGotoNextState 884897318 37 11’31"

Design [ batZ_1 ] // window manipulation 884897327 9 11’40"

Design [ batZ_1 ] cSLUIIdDWGotoPrevSibState 884897331 4 11’44" ***

Design [ batZ_1 ] cSLUIIdDWGotoPrevSibState 884897334 3 11’47" *** wondering between

Design [ batZ_1 ] cSLUIIdDWGotoPrevSibState 884897336 2 11’49" *** sibling layouts


Design [ batZ_1 ] cSLUIIdDWGotoPrevSibState 884897343 4 11’56" *** confused about seeing

Design [ batZ_1 ] cSLUIIdDWGotoPrevSibState 884897346 3 11’59" *** all partial layout

Design [ batZ_1 ] cSLUIIdDWGotoPrevSibState 884897348 2 12’01" *** solutions but no

Design [ batZ_1 ] cSLUIIdDWGotoPrevSibState 884897350 2 12’03" *** complete ones


Design [ batZ_1 ] // window manipulation 884897358 8 12’11" ***

Design [ batZ_1 ] cSLUIIdDWGotoNextSibState 884897365 7 12’18" ***










Design [ batZ_1 ] cSLUIIdDWGotoPrevState 884897401 9 12’54"





Design Space [ batZ_1 ] cSLUI_StateOpen 884897424 10 13’17"




Design [ batZ_1 ] cSLUIIdDWGotoNextSibState 884897442 6 13’35"




Design [ batZ_1 ] cSLUIIdDWGotoNextSibState 884897446 1 13’39" // locate batZ

LayoutProblem Manager cSLUIIdLPMActivate 884897455 9 13’48" // confirm batZ

Design Space [ mecZ_1 ] // window manipulation 884897459 4 13’52"

Design Space [ mecZ_1 ] cSLUI_StateOpen 884897462 3 13’55"

Design [ mecZ_1 ] // window manipulation 884897464 2 13’57"


Design [ mecZ_1 ] cSLUIIdDWGotoNextSibState 884897472 3 14’05"

Design [ mecZ_1 ] cSLUIIdDWGotoNextSibState 884897474 2 14’07" // locate mecZ

Design [ mecZ_1 ] cSLUIIdLPGoToParentProblem 884897486 12 14’19" // confirm mecZ

Design [ dorm_wing ] // window manipulation 884897496 10 14’29"


Design Space [ dayZ_1 ] cSLUI_StateOpen 884897517 10 14’50"


Design [ dayZ_1 ] cSLUIIdDWGotoNextSibState 884897527 3 15’00"




Appendix H 186





Design [ dayZ_1 ] cSLUIIdDWGotoNextSibState 884897633 1 16’46" // locate dayZ

LayoutProblem Manager cSLUIIdLPMActivate 884897646 13 16’59" // confirm dayZ

Design Space [ admZ_1s ] // window manipulation 884897649 3 17’02"



Design [ admZ_1s ] // window manipulation 884897654 5 17’07"


Design Space [ admZ_1s ] cSLUI_StateOpen 884897666 4 17’19"



Design [ admZ_1s ] cSLUIIdDWGotoNextSibState 884897678 5 17’31"




























































Appendix H 187

Control Treatment Post-task Interview Notes: B2

• LayoutProblem Manager window and Constituent Hierarchy window present information that seemed not related to each other, yet they should be.

• The display of context information (gray areas and lines showing superlayout) in the DW helps.





Design [ admZ_1s ] cSLUIIdDWGotoNextSibState 884897913 1 21’26" // locate admZ

LayoutProblem Manager cSLUIIdLPMActivate 884897937 24 21’50" // confirm admZ


Design [ adm_wing ] // window manipulation 884897965 21 22’18" // locate adm_wing

Design [ adm_wing ] // window manipulation 884897967 2 22’20"

Design Space [ adm_wing ] // window manipulation 884897967 0 22’20"



Design [ adm_wing ] // DU selection 884897974 7 22’27"

LayoutProblem Manager cSLUIIdLPMActivate 884897978 4 22’31" // confirm adm_wing



Design Space [ dorm_wing ] cSLUI_StateOpen 884898009 7 23’02"

Design [ dorm_wing ] cSLUIIdDWGotoNextSibState 884898016 7 23’09" // locate dorm_wing

LayoutProblem Manager cSLUIIdLPMActivate 884898049 33 23’42" // confirm dorm_wing

Map and Notepad Treatment Processed Keystroke Data: B2



Navigation Tools // experiment setup 885329425

Design [ adm_wing ] // window manipulation 885329428 3 0’00" // begin


// adjusting windows and changing focuses among them

2D Tree View // window manipulation 885329540 112 1’52"

2D Tree View cGOTONODE 885329560 20 2’12"

2D Tree View cMARKNODE 885329571 11 2’23" // attempt to mark Firestation problem







2D Tree View cMARKNODE 885329660 13 3’52" // mark Firestation






2D Tree View cMARKNODE 885329723 4 4’55" // mark dayZ










Design [ admZ_1s ] cZOOMIN 885329813 14 6’25"

2D Tree View cMARKNODE 885329821 8 6’33" // mark admZ







2D Tree View cMARKNODE 885329918 63 8’10" // attempt to mark adm_wing problem



Appendix H 188



2D Tree View cMARKNODE 885329973 12 9’05" // mark adm_wing









2D Tree View cMARKNODE 885330056 11 10’28" // mark dorm_wing







2D Tree View cMARKNODE 885330101 7 11’13" // mark mecZ













2D Tree View cMARKNODE 885330160 8 12’12" // mark batZ









2D Tree View cMARKNODE 885330193 5 12’45" // mark dorZ








My Design Space // window manipulation 885330225 0 13’17" // building relations between marked nodes (begin)

My Design Space // window manipulation 885330225 0 13’17"




My Design Space // marker selection 885330258 30 13’50"


My Design Space // placing marker into view 885330271 2 14’03"














My Design Space // selection 885330466 21 17’18"





Appendix H 189

Map and Notepad Treatment Post-task Interview Notes: B2

• most difficult: understanding the layout of the display in 2D Tree View window; what represents a problem and what a solution; knowing the location of the solutions (group/branch) of a problem

• the window is too small (to see the whole space).

• in general, this interface is better (compare to the control treatment).

• easier to get lost in the previous session (control treatment).

• markers help to know the current status during the task.

• the previous session (control treatment) used many windows, display various hierarchical structures, are confusing; one window (this session) is easier.

• My Design Space window gives the image of the final layout composition (a way to see how the solutions are composed).

















My Design Space // marker selection 885330634 0 20’06" // building relations between marked nodes (end)

Design [ FIRESTATION ] cQUIT 885330749 115 22’01"



Appendix H 190






Design [ adm_wing ] cSLUIIdDWOpenPHW 885413783 66 1’06"






Design [ adm_wing ] cSLUIIdDWOpenLPW 885413815 14 1’38"

Layout Problem [ adm_wing ] cCLOSE 885413828 13 1’51"



Design [ adm_wing ] cSLUIIdDWOpenLPM 885413834 5 1’57"










Design [ adm_wing ] // DU selection (3 clicks) 885413930 0 3’33"



Design [ dayZ_1 ] // DU selection 885413952 17 3’55"

Design [ dayZ_1 ] // window manipulation 885413952 0 3’55"

Design [ dayZ_1 ] cSLUIIdDWOpenDSW 885413977 25 4’20"







Design Space [ dayZ_1 ] cSLUI_StateOpen 885414033 5 5’16" // locate dayZ




Design Space [ dayZ_1 ] // window manipulation 885414046 2 5’29"

Design [ dayZ_1 ] // window manipulation 885414048 2 5’31" // confirm dayZ
































Appendix H 191

Control Treatment Post-task Interview Notes: B8

• in general, no big problems.

• in Design Space window, wish to be able to select states and manually organize them

• in Design window, wish to see constituent list displayed on a DU so that the user knows the DU could expand to a subproblem

• wish to be able to show/hide sublayouts














Design Space [ admZ_1s ] cSLUI_StateOpen 885414191 5 7’54" // locate admZ





Design [ admZ_1s ] // window manipulation 885414200 0 8’03" // confirm admZ






Design Space [ mecZ_1 ] cSLUI_StateOpen 885414240 5 8’43" // locate mecZ

LayoutProblem Manager cSLUIIdLPMActivate 885414248 8 8’51" // confirm mecZ






Design Space [ batZ_1 ] cSLUI_StateOpen 885414286 6 9’29" // locate batZ










Design Space [ dorm_wing ] cSLUI_StateOpen 885414356 3 10’39" // locate dorm_wing


Design [ adm_wing ] // DU selection 885414379 8 11’02" // locate/confirm adm_wing









Design Space [ FIRESTATION ] cSLUI_StateOpen 885414392 2 11’15" // locate/confirm Firestation




Appendix H 192




Design [ adm_wing ] // experiment setup 885573089






My Design Space // window manipulation 885573399 270 0’00" // begin



// adjusting 2DView


My Design Space // selection (1 ckick) 885573410 4 0’11"
















































My Design Space // marker selection 885573918 17 8’39" // checking marked nodes through marker list (begin)

My Design Space // go to marked node 885573920 2 8’41"











Appendix H 193

Map and Notepad Treatment Post-task Interview Notes: B8

• it’s difficult to understanding the versions/alternative concept through the interface representation

• marker is helpful

• it’s easier to understand the structure of the information (in one window vs. many windows)

• DW display (2 layers) is not very easy to understand compared to relations created in My Design Space

• likes the free arrangement interaction in My Design Space and would like to expand functionality in it

• version/alternative should be displayed at the same level











My Design Space // go to marked node 885573996 1 9’57" // checking marked nodes through marker list (end)

My Design Space // put marker into view 885574015 19 10’16" // building relations between marked nodes (begin)







Navigation Tools // window manipulation 885574042 0 10’43"



My Design Space // put marker into view 885574050 1 10’51"





















My Design Space // selection (1 click) 885574224 65 13’45" // building relations between marked nodes (end)

My Design Space cUNDO 885574398 174 16’39"



Appendix H 194

Control Treatment Processed Keystroke Data: C3



Design [ adm_wing ] cZOOMOUT 886623562 228 0’00" // begin




Design [ adm_wing ] cSLUIIdLPGoToParentProblem 886623683 118 0’03" // review task descriptions (time excluded in total)

Design [ FIRESTATION ] cSLUIIdDWGenSibState 886623686 3 0’06"

Design [ FIRESTATION ] cSLUIIdDWGotoPrevState 886623691 5 0’11"

Design [ FIRESTATION ] cSLUIIdDWGotoNextState 886623692 1 0’12"

Design [ FIRESTATION ] cSLUIIdDWGotoNextState 886623693 1 0’13" // locate Firestation

Design [ FIRESTATION ] // DU selection 886623701 8 0’21" // confirm Firestation

Design [ FIRESTATION ] cSLUIIdLPGoToChildProblem 886623708 7 0’28"

Design [ adm_wing ] cSLUIIdDWGotoPrevState 886623743 35 1’03"

Design [ adm_wing ] cSLUIIdDWGotoNextState 886623745 2 1’05"



Design [ adm_wing ] cSLUIIdLPGoToParentProblem 886623762 14 1’22"



Design [ FIRESTATION ] cSLUIIdDWGotoPrevState 886623790 2 1’50" ***

Design [ FIRESTATION ] cSLUIIdDWGotoNextState 886623791 1 1’51" *** wondering between

Design [ FIRESTATION ] cSLUIIdDWGotoNextState 886623791 0 1’51" *** layouts while attempting

Design [ FIRESTATION ] // window manipulation 886623794 3 1’54" *** to go to another

Design [ FIRESTATION ] cSLUIIdDWGotoPrevState 886623795 1 1’55" *** problem




Design [ FIRESTATION ] cSLUIIdDWGotoNextState 886623800 1 2’00" ***

Design [ FIRESTATION ] cSLUIIdDWGotoNextState 886623800 0 2’00" ***

Design [ FIRESTATION ] cSLUIIdDWGotoNextSibState 886623806 6 2’06" ***


Design [ FIRESTATION ] cSLUIIdLPGoToNextSibProblem 886623813 5 2’13"


Design [ FIRESTATION ] cSLUIIdLPGoToPrevSibProblem 886623819 4 2’19"





Design [ FIRESTATION ] cSLUIIdLPGoToParentProblem 886623850 2 2’50"




Design [ adm_wing ] cSLUIIdLPGoToPrevSibProblem 886623877 4 3’17"

Design [ dorm_wing ] cSLUIIdLPGoToNextSibProblem 886623880 3 3’20"

Design [ adm_wing ] cSLUIIdLPGoToNextSibProblem 886623883 3 3’23"



Design [ dorm_wing ] cSLUIIdLPGoToPrevSibProblem 886623889 2 3’29" // locate adm_wing

Design [ adm_wing ] // DU selection 886623909 20 3’49" // confirm adm_wing

Design [ adm_wing ] cSLUIIdLPGoToChildProblem 886623918 9 3’58"

Design [ admZ_1s ] cSLUIIdDWGotoPrevState 886623922 4 4’02"




Design [ admZ_1s ] cSLUIIdDWGotoNextState 886623930 1 4’10"

Design [ admZ_1s ] cSLUIIdDWGotoNextState 886623931 1 4’11"

Design [ admZ_1s ] cSLUIIdDWGotoNextState 886623931 0 4’11" // locate admZ

Design [ admZ_1s ] cSLUIIdLPGoToParentProblem 886623947 16 4’27" // confirm admZ


// moving between problems and solutions (seem aimless) *** wondering between problems

Design [ admZ_1s ] cSLUIIdLPGoToPrevSibProblem 886624474 526 13’14" *** and solutions (hints given)


Design [ dayZ_1 ] cSLUIIdDWGotoPrevState 886624490 7 13’30"








Design Space [ dayZ_1 ] cSLUI_StateOpen 886624527 26 14’07" // confirm dayZ


Appendix H 195

Design [ dayZ_1 ] cSLUIIdLPGoToParentProblem 886624535 5 14’15"












Design [ dorm_wing ] cSLUIIdLPGoToChildProblem 886624600 20 15’20" // confirm dorm_wing

Design Space [ dorZ_1 ] cSLUI_StateOpen 886624607 7 15’27"


Design Space [ dorZ_1 ] cSLUI_StateOpen 886624623 10 15’43" // confirm dorZ

Design [ dorZ_1 ] cSLUIIdLPGoToPrevSibProblem 886624632 9 15’52"
































Design [ batZ_1 ] cSLUIIdDWGotoPrevSibState 886624750 4 17’50"





Design [ batZ_1 ] cSLUIIdDWGotoPrevState 886624758 1 17’58"





















Appendix H 196

Control Treatment Post-task Interview Notes: C3

• most difficult: don’t know the search strategy for layouts in Design Space (DS) window

• DS window is helpful

• would like to be able to identify a subproblem to activate through a selected DU

• the information is organized better in this session (control treatment), i.e., the information is less cluttered; whereas it is difficult to understanding the structure of the information in the previous session (map treatment)

• the iconic layout displays in the previous session is much more helpful than the numbers in DS window in this session

















Design Space [ batZ_1 ] cSLUI_StateOpen 886624838 24 19’18" // confirm batZ

Design [ batZ_1 ] cSLUIIdLPGoToParentProblem 886624846 8 19’26"

Design [ dorm_wing ] cSLUIIdLPGoToChildProblem 886624859 13 19’39"


Design [ batZ_1 ] cSLUIIdLPGoToPrevSibProblem 886624869 4 19’49"









Design [ mecZ_1 ] cSLUIIdDWGotoNextSibState 886624898 1 20’18" // locate and confirm mecZ

Design [ mecZ_1 ] cSLUIIdDWOpenLPM 886625260 362 26’20"

Map Treatment Processed Keystroke Data: C3



2D Tree View cVIEWTOGGLE 886541745 322 0’00" // begin

2D Tree View cVIEWTOGGLE 886541790 45 45" *** exploring UI

2D Tree View cVIEWTOGGLE 886541796 6 51" ***

2D Tree View cZOOMRESET 886541803 7 58" ***

2D Tree View cVIEWTOGGLE 886541807 4 1’02" ***


2D Tree View cGOTONODE 886541966 120 3’41" ***




2D Tree View cMARKNODE 886542033 16 4’48" ***

2D Tree View // window manipulation 886542041 8 4’56" ***


Design [ dayZ_1 ] // window manipulation 886542052 7 5’07" ***


Design [ dayZ_1 ] // DU selection 886542056 4 5’11" ***






Appendix H 197



Design [ dayZ_1 ] // window manipulation 886542376 250 6’21" // review task descriptions (time excluded from total)








Design [ adm_wing ] // window manipulation 886542552 7 9’17" ***





Design [ adm_wing ] cZOOMOUT 886542560 4 9’25" ***















// slips (experimenter reopen 2D Tree View window) ***

2D Tree View cZOOMOUT 886542648 25 10’53"




2D Tree View cMARKNODE 886542701 22 11’46" // locate adm_wing




2D Tree View cVIEWTOGGLE 886542782 26 13’07"








2D Tree View cMARKNODE 886542929 2 15’34" // locate dayZ



2D Tree View // cUNDO (command not available) 886543004 30 16’49"

















2D Tree View cMARKNODE 886543092 2 18’17" // locate admZ



2D Tree View cZOOMIN 886543116 4 18’41"




Appendix H 198

Map Treatment Post-task Interview Notes: C3

• difficult to search for a specific layout solution; it doesn’t seem to have specific patterns indicating how solutions were generated (the strategy sought to gain through tutorial sessions; participant did majority of the tutorial without assistant)

• seeking layouts visually (layouts are displayed as image icons) is helpful

• wish to be able to have/see different organizations of the information in 2D Tree View window








2D Tree View cMARKNODE 886543244 3 20’49" // locate dorm_wing












2D Tree View cMARKNODE 886543319 3 22’04" // locate dorZ





2D Tree View cMARKNODE 886543397 2 23’22" // locate batZ





2D Tree View cMARKNODE 886543437 3 24’02" // locate mecZ

















2D Tree View cMARKNODE 886543676 3 28’01" // locate Firestation




Appendix H 199






Design [ adm_wing ] cSLUIIdDWOpenLPW 885151246 88 1’29"

Layout Problem [ adm_wing ] cCLOSE 885151268 22 1’51"


Design [ adm_wing ] cSLUIIdDWOpenLPM 885151282 14 2’05"



// manipulating DW



Design [ adm_wing ] cSLUIIdDWGotoNextSibState 885151343 21 3’06"


Design [ adm_wing ] cSLUIIdDWGotoPrevSibState 885151346 1 3’09"



Design [ adm_wing ] cSLUIIdDWGotoPrevSibState 885151356 2 3’19"


Design [ adm_wing ] cSLUIIdDWGotoNextSibState 885151359 1 3’22"


Design [ adm_wing ] cSLUIIdDWOpenDSW 885151371 11 3’34"



// changing focuses between DW and DSW



LayoutProblem Manager // get popup menu 885151390 7 3’53"


Design Space [ adm_wing ] cSLUI_StateOpen 885151400 9 4’03"

Design Space [ adm_wing ] cSLUI_StateOpen 885151403 3 4’06" // locate adm_wing




LayoutProblem Manager cSLUIIdLPMActivate 885151424 18 4’27" // confirm adm_wing






Design Space [ adm_wing ] cCLOSE 885151437 1 4’40"







Design [ dayZ_1 ] cSLUIIdDWOpenDSW 885151643 27 8’06"



Design [ dayZ_1 ] cSLUIIdDWGotoNextSibState 885151674 1 8’37" // locate dayZ

Design [ dayZ_1 ] cSLUIIdDWGotoPrevState 885151741 67 9’44" // confirm dayZ


Design [ dayZ_1 ] // node selection 885151751 6 9’54"





Design [ dayZ_1 ] // node selection (3 clicks) 885151758 0 10’01"








Design [ adm_wing ] // node selection 885151807 3 10’50"





Appendix H 200


• concepts and presentation of different versions/alternatives of Layout Problem are confusing

• would like the sibling navigation (< and >) in Design window loop-able.





Design [ admZ_1s ] cSLUIIdDWGotoPrevSibState 885151930 6 12’53"
















LayoutProblem Manager // get popup menu 885152135 46 16’18" // confirm admZ


Design Space [ dorm_wing ] // window manipulation 885152138 2 16’21"



Design [ dorm_wing ] cSLUIIdDWGotoNextSibState 885152172 1 16’55"










Design [ dorm_wing ] cSLUIIdDWGotoNextSibState 885152191 9 17’14" // locate dorm_wing

LayoutProblem Manager // get popup menu 885152224 33 17’47" // confirm dorm_wing





LayoutProblem Manager // get popup menu 885152251 11 18’14" // confirm mecZ














LayoutProblem Manager cSLUIIdLPMActivate 885152375 18 20’18" // confirm dorZ











Design [ FIRESTATION ] cSLUIIdDWOpenPHW 885152444 61 21’27"



Appendix H 201







// manipulating windows (DW and Navigation Tools) for experiment setup


2D Tree View // window manipulation 885239476 1 01"


// browsing 2DView and changing focuses between/sizes of DW and 2DView 03"





// browsing 2DView and changing focuses between DW and 2DView 3’21"









Design [ FIRESTATION ] cSLUIIdDWGotoNextSibState 885239764 3 4’49"




2D Tree View cMARKNODE 885239840 10 6’05" // mark Firestation problem (error)








2D Tree View cMARKNODE 885240061 26 9’46" // mark adyZ



Design [ dayZ_1 ] // selection 885240099 36 10’24"



































Appendix H 202


• most difficult: understanding the layout of the design space; what represents a problem and what a solution; knowing the location of the solutions (group/branch) of a problem

• the design space is large and difficult to navigate; feeling lost sometimes because of not knowing where the active state is

• in general, the display is more helpful (comparing to control treatment)

• presenting solutions in graphical icons showing the rough configuration is better than numerical ids (in control treatment)

• need to provide ways to highlight current focus, such as gray-out non-focused branches, or to filter out undesired information although this may be similar to using multiple windows




















// log interrupted due to seg fault



Appendix H 203




Design [ adm_wing ] cSLUIIdDWOpenLPW 885490792 316 0’00" // begin

Design [ adm_wing ] // window manipulation 885490807 15 0’15" *** exploring UI



Design [ adm_wing ] // DU selection 885490834 4 0’42" ***




LayoutProblem Manager cSLUIIdLPMActivate 885490870 31 1’18" ***



Layout Problem [ adm_wing ] // window manipulation 885490880 0 1’28" ***













Design [ dorm_wing ] // DU selection 885490919 12 2’07" ***








Design [ dorm_wing ] cSLUIIdLPMActivate 885490969 21 2’57" ***

Design [ dorm_wing ] cSLUIIdDWExpandDU 885490969 0 2’57" ***




Design [ adm_wing ] cSLUIIdDWOpenDSW 885491097 83 5’05" ***



Design [ adm_wing ] cSLUIIdDWGotoPrevSibState 885491102 3 5’10" ***




Design [ adm_wing ] cSLUIIdDWGotoPrevState 885491105 1 5’13" ***

Design Space [ adm_wing ] cSLUI_StateOpen 885491132 27 5’40" ***

Design Space [ adm_wing ] cSLUI_StateOpen 885491139 7 5’47" ***

Design [ adm_wing ] cSLUIIdDDWOpenPHW 885491192 53 6’40" ***










Design [ adm_wing ] // window manipulation 885491212 0 7’00" *** end exploring UI









Design [ FIRESTATION ] cSLUIIdLPGoToParentProblem 885491422 3 10’30" ***

Design [ FIRESTATION ] // window manipulation 885491423 1 10’31" *** confused problem

Design [ FIRESTATION ] cSLUIIdDWOpenLPW 885491438 15 10’46" *** hierarchy with layout

Layout Problem [ FIRESTATION ] // window manipulation 885491438 0 10’46" *** derivation hierarchy

Layout Problem [ FIRESTATION ] cHIDE_WIN 885491443 5 10’51" ***

Appendix H 204

Design [ FIRESTATION ] // window manipulation 885491443 0 10’51" *** attempt to go to

Design [ FIRESTATION ] cSLUIIdDWOpenLPM 885491447 4 10’55" *** other layouts but go to

Design [ FIRESTATION ] // window manipulation 885491447 0 10’55" *** other problems instead


Design [ FIRESTATION ] // window manipulation 885491451 0 10’59" *** (hint given to Design Space window)







Design [ FIRESTATION ] cSLUIIdDWOpenDSW 885491477 13 11’25"


Design Space [ FIRESTATION ] cSLUI_StateOpen 885491483 6 11’31"










Design [ FIRESTATION ] // DU selection 885491498 3 11’46" // confirm firestation






// manipulating DW




Design Space [ adm_wing ] cSLUI_StateOpen 885491582 9 13’10" // locate adm_wing

LayoutProblem Manager cSLUIIdLPMActivate 885491595 13 13’23" // activate dorm_wing





Design [ dorm_wing ] cSLUIIdDWGotoPrevSibState 885491628 15 13’56" // locate/confirm dorm_wing






LayoutProblem Manager cSLUIIdLPMActivate 885491798 66 16’46" *** question about 2 adm_wing

Design [ dayZ_1 ] cSLUIIdDWGotoNextState 885491813 15 17’01"

Design [ dayZ_1 ] cSLUIIdDWGotoPrevSibState 885491818 5 17’06"

Design [ dayZ_1 ] cSLUIIdDWGotoNextState 885491823 5 17’11" // locate dayZ









Design [ admZ_1s ] // DU selection 885491892 0 18’20"

















Appendix H 205


• the display of versions/alternatives of Layout Problem is confusing

• Design Space window presents information in such as way that it provides clues about where to look for target layout

• LayoutProblem Manager window is useful for the task

• node activation and selection methods (mouse button usage) are cumbersome.

• would like to have sublayout displaying capability

• displaying the entire FU hierarchy with partial highlight instead of partial tree in Constituent Hierarchy window.

























// changing focuses between DW and DSW 19’38"




// changing focuses between DW and DSW 19’48"














Design [ dorm_wing ] // DU selection 885492109 2 21’57"









Design [ batZ_1 ] // DU selection 885492224 10 23’52"


Design Space [ dorZ_1 ] cSLUI_StateOpen 885492261 32 24’29" // locate/confirm dorZ




Appendix H 206




Design [ adm_wing ] // experiment setup 885921209 214

Navigation Tools // experiment setup 885921210 1

Navigation Tools // experiment setup 885921214 4

// changing focuses between windows and adjusting windows (experiment setup)

Design [ adm_wing ] // window manipulation 885921221 7 0’00" *** exploring UI

Design [ adm_wing ] cSLUIIdDWOpenLPW 885921236 15 0’15" ***

Layout Problem [ adm_wing ] cCLOSE 885921243 7 0’22" ***





2D Tree View cMARKNODE 885921405 18 3’04" // testing mark command


// changing focuses between DW and NAV windows 3’18" ***









// changing focuses between DW and NAV windows 6’23" *** end exploring UI










2D Tree View cMARKNODE 885921796 8 9’35" // mark adm_wing problem (error)






2D Tree View cUNMARKNODE 885921841 17 10’20" // remove adm_wing problem marker

Remove Markers // select marker 885921841 0 10’20"

Remove Markers cIdCancel 885921851 10 10’30"































Appendix H 207


• most difficult: understanding the layout of the design space; what represents a problem and what a solution; knowing the location of the solutions (group/branch) of a problem

• the design space is large and difficult to navigate

• combine the info in LayoutProblem Manager window and Design Space window (windows in control treatment) is helpful

• one window is better than multiple windows

• being able to change views (simple and enhanced); enhanced view helps to limit the search

• direct go to command is helpful

• too much info in one window; info of different types are all displayed in the same tree can be confusing

• the display of version/alternative problems is misleading

• would like to be able to hide part of the tree or view only part of the tree

• alternative problems should be shown in parallel (at the same level)

• would like the system to display relationship between sub-solutions and super-solutions (i.e. the super/sub layout dimension)


2D Tree View cGOTONODE 885922389 114 19’28" *** mention about confusion of subproblems and solutions

















Appendix H 208

Control Treatment Processed Keystroke Data: D1



Design [ adm_wing ] // window manipulating 885495252 196 0’00" // begin

Design [ adm_wing ] cZOOMOUT 885495274 22 0’22"

Design [ adm_wing ] cZOOMOUT 885495275 1 0’23"

Design [ adm_wing ] cSLUIIdDWOpenDSW 885495283 8 0’31"

Design Space [ adm_wing ] cCLOSE 885495290 7 0’38"

Design [ adm_wing ] // window manipulating 885495290 0 0’38" ***

// manipulating DW *** exploring the UI

Design [ adm_wing ] // window manipulating 885495322 32 1’10" *** and wondering between

Design [ adm_wing ] cZOOMIN 885495324 2 1’12" *** layouts

Design [ adm_wing ] cZOOMIN 885495325 1 1’13" *** (hints given to

Design [ adm_wing ] cZOOMIN 885495325 0 1’13" *** Design Space window)


// manipulating DW ***


Design [ adm_wing ] CSLUIIdDWOpenLPW 885495386 27 2’14" ***

Layout Problem [ adm_wing ] cCLOSE 885495391 5 2’19" ***







Design [ admZ_1s ] // window manipulating 885495421 5 2’49" ***




Design [ FIRESTATION ] // window manipulating 885495426 1 2’54"

// manipulating DW




Design Space [ FIRESTATION ] // window manipulating 885495456 2 3’24"



Design [ FIRESTATION ] cZOOMOUT 885495466 2 3’34"

Design [ FIRESTATION ] cZOOMOUT 885495467 1 3’35"

Design [ FIRESTATION ] cSLUIIdDWGotoNextState 885495477 10 3’45"

Design [ FIRESTATION ] cSLUIIdDWGotoNextState 885495482 5 3’50" // locate Firestation

Design [ FIRESTATION ] // expanding DU 885495518 36 4’26" // confirm Firestation

Design [ FIRESTATION ] // expanding DU 885495534 16 4’42"


Design [ adm_wing ] // window manipulating 885495563 26 5’11"

// manipulating DW


Design [ adm_wing ] cSLUIIdDWGotoNextSibState 885495584 20 5’32" ***

Design [ adm_wing ] // window manipulating 885495586 2 5’34" *** wondering between

Design [ adm_wing ] cSLUIIdDWGotoNextState 885495589 3 5’37" *** layouts

Design [ adm_wing ] // window manipulating 885495590 1 5’38" *** (hints given to go

Design [ adm_wing ] cSLUIIdDWGotoPrevState 885495593 3 5’41" *** to another problem)

Design [ adm_wing ] cSLUIIdDWGotoNextState 885495595 2 5’43" ***

Design Space [ adm_wing ] // window manipulating 885495599 4 5’47" ***

// changing focuses between DW and DSW ***



LayoutProblem Manager cSLUIIdLPMActivate 885495665 63 6’53" // locate adm_wing

Design [ adm_wing ] cZOOMIN 885495684 19 7’12" // confirm adm_wing


// manipulating DW



Design [ dayZ_1 ] cSLUIIdDWGotoNextState 885495732 35 8’00"

Design [ dayZ_1 ] cSLUIIdDWGotoNextSibState 885495737 5 8’05" *** (hints given to the

Design [ dayZ_1 ] // window manipulating 885495739 2 8’07" *** use of Design Space

Design Space [ dayZ_1 ] cSLUI_StateOpen 885495760 21 8’28" *** window)





Design Space [ admZ_1s ] // window manipulating 885495788 4 8’56"

// changing focuses between DSW and DW

Design [ admZ_1s ] // window manipulating 885495799 11 9’07"

Appendix H 209


Design Space [ admZ_1s ] cSLUI_StateOpen 885495823 17 9’31" *** (more hints given

Design Space [ admZ_1s ] cSLUI_StateOpen 885495828 5 9’36" *** to Design Space

Design [ admZ_1s ] cSLUIIdDWGotoNextState 885495835 7 9’43" *** window and navigation

Design [ admZ_1s ] // window manipulating 885495837 2 9’45" *** buttons in Design

Design [ admZ_1s ] // window manipulating 885495842 5 9’50" *** window)























Design Space [ admZ_1s ] // changing to left-right display 885495939 15 11’27"































// manipulating DW



Design [ dorm_wing ] // window manipulating 885496054 2 13’22"

// manipulating DW

Design [ dorm_wing ] // window manipulating 885496060 6 13’28"










Appendix H 210

Control Treatment Post-task Interview Notes: D1

• most difficult: understanding problem decomposition hierarchy (PH) in LayoutProblem Manager (LPM) window and distinguishing it from functional unit hierarchy (FUH) in Constituent Hierarchy window (CHW) and layout derivation hierarchy in Design Space window (DSW)

• direct go to navigations in DSW is more helpful than stepping navigations in Design window (DW)

• CHW, DSW and LPM are all necessary (using them at the same time) for the task; CHW is less needed



Design [ mecZ_1 ] // DU selection 885496130 3 14’38"


Design [ batZ_1 ] // window manipulating 885496135 2 14’43"



Design [ batZ_1 ] cZOOMOUT 885496144 2 14’52"







Design [ batZ_1 ] cZOOMIN 885496206 7 15’54"

Design [ batZ_1 ] cZOOMIN 885496207 1 15’55"













Design [ dorZ_1 ] // window manipulating 885496276 34 17’04" // confirm dorZ

// manipulating DW

View Treatment Processed Keystroke Data: D1



Multilayer View // window manipulation 886782797 539 0’00" // begin

Multilayer View // window manipulation 886782797 0 0’00"





Navigation Tools // window manipulation 886782814 16 0’17" *** (reminded hints in task)

// changing focuses between Navigation Tools and Multilayer View


Navigation Tools cHIDE_WIN 886782818 3 0’21"



// resizing Multilayer View window


Multilayer View // go to super/subproblem 886782860 25 1’03" // activate Firestation



Multilayer View // go to super/subproblem 886782866 6 1’09" *** exploring UI

Multilayer View // go to super/subproblem 886782867 1 1’10" // activate adm_wing

Multilayer View // window manipulation 886782867 0 1’10" ***




Multilayer View // go to super/subproblem 886782871 1 1’14" ***



Appendix H 211
















Multilayer View // go to super/subproblem 886782897 2 1’40" // activate dayZ





Multilayer View // go to super/subproblem (3 clicks) 886782899 0 1’42" ***




Multilayer View // go to super/subproblem 886782902 1 1’45" // activate admZ
















Multilayer View cDSNavLayerControlStart+2 886782921 6 2’04" ***










Multilayer View cDSNavParentSolution 886782953 7 2’36" ***

Multilayer View cDSNavChildSolution 886782961 8 2’44" ***




Multilayer View cZOOMRESET 886782975 5 2’58" ***














Multilayer View cDSNavProblemControl 886783012 3 3’35" ***





Appendix H 212

Multilayer View // go to super/subproblem 886783058 12 4’21"




Multilayer View cDSNavChildSolution 886783067 7 4’30" // locate Firestation

Multilayer View // go to super/subproblem 886783075 8 4’38" // confirm Firestation


Multilayer View // window manipulation 886783076 0 4’39" // locate adm_wing

Multilayer View // go to super/subproblem 886783081 5 4’44" // confirm adm_wing




Multilayer View cDSNavChildSolution 886783089 6 4’52"


Multilayer View cDSNavNextSolution 886783103 5 5’06"

Multilayer View cDSNavNextSolution 886783104 1 5’07" // locate dayZ

Multilayer View // go to super/subproblem 886783109 5 5’12" // activate adm_wing/confirm dayZ




Multilayer View // go to super/subproblem 886783119 0 5’22" // activate admZ



Multilayer View cDSNavProblemControl 886783128 8 5’31"













Multilayer View cDSNavPrevSolution 886783167 2 6’10"






Multilayer View cDSNavParentSolution 886783177 2 6’20"
























Multilayer View cDSNavChildSolution 886783250 14 7’33" *** (hints given about

Multilayer View cDSNavParentSolution 886783266 16 7’49" *** layout derivation

Multilayer View cDSNavParentSolution 886783285 19 8’08" *** hierarchy structure)






Appendix H 213









Multilayer View cDSNavNextSolution 886783312 4 8’35" // locate admZ

Multilayer View // go to super/subproblem 886783320 8 8’43" // activate adm_wing/confirm admZ





Multilayer View // go to super/subproblem 886783323 2 8’46" // activate dorm_wing







Multilayer View cDSNavNextSolution 886783360 4 9’23" // locate dorm_wing

Multilayer View // go to super/subproblem 886783369 9 9’32" // activate mecZ/confirm dorm_wing









Multilayer View cDSNavNextSolution 886783392 1 9’55" // locate mecZ

Multilayer View // go to super/subproblem 886783398 6 10’01" // activate dorm_wing/confirm mecZ



Multilayer View // go to super/subproblem 886783402 1 10’05" // activate batZ





















Multilayer View cDSNavNextSolution 886783466 2 11’09" // locate batZ

Multilayer View // go to super/subproblem 886783471 5 11’14" // activate dorm_wing/confirm batZ


Multilayer View // go to super/subproblem 886783473 2 11’16" // activate dorZ






Multilayer View // go to super/subproblem 886783484 1 11’27" // activate dorm_wing


Multilayer View // go to super/subproblem 886783486 2 11’29" // activate dorZ







Appendix H 214

View Treatment Post-task Interview Notes: D1

• moving focuses between parent/child problems takes some time to understand

• DU name display causes confusion; however, the problem is alleviated because layers can be turned on and off

• this is more user-friendly; everything in one view so that one can search visually (mentally) instead of going through nodes in a tree display

• this interface is "simple" and unlike the previous one (control treatment), which is more complicated: it was like you were doing something important

• giving names to layers, instead of just "layer 1" and "layer 2", may be helpful



Multilayer View cDSNavChildSolution 886783509 4 11’52" // locate/confirm dorZ




Appendix H 215





Design [ adm_wing ] cSLUIIdDWOpenPHW 885400419 34 0’34"








Design [ adm_wing ] cSLUIIdDWGotoPrevState 885400442 1 0’57" *** confused about what to

Design [ adm_wing ] // window manipulation 885400444 2 0’59" "*** go to, a problem or a"

Design [ adm_wing ] cSLUIIdDWGotoPrevSibState 885400458 14 1’13" *** layout


Design [ adm_wing ] cSLUIIdDWGotoNextSibState 885400460 1 1’15" *** do not know the

Design [ adm_wing ] // window manipulation 885400462 2 1’17" *** problem decomposition

Design [ adm_wing ] cSLUIIdDWOpenPHW 885400469 7 1’24" *** hierarchy or confused

Design [ adm_wing ] // window manipulation 885400469 0 1’24" *** with layout derivation

Design [ adm_wing ] // window manipulation 885400471 2 1’26" *** hierarchy

Design [ adm_wing ] // DU selection 885400478 7 1’33" ***
















Design [ FIRESTATION ] cSLUIIdDWGotoPrevSibState 885400545 8 2’40"














Design [ adm_wing ] // expanding selected DU 885400628 1 4’03"



// changing focuses between DW and DSW ***

Design [ FIRESTATION ] // window manipulation 885400732 95 5’47" *** attempt to activate a

Design [ FIRESTATION ] cSLUIIdLPGoToChildProblem 885400793 61 6’48" *** subproblem through DU

Design [ adm_wing ] cSLUIIdDWGotoPrevSibState 885400796 3 6’51" "*** however, SL doesn't"

Design [ adm_wing ] // window manipulation 885400798 2 6’53" *** support that (hint given)

Design [ adm_wing ] cSLUIIdDWGotoNextSibState 885400799 1 6’54" *** continue wondering


Design [ adm_wing ] cSLUIIdLPGoToNextSibProblem 885400808 8 7’03"



Design [ dorm_wing ] cSLUIIdLPGoToPrevSibProblem 885400839 27 7’34" // locate adm_wing

Design [ adm_wing ] // DU selection 885400853 14 7’48" // confirm adm_wing

Design [ adm_wing ] // DU selection (3 clicks) 885400854 1 7’49"








Appendix H 216



Design [ admZ_1s ] cSLUIIdLPGoToNextSibProblem 885400895 16 8’30"


Design [ admZ_1s ] cSLUIIdLPGoToPrevSibProblem 885400898 1 8’33"







Design [ dayZ_1 ] cSLUIIdLPGoToPrevSibProblem 885400916 3 8’51"










Design [ dayZ_1 ] // window manipulation 885400978 26 9’53" // confirm dayZ
























Design Space [ admZ_1s ] cSLUI_StateOpen 885401106 7 12’01" *** do not seem to know

Design [ admZ_1s ] // window manipulation 885401153 47 12’48" *** how a new state is

Design [ admZ_1s ] cSLUIIdDWGotoNextSibState 885401153 0 12’48" "*** derived, ie, how the"

Design [ admZ_1s ] cSLUIIdDWGotoNextSibState 885401156 3 12’51" *** layout derivational

Design [ admZ_1s ] cSLUIIdDWGotoNextSibState 885401161 5 12’56" *** hierarchy grow

























Appendix H 217


























Design [ admZ_1s ] // window manipulation 885401306 7 15’21" // confirm admZ



Design [ admZ_1s ] cSLUIIdLPGoToParentProblem 885401350 8 16’05"




Design [ adm_wing ] cSLUIIdLPGoToNextSibProblem 885401399 9 16’54" *** still have trouble

Design [ adm_wing ] // window manipulation 885401401 2 16’56" *** to move around the

Design [ adm_wing ] cSLUIIdLPGoToParentProblem 885401405 4 17’00" *** problem decomposition

Design [ FIRESTATION ] cSLUIIdLPGoToNextSibProblem 885401414 9 17’09" *** hierarchy


Design [ FIRESTATION ] cSLUIIdLPGoToPrevSibProblem 885401419 2 17’14" ***













Design [ dorm_wing ] // window manipulation 885401469 1 18’04" // confirm dorm_wing

Design [ dorm_wing ] cSLUIIdDWGotoNextSibState 885401477 8 18’12" ***

Design [ dorm_wing ] cSLUIIdLPGoToChildProblem 885401485 8 18’20" *** still confused about

Design [ dorZ_1 ] cSLUIIdLPGoToChildProblem 885401538 53 19’13" *** problem hierarchy and

Design [ dorZ_1 ] // window manipulation 885401540 2 19’15" *** layout derivation

Design [ dorZ_1 ] cSLUIIdLPGoToNextSibProblem 885401549 9 19’24" *** hierarchy

Design [ dorZ_1 ] // window manipulation 885401552 3 19’27" ***


















Appendix H 218

Control Treatment Post-task Interview Notes: D7

• most difficult: finding the relationships between problems (never used LPM)


















Design [ batZ_1 ] cSLUIIdDWGotoNextState 885401686 2 21’41" // locate/confirm batZ

Design [ batZ_1 ] cSLUIIdLPGoToParentProblem 885401704 18 21’59" ***

Design [ dorm_wing ] cSLUIIdLPGoToChildProblem 885401721 17 22’16" *** wondering between

Design [ dorZ_1 ] cSLUIIdLPGoToPrevSibProblem 885401729 8 22’24" *** problems

Design [ batZ_1 ] cSLUIIdLPGoToNextSibProblem 885401737 8 22’32" ***

Design [ dorZ_1 ] cSLUIIdLPGoToNextSibProblem 885401739 2 22’34"





Design [ dorZ_1 ] cSLUIIdDWGotoNextState 885401762 11 22’57"







Design [ dorZ_1 ] cSLUIIdLPGoToParentProblem 885401789 2 23’24"


Design Space [ dorm_wing ] cSLUI_StateOpen 885401797 1 23’32" ***

Design [ dorm_wing ] // window manipulation 885401798 1 23’33" *** wondering between

Design Space [ dorm_wing ] // window manipulation 885401808 10 23’43" *** problems and layouts


Design Space [ dorm_wing ] // window manipulation 885401812 2 23’47" *** still confused about

Design [ dorm_wing ] // window manipulation 885401813 1 23’48" *** problem hierarchy

Design [ dorm_wing ] cSLUIIdDWGotoPrevSibState 885401814 1 23’49" *** and layout derivation

Design [ dorm_wing ] cSLUIIdLPGoToChildProblem 885401822 8 23’57" *** hierarchy

Design [ dorZ_1 ] cSLUIIdLPGoToParentProblem 885401832 10 24’07" ***









Design [ dorm_wing ] cSLUIIdLPGoToChildProblem 885401861 6 24’36" ***

Design [ dorZ_1 ] cSLUIIdLPGoToNextSibProblem 885401866 5 24’41" ***

Design [ dorZ_1 ] // window manipulation 885401867 1 24’42" ***

Design [ dorZ_1 ] cSLUIIdLPGoToPrevSibProblem 885401868 1 24’43" ***

Design Space [ batZ_1 ] // window manipulation 885401873 5 24’48" ***


Design Space [ batZ_1 ] // window manipulation 885401874 1 24’49" ***


Design [ batZ_1 ] cSLUIIdLPGoToPrevSibProblem 885401879 2 24’54"





Design Space [ mecZ_1 ] // window manipulation 885401908 16 25’23" // confirm mecZ




Appendix H 219







Multilayer View // window manipulation 885483548 1 0’00" // begin









Navigation Tools // window manipulation 885483558 0 0’10"

Design [ adm_wing ] cHIDE_WIN 885483558 0 0’10"




Multilayer View // go to super/subproblem 885483588 28 0’40" // go to Firestation







Multilayer View cDSNavChildSolution 885483623 7 1’15" // locate Firestation

Multilayer View cDSNavLayerControlStart+2 885483655 32 1’47"










Multilayer View cDSNavNextSolution 885483714 2 2’46" // locate adm_wing

Multilayer View // go to subproblem 885483718 4 2’50" // go to admZ problem






Multilayer View cDSNavNextSolution 885483743 6 3’15" *** have difficulty navigating

Multilayer View cDSNavNextSolution 885483747 4 3’19" *** layout derivation

Multilayer View cDSNavNextSolution 885483752 5 3’24" *** hierarchy (design space)

Multilayer View cDSNavNextSolution 885483754 2 3’26" ***

Multilayer View cDSNavNextSolution 885483756 2 3’28" *** (hint given)

Multilayer View cDSNavNextSolution 885483758 2 3’30" *** ...

Multilayer View cDSNavPrevSolution 885483761 3 3’33" ***























Appendix H 220






























Multilayer View cDSNavNextSolution 885483966 1 6’58" // locate admZ

Multilayer View cDSNavProblemControl 885483990 24 7’22" // go to dayZ problem

Multilayer View // selection 885483993 3 7’25"








Multilayer View cDSNavNextSolution 885484029 3 8’01" // locate dayZ

Multilayer View // go to superproblem 885484047 18 8’19" // go to adm_wing problem


Multilayer View cDSNavProblemControl 885484052 4 8’24" // go to dorm_wing problem







Multilayer View cDSNavNextSolution 885484096 4 9’08" // locate dorm_wing


Multilayer View // go to subproblem 885484115 10 9’27" // go to dorZ problem





Multilayer View cDSNavChildSolution 885484125 4 9’37" // locate dorZ

Multilayer View cDSNavProblemControl 885484138 13 9’50" // go to batZ problem

















Appendix H 221

View Treatment Post-task Interview Notes: D7

• most difficult: traversing the solution space; can’t see it.

• the multilayer display is similar to how architects work; the display shows the result; more like working on a drawing board

• display the solution space; it would be helpful











Multilayer View cDSNavNextSolution 885484213 1 11’05" // locate batZ

Multilayer View cDSNavProblemControl 885484224 11 11’16" // go to mecZ problem







Multilayer View cDSNavNextSolution 885484255 2 11’47" // locate mecZ





Multilayer View cCLOSE 885485807 895 37’39"

Design [ mecZ_1 ] cQUIT 885485813 6 37’45"



Appendix H 222

Appendix I 223

I. GOMS Analysis of SEED-Layout Navigation Utilities

The tasks to be analyzed in this sections are the performance of locating and revisitingtarget layouts using the navigation utilities in a SEED-Layout software prototype. Theanalysis is based on the original formulation of GOMS (Card, Moran and Newell, 1983),which is also referred to as CMN-GOMS in recent literature. The analyst-definedoperators are listed in Table I-1. Estimated times are given in seconds. Time for the mentaland physical operators are taken from Card, Moran and Newell (1983). The systemresponse times are considered insignificant in the analysis.

I.1 Control Treatment

I.1.1 First Visit Task

This analysis is based on a scenario illustrated in Figure I-1. The total time predicted toaccomplish the task of locating the target layout of batZ_1 is shown in Table I-2. Note inthis scenario, the view is adjusted 3 times (ADJUST-VIEW goal) to allow for a fullexamination of the solution space. In addition, the prediction assumes the most efficientsteps are used to review the 6 candidate target layouts (nodes 28 through 33 in Figure I-1)1, i.e. first use the direct go to command (1 time) then visit the sibling layouts throughthe step command (5 times).

Table I-1: Analyst-defined operators

Operator Time (second) Description

COMPARE-LAYOUT 1.35 Determine if the active layout matches the target layout

VERIFY 1.35 Verify success of operation

MOVE-POINTER/MOUSE 1.10 Move mouse pointer to target location on screen

CLICK-BUTTON 0.20 Press and release mouse button

PRESS-BUTTON 0.10 Hold down mouse button

RELEASE-BUTTON 0.10 Release mouse button

RECALL 1.35 Retrieve from long-term-memory

1. The successful determination of candidate target layouts is based on one’s understanding of thesolution derivation mechanism in SEED-Layout.

Appendix I 224

Table I-2: GOMS analysis for the first visit task in Control Treatment

GOAL: GO-TO-TARGET-LAYOUT(BATZ_1). [select GOAL: USE-STEP/GOTO-METHODS. . GOAL: GO-TO-TARGET-PROBLEM(BATZ_1)2 6.65. . GOAL: EXAMINE-SOLUTION-SPACE. . . GOAL: ADJUST-VIEW3 [email protected] 11.25. . GOAL: GO-TO-A-LAYOUT. . . [select GOAL: USE-GOTO-METHOD2 6.65. . . GOAL: USE-STEP-METHOD4] [email protected] 13.25. . . COMPARE-LAYOUT [email protected] 8.10. GOAL: USE-MARKER-METHODS]. VERIFY-TARGET-LAYOUT 1.35

TOTAL TIME PREDICTED (SECOND) 47.25

The keystroke-level steps for the GO-TO-TARGET-PROBLEM and USE-GOTO-METHODS goalsare identical and can be modeled as a general GO-TO-A-NODE goal.

Table I-3: GOMS analysis for the general GO-TO-A-NODE sub-task

GOAL: GO-TO-A-NODE. GOAL: SELECT-NODE. . MOVE-POINTER-TO-NODE 1.10. . CLICK-LEFT-MOUSE-BUTTON 0.20. . VERIFY-SELECTION 1.35. GOAL: ISSUE-GO-TO-COMMAND. . PRESS-RIGHT-MOUSE-BUTTON 0.10. . MOVE-MOUSE-TO-GOTO-OPTION 1.10. . VERIFY-HIGHLIGHT 1.35. . RELEASE-MOUSE-BUTTON 0.10. VERIFY-DISPLAY 1.35

TIME PREDICTED (SECOND) 6.65

The expansion of ADJUST-VIEW goal and the time estimate to accomplish this goal areshown in Table I-4.

Table I-4: GOMS analysis for the general ADJUST-VIEW sub-task

GOAL: ADJUST-VIEW. MOVE-POINTER-TO-SCROLLER-HANDLE 1.10. PRESS-LEFT-MOUSE-BUTTON 0.10. MOVE-MOUSE-TO-NEW-POSITION 1.10. VERIFY-DISPLAY 1.35. RELEASE-MOUSE-BUTTON 0.10


Table I-5 shows the predicted execution time and the expansion of USE-STEP-METHOD goal.

2. For the expansion and time estimate of this goal, see Table I-3.3. For the expansion and time estimate of this goal, see Table I-4.4. For the expansion and time estimate of this goal, see Table I-5.

Appendix I 225

Table I-5: GOMS analysis for the USE-STEP-METHOD sub-task

GOAL: USE-STEP-METHOD. MOVE-POINTER-TO-STEP-COMMAND 1.10. CLICK-MOUSE-BUTTON 0.20. VERIFY-DISPLAY 1.35


I.1.2 Revisit Task

This analysis is based on a scenario illustrated in Figure I-2. The total time predicted toaccomplish the task of revisiting the target layout of batZ_1 without marker aids is shownin Table I-6. Note in this scenario, the prediction assumes that the user correctly recall thelocation of the target layout (which has been visited once) and one adjustment of the viewis needed to view the location on screen.

Table I-6: GOMS analysis for the revisit task in Control Treatment

GOAL: GO-TO-TARGET-LAYOUT(BATZ_1). [select GOAL: USE-STEP/GOTO-METHODS. . GOAL: GO-TO-TARGET-PROBLEM(BATZ_1)5 6.65. . RECALL-TARGET-LAYOUT-LOCATION 1.35. . GOAL: ADJUST-VIEW6 [email protected] 3.75. . GOAL: GO-TO-A-LAYOUT. . . [select GOAL: USE-GOTO-METHOD5 [email protected] 6.65. . . GOAL: USE-STEP-METHOD]. . . COMPARE-LAYOUT 1.35. GOAL: USE-MARKER-METHODS]. VERIFY-TARGET-LAYOUT 1.35


5. For the expansion and time estimate of this goal, see Table I-3.6. For the expansion and time estimate of this goal, see Table I-4.

Appendix I 226

Figure I-1: Interaction sequence for locating the target layout of batZ_1 in Control Treatment

a. go to batZ_1 sub-problem

b. examine solution space

c. go to layout #28 andstep through sibling layouts

d. confirm target layout

1

2

3

4

5

Appendix I 227

Figure I-2: Interaction sequence for revisiting the target layout of batZ_1 in Control Treatment

a. go to batZ_1 sub-problem

b. adjust solution space viewand go to target solution

1

2

3

4

Appendix I 228

I.2 Map-and-Notepad Treatment


This analysis is based on a scenario illustrated in Figure I-3. The total time predicted toaccomplish the task of locating the target layout of batZ_1 is shown in Table I-7. Note inthis scenario, the view is adjusted 3 times (ADJUST-VIEW goal) to allow for a fullexamination of the solution space of the batZ_1 sub-problem. In addition, the predictionassumes that the user finds 6 candidate target layouts (nodes 28 through 33 in Figure I-3)based on the understanding of the solution-derivation mechanism in SEED-Layout.

Table I-7: GOMS analysis for the first visit task in Map-and-Notepad Treatment

GOAL: GO-TO-TARGET-LAYOUT(BATZ_1). [select GOAL: USE-STEP/GOTO-METHODS. . GOAL: EXAMINE-SOLUTION-SPACE. . . GOAL: ADJUST-VIEW7 [email protected] 3.75. . GOAL: GO-TO-A-LAYOUT. . . GOAL: USE-GOTO-METHOD8 [email protected] 39.90. . . COMPARE-LAYOUT [email protected] 8.10. GOAL: USE-MARKER-METHODS]. VERIFY-TARGET-LAYOUT 1.35


In order to take advantage of the marker support to make the task of revisiting the layouteasier, the user should mark the layout after it is located. Table I-8 shows the GOMS modelfor marking a node (either a layout or a problem) and the time estimate.

Table I-8: GOMS analysis for the task of marking a node

GOAL: MARK-NODE. GOAL: SELECT-NODE. . MOVE-POINTER-TO-NODE 1.10. . CLICK-LEFT-MOUSE-BUTTON 0.20. . VERIFY-SELECTION 1.35. GOAL: ISSUE-MARK-COMMAND. . PRESS-RIGHT-MOUSE-BUTTON 0.10. . MOVE-MOUSE-TO-MARK 1.10. . VERIFY-HIGHLIGHT 1.35. . RELEASE-MOUSE-BUTTON 0.10. GOAL: INPUT-MARKER. . GOAL: SELECT-ICON. . GOAL: INPUT-LABEL. . GOAL: CONFIRM-INPUT. . . MOVE-POINTER-TO-COMMIT 1.10. . . CLICK-LEFT-MOUSE-BUTTON 0.20. VERIFY-MARKED-NODE 1.35



Appendix I 229

I.2.2 Revisit Task

This analysis is based on a scenario illustrated in Figure I-4. The total time predicted toaccomplish the task of revisiting the target layout of batZ_1 with the aid of a marker list isshown in Table I-9.

Table I-9: GOMS analysis for the revisit task in Map-and-Notepad Treatment

GOAL: GO-TO-TARGET-LAYOUT(BATZ_1). [select GOAL: USE-STEP/GOTO-METHODS. GOAL: USE-MARKER-METHODS. . [select GOAL: GO-TO-MARKED-LAYOUT. . GOAL: GO-TO-MARKER8] 6.65. . COMPARE-LAYOUT] 1.35. VERIFY-TARGET-LAYOUT 1.35


Appendix I 230

Figure I-3: Interaction sequence for locating the target layout of batZ_1 in Map-and-NotepadTreatment

a. examine solution space of batZ_1

b. go to layout #28

c. verify layout #28 andgo to each sibling layouts

d. confirm target layout

1

2

3

4

Appendix I 231

Figure I-4: Interaction sequence for revisiting the target layout of batZ_1 in Map-and-NotepadTreatment

a. go to marked solution of batZ_1

b. confirm target layout

1

Appendix I 232

I.3 Map Treatment


This analysis is based on a scenario illustrated in Figure I-5. The total time predicted toaccomplish the task of locating the target layout of batZ_1 is shown in Table I-10. Note inthis scenario, the view is adjusted 4 times (ADJUST-VIEW goal) to allow for a fullexamination of the solution space of the batZ_1 sub-problem. In addition, the predictionassumes that the user finds 3 candidate target layouts based on the similarity of layoutconfigurations shown in Figure I-5b.

Table I-10: GOMS analysis for the first visit task in Map Treatment

GOAL: GO-TO-TARGET-LAYOUT(BATZ_1). [select GOAL: USE-STEP/GOTO-METHODS. . GOAL: EXAMINE-SOLUTION-SPACE. . . GOAL: ADJUST-VIEW9 [email protected] 15.00. . GOAL: GO-TO-A-LAYOUT. . . GOAL: USE-GOTO-METHOD10 [email protected] 19.95. . . COMPARE-LAYOUT [email protected] 4.05. GOAL: USE-MARKER-METHODS]. VERIFY-TARGET-LAYOUT 1.35


In order to take advantage of the marker support to make the task of revisiting the layouteasier, the user should mark the layout after it is located. The time estimate for marking anode is shown in Table I-8.

I.3.2 Revisit Task

This analysis is based on a scenario illustrated in Figure I-6. The total time predicted toaccomplish the task of revisiting the target layout of batZ_1 with the aid of markers isshown in Table I-11. Note in this scenario, the prediction assumes that the user change thedisplay mode from the enhanced display to the simple 2D tree display before beginningthe revisit task, and that the user is able to see the marked layout of batZ_1 withouthaving to adjust the view. The task of changing the display view is modeled in Table I-12.

Table I-11: GOMS analysis for the revisit task in Map Treatment

GOAL: GO-TO-TARGET-LAYOUT(BATZ_1). [select GOAL: USE-STEP/GOTO-METHODS. GOAL: USE-MARKER-METHODS. . [select GOAL: GO-TO-MARKED-LAYOUT. . . GOAL: ADJUST-VIEW 0.00. . . GOAL: GO-TO-MARKED-NODE10 6.65. . GOAL: GO-TO-MARKER]. . COMPARE-LAYOUT] 1.35. VERIFY-TARGET-LAYOUT 1.35



Appendix I 233

Table I-12: GOMS analysis for task of changing display in Map Treatment

GOAL: CHANGE-TO-SIMPLE-DISPLAY. GOAL: USE-MENU-COMMAND. . MOVE-POINTER-TO-VIEW-MENU 1.10. . PRESS-LEFT-MOUSE-BUTTON 0.10. . MOVE-POINTER-TO-SIMPLIFY-OPTION 1.10. . VERIFY-HIGHLIGHT 1.35. . RELEASE-MOUSE-BUTTON 0.10. VERIFY-DISPLAY 1.35


Appendix I 234

Figure I-5: Interaction sequence for locating the target layout of batZ_1 in Map Treatment (usingenhanced view)

a. locate batZ_1 sup-problem

b. go to layouts with desired

c. confirm target layout

and examine solution space

configuration and verify

1

2

3

4

5

6

Appendix I 235

Figure I-6: Interaction sequence for locating the target layout of batZ_1 in Map Treatment (usingsimple view)

a. go to marked solution of batZ_1

b. confirm target layout

1

Appendix I 236

Appendix J 237

J. Task Descriptions for Marker Assessment User Testing

Appendix J 238

Appendix J 239

Appendix J 240

a. design space navigation framework object...

Documents