<?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-05-0720</article-id>
      <article-id pub-id-type="publisher-id">23187</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.13 - Reusable Software</subject>
          <subject>D.2.1 - Requirements/Specifications</subject>
          <subject>D.2.2 - Design Tools and Techniques</subject>
          <subject>D.2.4 - Software/Program Verification</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Verification of Software Product Line Artefacts: A Checklist to Support Feature Model Inspections</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>De Mello</surname>
            <given-names>Rafael Maiani</given-names>
          </name>
          <email xlink:type="simple">rmaiani@cos.ufrj.br</email>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Teixeira</surname>
            <given-names>Eldanae Nogueira</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Schots</surname>
            <given-names>Marcelo</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Werner</surname>
            <given-names>Cláudia Maria Lima</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Travassos</surname>
            <given-names>Guilherme</given-names>
          </name>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">COPPE-Federal University of Rio de Janeiro, Rio de Janeiro, Brazil</addr-line>
        <institution>COPPE-Federal University of Rio de Janeiro</institution>
        <addr-line content-type="city">Rio de Janeiro</addr-line>
        <country>Brazil</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Rafael Maiani De Mello (<email xlink:type="simple">rmaiani@cos.ufrj.br</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>05</month>
        <year>2014</year>
      </pub-date>
      <volume>20</volume>
      <issue>5</issue>
      <fpage>720</fpage>
      <lpage>745</lpage>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/8F723AE2-0F12-5490-B3E1-270E39146A55">8F723AE2-0F12-5490-B3E1-270E39146A55</uri>
      <uri content-type="zenodo_dep_id" xlink:href="https://zenodo.org/record/5505117">5505117</uri>
      <history>
        <date date-type="received">
          <day>28</day>
          <month>07</month>
          <year>2013</year>
        </date>
        <date date-type="accepted">
          <day>15</day>
          <month>02</month>
          <year>2013</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>Rafael Maiani De Mello, Eldanae Nogueira Teixeira, Marcelo Schots, Cláudia Maria Lima Werner, Guilherme Travassos</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>Software Product Line Engineering (SPL) should ensure the correctness, completeness and consistenc y of its artefacts and related domain to prevent the propagation of defects in derived products. Software inspection techniques are effective in detecting defects in software artefacts and avoiding their propagation throughout the software development process. However, the results of a quasi-systematic review of the technical literature reported in this paper pointed to a lack of such techniques to support the inspection of SPL artefacts, including techniques to support the inspection of feature models (FMs) that are largely used in domain modelling. Therefore, a checklist-based inspection technique (FMCheck) has been developed to support the detection of defects on FMs. FMCheck is configurable and can be applied to the original feature model notation (the F ODA approach) and its extensions, including the Odyssey-FEX notation. The inspection technique was empirically evaluated, having indicated its feasibility and effectiveness. It is possible to see that inspectors applying FMCheck to inspect F-s can be more effective than those applying ad-hoc techniques, regarding four distinct domains.</p>
      </abstract>
    </article-meta>
  </front>
</article>
