2019
DOI: 10.1002/sys.21515
|View full text |Cite
|
Sign up to set email alerts
|

Modeling and structuring design rationale to enable knowledge reuse

Abstract: We aim to lend insights into "what" constitutes design rationale and "how" to capture these. We restrict the scope of design rationale to the cases of failures observed while testing real engineered systems. We propose a model as an integration of a system hierarchy, a causal chain, and a causality model to cast multiple views of design rationale. The model is structured into databases using a newly introduced version of design structure matrices and supported using a web interface called CRIS 4 P, which is de… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
5

Relationship

2
3

Authors

Journals

citations
Cited by 6 publications
(3 citation statements)
references
References 32 publications
0
3
0
Order By: Relevance
“…Scholars initially aimed to extract design requirements as meaningful terms, phrases and segments from internal reports to reuse these in the design process. Such requirements shall also be derived from the past cases of failure in which violated constraints were recorded (Siddharth, Chakrabarti, and Ranganath 2019a). As mentioned below, scholars initially encountered some challenges while extracting design requirements from internal reports.…”
Section: Requirement Extractionmentioning
confidence: 99%
See 1 more Smart Citation
“…Scholars initially aimed to extract design requirements as meaningful terms, phrases and segments from internal reports to reuse these in the design process. Such requirements shall also be derived from the past cases of failure in which violated constraints were recorded (Siddharth, Chakrabarti, and Ranganath 2019a). As mentioned below, scholars initially encountered some challenges while extracting design requirements from internal reports.…”
Section: Requirement Extractionmentioning
confidence: 99%
“…To represent design rationale, 11 scholars have proposed a variety of prescriptivegeneric ontologies (Ebrahimipour, Rezaie, and Shokravi 2010;Liu et al 2010;Zhang et al 2013;Aurisicchio, Bracewell, and Hooey 2016;Siddharth, Chakrabarti, and Ranganath 2019a) that build upon the fundamental idea of entity-relationship models (Taleb-Bendiab et al 1993). While generic ontologies are capable of capturing rationale from a variety of domains, the performances of these in terms of knowledge retrieval are expected to be low due to the level of abstraction.…”
Section: Ontology Constructionmentioning
confidence: 99%
“…Often information about the prototype and product development process is sparse, or known only to the team or individuals working on the project, as there is little to no expectation that it will be communicated to others (McAlpine et al, 2006). However, the information relating to the process of product development, rather than the information pertaining to the individual prototypes can yield interesting insights and learnings to improve future development activities (Barhoush et al, 2019;Bracewell et al, 2009;Siddharth et al, 2020). Soomro et al (2021) analysed six technologies aimed at supporting the capture of prototyping activities, categorising them into three groups: software, hardware and hybrid approaches.…”
Section: Prototypesmentioning
confidence: 99%