<?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-09-1304</article-id>
      <article-id pub-id-type="publisher-id">23490</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.5 - Testing and Debugging</subject>
          <subject>K.3.1 - Computer Uses in Education</subject>
          <subject>K.3.2 - Computer and Information Science Education</subject>
          <subject>L.0.0 - Assessment and Evaluation</subject>
          <subject>L.3.6 - Technology Enhanced Learning</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>FLOP: A User-Friendly System for Automated Program Assessment</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Llana</surname>
            <given-names>Luis</given-names>
          </name>
          <email xlink:type="simple">lana@sip.ucm.es</email>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Martin-Martin</surname>
            <given-names>Enrique</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Pareja-Flores</surname>
            <given-names>Cristóbal</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Velázquez-Iturbide</surname>
            <given-names>J. Ángel</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">Universidad Complutense de Madrid, Madrid, Spain</addr-line>
        <institution>Universidad Complutense de Madrid</institution>
        <addr-line content-type="city">Madrid</addr-line>
        <country>Spain</country>
      </aff>
      <aff id="A2">
        <label>2</label>
        <addr-line content-type="verbatim">Universidad Rey Juan Carlos, Madrid, Spain</addr-line>
        <institution>Universidad Rey Juan Carlos</institution>
        <addr-line content-type="city">Madrid</addr-line>
        <country>Spain</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Luis Llana (<email xlink:type="simple">lana@sip.ucm.es</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>09</month>
        <year>2014</year>
      </pub-date>
      <volume>20</volume>
      <issue>9</issue>
      <fpage>1304</fpage>
      <lpage>1326</lpage>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/B252CDDC-D141-59B7-B1B0-6FE45F47FFCC">B252CDDC-D141-59B7-B1B0-6FE45F47FFCC</uri>
      <uri content-type="zenodo_dep_id" xlink:href="https://zenodo.org/record/5505529">5505529</uri>
      <history>
        <date date-type="received">
          <day>08</day>
          <month>12</month>
          <year>2013</year>
        </date>
        <date date-type="accepted">
          <day>29</day>
          <month>08</month>
          <year>2014</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>Luis Llana, Enrique Martin-Martin, Cristóbal Pareja-Flores, J. Ángel Velázquez-Iturbide</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>Currently, automated systems for program submission and assessment play a central role in the teaching of programming. A number of such systems have been developed in the last two decades. However, their adoption in regular programming teaching presents an obstacle: the overhead work required for the design of each problem, for compilation of problem collections, and for mundane management tasks. An open challenge is to make these systems easier to use and to reduce to a minimum the number of management tasks. In this article we present the FLOP system, which was developed to satisfy this goal. The contribution of the article is twofold. On the one hand, we present the FLOP system itself and its user-friendly features. On the other hand, we present in detail the user-centered design process used to design and enhance the ease of use of FLOP. Several actions were undertaken to inquire users concerns and needs, with a usability evaluation of FLOP conducted with students being the most fruitful action.</p>
      </abstract>
    </article-meta>
  </front>
</article>
