\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Intentional Software Product Line},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2012-01 2012-05-15 (revised: January 2012 15 May 2012)}
\def\TheID{\makeatother }
\def\TheDate{2012-01 2012-05-15}
\title{Intentional Software Product Line}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Dr. Sami  OUALI}

             \author[2]{Naoufel  KRAIEM}

             \author[3]{Henda BEN  GHEZALA}

             \affil[1]{  National School of Computer Sciences University}

\renewcommand\Authands{ and }

\date{\small \em Received: 15 April 2012 Accepted: 2 May 2012 Published: 15 May 2012}

\maketitle


\begin{abstract}
        


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.

\end{abstract}


\keywords{Software Product Line, variability, intentional level, comparison framework, features modeling and metamodels.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{I. INTRODUCTION}]{I. INTRODUCTION}\par
oftware product line engineering optimizes the development of individual systems by leveraging their common characteristics and managing their differences in a systematic way \hyperref[b0]{(Clements \& Northrop, 2001}). These differences are called variabilities. In software product line engineering, two kinds of variability can be distinguished: product line variability and Software variability. Software variability refers to the ability of a software system to be efficiently extended, changed, customized or configured for use in a particular context \hyperref[b1]{(Svahnberg et al., 2005)}. While product line variability describes the variation between the systems that belong to a product line \hyperref[b2]{(Coplien et al., 1998;}\hyperref[b3]{Pohl et al., 2005;}\hyperref[b5]{Kang et al., 2002)} in terms of properties and qualities, like features that are provided or requirements that are fulfilled. Defining product line variability concerns the determination of what should vary between the systems in a product line. In SPLE, single system can be built rapidly from reusable assets, such as a set of components.\par
The framework analysis which we proposed in our previous work \hyperref[b8]{(Ouali et al., 2011)} allows us to identify many drawbacks of existing SPL construction methods. In these methods, apart requirement approaches ones, the problem is the matching between users' needs and the product offered by developers. Many writers have observed that there is a "conceptual mismatch" \hyperref[b6]{(Woodfield, 1997;}\hyperref[b7]{Kaabi, 2007)}. The position adopted in this paper is to suggest a move to intention-driven SPL to bridge the gap between high level users' goals and low level software product line obtained. We present in this paper a model for intentional SPL modeling.\par
Our process is based on goal modeling, feature modeling and metamodels. Goal models model stakeholder intentions to fulfill the system-to-be. Feature modeling allows us to model the common and variable properties of product-line members throughout all stages of product-line engineering. Metamodels allow the expression of common and variable characteristics of a set of applications. A metamodel represents the concepts, relationships, and semantics of a domain.\par
This paper is organized as follows. A brief description of different concept concerning software product line and variability is presented in the next section. Our previous work, which is the comparison framework, is described in section 3. An intentional software product line model is presented in section 4. In section 5 we present our proposed process. The section 6 concludes this work with our contribution and research perspectives. 
\section[{II.}]{II.} 
\section[{SOFTWARE PRODUCT LINE AND VARIABILITY CONCEPTS}]{SOFTWARE PRODUCT LINE AND VARIABILITY CONCEPTS}\par
Software product lines are recognized as a successful approach to reuse in software development \hyperref[b0]{(Clements \& Northrop, 2001;}\hyperref[b12]{Bosch, 2000)}. The idea behind software product line is to economically exploit the commonalities between software products, but also to preserve the ability to vary the functionality between these products. These differences refer to the variability which is a key success factor in product lines and reuse. This approach is based on the undertaking of the development of a set of products as a single, coherent development activity. Indeed, products are built from a collection of artifacts from a core asset base that have been specifically designed for use. Core assets include not only the architecture and its documentation but also specifications, software components, tools? Variability is the ability of a system to be efficiently extended, changed, customized or configured for use in a particular context \hyperref[b13]{(Van Grup, 2000)}. Another definition presents variability as the ability of a system, an asset, or a development environment to support the production of a set of artifacts that differ from each other in a preplanned fashion \hyperref[b14]{(Czarnecki \& Eisenecker, 2000)}. In this definition variability means the ability of a core variations in a product line context must be anticipated.\par
The purpose of Variability modeling is to present an overview of a product line's commonality and variability. Variability modeling terms concerns also commonality modeling. The content of a variability model serves as a basis for defining variability within the artifacts that make up the product-line infrastructure as well as for configuring individual product instances and deriving them from the infrastructure.\par
SPL engineering is defined \hyperref[b14]{(Czarnecki \& Eisenecker, 2000)} by distinguishing two levels of engineering: Domain Engineering and Application Engineering as presented in Fig.  {\ref 1}. 
\section[{Fig.1 : SPL Engineering levels}]{Fig.1 : SPL Engineering levels}\par
Domain Engineering corresponds to the study of the area of product line, identifying commonalities and variabilities among products, the establishment of a generic software architecture and the implementation of this architecture. Indeed, the domain engineering consists on the construction of reusable components known as asset which will be reused for the products building.\par
Application Engineering is used to find the optimal use for the development of a new product from a product line by reducing costs and development time and improve the quality. At this level, the results of the domain engineering are used for the derivation of a particular product. This derivation corresponds to the decision-making towards the variation points.\par
In the literature, the majority of variability research concerns requirements and architecture. But some works deals with implementation, verification and validation, traceability and software product line management. The literature basically proposes methods or techniques that address only a specific portion of SPL development. 
\section[{III.}]{III.} 
\section[{COMPARISON FRAMEWORK}]{COMPARISON FRAMEWORK}\par
We have elaborated a framework to compare different approaches for the construction of SPL. The idea is to consider a central concept (SPL) on four different points of view. Defining a comparison framework has proved its effectiveness in improving the understanding of various engineering disciplines (process, requirements, information systems?) \hyperref[b9]{(Rolland, 1998;}\hyperref[b10]{Jarke \& Pohl, 1993)}. Therefore, it can be helpful for the better understanding of the field of engineering SPLs. As a result, our framework (Fig.  {\ref 1}) is presented in \hyperref[b8]{(Ouali et al., 2011)}.\par
The framework analysis allows us to identify the following main drawbacks of existing SPL construction methods. We realize that we have a lack of sufficient tool support for them and for their interactivity with their users. The SPL approaches themselves are not enough automated for deriving automatically a product from a SPL. In addition, these methods didn't cover all aspects of SPL engineering. Indeed, every method tries to focus on a particular part of SPL construction process. Finally, in these methods, apart requirement approaches ones, the problem is the matching between users' needs and the product offered by developers. Many writers have observed that there is a "conceptual mismatch" \hyperref[b6]{(Woodfield, 1997;}\hyperref[b7]{Kaabi, 2007)}. We try in the next section of this paper to resolve this last drawback by the proposal of a model for intentional SPL modeling. We try to establish the matching between users' needs and the product offered by developers by the expression of users' needs in an intentional way. 
\section[{IV. INTENTIONAL SOFTWARE PRODUCT LINE META-MODEL}]{IV. INTENTIONAL SOFTWARE PRODUCT LINE META-MODEL}\par
This section describes a meta-model synthesizing the different interesting points that we previously identified after a state-of-the-art (software product line, intention, feature?). We chose to transform this meta-model into a UML profile to facilitate the integration into UML models and to use it in our MDA approach. 
\section[{a) Meta-model Description}]{a) Meta-model Description}\par
As depicted in Fig. \hyperref[fig_1]{3}, a product line contains features. A product belongs to one product line and is composed of features. These features associated to a product must check some constraints (mutual exclusion Intentional Software Product Line 
\section[{Global Journal of Computer Science and Technology Volume XII Issue I Version I}]{Global Journal of Computer Science and Technology Volume XII Issue I Version I}\par
and require relation) throw the conflict and require relationships. The recommends relationship concerns another feature that could be pertinent.\par
An intentional software product line is a set of features captured at the business level, in business comprehensible terms and described in an intentional perspective. In this perspective, we focus on the intention it allows to achieve rather than on the functionality it performs. A feature is a set of related requirements that allows the user to satisfy an intention.\par
We have two specializations of features which are MandatoryFeature and VariantFeature. Mandatory features are features which must be present in every configuration of a product from the product line.\par
A variant feature is modeled as a set of variation point. The metamodel allows atomic variation points (Variant) or composite ones (Composite VariationPoint) for a variant feature. We use the composite pattern to compose a variation point.\par
In our meta-model, we use a part of an existing meta-model map \hyperref[b15]{(Rolland et al., 1999c)} which is a Process Model in which a non-deterministic ordering of intentions and strategies has been included. Map is a labeled directed graph with intentions as nodes and strategies as edges between intentions. A map consists of a number of sections. Each section is a triplet formed by a source intention, a target intention and a strategy. A strategy is a manner to achieve an intention.  
\section[{V. PROPOSED PROCESS}]{V. PROPOSED PROCESS}\par
To avoid the drawbacks of the existing methods, we try to propose a new process for the construction of SPL. This process is a flexible approach for automatically building SPL based on variability models. This process is based basically on goal modeling, features modeling, metamodels, constraints?\par
In our process, we try to cover domain engineering and application engineering. The domain engineering process involves the creation of core assets. In this process, our interest concerns the elicitation of intentions and strategies using the MAP for the design of users' requirements. A map is a process model expressed in a goal driven perspective which can provides a process representation system based on goals and strategies. The directed nature of the graph shows which goals can follow which one. MAP is considered as Intention-oriented process modeling which follows the human intention of achieving a goal as a force which drives the process \hyperref[b16]{(Soffer \& Rolland, 2005)}. Having represented software product line features intentionality as maps, we will proceed in our process to determine features and their composition according to the Intentional Software Product line. This approach is presented in Fig. \hyperref[fig_2]{4}. Users' intentions are captured and modeled using Map Model to obtain an SPL Model. This model contains an intentional view. Variability in intentional software product line modelling is mandatory and due to the need to introduce flexibility in intention achievement. We use features diagrams to model variability in software product line. We try to capture commonality and variability of domain and to reuse it for the derivation of a specific requirement model in application Level. We try to manage variability in SPL construction process (functions, structures, behaviors, technologies). Our strategy follows feature modeling approach, MDA approach and the managing of the constraints. We base our work on the creation of features models representing the SPL structure. We use state machine to model the behavior in the SPL. This process is based on the automatic transformation of models until obtaining executable applications. The process is flexible because SPL developer has a lot of possibilities for the creation of SPL and its constraints. It permits the generation of a flexible SPL suitable to the users' requirements elicited in the beginning of the creation process and new ones. 
\section[{VI.}]{VI.} 
\section[{CONCLUSION}]{CONCLUSION}\par
In this paper, our contribution was the proposal of a model combining software product line, variability, requirements and intentions. This suggested model clarifies the notion of an intentional software product line to model SPL in intentional context. It was build to respond to the following purpose: to focus on the intention it allows to achieve rather than on the functionality it performs. An intentional software product line is captured at the business level, in business comprehensible terms and described in an intentional perspective. This model will be useful to improve the method used for software product line construction by avoiding the conceptual mismatch. We try to establish the matching between users' needs and the product offered by developers by the expression of users' needs in an intentional way.\par
In this paper, we have presented a proposal to manage variability during the SPLs construction process using a MAP for goals modeling, features diagrams allows us to model the common and variable properties of product-line members throughout all stages of product-line engineering, metamodels allow the expression of common and variable characteristics of a set of applications.\par
Our future work will be the proposal of a tool support to improve interactivity with users and to cover the overall lifecycle of SPL. This tool support will be based on Eclipse plug-in for feature modeling using the Eclipse Modeling Framework (EMF), which significantly reduced our development effort. Our tool support is based on generative development for goal modeling, feature modeling and metamodels. Integrating goals modeling, feature modeling and metamodels as part of a development environment helps to optimally support modeling variability in different artifacts including implementation code, models, documentation, development process guidance...\begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Fig. 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{3}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Fig. 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Fig. 4 :}\end{figure}
 			\footnote{January 2012© 2012 Global Journals Inc. (US)} 			\footnote{© 2012 Global Journals Inc. (US) Global Journal of Computer Science and Technology Volume XII Issue I Version I} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Conf]{b11}\label{b11} 	 		\textit{},  		 			Software Conf 		.  		Springer Verlag.  	 
