A method for building ontology-based electronic document management systems for quality standards—the case study of the ISO/TS 16949:2002 automotive standard

Castillo-Barrera, Francisco Edgar; Durán-Limón, Héctor A.; Médina-Ramírez, Carolina; Rodriguez-Rocha, Beatriz

doi:10.1007/s10489-012-0360-1

Cited by 9 publications

(3 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Recently, Software Engineers have had an interest in the use of ontologies to identify and share knowledge on the different phases of the software development cycle as presented in the works by Bathia et al [29] and de Souza et al [30]. In the literature, we can find different methodologies to develop ontologies including Diligent [31], On-To-Knowledge [32], Neon [33], OntoDocMan [34] and Methontology Framework [35], where each one follows a different approach.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Ontology for knowledge condensation to support expertise location in the code phase during software development process

et al. 2020

Self Cite

View full text Add to dashboard Cite

Software Development is a complex process, in which every software product is a knowledge representation of all the involved people. In agile software development, knowledge is prone to vaporise, because documentation is not a priority as indicated in the agile manifesto. This condition generates problems such as poor understanding of the requirements, knowledge transfer deficiency among developers, time wasted by developers while searching for knowledge. The objective of this work is to reduce architectural knowledge vaporisation by means of knowledge condensation to support expertise location (high-level knowledge at a given time). This through an ontology that will condensate the knowledge in the code phase. This study presents the description of an ontology development process following the Methontology Framework. Results show that the proposed ontology does not present incongruence or inconsistency and answers the competency questions correctly. The main contribution of this study is the ontology which brings several benefits such as a shared concept of the knowledge in the code phase and a way to link the artefacts (resources used by developers in the project) and the experts (artefacts provider).

show abstract

Section: Related Workmentioning

confidence: 99%

“…[30]. In the literature, we can find different methodologies to develop ontologies including Diligent [31], On‐To‐Knowledge [32], Neon [33], OntoDocMan [34] and Methontology Framework [35], where each one follows a different approach.…”

Section: Related Workmentioning

confidence: 99%

Ontology for knowledge condensation to support expertise location in the code phase during software development process

et al. 2020

Self Cite

View full text Add to dashboard Cite

show abstract

“…The research presented in Castillo- Barrera et al (2013) proposes a method to build an ontology-based electronic document management system, which captures the knowledge associated with a company's processes related to a quality standard. The use of this method was illustrated by the development of the ontology for the 16949 ISO/TS automotive quality standard.…”

Section: Related Workmentioning

confidence: 99%

Multilayer document model for semantic document management services

Sladić

Cverdelj-Fogaraši

Gostojić

et al. 2017

View full text Add to dashboard Cite

Purpose The purpose of this paper is to identify the benefits of an approach in which document management systems (DMSs) are based on a formal and explicit document model, primarily in terms of facilitating domain-specific customization. Design/methodology/approach Within this paper, a generic document model is proposed. The model consists of two layers. A general purpose layer, which represents common features of the documents, and a domain-specific layer, modeling properties particular to application domain. The general purpose layer is based on ISO 82045, providing high degree of interoperability with other systems developed with respect to this set of standard. Findings Splitting document model into the layers enables DMSs to be tailored for each particular domain of application, depending on the general purpose layer. The existence of domain-specific layer allows documents to be interpreted differently in different domains of application. Practical implications In order to enable customization of DMS for a particular domain, the implementation of domain-specific document layer is required. Also, the proposed model does not explicitly deal with document dynamics. Originality/value The proposed document ontology is general enough to provide the representation of documents not depending on a specific scope of application, yet flexible enough to enable extensions through which domain-specific document features can be expressed. The separation of document model enables development of core DMS offering services relying explicitly on the general purpose layer on one hand, as well as domain-specific customization of DMS on the other.

show abstract

Representing and Reasoning About XML with Ontologies

Zhang

2013

Appl Intell

View full text Add to dashboard Cite

A method for building ontology-based electronic document management systems for quality standards—the case study of the ISO/TS 16949:2002 automotive standard

Cited by 9 publications

References 22 publications

Ontology for knowledge condensation to support expertise location in the code phase during software development process

Ontology for knowledge condensation to support expertise location in the code phase during software development process

Multilayer document model for semantic document management services

Representing and Reasoning About XML with Ontologies

Contact Info

Product

Resources

About