<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//TaxonX//DTD Taxonomic Treatment Publishing DTD v0 20100105//EN" "../../nlm/tax-treatment-NS0.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:tp="http://www.plazi.org/taxpub" article-type="research-article" dtd-version="3.0" xml:lang="en">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">109</journal-id>
      <journal-id journal-id-type="index">urn:lsid:arphahub.com:pub:3dc5f44e-8666-58db-bc76-a455210e8891</journal-id>
      <journal-title-group>
        <journal-title xml:lang="en">JUCS - Journal of Universal Computer Science</journal-title>
        <abbrev-journal-title xml:lang="en">jucs</abbrev-journal-title>
      </journal-title-group>
      <issn pub-type="ppub">0948-695X</issn>
      <issn pub-type="epub">0948-6968</issn>
      <publisher>
        <publisher-name>Journal of Universal Computer Science</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.3217/jucs-019-13-1940</article-id>
      <article-id pub-id-type="publisher-id">23810</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Research Article</subject>
        </subj-group>
        <subj-group subj-group-type="scientific_subject">
          <subject>D.2.1 - Requirements/Specifications</subject>
          <subject>M.4 - KNOWLEDGE MODELING</subject>
          <subject>M.8 - KNOWLEDGE REUSE</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>A Tool-based Semantic Framework for Security Requirements Specification</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Daramola</surname>
            <given-names>Olawande</given-names>
          </name>
          <email xlink:type="simple">olawande.daramola@covenantuniversity.edu.ng</email>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Sindre</surname>
            <given-names>Guttorm</given-names>
          </name>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Moser</surname>
            <given-names>Thomas</given-names>
          </name>
          <xref ref-type="aff" rid="A3">3</xref>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">Covenant University, Ota, Nigeria</addr-line>
        <institution>Covenant University</institution>
        <addr-line content-type="city">Ota</addr-line>
        <country>Nigeria</country>
      </aff>
      <aff id="A2">
        <label>2</label>
        <addr-line content-type="verbatim">Norwegian University of Science and Technology (NTNU), Trondheim, Norway</addr-line>
        <institution>Norwegian University of Science and Technology (NTNU)</institution>
        <addr-line content-type="city">Trondheim</addr-line>
        <country>Norway</country>
      </aff>
      <aff id="A3">
        <label>3</label>
        <addr-line content-type="verbatim">Vienna University of Technology, Vienna, Austria</addr-line>
        <institution>Vienna University of Technology</institution>
        <addr-line content-type="city">Vienna</addr-line>
        <country>Austria</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Olawande Daramola (<email xlink:type="simple">olawande.daramola@covenantuniversity.edu.ng</email>).</p>
        </fn>
        <fn fn-type="edited-by">
          <p>Academic editor: </p>
        </fn>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2013</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>01</day>
        <month>07</month>
        <year>2013</year>
      </pub-date>
      <volume>19</volume>
      <issue>13</issue>
      <fpage>1940</fpage>
      <lpage>1962</lpage>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/E8F88A27-A59F-57C4-A1C3-B3E61F0643C8">E8F88A27-A59F-57C4-A1C3-B3E61F0643C8</uri>
      <uri content-type="zenodo_dep_id" xlink:href="https://zenodo.org/record/5505941">5505941</uri>
      <history>
        <date date-type="received">
          <day>07</day>
          <month>11</month>
          <year>2012</year>
        </date>
        <date date-type="accepted">
          <day>28</day>
          <month>06</month>
          <year>2013</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>Olawande Daramola, Guttorm Sindre, Thomas Moser</copyright-statement>
        <license license-type="creative-commons-attribution" xlink:href="" xlink:type="simple">
          <license-p>This article is freely available under the J.UCS Open Content License.</license-p>
        </license>
      </permissions>
      <abstract>
        <label>Abstract</label>
        <p>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.</p>
      </abstract>
    </article-meta>
  </front>
</article>
