<?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">Towards Multi-decision-maker Requirements Prioritisation via Multi-Objective Optimisation</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Fitsum</forename><forename type="middle">Meshesha</forename><surname>Kifetew</surname></persName>
							<email>kifetew@fbk.eu</email>
							<affiliation key="aff0">
								<orgName type="institution">Fondazione Bruno Kessler</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Angelo</forename><surname>Susi</surname></persName>
							<email>susi@fbk.eu</email>
							<affiliation key="aff0">
								<orgName type="institution">Fondazione Bruno Kessler</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Denisse</forename><surname>Muñante</surname></persName>
							<email>munante@fbk.eu</email>
							<affiliation key="aff0">
								<orgName type="institution">Fondazione Bruno Kessler</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Anna</forename><surname>Perini</surname></persName>
							<email>perini@fbk.eu</email>
							<affiliation key="aff0">
								<orgName type="institution">Fondazione Bruno Kessler</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Alberto</forename><surname>Siena</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">Delta Informatica</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Paolo</forename><surname>Busetta</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">Delta Informatica</orgName>
							</affiliation>
						</author>
						<title level="a" type="main">Towards Multi-decision-maker Requirements Prioritisation via Multi-Objective Optimisation</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">1E426AE21CB3268BDF432392D5BB93A0</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T06:10+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>
			<textClass>
				<keywords>
					<term>Requirements prioritisation</term>
					<term>multi-decision-maker prioritisation</term>
					<term>evolutionary algorithms</term>
					<term>multi-objective optimisation</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Requirements prioritisation is a key decision making activity of the software development process, which relies on the capability of different decision-makers to identify the optimal candidate rankings of the requirements, in order to be able to perform a strategic choice among them. In this paper, we formulate such multi-decision-maker requirements prioritisation as a multi-objective optimisation problem, and outline a solution that takes advantage of metaheuristic algorithms. The proposed solution allows different decision-makers to specify their rankings according to a set of prioritisation criteria, it then synthesises them into a set of Pareto optimal global rankings. The ultimate choice of the prioritisation of the requirements would be made upon a focused analysis of the trade-offs amongst the solutions on the Pareto frontier.</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>Requirements prioritisation is an important decision-making activity in the software development process that comes into the scene when the needs and desires of customers must meet the delivery capacity of the development team <ref type="bibr" target="#b0">[1]</ref>. Once requirements have been successfully gathered, constraints and limitations create a trade-off between the opportunity gained from implementing the largest possible part of them, and the disadvantage of attempting to implement too many of them. In this case, knowing which are the best candidate requirements worthy of passing to the implementation phase allows to reduce the risk of failing to deliver the product.</p><p>Practitioners mostly carry out the requirements prioritisation activity with traditional approaches, such as focus groups. Several approaches have also been proposed to guide practitioners perform requirements prioritisation in a structured way <ref type="bibr" target="#b0">[1]</ref>. A variety of automatic techniques to reduce the human effort in this process have been defined, which use, for example, the Analytical Hierarchy Process (AHP) <ref type="bibr" target="#b14">[15,</ref><ref type="bibr" target="#b1">2]</ref> method, and approaches based on Machine learning <ref type="bibr" target="#b10">[11]</ref>, or Constraint Satisfaction <ref type="bibr" target="#b9">[10]</ref>. However, such activity can become a complex decision-making problem in the presence of certain conditions, e.g., (a) the number of candidate requirements increases, (b) the number of criteria for the prioritisation increase, (c) the dependencies between requirements are not negligible, or (d) different stakeholders are involved in the decision-making process, with their specific roles and competences. In this situation, the challenge becomes that of identifying the set of global rankings that better meet the various perspectives, thus ensuring the optimality of the final requirements prioritisation decision.</p><p>We observed examples of this situation in two small-medium companies in the context of the SUPERSEDE<ref type="foot" target="#foot_0">3</ref> project, a project focusing on feedback-driven adaptation and evolution of software systems. The first company is SEnerCon, a German company working in the domain of energy efficiency management, providing online applications in support of household energy saving. SEnerCon reports that when major innovation of their products need to be planned, different actors are relevant in prioritising the candidate requirements that might include the new ones that have been identified along the funding opportunities <ref type="bibr" target="#b8">[9]</ref>.</p><p>The second company is Delta, an Italian company working in serious gaming for professional training. As part of an industrial project, called PRESTO <ref type="bibr" target="#b12">[13]</ref>, Delta is working with researchers in the area of serious gaming and interaction design, and with domain experts to develop a virtual reality application for training in emergency management. Also in this case, actors with different roles and expertise contribute to prioritise the requirements to be considered for development.</p><p>In such situations, each actor involved in the prioritisation process has his/her own view regarding the priorities of the requirements, depending on their expertise and goals. Furthermore, these views of the various actors are typically of conflicting nature. For instance, developers may tend to give higher priorities to requirements that could be implemented with less effort, while experts from management may give higher priorities to requirements that would bring higher customer satisfaction (even if they incur higher development effort). Hence, the problem then becomes how to reconcile these individual views on the priorities into a final prioritisation of the requirements. We refer to the human actors involved in such a process, by providing their own preferences regarding the prioritisation of the requirements, as decision-makers (DMs); and we refer to the problem as a Multi-decision-maker Requirements Prioritisation problem.</p><p>In this paper, we formulate the Multi-decision-maker Requirements Prioritisation problem as a multi-objective optimisation problem, and propose an approach that uses Evolutionary Algorithms (EA) to find optimal solutions to it. Given a set of rankings for the candidate requirements, which are made by different experts along multiple criteria, the proposed method allows to synthesise global requirements prioritisations located on a Pareto optimal frontier, thus supporting the decision-maker by providing him/her with a view on alternative optimal requirements prioritisations.</p><p>The main contributions of this paper include: (i ) a generic formulation of the Multi-decision-maker Requirements Prioritisation problem; (ii ) an approach based on multi-objective optimisation for finding optimal solutions to this problem.</p><p>The rest of this paper is organised as follows: in Section 2, the formulation of the problem is given. The proposed approach for Multi-decision-maker Requirements Prioritisation is outlined in Section 3. The related works are discussed in 4. Finally, conclusions are presented in Section 5.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Problem Formulation</head><p>In a generic requirements prioritisation process, multiple decision-makers involved in a software project express independently their own priority list. Each decision-maker has a relative weight with respect to the other decision-makers, depending on aspects such as his/her role, expertise and so on. Moreover, any number of evaluation criteria, each with its own weight with respect to the expected final decision, can be used to perform the prioritisation. These criteria could represent positive (values) or negative (costs) evaluations about a given prioritisation of requirements, what is important here is that decision-makers are not obliged to summarise their positive (or negative) considerations along one single criterion. Furthermore, the requirements to be prioritised have their own characteristics, which must be taken into consideration when deciding on the final ranking, such as dependencies among requirements.</p><p>The Multi-decision-maker Requirements Prioritisation problem consists of finding the best ranking that takes into account all the individual rankings of the various decision-makers. Reaching consensus regarding the final ranking of the requirements out of the individual rankings, given by the decision-makers, involves: (i) identifying the alternative global rankings that can be drawn from the decision-makers' opinions; and (ii) selecting the final ranking, through a decision process that takes into account additional contextual and strategic information. While the final decision remains a strategic action, the Multi-decision-maker Requirements Prioritisation problem concerns supporting the identification of the optimal rankings.</p><p>In summary, given:</p><p>a set of n decision-makers who providing their prioritisations; a set of m requirements to be prioritised (not necessarily independent); a set of dependencies where (R i → R j ) implies that requirement R i depends on requirement R j ; a set of k criteria along which the prioritisation is to be performed; weights corresponding to each criterion; weights corresponding to each decision-maker for each criterion; the prioritisations of each decision-maker with respect to each criterion; the Multi-decision-maker Requirements Prioritisation problem consists of finding the final prioritisation (ranking) of requirements with the minimum possible distance from the individual prioritisations (rankings) of all decision-makers, while respecting the constraints imposed by the dependencies. Distance represents a quantification of the dissimilarity between rankings.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Multi-Decision-Maker Prioritisation</head><p>The problem formulation presented in the previous section evidences the inherent multi-objective nature of the problem. In fact, the optimal solution to the problem involves trade-offs in different directions, in particular among the prioritisation criteria and among the preferences of the various decision-makers involved. Our proposed approach is based on the notion of minimising the dissimilarity among the preferences of the various decision-makers involved in the process. Given the preferences of each decision-maker with respect to each criterion, we try to find the prioritisation that is at the least possible level of dissimilarity from all the prioritisations of all decision-makers -the middle ground. In general, given a set of m requirements, there are m! possible prioritisation of these requirements. Hence, our approach employs multi-objective optimisation to explore this space of m! candidate solutions with the objective of finding those with the minimum levels of dissimilarity from those of the decisionmakers. Considering the potentially large number of alternatives, our proposed approach is based on Evolutionary Algorithms (EAs) <ref type="bibr" target="#b3">[4]</ref> which are proven to be effective at scaling to large search spaces while at the same time providing optimal solutions for smaller spaces as well.</p><p>EAs are a class of metaheuristic search algorithms inspired by the process of natural evolution in which a population of candidate solutions (individuals) interact with each other and evolve through generations following the principle of survival of the fittest <ref type="bibr" target="#b3">[4]</ref>. EAs are widely used to solve practical optimisation problems for which exact solutions could not be found in reasonable time. Furthermore, EAs follow a global search strategy which is quite robust in exploring the search space and finding globally optimal solutions by avoiding being trapped in local optimal, a phenomenon commonly associated to local search algorithms.</p><p>The right side of Figure <ref type="figure" target="#fig_0">1</ref> depicts a simplified overview of the main aspects of a typical EA, which starts by creating an initial population of individuals. It then evaluates each individual in the population by means of a fitness function and assigns it a fitness value. The EA then proceeds by selecting 'fitter' individuals (parents) from the current population and subjects them to the process of reproduction or crossover resulting in offspring. The offspring could further be subjected to a process of mutation with the aim of introducing diversity into the population. The EA then selects, from the combined pool of parents and offspring, the individuals that form the new population in the next generation (survivors). This process continues to iterate until some stopping condition is reached, in which case the EA terminates. Given the formulation of the multi-decision-maker requirements prioritisation problem outlined in Section 2, an instance of an EA could be applied to search within the space of all possible prioritisations, with the ultimate goal of finding one or more prioritisation(s) with minimal dissimilarity from all of the given rankings. To this end, we need to appropriately define the corresponding EA operations in such a way that we are able to find optimal solutions to our problem. Specifically, we need to define (1) the encoding and initialisation of individuals, (2) the fitness function for evaluating individuals with respect to the problem, and (3) the selection, crossover, and mutation operators that allow the EA to evolve the individuals through generations.</p><formula xml:id="formula_0">Initialise Evaluate Selection Reproduction Mutation Start Stop S 1 = R 2 R 3 R 1 ... ... S n = R 3 R 2 R 4 ... Requirements R 1 , R 2 , R 3 , …, R m Prioritisations by DMs [DM 1 ][C 1 ] R 4 R 2 R 1 … ... [DM 1 ][C k ] R 2 R 4 R 3 ... … [DM n ][C 1 ] R 2 R 3 R 1 … ... [DM n ][C k ] R 3 R 4 R 2 ... Criteria + Weights [C 1 ] cw 1 [C 2 ] cw 2 … [C k ] cw k Input Evolutionary Algorithm dist(S 1 ) = d 1 ... dist(S n ) = d n Select solutions with small distances Dependencies R 1 → R 2 … R 4 → R 3 DM Weights [DM 1 ][C 1 ] w 1 [DM 1 ][C 2 ] w 2 … [DM n ][C k ] w z</formula><p>Solution encoding and initialisation: Given m requirements to be prioritised, candidate solutions (individuals) are prioritisations (rankings) of these requirements. Hence, we encode an individual as: (r 1 , r 2 , . . . , r m ) where r i represents the rank of requirement i. For example, if m = 5, an individual could be: (1,3,2,5,4). In this individual, the rank of requirement 1 is 1, the rank of requirement 2 is 3, the rank of requirement 3 is 2, etc.</p><p>Fitness function: The goal of the fitness function is to objectively measure how good (fit) an individual is with respect to the problem being solved. For our problem, a good individual is one that has the lowest level of dissimilarity (disagreement) among the prioritisations of the decision-makers. Hence, we first quantify the level of dissimilarity between two rankings by means of a distance  For instance, we can define a distance metric based on the (average) differences between the ranks of the requirements:</p><formula xml:id="formula_1">d(I1, I2) = m i=1 |I1[i] − I2[i]|<label>(1)</label></formula><p>Similarly, other rank similarity metrics, such as Kendall's τ statistic <ref type="bibr" target="#b6">[7]</ref>, could be used to define a distance function:</p><formula xml:id="formula_2">d(I1, I2) = 1 − KendallTau(I1, I2)<label>(2)</label></formula><p>Based on the distance functions given in Equations 1 and 2, we define fitness functions for computing the fitness of an individual I in the EA. Specifically, we consider a multi-objective perspective in which we compute the distance of I with respect to more than one objective. For our problem formulation, we define a fitness function considering the distance of I from each criterion.</p><p>The EA searches for individual(s) with the minimum values for the fitness functions, i.e., solutions that represent minimal dissimilarity among the rankings of the various decision-makers.</p><p>EA operators: Here we describe the two most important operators, crossover and mutation, that enable the EA to evolve individuals through generations. Two point crossover in each individual's (parent) encoding, two points are randomly picked, and parts of the encoding are exchanged. Figure <ref type="figure" target="#fig_2">2a</ref> illustrates this crossover operation. In case the crossover operator results in invalid individuals (e.g., duplicated ranks), the individual will either be corrected in a subsequent phase, or the operation will be cancelled and performed again choosing different points of crossover. Swap mutation two points are randomly picked in the individual's encoding, and the values indicated by the selected points (indices) are swapped. Figure <ref type="figure" target="#fig_2">2b</ref> illustrates this mutation operation.</p><p>Algorithm: Given the problem formulation, the encoding of individuals, and the operators defined above, our approach employs a multi-objective EA (e.g., NSGA-II <ref type="bibr" target="#b2">[3]</ref>) based on the multi-objective fitness function described above to find a set of Pareto optimal solutions. Each solution in the Pareto frontier represents a trade-off within the space of the objectives being optimised. Hence, depending on the currently sought solution and context, the human expert should choose one of the solutions.</p><p>Dependencies among requirements could be handled in two ways: As hard constraints: candidate solutions that violate the dependency constraints will not be considered as valid candidates and hence will be discarded. As soft constraints: dependency constraint violation is computed as a secondary objective to be considered in case of equivalence in the first objective (i.e., dissimilarity). Candidate solutions that violate fewer constraints will be preferred in case of a tie between candidates with respect to their distances. This approach is useful in cases where the number of dependencies is high, and consequently the number of valid solutions is low.</p><p>In summary, the approach will search for optimal prioritisations that minimise dissimilarity (disagreement) among the various DMs involved in process, finding the middle ground.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Related Works</head><p>Requirements prioritisation is an area of requirements engineering which has received a significant amount of attention both from the research community and industry <ref type="bibr" target="#b0">[1]</ref>. This is mainly attributed to the fact that the decisions taken during prioritisation could have profound effects on strategic as well as technical (operational) aspects of an organisation <ref type="bibr" target="#b13">[14,</ref><ref type="bibr" target="#b7">8]</ref>. Relevant work identified and discussed the challenges of multi-stakeholder prioritisation from the perspective of traditional (closed) organisation, e.g. <ref type="bibr" target="#b15">[16,</ref><ref type="bibr" target="#b11">12]</ref>, and mostly addressed the multidecision-maker issue with negotiation approaches. Concerning the automatic techniques used in requirements prioritisation, several approaches have been presented that use constraints based techniques and search-based techniques such as Satisfiability Modulo Theory techniques, and heuristic based techniques, in particular genetic algorithms <ref type="bibr" target="#b9">[10,</ref><ref type="bibr" target="#b16">17]</ref>. Considering the latter techniques several search based approaches have been exploited for the solution of different kinds of requirements engineering problems such as multi-objective requirements prioritisation and next release problem <ref type="bibr" target="#b5">[6]</ref> also in presence of multiple customers <ref type="bibr" target="#b4">[5]</ref>. Our approach considers some of the issues and observations reported in the mentioned works and aims at extending them to offer a distributed mechanism for eliciting preferences from stakeholders with potentially different skills and expertise, by employing a collaborative process that allow to find optimal trade-offs among those preferences.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Conclusion</head><p>We presented a multi-objective formulation of the multi-decision-maker requirements prioritisation problem, and outlined a solution based on Evolutionary Algorithms. The proposed approach is based on the notion of finding Pareto optimal prioritisations that exhibit the minimum levels of disagreement among the various decision-makers involved in the process. The ultimate decision-maker selects one of the optimal solutions based on additional interests (e.g., strategic) not necessarily included in the prioritisation criteria. The work is currently ongoing and we are working towards an empirical evaluation of the proposed approach on real world case studies derived from the industry.</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: Overview of solution. Elements in the problem formulation (Input) are mapped into the main phases of EA. Requirements and Dependencies are used to encode and initialise population, Proritisations by DMs, Criteria, and Weights are used to evaluate solutions using the fitness function.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 2 :</head><label>2</label><figDesc>Fig. 2: EA Operators</figDesc></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_0">www.supersede.eu</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Acknowledgement. This work is a result of the SUPERSEDE project, funded by the H2020 EU Framework Programme under agreement number 644018.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title level="m" type="main">Requirements Prioritization</title>
		<author>
			<persName><forename type="first">P</forename><surname>Berander</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Andrews</surname></persName>
		</author>
		<editor>A. Aurum and C. Wohlin</editor>
		<imprint>
			<date type="published" when="2005">2005</date>
			<publisher>Engineering and Managing Soft. Requirements. Springer</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Toolsupported Collaborative Requirements Prioritisation</title>
		<author>
			<persName><forename type="first">P</forename><surname>Busetta</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">M</forename><surname>Kifetew</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Munante</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Perini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Siena</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Susi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the IEEE Int. Conference COMPSAC</title>
				<meeting>the IEEE Int. Conference COMPSAC<address><addrLine>Torino, Italy</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2017">July 4-7, 2017</date>
		</imprint>
	</monogr>
	<note>To appear</note>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">A fast elitist multi-objective genetic algorithm: NSGA-II</title>
		<author>
			<persName><forename type="first">K</forename><surname>Deb</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Pratap</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Agarwal</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Meyarivan</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE Trans. on Evol. Comp</title>
		<imprint>
			<biblScope unit="volume">6</biblScope>
			<biblScope unit="page" from="182" to="197" />
			<date type="published" when="2000">2000</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m" type="main">Introduction to evolutionary computing</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">E</forename><surname>Eiben</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E</forename><surname>Smith</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2003">2003</date>
			<publisher>Springer Science &amp; Business Media</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">A search based approach to fairness analysis in requirement assignments to aid negotiation, mediation and decision making</title>
		<author>
			<persName><forename type="first">A</forename><surname>Finkelstein</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Harman</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Mansouri</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Ren</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Zhang</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Requirements engineering</title>
		<imprint>
			<biblScope unit="volume">14</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="231" to="245" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Software release planning: an evolutionary and iterative approach</title>
		<author>
			<persName><forename type="first">D</forename><surname>Greer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Ruhe</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Information and Software Technology</title>
		<imprint>
			<biblScope unit="volume">46</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="243" to="253" />
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">A new measure of rank correlation</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">G</forename><surname>Kendall</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Biometrika</title>
		<imprint>
			<biblScope unit="volume">30</biblScope>
			<biblScope unit="issue">1/2</biblScope>
			<biblScope unit="page" from="81" to="93" />
			<date type="published" when="1938">1938</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Challenges of shared decision-making: A multiple case study of agile software development</title>
		<author>
			<persName><forename type="first">N</forename><forename type="middle">B</forename><surname>Moe</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Aurum</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Dybå</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Inf. Softw. Technol</title>
		<imprint>
			<biblScope unit="volume">54</biblScope>
			<biblScope unit="issue">8</biblScope>
			<biblScope unit="page" from="853" to="865" />
			<date type="published" when="2012-08">Aug. 2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Modelling prioritisation decisionmaking in software evolution</title>
		<author>
			<persName><forename type="first">D</forename><surname>Muñante</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">M</forename><surname>Kifetew</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Albrecht</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Joint Proceedings of REFSQ-2017 Workshops, Doctoral Symposium, Research Method Track, and Poster Track co-located with the 22nd International Conference on Requirements Engineering: Foundation for Software Quality (REFSQ 2017)</title>
				<meeting><address><addrLine>Essen, Germany</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2017-02-27">February 27, 2017. 2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Using an smt solver for interactive requirements prioritization</title>
		<author>
			<persName><forename type="first">F</forename><surname>Palma</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Susi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Tonella</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ESEC/FSE &apos;11</title>
				<meeting><address><addrLine>New York, NY, USA</addrLine></address></meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2011">2011</date>
			<biblScope unit="page" from="48" to="58" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">A Machine Learning Approach to Software Requirements Prioritization</title>
		<author>
			<persName><forename type="first">A</forename><surname>Perini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Susi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Avesani</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Software Engineering</title>
		<imprint>
			<biblScope unit="volume">39</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="445" to="461" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
	<note>IEEE Transactions on</note>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">An industrial case study on distributed prioritisation in market-driven requirements engineering for packaged software</title>
		<author>
			<persName><forename type="first">B</forename><surname>Regnell</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Höst</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">N</forename><surname>Dag</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Beremark</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Hjelm</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Requirements Engineering</title>
		<imprint>
			<biblScope unit="volume">6</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="51" to="62" />
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<title level="m" type="main">Applying bdi to serious games: The presto experience</title>
		<author>
			<persName><forename type="first">M</forename><surname>Robol</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Busetta</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
		<respStmt>
			<orgName>Universita di Trento</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">Technical report</note>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">The art and science of software release planning</title>
		<author>
			<persName><forename type="first">G</forename><surname>Ruhe</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">O</forename><surname>Saliu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE Softw</title>
		<imprint>
			<biblScope unit="volume">22</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page" from="47" to="53" />
			<date type="published" when="2005-11">Nov. 2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<title level="m" type="main">What is the analytic hierarchy process? In Mathematical models for decision support</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">L</forename><surname>Saaty</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1988">1988</date>
			<publisher>Springer</publisher>
			<biblScope unit="page" from="109" to="121" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Enabling collaboration in distributed requirements management</title>
		<author>
			<persName><forename type="first">V</forename><surname>Sinha</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Sengupta</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Chandra</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Software</title>
		<imprint>
			<biblScope unit="volume">23</biblScope>
			<biblScope unit="issue">5</biblScope>
			<biblScope unit="page" from="52" to="61" />
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
	<note>IEEE</note>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Interactive requirements prioritization using a genetic algorithm</title>
		<author>
			<persName><forename type="first">P</forename><surname>Tonella</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Susi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Palma</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Inf. Softw. Technol</title>
		<imprint>
			<biblScope unit="volume">55</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="173" to="187" />
			<date type="published" when="2013-01">Jan. 2013</date>
		</imprint>
	</monogr>
</biblStruct>

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