Towards the design of intelligent CAD systems: An ontological approach

Supporting the designer’s and the user’s perspectives in computer-aided architectural design

“…Such an ontology-based approach will enable a more strict, formal representation and reasoning about expectancies of both designer and user, allowing for a better adaption to the given situation (cf. also [42]). Finally, exploratory empirical studies will provide feedback on a designer's interaction with CosyCAD and will allow for identifying further factors that may help improve users' wayfinding performance.…”

Transforming expertise into Knowledge-Based Engineering tools: A survey of knowledge sourcing in the context of engineering design

“…Table 2 underlines the most common engineering domains and sectors where KBE applications have been implemented. van Tooren [21], J. Choi [22], W. Chen et al [23] Design optimisation in aerospace G. La Rocca [20], K. Amadori et al [24] , C. van der Velden et al [25], S. Kumar and R. Singh [26] Design automation in aerospace J. Nacsa et al [27], N. Gardan and Y. Gardan [28], W. Skarka [29], G. Colombo et al [30], U. Roy [31] Support implementation of the engineering design process in aerospace C. Chapman and M. Pinfold [5,32] Design automation in automotive C. Verhagen [33], M. Pinfold and C. Chapman [34] Support implementation of the engineering design process in automotive R. Ratnayake [35], P. Potes-Ruiz et al [36] Support in maintenance activities H. Yang et al [37], J. Cui and D. Wang [38] Design optimisation in ship building Y. Wu and H. Shaw [39] Support implementation of the engineering design process in ship building Specific software applications known as KBE systems are usually required to effectively carry out knowledge-based engineering tasks, enabling the systematic capture, transfer and reuse of engineering knowledge in a way that it is easier to use and maintain [40]. A list of the available KBE software tools in the market is found in [41].…”

Formal modelling, knowledge representation and reasoning for design and development of user-centric pervasive software: a meta-review

“…Our focus is on software as an engineering artefact. There has been a considerable debate on the formal/informal form of software specifications (Colburn, 2000) gathering structural knowledge (about the components which comprise the design object and their relations), behavioural knowledge (about the behaviour of the design object), teleological knowledge (about the purpose and the way the design object is intended to be used), and functional knowledge (about the behaviours and goals of the artefact itself) (Colombo et al, 2007).…”