Abstract
An ontology-driven approach to applying styles in software engineering is developed in the study. The essence of the approach is to use ontology not only to represent styles but also to control the use of styles when creating and maintaining software. For such purposes, appropriate ontology and developer support tools are provided to represent a style, and tools (reasoners) are created on the ground of the ontological knowledge base to control the application of the style in work products of the software lifecycle phases. Based on descriptive logic, the knowledge base contains two components – terminological (TBox) and factual (ABox). The first component was created in advance by performing a domain analysis. The second component was created when analysing the representation of the corresponding work product. For the purpose of typification in the context of the developed approach, templates for the kernel ontology of the software engineering style were created by analysing the concept of style in different domains. The basic characteristics of style as a domain-independent concept, which are presented in the templates, are formulated in the article. In this case, the Work Product Pattern Application pattern of the Unified Foundational Ontology is used to select the number of templates needed to represent the style. The pattern describes actions that may exist regarding the Work Product style. An example of using the approach is considered by investigating the proposed ontology-driven method for programming style application in software engineering and building the architecture of the tool that implements it. Protege use shows how to build the ontology of a programming style and programmer support. The architecture of the tool for controlling the application of style is developed and implemented in a work product of the design phase – a programme text. The basis of the architecture is the knowledge base of the corresponding style. The terminological component of the knowledge base contains information regarding programming languages and styles, and it is created in advance by the ontology developer. The actual component is created by the reasoner for each representation of the work product – the programme text. The tools developed in the context of the proposed approach automate the processes that take place when applying styles to work products of the software lifecycle phases.
Highlights
To date, methods and tools have become widely common in creating and maintaining reusable software products
The use of a style in software engineering has traditionally been associated with construction, but today, due to the aforementioned circumstances, styles should be applied to all other software lifecycle processes
An ontology-driven approach to the application of styles in software engineering has been suggested in the study
Summary
Methods and tools have become widely common in creating and maintaining reusable software products. The use of a style in software engineering has traditionally been associated with construction, but today, due to the aforementioned circumstances, styles should be applied to all other software lifecycle processes This is required by the Eastern-European Journal of Enterprise Technologies ISSN 1729-3774. The use of a style is very important, but it involves additional spending while solving the problems of learning the style description and adhering to it when creating work products of the lifecycle phases. These tasks are virtually unsolved except for individual construction phase processes. It is proposed to use ontologies as a form of representing style knowledge, regardless of the lifecycle phase, to solve the problems of studying the description of a style and adherence to it when creating software products
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
