<!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>Invited Keynote: Teaching and Integrating i* in a Conceptual Schema- Centric Development</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Oscar Pastor</string-name>
          <email>opastor@dsic.upv.es</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>D en Métodos de Producción de Software (PROS)</institution>
          ,
          <country country="ES">Spain</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Universitat Politècnica de València, Centro de I</institution>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2015</year>
      </pub-date>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Teaching and Integrating i* in a Conceptual Schema-Centric Development
Conceptual-Schema Centric Development (CSCD), Extreme Non-Programming
(XNP), Conceptual Programming… are part of the many current approaches that
advocate the use of Conceptual Models as the very basic artifact of a sound and
effective software production process. But if Conceptual Models (CM) act as a such
essential sofware artefact, a basic question has to be answered: where do CMs come
from? Being i* a well-known, widely-accepted approach for goal-oriented
requirements engineering, using i* as an starting point to guide a CSCD software
process appears to be a good decission. This talk will explore this approach. Using i*
to represent organizational, actor-oriented and goal-based requirements, and to assure
software traceability by transforming i* models into executable conceptual models
conforms a methodological challenge to link requirements with application code.
Additionally, the correct use of i* models is reinforced by the use of precise teaching
practices whose experience in our teaching context will also be discussed.</p>
    </sec>
  </body>
  <back>
    <ref-list />
  </back>
</article>