Automatic SUMO to UML Translation
Journal Title: e-Informatica Software Engineering Journal - Year 2016, Vol 10, Issue 1
Abstract
Existing ontologies are a valuable source of domain knowledge. This knowledge could be extracted and reused to create domain models. The extraction process can be aided by tools that enable browsing ontology, marking interesting notions and automatic conversion of selected elements to other notations. The paper presents a tool that can be used for SUMO to UML translation. Such a transformation is feasible and results in a high-quality domain model which is consistent, correct, and complete, providing that input ontology has the same features.
Authors and Affiliations
Bogumiła Hnatkowska
Keywords
Related Articles
- EP ID EP201185
- DOI 10.5277/e-Inf160103
- Views 114
- Downloads 0
Applying Machine Learning to Software Fault Prediction
Introduction: Software engineering continuously suffers from inadequate software testing. The automated prediction of possibly faulty fragments of source code allows developers to focus development efforts on fault-prone...
Are We Working Well with Others? How the Multi Team Systems Impact Software Quality
Background: There are many studies on software development teams, but few about the interactions between teams. Current findings suggest that these multi-team systems may have a significant impact on software development...
Software Startups -- A Research Agenda
Software startup companies develop innovative, software-intensive products within limited time frames and with few resources, searching for sustainable and scalable business models. Software startups are quite distinct f...
An Approach to Assessing the Quality of Business\ Process Models Expressed in BPMN
Introduction: The quality of business process models is important in the area of model-based software development. To the best knowledge of the author there is no working practical model for quality assessment of BPMN 2....
Data Flow Approach to Testing Java Programs Supported with DFC
Code based (``white box'') approach to testing can be divided into two main types: control flow coverage and data flow coverage. The data flow testing was introduced to structural programming languages and later adopted...