<?xml version="1.0" encoding="UTF-8"?>
<article article-type="research-article" xml:lang="en" xmlns:xlink="http://www.w3.org/1999/xlink">
<front>
<journal-meta>
<journal-id journal-id-type="publisher">global-journal-of-computer-science-and-technology</journal-id>
<journal-title-group>
<journal-title>Global Journal of Computer Science and Technology</journal-title>
</journal-title-group>
<issn publication-format="print">0975-4350</issn>
<issn publication-format="electronic">0975-4172</issn>
<publisher><publisher-name>Global Journals Publishing Group Incorporated</publisher-name></publisher>
<self-uri xlink:href="https://globaljournals.org/journal-seo-export/jats/73961.xml" />
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">73961</article-id>
<title-group>
<article-title>Security requirement engineering for Intentional Software Product Line</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author"><name><surname>OUALI</surname><given-names>Dr. Sami</given-names></name><xref ref-type="aff" rid="aff1" />
</contrib>
<contrib contrib-type="author"><name><surname>KRAIEM</surname><given-names>Naoufel</given-names></name></contrib>
<contrib contrib-type="author"><name><surname>GHEZALA</surname><given-names>Henda BEN</given-names></name></contrib>
</contrib-group>
<aff id="aff1">TUNISIA, National School of Computer Sciences University</aff>
<pub-date publication-format="electronic" date-type="pub" iso-8601-date="2012-05-15">
<day>15</day>
<month>05</month>
<year>2012</year>
</pub-date>
<volume>12</volume>
<issue>1</issue>
<fpage>27</fpage>
<lpage>31</lpage>
<abstract><p>Software product line engineering optimizes the development of individual systems by leveraging their common characteristics and managing their differences in a systematic way. These differences are called variabilities. We argue that it is difficult for business people to fully benefit of the SPL if it remains at the software level. The paper proposes a move towards a description of software product line in intentional terms, i.e. intentions and strategies to achieve business goals. We present ISPL, the model to describe intentional Software Product Line. Thereafter, we propose our process to show how to use this model.</p></abstract>
<kwd-group kwd-group-type="author-generated">
<kwd>Software Product Line</kwd>
<kwd>variability</kwd>
<kwd>intentional level</kwd>
<kwd>comparison framework</kwd>
<kwd>features modeling and metamodels.</kwd>
</kwd-group>
<self-uri content-type="pdf" xlink:href="https://globaljournals.org/GJCST_Volume12/5-Intentional-Software-Product-Line.pdf" />
<self-uri content-type="html" xlink:href="https://globaljournals.org/scholarly-articles/security-requirement-engineering-for-intentional-software-product-line/" />
</article-meta>
</front>
<body>
<sec>
<title>Full Text</title>
<p>Software product line engineering optimizes the development of individual systems by leveraging their common characteristics and managing their differences in a systematic way. These differences are called variabilities. We argue that it is difficult for business people to fully benefit of the SPL if it remains at the software level. The paper proposes a move towards a description of software product line in intentional terms, i.e. intentions and strategies to achieve business goals. We present ISPL, the model to describe intentional Software Product Line. Thereafter, we propose our process to show how to use this model.</p>
</sec>
</body>
</article>