<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Goal-Based Self-Contextualization</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Raian</forename><surname>Ali</surname></persName>
							<email>raian.ali@disi.unitn.it</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Trento -DISI</orgName>
								<address>
									<postCode>38100</postCode>
									<settlement>Povo</settlement>
									<region>Trento</region>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Fabiano</forename><surname>Dalpiaz</surname></persName>
							<email>fabiano.dalpiaz@disi.unitn.it</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Trento -DISI</orgName>
								<address>
									<postCode>38100</postCode>
									<settlement>Povo</settlement>
									<region>Trento</region>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Paolo</forename><surname>Giorgini</surname></persName>
							<email>paolo.giorgini@disi.unitn.it</email>
							<affiliation key="aff0">
								<orgName type="institution">University of Trento -DISI</orgName>
								<address>
									<postCode>38100</postCode>
									<settlement>Povo</settlement>
									<region>Trento</region>
									<country key="IT">Italy</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Goal-Based Self-Contextualization</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">5827571732E010AAA223A19308269974</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T05:18+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>System self-contextualizability is the system ability to autonomously adapt its behavior to the uncontrollable relevant context to keep its objectives satisfied. Self-contextualizable system must have alternative behaviors each fitting to a set of contexts. We propose to start considering context at the level of requirements engineering, adopting Tropos goal model to express requirements and complementing it with our proposed context analysis. We define variation points on goal model where a context-based decision might need to be taken, and propose constructs to analyze context. While goal analysis provides constructs to hierarchically analyze goals and discover alternative sets of tasks to be executed to satisfy a goal, our proposed context analysis provides constructs to hierarchically analyze context and discover alternative sets of facts to be monitored to verify a context.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Self-contextualizable software is able to monitor context and to autonomously adapt to it in order to keep its design objectives satisfied. This mainly means that the developed software has a space of alternative behaviors each fitting to a specific context. Consequently, and to allow for a systematic behavior adaptation to context, we need to specify the relation between each behavior and the context where such behavior is adoptable.</p><p>Context modeling, (e.g. <ref type="bibr" target="#b0">[1]</ref>), concerns finding modeling constructs to represent context, but there is still a gap between the context models and the software behavior models, i.e. the relation between context and its use is missed. We need to reduce such gap and to allow for answering questions like: "how do we decide the relevant context?", "why do we need context?" and "how does context influence software and user behavior adaptation?". Salifu et al. <ref type="bibr" target="#b1">[2]</ref> investigate the use of problem descriptions to represent and analyze variability in context-aware software; the work recognizes the link between requirements and context as a basic step to design context aware systems.</p><p>Goal analysis (i* <ref type="bibr" target="#b2">[3]</ref>, Tropos <ref type="bibr" target="#b3">[4]</ref>, and KAOS <ref type="bibr" target="#b4">[5]</ref>), provides a way of analyzing high level goals to discover and represent alternative sets of tasks that can be executed to achieve such goals. Goal model is used to represent the rationale of both humans and software systems, and is a mainstream technique for requirements engineering and helps for representing software design alternatives. These features are important for self-contextualizable software that must have alternatives and a rationale that reflects users and software adaptation to context in order to adopt a useful execution course <ref type="bibr" target="#b5">[6]</ref>. From a goal perspective, a self-contextualiazable software is assigned a set of goals and has to keep them satisfied in a way tailored to the context. However, there is still a gap between goal analysis that discovers the space of alternatives to reach a goal, and the context where each alternative is adoptable.</p><p>Customizing goal models to fit to user skills and preferences was studied in <ref type="bibr" target="#b6">[7,</ref><ref type="bibr" target="#b7">8]</ref>. The selection between goal satisfaction alternatives is based on one dimension of context, i.e. user skills, related to the executable tasks of the goal hierarchy, and on user preferences which are expressed over softgoals. <ref type="bibr">Lapouchnian et al. [9]</ref> propose techniques to design autonomic software based on an extended goal modeling framework, but the relation with the context is not focused on. Liaskos et al <ref type="bibr" target="#b9">[10]</ref>, study the variability modeling under the requirements engineering perspective and propose a classification of the intentional variability when Or-decomposing a goal. Differently, we focus on context variability, i.e. the unintentional variability, which influences the applicability and appropriateness of each goal satisfaction alternative.</p><p>In this paper, we extend our previous goal modeling framework <ref type="bibr" target="#b10">[11]</ref><ref type="bibr" target="#b11">[12]</ref><ref type="bibr" target="#b12">[13]</ref> to support the self-contextualizability at the goal level. We use goal analysis in conjunction with our proposed context analysis to build self-contextualizable goal models. We provide constructs to hierarchically analyze context at the variation points of Tropos goal model. The proposed hierarchial context analysis will help us to identify the data the system has to monitor to verify each context, i.e. it helps to identify the monitoring requirements. In what follows, we describe our vision and proposed framework.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Self-Contextualizable Goal Model</head><p>Self-contextualization, from a goal oriented perspective, is the autonomous selection between goal satisfaction alternatives to fit to the variable context. The basic idea is to keep the goals satisfied in different contexts through an adaptable course of execution. Here we give four principles for self-contextualizability from a goal perspective: Context effects: context influences the set of satisfiable goals, the need to satisfy each goal, the possible goal satisfaction alternatives, and the quality of each alternative. Context is not adaptable: context does not adapt to users and software; rather, users and software have to adapt to context to satisfy, and/or to better satisfy, their goals. Users contextualizability comes first: defining software self-contextualizability has to be based on how its users behave in different contexts. We need to analyze users goals to discover a space of satisfaction alternatives, and to analyze how context influences users in deciding and choosing among different alternatives for satisfying their goals. Self-contextulaizable software has to reflect users adaptation to the context first, and then adapt itself to context. Contextualization times: software contextualization can be done while deploying the software, that supports different alternatives, in a certain environment to adapt it to some contextual characteristics that never change, i.e. some alternatives are not usable and redundant in that environment. Other variable characteristics necessitate keeping different alternatives and adopting one of them at runtime based on which context is valid. In both cases, the systematic contextualization needs specifying the relation between goal alternatives and context.</p><p>Fig. <ref type="figure" target="#fig_0">1</ref> represents a partial goal model for a promotion information system that will interact with customers and sales staff, through their PDAs, for promoting products with a number of alternatives. To make it self-contextualizable, we need to explicitly represent the relation between these alternatives and context. Contexts can be related to the following variation points of Tropos goal model: We need to analyze context to discover, represent, and to agree on how it can be verified. Differently from the research in context modeling (see the survey <ref type="bibr" target="#b13">[14]</ref>), we do not provide an otology or a modeling language for representing context, but modeling constructs to hierarchically analyze context. We specify context by a high level statement and start to refine it to get by the end alternative sets of facts that are definable on monitorable data. The truth value of facts is bottom-up propagated to define the truth value of the high level statement (see Fig. <ref type="figure" target="#fig_1">2</ref>). We also need to keep track of the elements of environment the different goals, tasks, statements and facts are concerned with. To do this, we propose to parameterize goals, tasks, statements, and facts. Parametrization is necessary to decide and make it explicit the domain of discourse of goals, tasks, statements, and facts, i.e. the elements of the environment under discussion.</p><p>To better explain the approach, let us consider the Or-alternative " Promote by crossselling the product to customer" which concerns the elements: product, and customer.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>The parameterized goal is "Promote by cross-selling the product [p] to customer [c]".</head><p>A simplified analysis of the context where this alternative is adoptable is shown in Fig. <ref type="figure" target="#fig_1">2</ref>.a. Moreover, by analyzing the elicited facts, the analyst can extract the conceptual data model the monitoring system has to instantiate to make facts validation possible. The analysis of the last context facts leads to the conceptual data model of Fig. <ref type="figure" target="#fig_1">2</ref>  We provide a set of modeling constructs to analyze high-level context statements and to elicit the monitorable facts that are used to assign truth values to statements. Context, the reification of the environment that surrounds the system and influences it, can be monitored but not controlled by the system itself <ref type="bibr" target="#b14">[15]</ref>. Under this assumption, systems cannot change the context but should adapt to it for satisfying users objectives.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Definition 1 (Fact) a boolean predicate specifying a current or a previous context, whose truth value can be computed objectively.</head><p>The objective method to compute a fact truth value requires monitoring some characteristics and history of a set of relevant environment elements.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Definition 2 (Statement) a boolean predicate specifying a current or a previous context, whose truth value can not be computed objectively.</head><p>Statement verification could not be objectively done because the system is not able to monitor and get all the data needed to compute the truth value of a statement, or because there could be no consensus about the way of knowing the truth value of a statement. Anyhow, to handle such problem we adopt a relaxed confirmation relation between facts, which are objectively computable by definition, and statements, in order to assign truth values to statements. We call this relation "help" and define it as following:</p><formula xml:id="formula_0">Definition 3 (Help) Let f be a fact, s be a statement. help(f, s) ⇐⇒ f → s</formula><p>The relation help is strongly subjective, since different stakeholders could define different help relations for the same statement. Our proposed hierarchical context analysis has the potential to make a context (i) more understandable for the stakeholders, (ii) easily modifiable as it is not given as one monolithic block, and (iii) more reusable as parts of the statement analysis hierarchy can be also used for other variation points or other stakeholders context specifications. Moreover, the analysis justifies why the monitoring system has to capture environmental data, as such data are needed to verify facts that in turn confirm or disapprove statements that are needed to make a decision at the variation points of the goal model. Specifying for each fact the related fragments of the data conceptual model is useful for purpose of tracking. For example, if for some reason, a group of stakeholders decided to drop, to alter, or to reuse one alternative, statement, or fact, we still can track which fragments in the conceptual data model could be influenced.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Conclusions and Future Work</head><p>In this paper, we have introduced a goal-oriented framework for self-contextualizable systems. We have discussed the self-contextualizability from goal-based perspective. We have proposed the association between goal satisfaction alternatives and context. In turn, context is defined through statement analysis that elicits the alternative sets of facts the system has to validate on monitorable data so to confirm the high level statements. As future work, we will define models covering all development phases of selfcontextualizable software and a process to facilitate the development of high quality self-contextualizable software. We also want to extend the formalization and reasoning mechanisms we proposed in <ref type="bibr" target="#b10">[11,</ref><ref type="bibr" target="#b11">12]</ref> to fit to the modeling framework introduced in this paper. We will work on complex case studies in order to better validate our approach. Finally, statements and facts suffer of interaction problems; therefore, supporting tools and reasoning techniques should be proposed to support the design and verification of models.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 1 .</head><label>1</label><figDesc>Fig. 1. A partial goal model of the promotion scenario</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. Statement analysis (a). Correspondent data conceptual model (b).</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>.b.</figDesc><table><row><cell>A</cell><cell cols="4">that customer [c] already has give more value to a related product [rp] product to promote [p] in mall [m] can</cell></row><row><cell cols="2">[c] does not already have [p]</cell><cell cols="2">[p] has a common use with [rp]</cell><cell>[c] already has [rp]</cell></row><row><cell>[c] did not get [p] from [m] recently</cell><cell></cell><cell>[p]compleme nts [rp] functionality</cell><cell cols="2">[p] and [rp] usually sold together</cell></row><row><cell>[c] did not buy [p] from [m] recently</cell><cell></cell><cell>[p] is not in cart of [c]</cell><cell cols="2">[c] bought [rp] from [m] recently</cell><cell>[rp] in the cart of [c]</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Definition 4 (And-decomposition)</head><label></label><figDesc>Let {s, s 1 , . . . , s n }, n ≥ 2 be statements (facts). and decomposed(s, {s 1 , . . . , s n }) ⇐⇒ s 1 ∧ . . . ∧ s n → s Let {s, s 1 , . . . , s n }, n ≥ 2 be statements (facts). or decomposed(s, {s 1 , . . . , s n }) ⇐⇒ ∀i ∈ {1, . . . , n}, s i → s Here we give some examples to illustrate the previous concepts:-"two products, [p1] and [p2], are usually sold together" is a fact the system can verify through checking the sales record of all customers and check if the two products are often sold together. -"customer [c] is interested in the product [p]" is a statement since the system can not objectively compute its truth value. This statement can be Or-decomposed into "customer [c] is behaviorally interested in product [p]" and "customer [c] However both facts do not ensure that the customer does not have the product (e.g., the system cannot verify if the customer was given the product as a gift, or bough it from another mall).</figDesc><table><row><cell>evidence of the first substatement through the help of the fact "[c] holds [p] for long time", or the fact "[c] comes to [p] area so often". The second substatement can be verified through the fact "[c] buys periodically [p]" or the fact "[c] buys usually of [p] category". -"customer [c] does not have the product [p]" is a statement that can be verified through the fact "[c] did not get [p] recently from the mall [m]", that is And-decomposed into "[c] did not buy [p] recently from [m]" and "[c] does not have Definition 5 (Or-decomposition) is historically interested in product [p]" substatements. The system can get some [p] in his/her shopping cart".</cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" xml:id="foot_0">Proceedings of CAiSE Forum 2009</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgement</head><p>This work has been partially funded by EU Commission, through the SERENITY, and COMPAS projects, and by the PRIN program of MIUR under the MEnSA project. We would also like to thank Prof. Jaelson Brelaz de Castro for the valuable discussion we had about this work.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">A software engineering framework for context-aware pervasive computing</title>
		<author>
			<persName><forename type="first">K</forename><surname>Henricksen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Indulska</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. Second IEEE Intl. Conference on Pervasive Computing and Communications (PerCom&apos;04)</title>
				<meeting>Second IEEE Intl. Conference on Pervasive Computing and Communications (PerCom&apos;04)</meeting>
		<imprint>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page">77</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Specifying monitoring and switching problems in context</title>
		<author>
			<persName><forename type="first">M</forename><surname>Salifu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Yu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Nuseibeh</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. 15th Intl. Conference on Requirements Engineering (RE&apos;07)</title>
				<meeting>15th Intl. Conference on Requirements Engineering (RE&apos;07)</meeting>
		<imprint>
			<date type="published" when="2007">2007</date>
			<biblScope unit="page" from="211" to="220" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<author>
			<persName><forename type="first">E</forename><surname>Yu</surname></persName>
		</author>
		<title level="m">Modelling strategic relationships for process reengineering</title>
				<imprint>
			<date type="published" when="1995">1995</date>
		</imprint>
		<respStmt>
			<orgName>University of Toronto</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">Ph.D. Thesis</note>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Tropos: An agentoriented software development methodology</title>
		<author>
			<persName><forename type="first">P</forename><surname>Bresciani</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Perini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Giorgini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Giunchiglia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Mylopoulos</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Autonomous Agents and Multi-Agent Systems</title>
		<imprint>
			<biblScope unit="volume">8</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="203" to="236" />
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Goal-directed requirements acquisition</title>
		<author>
			<persName><forename type="first">A</forename><surname>Dardenne</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Van Lamsweerde</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Fickas</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Science of computer programming</title>
		<imprint>
			<biblScope unit="volume">20</biblScope>
			<biblScope unit="issue">1-2</biblScope>
			<biblScope unit="page" from="3" to="50" />
			<date type="published" when="1993">1993</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Requirements monitoring in dynamic environments</title>
		<author>
			<persName><forename type="first">S</forename><surname>Fickas</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Feather</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Second IEEE International Symposium on Requirements Engineering</title>
				<meeting>the Second IEEE International Symposium on Requirements Engineering<address><addrLine>Washington, DC, USA</addrLine></address></meeting>
		<imprint>
			<publisher>IEEE Computer Society</publisher>
			<date type="published" when="1995">1995</date>
			<biblScope unit="page">140</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Requirements analysis for customizable software goalsskills-preferences framework</title>
		<author>
			<persName><forename type="first">B</forename><surname>Hui</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Liaskos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Mylopoulos</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE Computer Society</title>
		<imprint>
			<biblScope unit="page" from="117" to="126" />
			<date type="published" when="2003">2003</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<monogr>
		<title level="m" type="main">Representing and reasoning with preference requirements using goals</title>
		<author>
			<persName><forename type="first">S</forename><surname>Liaskos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Mcilraith</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Mylopoulos</surname></persName>
		</author>
		<ptr target="ftp://ftp.cs.toronto.edu/pub/reports/csrg/542" />
		<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
		<respStmt>
			<orgName>Dept. of Computer Science, University of Toronto</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">Technical report</note>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Requirements-driven design of autonomic application software</title>
		<author>
			<persName><forename type="first">A</forename><surname>Lapouchnian</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Yu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Liaskos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Mylopoulos</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. 2006 conference of the Center for Advanced Studies on Collaborative research (CASCON &apos;06)</title>
				<meeting>2006 conference of the Center for Advanced Studies on Collaborative research (CASCON &apos;06)</meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2006">2006</date>
			<biblScope unit="page">7</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">On goal-based variability acquisition and analysis</title>
		<author>
			<persName><forename type="first">S</forename><surname>Liaskos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Lapouchnian</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Yu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Yu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Mylopoulos</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. 14th IEEE Intl. Requirements Engineering Conference (RE&apos;06)</title>
				<meeting>14th IEEE Intl. Requirements Engineering Conference (RE&apos;06)</meeting>
		<imprint>
			<date type="published" when="2006">2006</date>
			<biblScope unit="page" from="76" to="85" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Location-based variability for mobile information systems</title>
		<author>
			<persName><forename type="first">R</forename><surname>Ali</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Dalpiaz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Giorgini</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CAiSE</title>
		<title level="s">Lecture Notes in Computer Science</title>
		<editor>
			<persName><forename type="first">Z</forename><surname>Bellahsene</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">M</forename><surname>Léonard</surname></persName>
		</editor>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2008">2008</date>
			<biblScope unit="volume">5074</biblScope>
			<biblScope unit="page" from="575" to="578" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Modeling and analyzing variability for mobile information systems</title>
		<author>
			<persName><forename type="first">R</forename><surname>Ali</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Dalpiaz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Giorgini</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ICCSA (2</title>
		<title level="s">Lecture Notes in Computer Science</title>
		<editor>
			<persName><forename type="first">O</forename><surname>Gervasi</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">B</forename><surname>Murgante</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">A</forename><surname>Laganà</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">D</forename><surname>Taniar</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">Y</forename><surname>Mun</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">M</forename><forename type="middle">L</forename><surname>Gavrilova</surname></persName>
		</editor>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2008">2008</date>
			<biblScope unit="volume">5073</biblScope>
			<biblScope unit="page" from="291" to="306" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Location-based software modeling and analysis: Troposbased approach</title>
		<author>
			<persName><forename type="first">R</forename><surname>Ali</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Dalpiaz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Giorgini</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="s">Lecture Notes in Computer Science</title>
		<editor>Li, Q., Spaccapietra, S., Yu, E., Olivé, A.</editor>
		<imprint>
			<biblScope unit="volume">5231</biblScope>
			<biblScope unit="page" from="169" to="182" />
			<date type="published" when="2008">2008</date>
			<publisher>Springer</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">A context modeling survey</title>
		<author>
			<persName><forename type="first">T</forename><surname>Strang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Linnhoff-Popien</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Workshop on Advanced Context Modelling, Reasoning and Management as part of UbiComp</title>
				<imprint>
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">A framework for requirements engineering for context-aware services</title>
		<author>
			<persName><forename type="first">A</forename><surname>Finkelstein</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Savigni</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Street</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proc. 1st Int. Workshop on From Software Requirements to Architectures (STRAW)</title>
				<meeting>1st Int. Workshop on From Software Requirements to Architectures (STRAW)</meeting>
		<imprint>
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
