How to write and use the Ontology Requirements Specification Document

The goal of the ontology requirements specification activity is to state why the ontology is being built, what its intended uses are, who the end-users are, and which requirements the ontology should fulfill. The novelty of this paper lies in the systematization of the ontology requirements specification activity since the paper proposes detailed methodological guidelines for specifying ontology requirements efficiently. These guidelines will help ontology engineers to capture ontology requirements and produce the ontology requirements specification document (ORSD). The ORSD will play a key role during the ontology development process because it facilitates, among other activities, (1) the search and reuse of existing knowledge-aware resources with the aim of re-engineering them into ontologies, (2) the search and reuse of existing ontological resources (ontologies, ontology modules, ontology statements as well as ontology design patterns), and (3) the verification of the ontology along the ontology development. In parallel to the guidelines, we present the ORSD that resulted from the ontology requirements specification activity within the SEEMP project, and how this document facilitated not only the reuse of existing knowledge-aware resources but also the verification of the SEEMP ontologies. Moreover, we present some use cases in which the methodological guidelines proposed here were applie

A Tool-based Semantic Framework for Security Requirements Specification

Attaining high quality in security requirements specification requires first-rate professional expertise, which is scarce. In fact, most organisations do not include core security experts in their software team. This scenario motivates the need for adequate tool support for security requirements specification so that the human requirements analyst can be assisted to specify security requirements of acceptable quality with minimum effort. This paper presents a tool-based semantic framework that uses ontology and requirements boilerplates to facilitate the formulation and specification of security requirements. A two-phased evaluation of the semantic framework suggests that it is usable, leads to reduction of effort, aids the quick discovery of hidden security threats, and improves the quality of security requirements

Ontology-Based Support for Security Requirements Specification Process

The security requirements specification (SRS) is an integral aspect of the development of secured information systems and entails the formal documentation of the security needs of a system in a correct and consistent way. However, in many cases there is lack of sufficiently experienced security experts or security requirements (SR) engineer within an organization, which limits the quality of SR that are specified. This paper presents an approach that leverages ontologies and requirements boilerplates in order to alleviate the effect of lack of highly experienced personnel for SRS. It also offers a credible starting point for the SRS process. A preliminary evaluation of the tool prototype – ReqSec tool - was used to demonstrate the approach and to confirm its usability to support the SRS process. The tool helps to reduce the amount of effort required, stimulate discovery of latent security threats, and enables the specification of good quality SR

Requirements Modeling Methodology Based on Knowledge Engineering: A Case Study of Railway Control System

The complexity of the verification and the validation of embedded systems is increasing. This paper explores the first requirements engineering processes in the solution domain, which are analysis and specification. In this work we present an architecture of a requirement specification system. We show how the requirements are analysed and structured to generate a dependency graph. This latter will serve to analyse requirements and to model specifications on goal model. In this paper we will focus on the analysis, and structuring processes. We will explain the requirement classification criteria. Keywords: Requirements Modeling, Qualification Strategy, Knowledge Engineering, Ontology, Dependency Graph, Embedded System, ERTMS/ETC

An Experiment in Retrofitting Competency Questions for Existing Ontologies

Competency Questions (CQs) are a form of ontology functional requirements expressed as natural language questions. Inspecting CQs together with the axioms in an ontology provides critical insights into the intended scope and applicability of the ontology. CQs also underpin a number of tasks in the development of ontologies e.g. ontology reuse, ontology testing, requirement specification, and the definition of patterns that implement such requirements. Although CQs are integral to the majority of ontology engineering methodologies, the practice of publishing CQs alongside the ontological artefacts is not widely observed by the community. In this context, we present an experiment in retrofitting CQs from existing ontologies. We propose RETROFIT-CQs, a method to extract candidate CQs directly from ontologies using Generative AI. In the paper we present the pipeline that facilitates the extraction of CQs by leveraging Large Language Models (LLMs) and we discuss its application to a number of existing ontologies

An incremental hybridisation of heterogeneous case studies to develop an ontology for capability engineering

An analysis of perspectives for “capability engineering” has been conducted by the INCOSE UK Capability Working Group (CWG). This paper is a continuation of this study led by the CWG ontology work stream that aims to develop a single shared ontology for the concept of capability engineering to enable semantic interoperability and to support a formal and explicit specification of a shared conceptualisation. Case study material from the different domains of rail, defence and information services was used. The ontology development was executed in three phases; (1) pre-analysis, (2) ontology modelling and (3) post-analysis. The pre-analysis involved literature reviews, requirements specification, systems engineering process utilisation; and resource identification i.e. examination of the case study material. The ontology modelling phase comprised information extraction and classification in addition to modelling and code representation using a mark-up tool, MS Excel and Protégé. The post-analysis involved validation workshops through using expert focus groups

Specification of requirements models

The main aim of this chapter is to present and discuss a set of modeling and specification techniques, in what concerns their ontology and support in the requirements representation of computer-based systems. A systematic classification of meta-models, also called models of computation, is presented. This topic is highly relevant since it supports the definition of sound specification methodologies in relation to the semantic definition of the modeling views to adopt for a given system. The usage and applicability of Unified Modeling Language (UML) diagrams is also related to their corresponding meta-models. A set of desirable characteristics for the specification methodologies is presented and justified to allow system designers and requirements engineers to more consciously define or choose a particular specification methodology. A heuristic-based approach to support the transformation of user into system requirements is suggested, with some graphical examples in UML notation.(undefined