Understanding the knowledge needs of novice designers in the aerospace industry

Mesleki Öz Bilgi Olarak Tasarım Düşüncesi

“…Formel tasarım eğitiminin amacı bu gelişim sürecini oluşturmaktır. Tasarım literatüründe tasarım eğitime dönük birçok çalışmada tecrübesiz ve deneyimli tasarımcı adaylarının tasarım düşüncesini kullanma beceri ve seviyeleri konu edilmiştir (Ahmed, Wallace ve Blessing, 2003;Ahmed ve Wallace, 2004;Stones ve Cassidy 2007;Liikkanen ve Perttula, 2009, Özkan ve Doğan, 2013. Bu tür çalışmaların tümünde ampirik olarak tecrübesiz ve deneyimli tasarımcıların arasında tasarım düşüncesi açısından bilgi kaynaklarını kullanmada, süreci gerekçelendirmede, hedef ve sonuç ilişkisini kurgulamada farkların oluştuğu, deneyimin artması ile beraber daha etkin tasarım süreçlerinin ortaya çıktığı belirtilmektedir.…”

Educating Aerospace Design Engineers: Perspectives from Design Creativity Theory

“…When facing the aerospace design problem, novice designers can be overwhelmed by the huge amount of information and options available [9], especially for the illdefined, open-ended design problem that is aircraft conceptual and preliminary design. The ideal aerospace design engineer understands the requirements of both the manufacturer, the operator and the end user, the physical and regulatory environment in which the product is expected to operate, the technological design constraints resulting from performance, reliability and certification requirements and the cost and schedule constraints that can drive a design program.…”

An approach for design rationale retrieval using ontology-aided indexing

“…On the one hand, traditional DR representations do not have enough expressing ability; on the other hand, most of them are not formal enough to be understood by the computer. Ahmed and Wallace (2004) did a comprehensive analysis of the discourse between novice designers and experienced designers and identified eleven main kinds of knowledge needs including how does it work, why, what issues to consider, when to consider issues and design process. IBIS (Kunz and Rittel 1970) is a traditional DR representation which can express most of the first three knowledge needs, moreover, we find that Requirement can answer why and when, Function describes how, and Artifact is highly related to L. Li et al …”

“…The expressivity of natural language enables the DR retrieval to take advantage of some relationships in DR ontology. According to the designers' requirements on design knowledge identified by Ahmed and Wallace (2004) and considering the existing NLP technologies, we adopt question-answering strategy to deal with natural language input query, and four types of questions are considered as listed in Table 4. To effectively handle the four types of questions and get the required answers, five steps are given as follows:…”