<?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-020-06-0842</article-id>
      <article-id pub-id-type="publisher-id">23251</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Research Article</subject>
        </subj-group>
        <subj-group subj-group-type="scientific_subject">
          <subject>I.3.8 - Applications</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Using and Extending Formal Concept Analysis to Visualise Variability during Requirements Engineering</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Huysegoms</surname>
            <given-names>Tom</given-names>
          </name>
          <email xlink:type="simple">tom.huysegoms@kuleuven.be</email>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Snoeck</surname>
            <given-names>Monique</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Dedene</surname>
            <given-names>Guido</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Goderis</surname>
            <given-names>Antoon</given-names>
          </name>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Stumpe</surname>
            <given-names>Frank</given-names>
          </name>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">KU Leuven, Leuven, Belgium</addr-line>
        <institution>KU Leuven</institution>
        <addr-line content-type="city">Leuven</addr-line>
        <country>Belgium</country>
      </aff>
      <aff id="A2">
        <label>2</label>
        <addr-line content-type="verbatim">KBC Global Services, Brussels, Belgium</addr-line>
        <institution>KBC Global Services</institution>
        <addr-line content-type="city">Brussels</addr-line>
        <country>Belgium</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Tom Huysegoms (<email xlink:type="simple">tom.huysegoms@kuleuven.be</email>).</p>
        </fn>
        <fn fn-type="edited-by">
          <p>Academic editor: </p>
        </fn>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2014</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>01</day>
        <month>06</month>
        <year>2014</year>
      </pub-date>
      <volume>20</volume>
      <issue>6</issue>
      <fpage>842</fpage>
      <lpage>858</lpage>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/E6189089-EAF5-54B5-88F2-63DE796D4531">E6189089-EAF5-54B5-88F2-63DE796D4531</uri>
      <uri content-type="zenodo_dep_id" xlink:href="https://zenodo.org/record/5505211">5505211</uri>
      <history>
        <date date-type="received">
          <day>01</day>
          <month>07</month>
          <year>2013</year>
        </date>
        <date date-type="accepted">
          <day>14</day>
          <month>02</month>
          <year>2014</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>Tom Huysegoms, Monique Snoeck, Guido Dedene, Antoon Goderis, Frank Stumpe</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>Research on variability in software artefacts is something which is already studied extensively in research. The visualisation of variability is one aspect of this research, and results like e.g. feature diagrams are well-known and well-spread. When it concerns the origin of the variability within the phase of requirements engineering, research is much scarcer. A visualisation technique for both representing the origin and the amount of variability in requirements is not readily available in research. This paper provides a way to represent the origin of variability in requirements with the aid of a technique called formal concept analysis (FCA). Additionally the support that FCA can provide for variability related decisions during (early) requirements engineering is also depicted in this paper. Proof of the usability of FCA for the visualization, and documentation, of variability is shown with the aid of a real-life case study. FCA is also applied in the real-life case study to check the compatibility of FCA as a visualization method to support variability decision making during requirements engineering.</p>
      </abstract>
    </article-meta>
  </front>
</article>
