<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>A Framework for Information Quality Requirements Engineering</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mohamad Gharib</string-name>
          <email>gharib@disi.unitn.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Paolo Giorgini</string-name>
          <email>paolo.giorgini@disi.unitn.it</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>A Framework for Capturing IQ Requirements</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>University of Trento - DISI</institution>
          ,
          <addr-line>38123, Povo, Trento</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
      </contrib-group>
      <fpage>218</fpage>
      <lpage>219</lpage>
      <abstract>
        <p>Information Quality (IQ) is a key success factor for the efficient performance of any organization. Despite this, most Requirements Engineering frameworks either ignore or loosely define IQ requirements. To this end, we propose a novel conceptual framework for modeling and analyzing IQ requirements of the system-to-be. The importance of IQ for organizations is out of discussion, and several solutions for dealing with IQ needs have been proposed in the literature (e.g., integrity constraints, etc.). However, most of these solutions mainly focus on the technical aspects of IQ, and they do not solve problems that may rise at organizational or social levels. More specifically, these techniques do not satisfy the needs of current complex systems, such as socio-technical systems, where humans and organizations are integral part of the system along with the technical components (e.g., smart cities, etc.). At the other hand, we have several Requirements Engineering (RE) approaches that are able to capture the organizational along with the social needs of the system-to-be (e.g., secure Tropos [1], etc.), but their main focus is on the functionality of the system, and they either ignore or loosely define IQ needs. To tackle this problem, we propose a RE framework that is based on secure Tropos and extends it with concepts for capturing IQ requirements. Secure Tropos [1] introduces concepts for modeling actors along with their objectives, entitlements and capabilities. However, it does not provide concepts for capturing IQ needs. Thus, we extended its conceptual model with the following concepts to model and analyze IQ requirements1: (1) Goal-information relations: we provide more refined concepts to capture goals/ information relations, namely: produces, optional read, required read, and sends; (2) Information accuracy: we provide trusted production/ trusted provision concepts to analyze accuracy. For example, information is accurate for read, if it is produced by trusted actor (it will not produce falsified/ fraud information), and 1 For more information about the concepts/formal framework, you can refer to [2,3]</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        it has been transferred through trusted provision (it will not be intentionally/
unintentionally modified during its transfer). While sender cares only about the
trusted provision to analyze the accuracy of its information; (
        <xref ref-type="bibr" rid="ref3">3</xref>
        ) Information
completeness: we provide the part of concept that enables for addressing
information completeness, i.e., information is complete, if it has all its sub parts;
(4) Information timeliness: we provide information volatility, read timeliness,
send timeliness, and information provision time concepts to analyze information
validity. For example, information is valid for read, if its read timeliness is less
than its volatility. While it is valid for send, if its read timeliness at its
destination is less than the required send time, and it is invalid otherwise; (5)
Information consistency: we provide interdependent readers and read-time concepts
to analyze information consistency, where information is consistent, if all its
interdependent readers have the same read-time, otherwise it is inconsistent.
3
      </p>
    </sec>
    <sec id="sec-2">
      <title>ST-IQ Tool</title>
      <p>
        Our framework is supported by a CASE tool (ST-IQ tool)2 that consists of 3
main parts: (
        <xref ref-type="bibr" rid="ref1">1</xref>
        ) GUI that enables for drawing the requirements model; (
        <xref ref-type="bibr" rid="ref2">2</xref>
        )
modelto-text techniques that translate the visual requirements model into Datalog
formal specifications; and (
        <xref ref-type="bibr" rid="ref3">3</xref>
        ) automated reasoning support (DLV system3) that
is used to verify the correctness and consistency of the requirements model. We
demonstrate the utility of our tool by modeling and analyzing IQ requirements
of case study concerning a main U.S stock market crash (the Flash Crash) [2,3].
4
      </p>
    </sec>
    <sec id="sec-3">
      <title>Ongoing and Future Work</title>
      <p>We are working on extending the framework to be able to derive the final IQ
specifications from the requirements model in terms of IQ policies that define
the permitted, forbidden and obligated actors’ activities toward information.
Moreover, we aim to enrich the trust analysis among actors concerning IQ by
relaying on beliefs related to their internal structure (capabilities and intentions).
2 http://mohamadgharib.wordpress.com/
3 http://www.dlvsystem.com/dlv/</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Mouratidis</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Giorgini</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Secure tropos: A security-oriented extension of the tropos methodology</article-title>
          .
          <source>International Journal of Software Engineering and Knowledge Engineering</source>
          <volume>17</volume>
          (
          <issue>2</issue>
          ) (
          <year>2007</year>
          )
          <fpage>285</fpage>
          -
          <lpage>309</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Gharib</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Giorgini</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Detecting conflicts in information quality requirements: the may 6, 2010 flash crash</article-title>
          .
          <source>Technical report, Universit`a degli studi di Trento</source>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Gharib</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Giorgini</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Modeling and reasoning about information quality requirements</article-title>
          . In: Requirements Engineering:
          <article-title>Foundation for Software Quality (REFSQ15)</article-title>
          , To appear. Springer (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>