Design Requirements Management using an Ontological Framework

Roy, Rajkumar; Kerr, Clive; Sáckett, Peter; Corbett, John

doi:10.1016/s0007-8506(07)60061-4

Cited by 24 publications

(18 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…It is not until the last two decades that researchers started to apply ontology [30,43,46,149,155] to automating design research, and it was around the time when AI technology began to boom. One representative theory is the FBS design prototype.…”

Section: Fbs Prototype Based On Ontologymentioning

confidence: 99%

“…It often originates from a wide variety of sources-heuristic, qualitative, quantitative, etc. Moreover, modern product development process involves the collaboration of engineers from different organizations or different areas of expertise [149]. Thus, a consensus must be reached on the understanding of one specification.…”

Section: Ontology-based Knowledge Management For Automating Designmentioning

confidence: 99%

“…Ontological modelling of requirement is extremely significant, due to the fact that an unambiguous description of requirements can unify the initial imports, which facilitate the automatic reasoning of automating design. A knowledge-based tool for the specification of the requirements in automotive systems has been developed through the application of ontology by Roy [149]. The ontology for managing requirement has been developed in products, information and process levels to achieve a consensual understanding of a product between automotive OEM and suppliers.…”

Section: Ontological Modelling Of Knowledgementioning

confidence: 99%

See 2 more Smart Citations

Automating design with intelligent human–machine integration

et al. 2015

View full text Add to dashboard Cite

Section: Fbs Prototype Based On Ontologymentioning

confidence: 99%

Section: Ontology-based Knowledge Management For Automating Designmentioning

confidence: 99%

Section: Ontological Modelling Of Knowledgementioning

confidence: 99%

See 1 more Smart Citation

Automating design with intelligent human–machine integration

et al. 2015

View full text Add to dashboard Cite

“…Requirements management presents significant difficulties when stakeholders are distributed, as in today's global projects and is identified as one of the most collaboration-intensive activities in software development (Sinha, Sengupta and Chandra, 2006). In product development through the extended enterprise, Roy et al (2005) recognize the necessity to formalize and automate the requirements management process which is manual and time consuming in order to reduce the product development time and cost. Halbleib (2004) indicates that managing requirements is not an event but a process which starts at the outset of a project and continues until the developed system has been discontinued and is no longer supported.…”

Section: Requirements Managementmentioning

confidence: 99%

An empirical study of the complexity of requirements management in construction projects

Jallow

Demian

Baldwin

et al. 2014

Engineering, Construction and Architectural Management

View full text Add to dashboard Cite

Purpose -The aim of this paper was to investigate in-depth the current approach of managing client requirements in construction and to highlight the significant factors, which contribute to the complexity of managing the requirements in order to define a better approach.Design/methodology/approach -A case study of a leading international global built asset and engineering consultancy organization was conducted over two years. The case study was conducted principally using semi-participant observations supplemented with other qualitative data collection methods (i.e., interviews, questionnaires and document analysis). Thematic analysis was used to analyse the data.Findings -The results highlight major factors associated with the complexity of managing client requirements information, which include: mechanisms for documentation, storage and access, distribution of requirements information between stakeholders and across lifecycle phases of a project, traceability management and the provision of effective change management incorporating dependency checking and impact analysis.Research limitations/implications -The main limitation of the research is the use of an in-depth study of a single organization, which applied the same project management method across all the projects they managed. Further work is planned to develop the proposed framework fully, and develop a software prototype to operationalize and evaluate its industrial applicability with construction projects.Practical implications -The implications of this research is that a better approach to managing requirements information is needed, which will facilitate the design, construction and operations of buildings within budget and time. An integrated framework and an associated tool are suggested to implement the approach.Originality/value -This study identifies major research gaps and problems in the AEC/FM industry; proposes and presents eRIM framework to facilitate lifecycle management of the requirements.

show abstract

“…First, a building is composed of many pieces of elements, which are geometrically complex and interwoven [3], so manual design checking is error-prone and the results are unreliable [2]. Second, designers may misinterpret design requirements in an RFP due to the ambiguous nature of natural language or through human error [4,5]. Third, RFP-based design checking is very time consuming and labor intensive.…”

Section: Introductionmentioning

confidence: 99%