Design for IDSSWhat is design?Slide 3Classifying Design TaskRoutine DesignInnovative DesignComplex DesignComplex and Innovative Tasks (1)Complex and Innovative Tasks (2)Case Based DesignSlide 11Slide 12Example of Complex Case UsageSlide 14Slide 15Knowledge RepresentationVocabularyCase BaseCase Base (cont)Similarity MeasureComputational ApproachRepresentational ApproachCBR for Innovative and Creative DesignSolution Transformation and Case AdaptationSlide 25Fish and ShrinkSlide 27Fish and Shrink (2)Structural SimilaritySlide 30Slide 31Slide 32Slide 33Case Study – EADOCSEADOCS (2)EADOCS (3)EADOCS (4)EADOCS (5)EADOCS (6)Final RemarksReferencesDesign for IDSSLiam PageCSE 43523 October 2006What is design?Construction of an artifact from single parts that may be either known and given or newly created for this particular effect (Börner 1998)Design systems assist a user in producing better designs in shorter amount of timeWhat is design?How does design help with:decreasing design times?increasing design quality?improving design predictability?Classifying Design TaskThree classifications:Routine DesignInnovative DesignCreative DesignRoutine DesignState space is well defined using potential designsNew designs can be derived entirely from existing designsOutcomes known before handFinal design agrees with configurable constraintsUsed mostly in KB-systemsInnovative DesignWell defined state space of potential designs, non-routine design desiredValues for variables may changeSolution is similar to old designs, but also appears to be new due to variablesComplex DesignNon-routine designNew variablesExtends/moves state space of potential designsComplex and Innovative Tasks (1)Often unsure what the final design constraints will beTypically ordered in accordance to preference criteriaAbstract -> ConcreteReduction of design spaceComplex and Innovative Tasks (2)Ideal systemAssists user, not automatedUser interface logically constructed for type of design taskLearns from past solutions and user’s response to solutions (accept, correct, refuse)Case Based DesignThemes of case based designed systems (Maher and Gomez de Silva Garza 1997)representation and management of complex casescase augmentation using generalized design knowledgeformalization of informal knowledgeCase Based DesignWhat can be a complex case?Sample of larger data modelData represented structurally (graphs)Non-static variablesFlexible – may have multiple interpretationsAdaptable to solve new problemsCase Based DesignImplications of complex casesMust be able to reinterpret and reformulate new problemsOverlapping of problem and past cases must be identifiedParts must be chosen for transfer and combinationSimilarity functions must be flexibleJoint consideration of case aspects is possibleExample of Complex Case UsageCase: DeluxeBathroom1• Dimensions = (20’-40’)x (20’-40’)• Doors = 1 – 2• Outlets = 4 – 6• Hot tub = yes• …Case: DeluxeBathroom2• Dimensions = ( 30’ 50’)x (30’x50’)• Doors = 2 – 3• Outlets – 6 – 10• Deluxe Standing Shower = yes• …Transformed Solution• Dimensions = 30’ x 30’• Doors = 1• Outlets = 6• Deluxe Standing Shower = yes• …Case Based DesignGeneralized design knowledge to augment casesIncludes causal models, state interactions, heuristic models/rules, geometric constraintsTypically not available for innovative and creative tasksCase Based DesignNeed formalization of knowledge for CBR automationProblem: human knowledge of design is difficult to formalize into rules and variables that the system can utilizeIn cases where it is only possible to create an informal body of knowledge, system should be developed to merely support a human designerKnowledge RepresentationFour knowledge containers in CBRVocabularyCase baseSimilarity measureSolution transformationVocabularyVocabulary – task and domain dependentShould capture all important features of designSupports problem solving in relevant domainCase BaseRepresent past design experienceUsage – abnormal/normalGranularity – grain size of cases is equal to grain size of design taskLevel of AbstractionOssified cases – general rules of thumbParadigmatic cases – represent learned expertise Stories – complex, relate to large number of circumstanceCase Base (cont)PerspectiveState-oriented – case represents problem and solutionSolution-path – case refer to problem or operator that determines solution from problem descriptionSimilarity MeasureTwo different approaches to similarity assessmentComputational (similarity) approachRepresentational approachComputational ApproachUnstructured organizationUsefulness of cases based on presence or absence of featuresMany cases Are Called – candidate casesFew Are Chosen – structural comparison between problem and possible solutionsRepresentational ApproachPre-structured case base (indexing structure)Neighboring cases are assumed to be similarProbes constraints in memory to determine possible solutionsCBR for Innovative and Creative DesignFlexible case retrievalRetrieved cases show similar aspects to the problemDifferent similarity measures have to be dynamically composed during retrievalFish and Shrink AlgorithmStructural similarity assessmentStructural cases are processed and represented as variables taking the role of problem or solution variablesSolution Transformation and Case AdaptationNew situations often different from old solutionsSolutions must be adapted to fit the constraints of the problem using parts from other past solutionsSolution Transformation and Case AdaptationThree kinds of adaptation (Cunningham and Slattery 1993)Parametric adaptation – modifying parametersStructural adaptation – adaptation operators (grammar rules)Generative Adaptation – reuse and adaptation for derivations of past problem-solving episodesFish and ShrinkAlgorithm for flexible case retrievalAllows for rapid searching through case base (even if significant aspects are combined at query time)Can be stopped at any time and still produce usable results (though not complete)Fish and ShrinkSimilarity measure of emphasized attributes between all cases and a set of test cases are retrieved and
View Full Document