China
Africa
Explore chapters and articles related to this topic
Keeping Traces of Design Meetings through Intermediary Objects
Published in Janet McDonnell, Peter Lloyd, Fraser Reid, Rachael Luck, Nigel Cross, About: Designing, 2009
Emine Serap Arıkoğlu, Eric Blanco, Franck Pourroy
Thus, we assume that linking sketches with a representation capable of capturing design rationale can be useful. In the analysis presented here we used a tool based on the IBIS model (Issue-Based Information System). IBIS was developed by Horst Rittel and colleagues during the early 1970’s14. The heart of IBIS is the matrix of questions, ideas, and arguments that combine together to create a conversation, question states a question; idea proposes a possible resolution for the question; and argument states an opinion or judgment that either supports or objects to one or more ideas.
Configuration Management
Published in Jon M. Quigley, Kim L. Robertson, Configuration Management, 2019
Jon M. Quigley, Kim L. Robertson
Issue-based information system (IBIS): A structuring method that allows the rationale underlying requirements to be organized and tracked. IBIS has several advantages. It is easy to learn and use. An indented text system was used in an early implementation of a tool for IBIS, and it was well accepted because the users were already familiar with the components (personal computers and text editors) used for the tool.
Identifying and addressing challenges in the engineering design of modular systems – case studies in the manufacturing industry
Published in Journal of Engineering Design, 2019
Jarkko Pakkanen, Tero Juuti, Timo Lehtonen
Aspects of design knowledge management are also important when discussing product variety management. Knowledge capturing, indexing, and retrieval can be considered part of the design process, and research on this topic has explored design rationale and support systems. Information systems should help designers store, represent, search, and use reusable knowledge (Sivaloganathan and Shahin 1999). Derivatives of issue-based information systems (IBIS) (Kunz and Rittel 1970) are probably the most popular solution in this context. Bracewell and Wallace (2003) and Bracewell et al. (2009a) presented two generations of design rationale editor (DRED) tools for formally capturing and communicating issues that have been addressed, options being considered, and arguments for and against each option. In addition to factors inhibiting design reuse, Bracewell et al. (2009) noted that design rationale capture tools have great potential, but must fit naturally with designers’ working methods and consider the challenges inherent in large and complex projects to ensure clarity. Other tools, such as Compendium, support the building of shared understanding and structured knowledge (Conklin et al. 2001). Leake and Wilson (2001) discussed the role of concept maps in capturing reusable knowledge to support case-based reasoning. Ontologies, or collections of knowledge that include structured conceptualisations defining specific pieces of knowledge (Chandrasekaran, Josephson, and Richard Benjamins 1999), have also been discussed as ways of representing components and parts to support the reuse of product information (Moon, Simpson, and Kumara 2010).