<!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>Architecture for the Use of Synergies between Knowledge Engineering and Requirements Engineering - Extended Abstract ?</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jose del Sagrado</string-name>
          <email>jsagrado@ual.es</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Isabel M. del Aguila</string-name>
          <email>imaguila@ual.es</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Francisco J. Orellana</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Dpt. Languages and Computation</institution>
          ,
          <addr-line>Ctra Sacramento s/n, 04120 University of Almer a</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Expert knowledge is involved in every software development project since developers must face numerous decision tasks during requirements management, analysis, design, and implementation stages. Therefore, if expert knowledge could be properly modelled and incorporated in the di erent processes of software development as well as in the CASE tools that support these processes, that would mean a great advantage for any software development. In software development, requirements stage is considered a good application domain for Arti cial Intelligence (AI) techniques because of requirements nature. Software requirements express and establish the needs and constraints that contribute to the solution of a real world problem [7]. However, requirements tend to be imprecise, incomplete and ambiguous[3] and has a big impact in whole development stages [5, 15, 1, 2]. Therefore, the use of AI techniques in order to improve requirements stage will favorably a ect the whole software life cycle, but we need a seamless integration of Requirement Engineering (RE) and AI techniques to exploit the bene ts of collaboration between these two knowledge areas [10]. Besides, the biggest breakthrough in requirement management is when you stop thinking of documents and start thinking about information. Here, is where CARE (Computer-Aided Engineering Requirement) tools help us in order to be able to handle all of this information. InSCo Requisite is an academic web CARE tool, developed by DKSE group at the University of Almer a, which aids during the requirement development stage [11]. This work presents the architecture for the seamless integration of a CARE tool to manage requirements (i.e. InSCo Requisite) with some AI techniques (i.e. Bayesian networks [12, 6] and metaheuristics). Speci cally, a Bayesian network, called Requisites [13], is used in the requirement validation task in order to validate the Software Requirements Speci cation (SRS) of a software development project, they has been successfully applied in SE, [9, 4, 8, 13]. Metaheuristic techniques (Simulated Annealing, Genetic Algorithms and Ant Colony Systems) are used in the problem of selecting the subset of requirements among a whole ? This is a long abstract of the paper published in Lozano,J.A., Gamez, J.A., Moreno, J.A. (eds.) LNAI Series, Current Topics in Arti cial Intelligence. 14th Conference of the Spanish Association for Arti cial Intelligence, CAEPIA 2011, La Laguna, Spain, November 8-11, 2011, Selected Papers.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        set of candidate requirements proposed by a group of stakeholders, that will be
included in the development of a nal software product [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ].
      </p>
      <p>The RE work ow depicted in Figure 1 shows an organization of the tasks that
must be done in a software development project during RE stage. Requirements
are elicited or gathered from users, next they are speci ed in a document or
its electronic equivalent, known as Software Requirements Speci cation (SRS).
CARE tools provide environments that make use of databases, allowing an
effective management of the requirements of any software project. Requirements
validation checks whether the elicited and speci ed requirements present
inconsistencies; if the information is incomplete or if there are ambiguities in the
system de nition. Requisite Bayesian network provide developers an aid, under
the form of a probabilistic advice (i.e. an estimation of the degree of revision for
the SRS), helping them at the time of making a decision about the stability of
the current requirements speci cation. Finally, requirements selection task has as
main objective to choose, from all the requirements de ned in the speci cation,
the subset of requirements that will be implemented.</p>
      <p>
        Bayesian networks and metaheuristic techniques have demonstrated to
obtain interesting results through di erent tests data [
        <xref ref-type="bibr" rid="ref13 ref14">13, 14</xref>
        ]. However, it is di cult
to put them in practice in real software projects. We strongly believe that
having these AI techniques available in a CARE tool would be considerably helpful
for any development team, making them more accessible even for non-expert
people. However, IA techniques and the CARE tools have been developed
independently of each other. Therefore, it is necessary to de ne a communication
interface between them preserving the independent evolution of both areas and
achieving a synergic bene c e ect between them. This seamless synergic
architecture is shown in Figure 1. The architectural pattern distinguish between three
logically separated layers (see Fig. 1) : the presentation (i.e. interface layer), the
application processing (i.e. service layer), and the data management (i.e. data
layer).
      </p>
      <p>The interface is a web environment accessed from a web browser. Data layer
is in charge of storing and managing the electronic representation of SRS
handled by InSCo Requisite tool and the knowledge base that contains the Bayesian
network Requisites. Service layer is composed by the CARE tool (i.e. InSCo
Requisite), the AI techniques used to address requirements validation (i.e. Bayesian
network Requisites) and requirements selection (i.e. metaheuristics algorithms)
tasks. Communication interface connect CARE and knowledge-based tools
passing the required information needed for the execution of the appropriated
processes. Thus, requirement validation receives metrics on the SRS and returns
an estimation of the degree of revision for SRS; requirement selection receives
resources e ort bound and speci c measures on individual requirements and set
the set of requirements in order to be implemented. All of these communication
processes are performed through XML les.</p>
      <p>The purpose of this work is to de ne a three-layer architecture which: a)
