<?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">Creative Leaf: A Creative iStar Modeling Tool</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Jennifer</forename><surname>Horkoff</surname></persName>
							<email>horkoff@city.ac.uk</email>
							<affiliation key="aff0">
								<orgName type="department">Center for Creativity in Professional Practice</orgName>
								<orgName type="institution">City University London</orgName>
								<address>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Neil</forename><surname>Maiden</surname></persName>
							<email>n.a.m.maiden@city.ac.uk</email>
							<affiliation key="aff0">
								<orgName type="department">Center for Creativity in Professional Practice</orgName>
								<orgName type="institution">City University London</orgName>
								<address>
									<country key="GB">UK</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Creative Leaf: A Creative iStar Modeling Tool</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">45F763FBDA8A5EE6CE190FA168158EAA</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T05:47+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>creativity</term>
					<term>istar</term>
					<term>goal modeling</term>
					<term>method</term>
					<term>tool support</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>iStar models allow users to capture high-level social requirements, including alternatives and qualities. Typical approaches advocate discovering model content through traditional Requirements Engineering (RE) elicitation methods, such as interviews, observations, and domain documents. For the typical, familiar space of requirements, such techniques may be sufficient, but stakeholders may not always know the best way to meet their needs, and may have difficultly articulating their goals. Creativity theories and activities have been successfully applied to RE in order to discover both creative and more typical requirements. In this work we describe the web-based Creative Leaf tool that facilitates a combination of established creativity techniques with iStar modeling. Divergent techniques help the discovery of ideas, while selection, evaluation and modeling techniques help to converge over ideas, integrating them into the model and system design.</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>Goal models, such as iStar, provide a concrete graphical way to help ensure that potential system requirements meet user goals and qualities. But where do potential requirements come from? How do we find the goals and desired qualities of systems stakeholders? Traditional Requirements Engineering (RE) approaches advocate for various forms of elicitation (interviews, observations, domain documents). For the typical, familiar space of requirements, such techniques may be sufficient. But users and stakeholders may not always know the best way to solve their problems, to meet their needs, or even to identify what those needs may be. Stakeholders are biased by their own experiences, and are often too-grounded in the use of existing tools <ref type="bibr" target="#b9">[10]</ref>. Goals, although helpful in grounding function to purpose, are often difficult for stakeholders to articulate <ref type="bibr" target="#b15">[16]</ref>. There is a need for methods to expand the space of known requirements, to consider and evaluate possibilities beyond the typical space of functions and intentions. Such divergent thinking is critical to support the development of creative requirements, leading to innovative systems which create competitive advantages.</p><p>The role of creativity theories and techniques has been investigated and applied in an RE-context for more than ten years, e.g., <ref type="bibr" target="#b9">[10,</ref><ref type="bibr" target="#b10">11,</ref><ref type="bibr" target="#b1">2,</ref><ref type="bibr" target="#b11">12,</ref><ref type="bibr" target="#b8">9]</ref>. The research outputs of such efforts include the design of structured creativity workshops, RE-focused creativity techniques, and a series of guidelines for applying creativity in practice. Workshops use a series of creativity activities (e.g., brainstorming, role playing, and BrightSparks). These are structured activities which attempt to guide participants through activities or steps which may produce new ideas. Although creative requirements workshops have seen success when applied to real contexts such as Air Traffic Control and Food Safety, workshops are expensive to run, require highly-skilled facilitators, and produce output which is often fragmented and only lightly structured (ideas, scenarios, use cases) <ref type="bibr" target="#b10">[11]</ref>. RE-focused creativity techniques (such as <ref type="bibr" target="#b1">[2,</ref><ref type="bibr" target="#b11">12]</ref>), can be useful, but the power of creativity is better harnessed by use of successive and varied techniques, in order to expand the search space in differing ways. Existing work has also begun to explore the synergies between creativity and goal modeling from the perspective of transformational creativity, but without yet providing a more general tool <ref type="bibr" target="#b14">[15]</ref>.</p><p>In order to address many of these drawbacks in both goal modeling and creativity approaches as used in RE, our work has combined the two approaches, producing a concrete tool and guiding methodology: Creative Leaf<ref type="foot" target="#foot_0">1</ref> . Our overall intention is to facilitate the structured capture of creative requirements -those requirements which are not obvious, typical, or which do not immediately come to the mind of the stakeholders.</p><p>Creative Leaf is an output of a design research process involving a series of formative and summative studies conducted over the last 1.5 years. We leave the reporting of these studies to further work, and in this short paper focus on describing the resulting tool. We have previously published initial visions of how the tool and method may work, using historical examples <ref type="bibr" target="#b4">[5,</ref><ref type="bibr" target="#b6">7,</ref><ref type="bibr" target="#b5">6]</ref>. In this paper, we describe the concrete output of the design process, including embedded exploratory creativity activities, and activities designed to help users evaluate, prioritize and model their ideas.</p><p>Section 2 describes the design and functionality of the tool. Section 3 concludes the paper and makes a call for participation in the use and evaluation of Creative Leaf.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Creative Leaf</head><p>A screenshot of Creative Leaf is shown in 1. The left hand panel contains a palette with iStar elements. The included elements and links were based on an early version of the iStar 2.0 core <ref type="bibr" target="#b3">[4]</ref>. We have plans to update the palette to conform to the latest version of the iStar core. To support high-level creative thought, the tool allows user to draw ideas and assumptions along with the typical iStar elements. These new elements can be connected to other elements with the typical iStar links, in other words, they are firstclass modeling elements. The middle of the tool contains the canvas, where the model can be drawn, and the creative ideas placed. The right hand side contains the creativity panel. Each of the gray boxes are clickable, opening a window guiding users through a particular creative activity. The right and left panels are collapsible, allowing modelers to focus on the center canvas when needed, particularly when using smaller screens.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.1">Implementation Details</head><p>The iStar modeling capability of Creative Leaf is based off the Leaf Beta tool developed at the University of Toronto by Alicia Grubb et al. <ref type="foot" target="#foot_1">2</ref> . The Leaf code has been modified and adapted, e.g., to add ideas and assumptions. (Creative) Leaf uses both the Join-tJS and Rappid 3 HTML 5 diagramming frameworks. JointJS is available via an open Fig. <ref type="figure">1</ref>: Screenshot of Creative Leaf Tool license, while Rappid is a commercial product, but provides free academic licenses. Code is written in JavasScript, using CSS and HTML files for formatting and display. Creative Leaf code is stored on a private GitHub repository, forked from the Leaf code base. Access can be made available to other institutions which acquire a license for Rappid (all other sections of code apart from the Rappid libraries are Open Source and are available on request).</p><p>In addition to modeling and creative functions, the tool has an embedded tracking function which tracks user actions with time stamps. Users have the option to turn off or on this tracking at first use, and later via the Options menu. Creative Leaf uses a series of unobtrusive prompts to guide users to the next likely activity, particularly when the user is inactive for some period of time. These prompts can also be disabled via Options.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.2">Exploratory Creativity</head><p>The Creativity panel on the right of the tool allows users to work through a number of established creativity activities. Following the model of the Creative Problem Solving (CPS) method, creative activities are aimed to support either divergent creativity, generating ideas, or convergent creativity, selecting, combining and developing ideas <ref type="bibr" target="#b12">[13]</ref>. The first five activities within Creative Leaf support exploratory creativity, while the last two begin to support convergence.</p><p>Exploratory creativity activities in Creative Leaf include Brainstorming, CRUISE creative search, Pairwise Comparison, Creativity Triggers, and Bright Sparks (Hall of Fame). More information about the general form of these activities can be found within Fig. <ref type="figure">2</ref>: Screenshot of CRUISE Exploratory Activity within Creative Leaf Tool the BeCreative Creativity Support tool <ref type="bibr" target="#b0">[1]</ref>. Each activity (apart from Brainstorming) takes as input some piece of the iStar model. Ideas can be recorded in the tool by typing in the text field on the bottom part of the activity window. When the users are done an activity (they've run out of ideas), they can "Add ideas to the Model Canvas and exit" where each idea appears as a yellow idea "post-it" on the model. Such idea elements can be moved around and attached to other model elements via the typical iStar links, e.g., this idea helps this Softgoal/Quality. We describe each Creativity Activity in more detail in the following.</p><p>Brainstorming is the very general activity encouraging people to capture all the "obvious" ideas, which they already have in mind. Studies showed that without this initial activity, users ignored the structure and prompts of further activities and only listed the ideas they already had. The CRUISE activity calls an external creativity service, a result of the Collage Project<ref type="foot" target="#foot_3">4</ref> . The input search string is a selected iStar element, actor or idea. The CRUISE service returns a cloud of images, links and text which are tangentially related to the search string. Ideas prompted by the output are captured at the bottom of the window. An example screenshot of the CRUISE activity can be seen in Fig. <ref type="figure">2</ref>.</p><p>The Pairwise Comparison activity, inspired by Poincare's emphasis on creativity through connections <ref type="bibr" target="#b13">[14]</ref>, displays pairs of iStar elements from the model, avoiding elements directly connected. Users can iterate through pairs until they find one or more which inspires ideas. The Creativity Trigger activity compares available triggers with a selected iStar element, using the text and image trigger cards developed by Robertson &amp; Robertson, and explored empirically in a recent paper <ref type="bibr" target="#b2">[3]</ref>. Users can iterate through triggers (Connections, Convenience, Information and Choices, Participation, Service, and Trust) until they find one or more which inspires ideas. BrightSparks, like CRUISE, makes a call to an external service 5 . This activity takes an actor as input and asks the user to think of the actor being played by a famous persona (e.g., Batman, Joan of Arc, Henry Ford), allowing the user to iterate through personas.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.3">Analysis, Selection &amp; Modeling</head><p>Once ideas have been discovered, the user needs help selecting amongst ideas and developing the selected ideas by integrating them into the iStar model. We offer a selection activity which guides users through the process, see the text in Fig. <ref type="figure" target="#fig_0">3a</ref>. Part of the selection activity introduces the Hover Evaluation feature included in Creative Leaf. This feature is based on qualitative evaluation from the first author's previous work <ref type="bibr" target="#b7">[8]</ref>, but is fully automated for simplicity. When the user hovers over an element, it is treated as satisfied and the effects of that satisfaction are propagated up the model, see Fig. <ref type="figure" target="#fig_0">3b</ref> for an example. In this way, users can explore the effects of their ideas on the model. Ideas can be marked by the user as Must-Have (green), Nice-to-Have (yellow) or Rejected (removed from canvas).</p><p>The final activity encourages users to model their best ideas in iStar, manually converting their idea to a number of iStar elements and links, connecting them to the existing model. This step is currently fully manual, but we are looking into providing users with suggested mappings of their ideas into iStar elements. Once an idea has been modeled, it is marked as modeled and removed (automatically) from the canvas. All ideas, including rejected and modeled ideas can be found via the idea list, accessible via a button on the top right of the tool. More information, including tutorial videos and a user guide can be found in the following support site: https: //sites.google.com/site/creativitygm4re. </p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>5Fig. 3 :</head><label>3</label><figDesc>Fig. 3: Creative Leaf Details</figDesc><graphic coords="5,134.77,438.38,172.91,207.37" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="3,134.77,115.84,345.84,240.85" type="bitmap" /></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">http://creativeleaf.city.ac.uk/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_1">http://www.cs.toronto.edu/ ˜amgrubb/leaf</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_2">http://www.jointjs.com/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_3">http://cruise.imuresearch.eu/ui/explore</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" xml:id="foot_4">Proceedings of the Ninth International i* Workshop (iStar 2016), CEUR Vol-1674</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" xml:id="foot_5">Creative Leaf: A Creative iStar Modeling Tool</note>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>We have introduced the reader to the Creative Leaf tool, combining goal modeling with established creativity techniques. We encourage users to try out the tool, and provide feedback to the authors at creativeleaf@city.ac.uk. After extensive in-lab evaluation of the tool, we are looking for organizations with real problems willing to try out the tool and provide feedback. We hope to use this realistic evaluation to improve the functionality and general applicability of the tool.</p><p>Acknowledgments. This research is supported by an ERC Marie Skodowska-Curie Intra European Fellow-ship (PIEF-GA-2013-627489) and a Natural Sciences and Engineering Research Council of Canada Postdoctoral Fellowship (Sept. 2014 -Aug. 2016).</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<title/>
		<author>
			<persName><surname>Becreative</surname></persName>
		</author>
		<ptr target="http://becreative.city.ac.uk/index.php" />
		<imprint>
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Automated support for combinational creativity in requirements engineering</title>
		<author>
			<persName><forename type="first">T</forename><surname>Bhowmik</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Niu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Mahmoud</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Savolainen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IEEE 22nd International Requirements Engineering Conference (RE14)</title>
				<imprint>
			<date type="published" when="2014">2014</date>
			<biblScope unit="page" from="243" to="252" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Stimulating stakeholders&apos; imagination: New creativity triggers for eliciting novel requirements</title>
		<author>
			<persName><forename type="first">C</forename><surname>Burnay</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Horkoff</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Maiden</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Int. Requirements Engineering</title>
				<imprint>
			<date type="published" when="2016">2016. 2016</date>
		</imprint>
	</monogr>
	<note>RE&apos;16. 16th IEEE. IEEE</note>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">0 language guide</title>
		<author>
			<persName><forename type="first">F</forename><surname>Dalpiaz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">X</forename><surname>Franch</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Horkoff</surname></persName>
		</author>
		<ptr target="http://arxiv.org/abs/1605.07767" />
	</analytic>
	<monogr>
		<title level="j">istar</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Creativity and conceptual modeling for requirements engineering</title>
		<author>
			<persName><forename type="first">J</forename><surname>Horkoff</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Maiden</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">CreaRE: Fifth International Workshop on Creativity in Requirements Engineering</title>
				<imprint>
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Supporting creative RE with i*</title>
		<author>
			<persName><forename type="first">J</forename><surname>Horkoff</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Maiden</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Eighth Int. i*Workshop -iStar 2015</title>
				<meeting>the Eighth Int. i*Workshop -iStar 2015</meeting>
		<imprint>
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Creativity and goal modeling for software requirements engineering</title>
		<author>
			<persName><forename type="first">J</forename><surname>Horkoff</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Maiden</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Lockerbie</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Creativity &amp; Cognition</title>
				<imprint>
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
	<note>poster</note>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Interactive goal model analysis for early requirements engineering</title>
		<author>
			<persName><forename type="first">J</forename><surname>Horkoff</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><forename type="middle">S K</forename><surname>Yu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Requir. Eng</title>
		<imprint>
			<biblScope unit="volume">21</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="29" to="61" />
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Collaborative creativity in requirements engineering: Analysis and practical advice</title>
		<author>
			<persName><forename type="first">M</forename><surname>Mahaux</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Gotel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Mavin</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Nguyen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Mich</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Schmid</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IEEE 7th International Conference on Research Challenges in Information Science (RCIS13)</title>
				<imprint>
			<date type="published" when="2013">2013</date>
			<biblScope unit="page" from="1" to="10" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Requirements engineering as creative problem solving: A research agenda for idea finding</title>
		<author>
			<persName><forename type="first">N</forename><surname>Maiden</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Jones</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Karlsen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Neill</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Zachos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Milne</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">18th IEEE International Requirements Engineering Conference (RE10)</title>
				<imprint>
			<date type="published" when="2010">2010</date>
			<biblScope unit="page" from="57" to="66" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Can requirements be creative? experiences with an enhanced air space management system</title>
		<author>
			<persName><forename type="first">N</forename><surname>Maiden</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Ncube</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Robertson</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">ICSE 2007. 29th International Conference on</title>
				<imprint>
			<date type="published" when="2007-05">2007. May 2007</date>
			<biblScope unit="page" from="632" to="641" />
		</imprint>
	</monogr>
	<note>Software Engineering</note>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">Requirements engineering and creativity: An innovative approach based on a model of the pragmatics of communication</title>
		<author>
			<persName><forename type="first">L</forename><surname>Mich</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Anesi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">M</forename><surname>Berry</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Requirements Engineering: Foundation of Software Quality (REFSQ04)</title>
				<imprint>
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">F</forename><surname>Osborn</surname></persName>
		</author>
		<title level="m">Applied Imagination; Principles and Procedures of Creative Problem-solving: Principles and Procedures of Creative Problem-solving</title>
				<imprint>
			<publisher>Scribner</publisher>
			<date type="published" when="1963">1963</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<title level="m" type="main">Science and method</title>
		<author>
			<persName><forename type="first">H</forename><surname>Poincare</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1918">1918</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Using i* for transformational creativity in requirements engineering</title>
		<author>
			<persName><forename type="first">S</forename><surname>Rayasam</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Niu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Eighth Int. i*Workshop -iStar 2015</title>
				<meeting>the Eighth Int. i*Workshop -iStar 2015</meeting>
		<imprint>
			<date type="published" when="2015">2015</date>
			<biblScope unit="page" from="67" to="72" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">Guiding goal modeling using scenarios</title>
		<author>
			<persName><forename type="first">C</forename><surname>Rolland</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><surname>Souveyet</surname></persName>
		</author>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">B</forename><surname>Achour</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Software Engineering, {IEEE} Transactions on</title>
		<imprint>
			<biblScope unit="volume">24</biblScope>
			<biblScope unit="issue">12</biblScope>
			<biblScope unit="page" from="1055" to="1071" />
			<date type="published" when="1998">1998</date>
		</imprint>
	</monogr>
</biblStruct>

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