\bibitem[Pohl et al. ()]{b3}\label{b3} 	 		\textit{},  		 			K Pohl 		,  		 			G Böckle 		,  		 			F Van Der Linden 		.  		2005.  	 
\bibitem[Rolland ()]{b9}\label{b9} 	 		‘A Comprehensive View of Process Engineering’.  		 			C Rolland 		.  	 	 		\textit{Proceeding of the 10th International Conference CAiSE'98},  				 			C Pernici,  			Thanos 		 (ed.)  		 (eeding of the 10th International Conference CAiSE'98Pisa, Italie)  		1998. Springer Verlag. 1413 p. .  	 
\bibitem[Ouali et al. ()]{b8}\label{b8} 	 		‘A Flexible Process for SPL construction’.  		 			S Ouali 		,  		 			N Kraïem 		,  		 			H Ben Ghezala 		.  	 	 		\textit{Journal of Computer Science and Engineering}  		2011. 8  (1) .  	 
\bibitem[Rolland et al. ()]{b15}\label{b15} 	 		‘A Multi-Model View of Process Modelling’.  		 			C Rolland 		,  		 			N Prakash 		,  		 			A Benjamen 		.  	 	 		\textit{Requirements Engineering Journal}  		1999c. 4  (4)  p. .  	 
\bibitem[Svahnberg et al. ()]{b1}\label{b1} 	 		‘A taxonomy of variability realization techniques’.  		 			M Svahnberg 		,  		 			J Van Gurp 		,  		 			J Bosch 		.  	 	 		\textit{Software Practice \& Experience}  		2005. 35  (8)  p. .  	 
\bibitem[Soffer and Rolland ()]{b16}\label{b16} 	 		‘Combining Intention-Oriented and State-Based Process Modelling’.  		 			P Soffer 		,  		 			C Rolland 		.  	 	 		\textit{Proceedings of the International Conference on ER'05},  		LNCS  		 (the International Conference on ER'05)  		2005. p. .  	 
\bibitem[Coplien et al. ()]{b2}\label{b2} 	 		‘Commonality and variability in software engineering’.  		 			J Coplien 		,  		 			D Hoffman 		,  		 			D Weiss 		.  	 	 		\textit{IEEE Software}  		1998. 15  (6)  p. .  	 
\bibitem[Czarnecki and Eisenecker ()]{b14}\label{b14} 	 		 			K Czarnecki 		,  		 			W Eisenecker 		.  		\textit{Generative Programming: Methods, Tools, and Applications},  				2000. Addison-Wesley.  	 
\bibitem[Bosch ()]{b12}\label{b12} 	 		\textit{Design \& Use of Software Architectures, Adopting and Evolving a product-line approach},  		 			J Bosch 		.  		2000. Addison-Wesley.  	 
\bibitem[Kang et al. ()]{b5}\label{b5} 	 		‘Featureoriented project line engineering’.  		 			K C Kang 		,  		 			J Lee 		,  		 			P Donohoe 		.  	 	 		\textit{IEEE Software}  		2002. 19  (4)  p. .  	 
\bibitem[Jarke and Pohl ()]{b10}\label{b10} 	 		‘Requirements Engineering: An Integrated View of Representation, Process and Domain’.  		 			M Jarke 		,  		 			K Pohl 		.  	 	 		\textit{Procedings 4th Euro},  				 (edings 4th Euro)  		1993.  	 
\bibitem[Software Product Line Engineering: Foundations, Principles and Techniques]{b4}\label{b4} 	 		\textit{Software Product Line Engineering: Foundations, Principles and Techniques},  		Springer.  	 
\bibitem[Clements and Northrop ()]{b0}\label{b0} 	 		\textit{Software Product Lines: Practices and Patterns},  		 			P Clements 		,  		 			L Northrop 		.  		2001. Boston, MA: Addison-Wesley.  	 
\bibitem[Van Grup (2000)]{b13}\label{b13} 	 		‘Sweden: University of Groningem’.  		 			J Van Grup 		.  	 	 		\textit{Variability in Software Systems, the key to software reuse (Thesis)},  				2000. January 2012.  	 
\bibitem[Woodfield ()]{b6}\label{b6} 	 		\textit{The Impedance Mismatch between Conceptual Models and Implementation Environments, ER'97 Workshop on Behavioral Models and Design Transformations: Issues and Opportunities in Conceptual Modeling},  		 			S N Woodfield 		.  		1997. UCLA, Los Angeles, California.  	 
\bibitem[Kaabi ()]{b7}\label{b7} 	 		\textit{Une Approche Méthodologique pour la Modélisation Intentionnelle des Services et leur Opérationnalisation (Thèse de doctorat)},  		 			R Kaabi 		.  		2007.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