allows the seamless collaboration between RE tasks and some AI techniques
(Bayesian networks, simulated annealing, genetic algorithms and ant colony
sys</p>
      <p>Fig. 1. Seamless synergic architecture.
tems) in order to perform a software development project; b) facilitates their
parallel and independent evolution.</p>
      <p>Acknowledgments. This work was supported by the Spanish Ministry of
Science and Innovation under project TIN2010-20900-C04-02 and by the Junta of
Andaluc a under project TEP-06174.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. Standish Group:
          <source>Chaos Report. Technical report</source>
          , Standish Group International (
          <year>1994</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Johnson</surname>
          </string-name>
          , J.:
          <source>CHAOS chronicles v3.0. Technical report</source>
          , Standish Group International (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. Cheng,
          <string-name>
            <given-names>B.H.</given-names>
            ,
            <surname>Atlee</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.M.:</surname>
          </string-name>
          <article-title>Research directions in requirements engineering</article-title>
          . In: Future of Software Engineering, FOSE'
          <volume>07</volume>
          , pp.
          <fpage>285</fpage>
          -
          <lpage>303</lpage>
          . Institute of Electrical and Electronics Engineers, Minneapolis, Minnesota (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Fenton</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Neil</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marsh</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hearty</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marquez</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Krause</surname>
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mishra</surname>
          </string-name>
          , R.:
          <article-title>Predicting software defects in varying development lifecycles using Bayesian nets</article-title>
          ,
          <source>Information and Software Technology</source>
          <volume>49</volume>
          (
          <issue>1</issue>
          )
          <fpage>32</fpage>
          -
          <lpage>43</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Glass</surname>
            <given-names>A.R.L.</given-names>
          </string-name>
          :
          <article-title>Facts and Fallacies of Software Engineering</article-title>
          . Pearson Education, Inc.,Boston, MA (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Jensen</surname>
            <given-names>F.V.</given-names>
          </string-name>
          :
          <article-title>Bayesian Networks and decision graphs</article-title>
          . Springer-Verlag, New York (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Kotonya</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sommerville</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          : Requirements Engineering: Processes and Techniques. Wiley (
          <year>1998</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Lauria</surname>
            ,
            <given-names>E.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Duchessi</surname>
            ,
            <given-names>P.J.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>A Bayesian</given-names>
            <surname>Belief</surname>
          </string-name>
          <article-title>Network for IT implementation decision support</article-title>
          .
          <source>Decision Support Systems</source>
          <volume>42</volume>
          (
          <issue>3</issue>
          ),
          <fpage>1573</fpage>
          -
          <lpage>1588</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>de Melo</surname>
            <given-names>A.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sanchez</surname>
            ,
            <given-names>A.J.:</given-names>
          </string-name>
          <article-title>Software maintenance project delays prediction using Bayesian Networks</article-title>
          .
          <source>Expert Systems with Applications</source>
          <volume>34</volume>
          (
          <issue>2</issue>
          ),
          <fpage>908</fpage>
          -
          <lpage>919</lpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Meziane</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vadera</surname>
          </string-name>
          , S. (eds.):
          <article-title>Arti cial intelligence applications for improved software engineering development: new prospects</article-title>
          .
          <source>IGI Global</source>
          , Hershey, New York (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Orellana</surname>
            ,
            <given-names>F.J.</given-names>
          </string-name>
          , Can~adas, J.,
          <string-name>
            <surname>del Aguila</surname>
            ,
            <given-names>I.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tunez</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>INSCO requisite - a WebBased RM-Tool to support hybrid software development</article-title>
          .
          <source>In: International Conference of Enterprise Information System ICEIS (3-1)</source>
          , pp.
          <fpage>326</fpage>
          -
          <lpage>329</lpage>
          . Barcelona,
          <string-name>
            <surname>Spain</surname>
          </string-name>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Pearl</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          :
          <article-title>Probabilistic reasoning in intelligent systems: networks of plausible inference</article-title>
          .
          <source>Morgan Kaufman</source>
          , San Mateo, CA (
          <year>1988</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>del Sagrado</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>del Aguila</surname>
            ,
            <given-names>I.M.:</given-names>
          </string-name>
          <article-title>A Bayesian Network for Predicting the Need for a Requirements Review</article-title>
          . In: Meziane,
          <string-name>
            <given-names>F.</given-names>
            ,
            <surname>Vadera</surname>
          </string-name>
          , S. (eds.):
          <article-title>Arti cial intelligence applications for improved software engineering development: new prospects</article-title>
          , pp.
          <fpage>106</fpage>
          -
          <lpage>128</lpage>
          . IGI Global, Hershey, New York (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>del Sagrado</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>del Aguila</surname>
            ,
            <given-names>I. M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Orellana</surname>
            ,
            <given-names>F. J.:</given-names>
          </string-name>
          <article-title>Requirement selection: Knowledge based optimization techniques for solving the next release problem</article-title>
          .
          <source>In: 6th Workshop on Knowledge Engineering and Software Engineering (KESE</source>
          <year>2010</year>
          ), pp.
          <fpage>40</fpage>
          -
          <lpage>51</lpage>
          . CEUR-WS, Karlsruhe, German (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Sommerville</surname>
            <given-names>I.: Software</given-names>
          </string-name>
          <string-name>
            <surname>Engineering. Addison-Wesley Longman</surname>
          </string-name>
          Publishing Co., Inc., Boston (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>