<?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">Continuous Business Model Planning with the Value Management Platform</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Geert</forename><surname>Poels</surname></persName>
							<email>geert.poels@ugent.be</email>
							<affiliation key="aff0">
								<orgName type="department" key="dep1">Department of Business Informatics and Operations Management</orgName>
								<orgName type="department" key="dep2">Faculty of Economics and Business Administration</orgName>
								<orgName type="institution">Ghent University</orgName>
								<address>
									<addrLine>Tweekerkenstraat 2</addrLine>
									<postCode>9000</postCode>
									<settlement>Gent</settlement>
									<country key="BE">Belgium</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Ben</forename><surname>Roelens</surname></persName>
							<email>ben.roelens@ugent.be</email>
							<affiliation key="aff0">
								<orgName type="department" key="dep1">Department of Business Informatics and Operations Management</orgName>
								<orgName type="department" key="dep2">Faculty of Economics and Business Administration</orgName>
								<orgName type="institution">Ghent University</orgName>
								<address>
									<addrLine>Tweekerkenstraat 2</addrLine>
									<postCode>9000</postCode>
									<settlement>Gent</settlement>
									<country key="BE">Belgium</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Henk</forename><surname>De Man</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">VDMbee</orgName>
								<address>
									<addrLine>Schietboom 2</addrLine>
									<postCode>3905TD</postCode>
									<settlement>Veenendaal</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Theo- Door</forename><surname>Van Donge</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">VDMbee</orgName>
								<address>
									<addrLine>Schietboom 2</addrLine>
									<postCode>3905TD</postCode>
									<settlement>Veenendaal</settlement>
									<country key="NL">The Netherlands</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Continuous Business Model Planning with the Value Management Platform</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">BB6D544223F215F55D6B6ECE8AB3F3C2</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T16: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>Conceptual Modeling</term>
					<term>Enterprise Modeling</term>
					<term>Value Modeling</term>
					<term>Business Ontology</term>
					<term>VDML</term>
					<term>Business Model Planning</term>
					<term>Business Innovation</term>
					<term>Business Transformation</term>
					<term>Strategy Exploration</term>
					<term>Managerial Decision Making</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>The Value Delivery Modeling Language (VDML) is a standardized language for developing conceptual models that are used for the analysis and design of value creation and value capture in enterprise operations. Although the VDML 1.0 specification was published by the Object Management Group (OMG) in October 2015, as of yet, little is known about applications and experiences of value modeling with VDML. We report in this paper on the industrial practice of applying VDML for continuous business model planning using the Value Management Platform (VMP) tool of the Dutch company VDMbee. Neither the VMP user guide nor the VDML specification prescribe how to perform value modeling using the tool/language. With this paper, we add to the procedural knowledge of value modeling by analyzing the method applied in a continuous business model planning case-study of a low-cost carrier. We focus particularly on how the VMP was used in this case-study for supporting managerial decision making and strategy exploration regarding the company's future growth on both the existing business model and innovation-driven business transformation. By identifying, extracting, and making explicit the method of continuous business model planning using the VMP, we contribute to a better understanding of the practice of value modeling with VDML.</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>A value model is a type of enterprise model that shows how value is delivered in a network of actors (e.g., a supply chain, a consumer market, a smart grid, a healthcare system). As such, value modeling can be used for strategic analysis and the (re)design of value networks. Since the early 2000's, different modeling approaches have been proposed with specific emphasis on value-related aspects (e.g., exchange, impact and value creation analyses <ref type="bibr" target="#b0">[1]</ref>, e-service design <ref type="bibr" target="#b1">[2]</ref>). The Value Delivery Modeling Language (VDML) <ref type="bibr" target="#b2">[3]</ref>, which integrates many concepts of other value modeling as well as business modeling approaches, has been adopted as a standard business modeling specification by the Object Management Group (OMG) <ref type="bibr" target="#b3">[4]</ref>. Tool support for VDML is offered by the Dutch company VDMbee <ref type="bibr" target="#b4">[5]</ref>. Their Value Management Platform (VMP) provides a user-friendly tool for working with VDML using different kinds of business canvas/map templates and storytelling/mapping techniques for model building. The transparent creation of VDML meta-model instantiations via the tool's highly visual interfaces instead of directly working with the language, targets value management professionals with a business-oriented profile rather than a technology-oriented profile.</p><p>The approach to value modeling adopted in the VMP is called continuous business model planning (CBMP) <ref type="bibr" target="#b5">[6]</ref>, to stress that it is an approach that uses a business model framework to connect strategy and operations, in a spirit of 'continuous improvement' by steering the business on values. The VMP is thus used as a dashboard for planning and monitoring strategic change and as a decision support system for exploring, evaluating and deciding on strategic plans. A complete enterprise modeling approach entails more than the definition of a metamodel, a notation, and the development of modeling, analysis, and design tools. A modeling method also consists of a modeling procedure which guides the creation and analysis of models <ref type="bibr" target="#b6">[7]</ref>. Currently, there is no research on how to apply VDML as related research focuses on ontological analysis of the conceptualization of value <ref type="bibr" target="#b7">[8]</ref><ref type="bibr" target="#b8">[9]</ref><ref type="bibr" target="#b9">[10]</ref><ref type="bibr" target="#b10">[11]</ref>, VDML extensions and analysis techniques for applications like business model analysis <ref type="bibr" target="#b11">[12,</ref><ref type="bibr" target="#b12">13]</ref>, compliance engineering <ref type="bibr" target="#b13">[14]</ref> and reputation systems design <ref type="bibr" target="#b14">[15]</ref>, and integration of VDML into enterprise architecture modeling approaches (e.g., ArchiMate <ref type="bibr" target="#b15">[16,</ref><ref type="bibr" target="#b16">17]</ref>). 1 Regarding CBMP with the VMP, a brief overview of its stages can be found in the literature <ref type="bibr" target="#b13">[14]</ref>. A more up-to-date overview can be found in <ref type="bibr" target="#b5">[6]</ref>, which is a VDMbee blog post that is deliberately high-level and introductory. Apart from largely anecdotic evidence of (showcase) VDML applications (e.g., case-studies reports <ref type="bibr" target="#b4">[5]</ref>, master thesis projects <ref type="bibr" target="#b17">[18]</ref><ref type="bibr" target="#b18">[19]</ref><ref type="bibr" target="#b19">[20]</ref>), knowledge on the practice of value modeling with VDML is largely tacit. For CBMP, this knowledge is embedded in the VMP code and in its documentation, video tutorials and other training materials, not forgetting the tacit knowledge 'embodied' by the tool developers themselves.</p><p>The goal of this paper is to make this tacit knowledge explicit. We intend to contribute procedural knowledge (i.e., how to?) of CBMP by making the method underlying the use of the VMP explicit. Via the specific value modeling approach chosen, we also intend to better the understanding of the practice of value modeling. We believe that by demonstrating the VMP-supported approach as a for managers transparent practice of VDML that guides and supports their strategic planning processes regarding continuous 1 A systematic search on Google Scholar on December 18, 2017 returned 589 hits for the search string "continuous business model planning" OR "VDML" OR "value delivery modeling language" OR "value delivery modelling language" OR "value delivery metamodel" OR "value delivery meta-model". These hits revealed 108 unique documents in English which referred to VDML as acronym for value delivery modeling language (or value delivery meta-model as it was first coined by the OMG) and one document that mentioned CBMP using the VMP.</p><p>innovation and transformation, we help increasing the maturity of value modeling practice and boosting the adoption of VDML. Making the method explicit will also facilitate further research on the use of VDML.</p><p>To identify and extract the method underlying the use of VMP for CBMP, we follow the Design Science Research Method for Information Systems Research <ref type="bibr" target="#b20">[21]</ref>. In particular, we conducted client/context-initiated design-based research. According to <ref type="bibr">[21, p. 56</ref>] "a client/context-initiated solution may be based on observing a practical solution that worked; it starts with activity 4 [Demonstration: find suitable context &amp; use artifact to solve problem], resulting in a D[esign]S[cience] solution if researchers work backward to apply rigor to the process retroactively". In our case, the client is VDMbee that asked us for help to make tacit knowledge about the CBMP method explicit. The context is the application of the approach to the CBMP process of a low-cost carrier (LCC). This LCC case-study was developed by the VDMbee Academy to be used for training value management professionals in the use of the VMP.</p><p>VDMbee provided us access to the case-study documentation and data (i.e., business model packages stored in the VMP) and the two VDMbee value architects who were involved in the development of the case-study, joined the research team. The participation of the value architects greatly helped us to reconstruct the development process, while ensuring the correct interpretation of the case-study materials. So, our main research activity was to reverse engineer the demonstration of VMP-based value modeling in the LCC context, to find out the activities performed and techniques applied, and to add some rigor to the CBMP method's design rationale by grounding design decisions in the Information Systems and Strategic Management knowledge base <ref type="bibr" target="#b21">[22]</ref>. We decided that the evaluation of this method is outside the research scope of this paper. We also emphasize that this is only a first iteration of adding rigor as we report on an industrial practice, focusing on describing the method underlying the use of the VMP as observed from a particular instantiation (i.e., the LCC case-study). Consequently, the maturity level of the knowledge contribution of our research is still low, being of the type 'situated implementation of artifact' <ref type="bibr" target="#b22">[23]</ref>. Further research is required to raise the level of knowledge of CBMP to that of a design theory.</p><p>The paper is structured as follows. The second section of the paper introduces the LCC case-study. The third section analyses how the VMP was used in the case-study to identify and extract the underlying CBMP method. The fourth section discusses the most distinctive features of the method, the limitations of the research, and the next steps in developing the VMP and in conducting research on CBMP. The final section concludes by outlining our contribution and its implications for practice and research.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Case-study</head><p>The LCC studied differentiates itself most clearly from a full-service carrier through the adoption of the 'no-frills' business model pattern <ref type="bibr" target="#b23">[24]</ref>. Passengers can buy cheap tickets to be transported from point A to point B, but basically any other service (e.g., hold luggage, carry-on luggage, food and beverages, seat allocation) must be bought as add-ons at a premium price. The ancillary revenues generated by the add-ons combined with a cost-cutting focus (e.g., minimal turnaround time, minimal fuel carriage and consumption, maximal aircraft utilization, low wages) allow keeping ticket prices low.</p><p>Apart from low costs, other key values of the LCC under study are environmental sustainability (i.e., consuming less fuel per passenger kilometer than competitors do) and passenger satisfaction, which is determined by ticket prices, promptness (i.e., flights in time) and the variety of destinations within the European Union that are served. Despite the success of the current business model, the LCC's management team realizes that further strategic thinking and action is required to cope with emerging challenges and threats, including a worsening reputation (in terms of lack of customer service quality and bad treatment of personnel), projected market (share) growth (necessitating investments in hundreds of new aircrafts), increased competition by so-called ultra-low-cost carriers, and the Brexit (potentially resulting in a reversing of deregulation and liberalization for flights to and from the UK).</p><p>To cope with these challenges and threats, and to realize the CEO's ambition to grow, several ideas for business model innovation are actively being pursued, including operating long-haul flights (e.g., inter-Atlantic flights), setting up short-haul operations in the Middle-East, and offering connecting flights (i.e., feeder lines) for long-haul airlines. Also, several alternatives of the current business model are being explored, to find the best basis for future growth (e.g. lowering of fares, leasing of planes). To structure this strategic thinking and turn it into a systematic strategic planning process, the VMP was used. Using the VMP, business model innovation is moved from ideation to prototyping, allowing managers to take informed decisions on the adoption and implementation of new/modified business models and on the phasing of the business transformation. The VMP informs managerial decision-making by means of prognoses and analyses of scenarios regarding the value impact of the continuation of current business models and/or business model innovation. For instance, a value management dashboard can be created to show the trade-offs in and/or evolution of 'plan values' (see Fig. <ref type="figure" target="#fig_0">1</ref> for an example). The method underlying the application of the VMP is demonstrated and analyzed in the next section.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Continuous Business Model Planning Method</head><p>In this section, a first subsection presents the analysis of the CBMP process performed for the LCC under study. The analysis looks into what activities were performed, for which purpose, in what order, and how they were organized as to who is involved and where they took place. The second subsection then looks specifically into the question with what means the activities were performed. The different techniques incorporated in the VMP are demonstrated on the LCC case and are mapped onto applicable constructs and diagrams of VDML.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Analysis of the Continuous Business Model Planning Process</head><p>In CBMP, the business model is considered as the unit of strategic planning. In line with OMG's Business Motivation Model (BMM) <ref type="bibr" target="#b24">[25]</ref>, strategy is seen as a description of a course of action to reach goals, which express the enterprise's aspirations (i.e., its vision). In other words, the BMM defines a strategy as a component of the plan for the realization of the mission that makes the vision operative. A strategy guides efforts towards the achievement of objectives that quantify the enterprise goals. As CBMP is meant to steer the business on values, the objectives defined are those pertaining to value delivery. In this context, the VDML definition of value as a measurable factor of benefit, of interest to a recipient <ref type="bibr" target="#b3">[4]</ref> is adopted.</p><p>Value objectives can be defined and managed per phase in the plan for the mission. For each phase, alternatives can be defined to explore different approaches for achieving the phase's value objectives. <ref type="foot" target="#foot_1">3</ref> Strategies are incorporated into the plan as business models for phases/alternatives that define how the business operates in each phase (i.e., business model evolution) and alternative (i.e., business model variation). The mission is thus decomposed in a set of interacting business models, together covering all business activities, both customer-facing and internal. It is important to understand that a business model is not merely the formulation of a product-market strategy (e.g., product differentiation, cost leadership), but rather the blueprint of a value proposition and activity system used to deliver value to customers <ref type="bibr" target="#b25">[26]</ref>. The CBMP thus focuses on rationalizing strategy in terms of customer and partner relationships, business activities and required competencies, and assessing the impact of strategy implementation on the achievement of the value objectives in the future <ref type="bibr" target="#b5">[6]</ref>.</p><p>In the case-study, the VMP was used to define a phased plan for the LCC's mission, distinguishing the current model (year 0), growth (year 1), and growth (year 2) (see Fig. <ref type="figure" target="#fig_1">2</ref>). The growth phases take into account both market growth (in terms of prognoses of tickets sold) and the projected growth of LCC's business. For the growth (year 1) phase, three alternatives were defined: unchanged policy, lower fares, and lower fares &amp; partial lease. The first alternative concerns a slight increase in market size and market share, without change of operating model. The second alternative explores a significant increase in market share as a result of dramatic lowering of ticket prices, but also necessitating a significant increase in fleet size. The third alternative builds on the second one, but reflects also a change in LCC's policy of fleet ownership by considering leasing planes instead of buying them. When looking into the activities performed, Fig. <ref type="figure" target="#fig_2">3</ref> shows that in the LCC case-study, the VMP was used in three different stages. These stages (i.e., Discover, Prototype and Adopt) provide a high-level structuring of the CBMP process. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Discover Stage. The purpose of the Discover stage is the discovery of the As-Is and</head><p>To-Be business models to be further elaborated in the Prototype stage. The discovery of business models to be described, analyzed, experimented, innovated and evaluated across the defined phases and alternatives is done in a collaborative workshop involving the stakeholders in the CBMP initiative. These stakeholders include a value management analyst (that facilitates the workshop) and one or more participants of the enduser organization that are responsible for strategic planning (possibly with strategic decision-making authority) and possibly participants that are subject matter experts in the end-user organization or from other organizations in the ecosystem of the end-user organization.</p><p>The workshop is organized in four sessions, each with their own objectives (see Fig. <ref type="figure" target="#fig_3">4</ref>). In the first session, the business ecosystem is sketched and key participants, from whose perspective business models will be discovered, are identified. In the second session, the business models of these key participants are described and related to each other, consistent with the ecosystem. In the third session, the values to steer on are decided upon and other values, which influence them or are influenced by them, are identified by relating them through cause-and-effect relations. In the fourth session, the plan for the mission is outlined or, if already available in case of a continued engagement in the CBMP, further extended with one or more additional phases. The values to steer on are defined as plan values, i.e., values that are the basis for management and measurement of plan progress and the success of plan outcomes, while the other values are related to the business models into which the plan is decomposed. Phases in the plan are defined to add phase-specific objectives for the plan values. Furthermore, phase alternatives can be used to describe scenarios that analyze risks, assumptions, and strategic choices.</p><p>The techniques employed during these sessions and their demonstration on the LCC case are presented in the next subsection. In the case-study, four interrelated business models owned by the LCC under study were discovered (see Fig. <ref type="figure" target="#fig_4">5</ref>): <ref type="foot" target="#foot_2">4</ref>• Business plus: Offering cheap tickets to business passengers; • Economy: Offering cheap tickets to economy passengers; • Flights: Internal business model for offering of the fleet and flights to the LCC Travel business unit by the LCC Operations business unit;</p><p>• Shops: In-flight offering of customers to duty free companies. The business model concept embraced by CBMP is inspired by Lindgren's Business Model Cube <ref type="bibr" target="#b26">[27]</ref>. CBMP's business model cube concept provides a 'canonical' form of business model representation that is adequate for an unambiguous description of business models that live in an ecosystem of interacting business models. Using this representation, all ecosystem business models can be balanced in terms of customer and partner relationships and exchanges of value between all participants in all directions, following a universal concept of value that is adequate for simulation and calculation. The conceptualization of a business model as a cube implies that there are six faces:</p><p>─ Value propositions offered and received, including my propositions (i.e., results of the business model as captured by the owning enterprise, also known as 'the business'); ─ Customers as business ecosystem participants that are served by the business -this determines the main purpose of the business model; ─ Partners as business ecosystem participants that are involved in the business model to help creating the values to be delivered to the customers; ─ Activities as work performed by participants in a role (i.e., partner roles, customer roles, roles of the business) and part of value streams<ref type="foot" target="#foot_3">5</ref> that pursue value propositions; ─ Competencies as capabilities and resources that the business has and applies in order to perform the work represented by activities;<ref type="foot" target="#foot_4">6</ref> ─ Values as benefits or interests to customers and partners (in value propositions offered), as captured by the business (in my propositions), as qualifying customer rewards or partner offerings (in value propositions received), and as internal (created by activities).</p><p>For all these business model components, the VMP uses definitions that can be traced back to the VDML meta-model. Value proposition, value (in a value proposition), activity, capability and resource are VDML constructs. Customers, partners and the business itself are VDML participants in VDML business networks, while 'the business', 'customer' and 'partner' are business model cube manifestations of generic VDML roles. An activity value is a VDML value add (representing a value contribution of the activity). Competency is a generalization of VDML capability and VDML resource.</p><p>The invisible seventh dimension of Lindgren's Business Model Cube (i.e., the interior of the cube) that refers to the 'wiring' (i.e., relationships) of the business model components on the visible faces <ref type="bibr" target="#b26">[27]</ref>, is formalized in the VMP through the relationships between constructs in the VDML meta-model. Fig. <ref type="figure" target="#fig_5">6</ref> shows a VMP screenshot of the business model cube visualization of the LCC's 'shops' business model. In the case-study, prototyping the discovered business models for all phases and alternatives of the plan involved four steps: As shown in Fig. <ref type="figure" target="#fig_3">4</ref>, the Prototype stage is performed using an agile approach in two or three weekly sprints. The prototyping is done by the value management analyst, based on the input received during the Discover stage. At the end of each sprint, feedback is obtained from the stakeholders of the involved organizations. This cycle continues until these stakeholders are satisfied with the results and are able to make decisions in the Adopt stage.</p><p>Adopt Stage. The purpose of this stage is to present the prototyping results to strategic decision-makers, allowing them to decide on adoption and initiation of the required changes. Value management professionals support the decision-making process by using the built-in dashboard, reporting, and what-if scenario analysis techniques of the VMP (see next subsection).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Techniques of Continuous Business Model Planning</head><p>The techniques used in the CBMP activities are demonstrated for the LCC case-study in the order of the process stages presented in the previous subsection.</p><p>Discover Stage. The sketching of the business ecosystem and the identification of key participants is supported by the VMP through the business ecosystem map (see Fig. <ref type="figure" target="#fig_7">7</ref>). This model is essentially the same as the VDML value proposition exchange diagram, though there is an option to include VDML participants (i.e., enterprises (i.e., VDML organization units), market segments (i.e., VDML communities) or individuals (i.e., VDML actors) or VDML business models instead of VDML roles. Fig. <ref type="figure" target="#fig_7">7</ref> illustrates the former option, where participants and exchanged value propositions are given pictorial representations. The business ecosystem map provides a more abstract view of the VDML role collaboration diagram, which shows the flows of tangible and intangible deliverables between participant roles, based on Allee's Value Network concept <ref type="bibr" target="#b0">[1]</ref>. In the LCC case-study, six participants were identified, from whom the LCC Travel and LCC Operations business units are key participants. These participants exchange sixteen value propositions in the ecosystem, based on which the four business models of Fig. <ref type="figure" target="#fig_4">5</ref> were discovered. <ref type="foot" target="#foot_6">8</ref>The VMP supports the description of the key participants' business models through business canvasing techniques. Although different types of business canvases are supported, in the LCC case-study only use was made of the widely known business model canvas <ref type="bibr" target="#b28">[29]</ref>, which is based on Osterwalder's Business Model Ontology <ref type="bibr" target="#b29">[30]</ref>. Although, there is no VDML diagram equivalent to the business model canvas, the VMP also supports a business model canvas variant called business model innovation canvas. This variant has the six faces of the business model cube as components, which allows direct traceability to the corresponding VDML constructs. Fig. <ref type="figure" target="#fig_8">8</ref> shows as an example the business model canvas for the 'flights' business model, which is owned by the LCC Operations business unit. Based on the business ecosystem map, which resulted from the first workshop session (see Fig. <ref type="figure" target="#fig_7">7</ref>), the value management analyst had pre-filled LCC travel as the customer, airports and oil companies as partners, and fleet and flights as value propositions offered to the customer. In the second workshop session, workshop participants used the canvas to systematically think about key activities and resources required to pursue the value propositions, their costs, and the revenue streams that will be generated. To support the identification of plan values and business model values and how values influence each other, strategy maps are used as a storyboard for cause-and-effect value creation. This technique is based on the homonymous technique presented by Kaplan and Norton <ref type="bibr" target="#b30">[31]</ref>.</p><p>An example strategy map, from the case-study, is shown in Fig. <ref type="figure" target="#fig_9">9</ref>. It shows how competencies and activities influence values for the LCC (e.g., low overhead, low maintenance costs, low aircraft acquisition costs) and for its customers (e.g., high promptness). Finally, the last workshop session is supported through the VMP's functionality to model phases and alternatives (see Fig. <ref type="figure" target="#fig_1">2</ref>) and to enter plan values (which can for large part be derived from the strategy maps and business canvases).  The analysis of the LCC case-study taught us that in reality much of the data in the business model cubes was already filled by the value management analyst in between and after the Discovery stage workshop sessions. Based on the business ecosystem map 9 Limited to value propositions offered to customers. The business model canvas does not allow including other value propositions (e.g., those received from customers and those offered to and received from partners). 10 Also plan values (i.e., not part of a particular business model in the mission plan).</p><p>(see Fig. <ref type="figure" target="#fig_7">7</ref>), the analyst created business models, identified participant networks (see the different colors of the value proposition provide and receive arrows in Fig. <ref type="figure" target="#fig_7">7</ref>), and filled in customers, partners and value propositions in the business model cubes. Based on the business model canvases (see Fig. <ref type="figure" target="#fig_8">8</ref>), the analyst then started to fill the remaining gaps in the cubes.</p><p>To facilitate this process, the VMP includes a mapping wizard, which provides the user an interactive mapping functionality back and forth between business ecosystem map elements and business model cube elements and between the slips on a business canvas (shown as post-it notes in Fig. <ref type="figure" target="#fig_8">8</ref>) and business model cube elements (see Table <ref type="table" target="#tab_0">1</ref> for a mapping that holds for the business model canvas) <ref type="foot" target="#foot_7">11</ref> . Using this mapping functionality, the structured models used in the Prototype stage can largely be generated from the graphical models used in the Discover stage. Vice-versa, a large amount of the data in the business model cubes can be visually represented in the business ecosystem map and business canvases. The mapping thus affords a great deal of flexibility in CBMP process, providing two-way traceability and allowing to move back and forth between Discover and Prototype stages, and choosing between top-down, bottom-up or hybrid approaches to strategic planning.</p><p>Finally, the competencies, activities and values in the strategy map and the information on plan phases and alternatives were used by the analyst in the Prototyping sprints to further elaborate the business model cubes (e.g., entering value formulas and other measurement-related detail to complete their value aggregation structures).</p><p>Adopt Stage. The VMP offers 'dashboarding' functionality for comparing values across plan phases and alternatives. First, a report, as another type of model in the VMP, can be created to tell the story of the plan. The reporting functionality comes with an embedded rich text editor and supports the direct incorporation of Discover stage diagrams such as business ecosystem maps and business canvases. Second, interactive dashboards can be generated from the information in the mission plan presenting comparisons of values using tables and various types of charts (see Fig. <ref type="figure" target="#fig_0">1</ref> for an example of a bar chart). Dashboards can be extended with the creation of scenarios for what-if analyses and simulation, by entering different sets of measurements for selected input values. Scenario results can then be presented in the dashboard, for comparison reasons, as well. It is also possible to promote a 'best' scenario to update the plan. Value measurements can be imported from csv-files and exported as csv-files or as xlsx-files (for further analysis in Excel). Using the import functionality, actual values can also be compared with values in the plan, typically based on a time line view in the dashboards. This functionality is essential for monitoring plan implementation, as part of the 'continuous' strategic planning process of the CBMP method.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Discussion</head><p>The analysis of the LCC case-study taught us that the approach to value modeling with VDML using the VMP has some distinctive features, which might not be shared with other value modeling approaches and applications. Probably the most distinctive feature is that CBMP is highly business-oriented in the sense that value models are constructed through a transparent use of VDML. Value management professionals and other strategic planning stakeholders are offered business-friendly interfaces (e.g., business canvases, business ecosystem maps, strategy maps, business model cubes, interactive dashboards), without ever having to work directly with VDML. In other words, no VDML knowledge is required to use the method. Nevertheless, all business model packages stored in the VMP are valid VDML value delivery models. <ref type="foot" target="#foot_8">12</ref> Hence, all VMP model contents are instantiations of the VDML and SMM meta-models. Another distinctive feature is that value modeling is used for strategic planning. Specifically, CBMP regards the business model as the unit for strategic planning, employing a business model framework that is multi-perspective (resulting in an ecosystem of interrelated business models), considers structured relationships in terms of value proposition exchanges between all ecosystem participants (and not just customer value propositions and customer relationships), uses a uniform, unambiguous concept of value (for all participants), and is highly dynamic (allows for a continuous process of strategic planning). Based on the review of strategic planning theories and models in <ref type="bibr" target="#b31">[32]</ref>, we can characterize the CBMP approach to strategic planning as assuming a goalbased strategic model (i.e., setting value objectives aligned with mission and vision, and phased over time) and to some extent also a scenario planning model (i.e., exploring different alternatives per phase in the strategic plan to cope with external forces). The goal-based model is the most adopted model of strategic planning <ref type="bibr" target="#b31">[32]</ref>, which provides some justification to the design rationale of the CBMP method.</p><p>Of course, more research is needed on the design of the CBMP method. Our current client/context-initiated design-based research is not without limitations. First, the method as presented in this paper was the result of the analysis of a single case-study. Furthermore, this case did not result from a real-life application of the CBMP, but was developed for training value management professionals in the use of the VMP. To mitigate the threat that our analysis is not valid or generalizable, the two value architects from VDMbee who developed the case-study, were involved in the research and helped the researchers to interpret the case-study data. These value management experts have applied CBMP using the VMP in numerous real-life projects and used this experience to develop the case-study, which is not fictional but based on real data about Ryanair that is publicly available on the Internet. Nevertheless, we acknowledge that to raise the level of knowledge of CBMP to that of a design theory, we need to investigate more in-depth its theoretical underpinning and also evaluate the method.</p><p>Further plans for developing the CBMP method as supported by the VMP tool include (but are not limited to) providing explicit visualization of value streams and competencies (e.g., value stream maps based on VDML activity network diagrams), incorporating and visualizing libraries <ref type="foot" target="#foot_9">13</ref> (e.g., VDML role libraries, VDML capability library diagrams, VDML capability heatmaps), and automated monitoring of strategy plan implementation. In the near future, VDMbee also intends to add views for showing differences between As-Is and To-Be in a user-friendly way, such that specific differences between previous and next phases can be framed into requirements for projects to implement the plan. To support this development, we plan to conduct research on the integration of CBMP with methods of capability-based planning, portfolio management, enterprise architecture management, business process management, and change management. Given the raising importance of capability-based enterprise modeling in the field, we also plan to investigate the integration of CBMP's multi-perspective business model ecosystem with the service ecosystem view for strategic sourcing of capabilities developed in <ref type="bibr" target="#b32">[33]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Conclusion</head><p>This paper presents an account of the industrial practice of value modeling with VDML by means of the specific approach taken by value management analysts when using the Value Management Platform (VMP) tool of the company VDMbee. The contribution of this paper is to make the tacit knowledge of this approach, called continuous business model planning (CBMP) and currently only described at an introductory level <ref type="bibr" target="#b5">[6]</ref>, explicit by identifying and extracting the method underlying the use of the VMP for CBMP. By analyzing the CBMP case-study of a low-cost carrier, we were able to describe a 'situated implementation' of the CBMP method artifact, in terms of purpose, process, activities, organization, participants, models, and techniques used.</p><p>Our research addresses the knowledge gap of 'how' to apply VDML as currently only anecdotic evidence is publicly available. We hope this paper helps furthering the understanding of value modeling with VDML of both value management professionals and value modeling researchers. By presenting the specific tool-supported method of CBMP, we intend to increase the maturity level of value modeling and raise the interest of practitioners and researchers in further exploring and researching this method.</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. VMP screenshot showing a comparison of four calculated plan values in the next year for alternative implementations of the current business model, based on market prognoses 2 .</figDesc><graphic coords="4,216.24,387.36,162.96,197.76" type="bitmap" /></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. VMP screenshot showing three phases in the plan for the mission.</figDesc><graphic coords="6,124.80,315.36,345.84,59.04" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 3 .</head><label>3</label><figDesc>Fig.3. High-level overview of continuous business model planning (taken from<ref type="bibr" target="#b5">[6]</ref>).</figDesc><graphic coords="6,158.40,451.44,278.40,167.52" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Fig. 4 .</head><label>4</label><figDesc>Fig. 4. Organization of the continuous business model planning engagement (taken from [6])</figDesc><graphic coords="7,181.44,447.36,232.56,95.76" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Fig. 5 .</head><label>5</label><figDesc>Fig. 5. VMP screenshot showing four business models owned by the LCC under study.</figDesc><graphic coords="8,156.72,171.60,281.52,51.60" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head>Fig. 6 .</head><label>6</label><figDesc>Fig. 6. VMP screenshot showing the 'shops' business model cube visualization.</figDesc><graphic coords="9,166.56,303.36,262.32,254.88" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_6"><head>1 . 3 . 4 .</head><label>134</label><figDesc>Value network design: Designing participant networks by defining participants, their roles, value propositions exchanged (i.e., offered and received) and their valuespertaining to value propositions, customers, partners and values faces of the business model cubes; 2. Value stream design: Designing value streams by defining activities that pursue value propositions, the participant roles that perform those activities, the values they create, and the values of value propositions and my propositions they contribute to -pertaining to activities and value faces of the business model cubes; Competency design: Identifying the capabilities and resources that are needed to perform the work represented by the activities -pertaining to the competencies face of the business model cubes; Value impact design &amp; measurement: Designing the value aggregation structure by entering value measurements 7 and value formulas that relate business model values (i.e., activity values, value proposition values and my proposition values) and plan values, within and if relevant across plan phases -pertaining to value propositions, activities, and values faces of the business model cubes and to plan values.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_7"><head>Fig. 7 .</head><label>7</label><figDesc>Fig. 7. VMP screenshot showing the LCC business ecosystem map</figDesc><graphic coords="11,125.28,147.36,344.64,185.76" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_8"><head>Fig. 8 .</head><label>8</label><figDesc>Fig. 8. VMP screenshot showing the LCC operation's 'flights' business model canvas.</figDesc><graphic coords="12,124.80,147.36,345.84,130.32" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_9"><head>Fig. 9 .</head><label>9</label><figDesc>Fig. 9. One of the strategy maps used in the LCC case-study.</figDesc><graphic coords="12,124.80,414.72,345.84,200.40" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_10"><head>Fig. 10 .</head><label>10</label><figDesc>Fig. 10. VMP screenshot showing the filled story-telling form for the 'flights' value proposition in the 'flights' business model.</figDesc><graphic coords="13,189.36,147.36,216.72,174.72" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head>Table 1 .</head><label>1</label><figDesc>Construct mappings supported by the VMP</figDesc><table><row><cell>BM canvas</cell><cell>BM cube</cell><cell>Business ecosystem</cell><cell>VDML</cell></row><row><cell></cell><cell></cell><cell>map</cell><cell></cell></row><row><cell>Key partners</cell><cell>Partners</cell><cell>Enterprises, market seg-</cell><cell>Participant</cell></row><row><cell></cell><cell></cell><cell>ments, individuals</cell><cell>(partner role)</cell></row><row><cell>Key activities</cell><cell>Activities</cell><cell></cell><cell>Activities</cell></row><row><cell>Key resources</cell><cell>Competencies</cell><cell></cell><cell>Resources</cell></row><row><cell>Value propositions 9</cell><cell cols="2">Value propositions Value propositions</cell><cell>Value propositions</cell></row><row><cell>Customer segments</cell><cell>Customers</cell><cell>Enterprises, market seg-</cell><cell>Participants</cell></row><row><cell></cell><cell></cell><cell>ments, individuals</cell><cell>(customer role)</cell></row><row><cell>Cost structures</cell><cell>Values 10</cell><cell></cell><cell>Value Elements</cell></row><row><cell>Revenue streams</cell><cell>Values 10</cell><cell></cell><cell>Value Elements</cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="2" xml:id="foot_0">Market size increases from 2200 million tickets in year 0 to 2250 million tickets in year 1 and market share increases from 5% in year 0 to 5.5% (unchanged policy) or 10% (low fares, low fares &amp; partial lease) in year 1.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_1">A phase alternative in the VMP thus matches with a VDML scenario within a VDML value delivery model.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_2">The LCC owns many other business models, but for the sake of simplicity we limit the demonstration of the CBMP to the four models listed.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_3">Currently, VDML value streams have no direct representation in the VMP, but based on the information provided by the tool, value stream maps can be constructed that are consistent with VDML activity network diagrams.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_4">In VMP's business model framework, the competencies of customers and partners, if needed to model, can be described in the business models owned by them.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_5">Value measurement in the VMP is fully consistent with the OMG's Structured Metrics Metamodel (SMM)<ref type="bibr" target="#b27">[28]</ref>.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_6">The business ecosystem map also allowed discovering two further business models not owned by key participants: 'LCC hosting' owned by airports and 'LCC customers' owned by duty free companies. These business models were not further elaborated in the case-study.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="11" xml:id="foot_7">For other types of business canvas supported by the VMP, other mappings exist. The mapping from the business model innovation canvas to the business model cubes is the most straightforward.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="12" xml:id="foot_8">Allowing entire plans (with all data) to be imported and exported to facilitate collaboration, but also 'downstream development' using a model-driven approach (e.g., derive business process skeletons, software skeletons).</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="13" xml:id="foot_9">The VMP already allows for the creation, import and export of vocabulary libraries such that users can label model elements with terms that are common to their community.</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Value network analysis and value conversion of tangible and intangible assets</title>
		<author>
			<persName><forename type="first">V</forename><surname>Allee</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of intellectual capital</title>
		<imprint>
			<biblScope unit="volume">9</biblScope>
			<biblScope unit="page" from="5" to="24" />
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">E-service design using i* and e 3 value modeling</title>
		<author>
			<persName><forename type="first">J</forename><surname>Gordijn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Yu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Van Der Raadt</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEEE software</title>
		<imprint>
			<biblScope unit="volume">23</biblScope>
			<biblScope unit="page" from="26" to="33" />
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<title level="m" type="main">Building the Agile Enterprise: With Capabilities, Collaborations and Values</title>
		<author>
			<persName><forename type="first">F</forename><forename type="middle">A</forename><surname>Cummins</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2016">2016</date>
			<publisher>Morgan Kaufmann</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m">Object Management Group: Value Delivery Metamodel</title>
				<imprint>
			<publisher>OMG</publisher>
			<date type="published" when="2015">2015</date>
			<biblScope unit="volume">1</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<ptr target="http://www.vdmbee.com" />
		<title level="m">VDMbee Homepage</title>
				<imprint>
			<date type="published" when="2017-12-18">2017/12/18</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<monogr>
		<author>
			<persName><forename type="first">H</forename><surname>De Man</surname></persName>
		</author>
		<ptr target="https://vdmbee.com/2017/12/" />
		<title level="m">Continuous Business Model Planning with VDMbee</title>
				<imprint>
			<date type="published" when="2017-12-18">2017/12/18</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Multi-perspective enterprise modeling: foundational concepts, prospects and future research challenges</title>
		<author>
			<persName><forename type="first">U</forename><surname>Frank</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Software and Systems Modeling</title>
		<imprint>
			<biblScope unit="volume">13</biblScope>
			<biblScope unit="page" from="941" to="962" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Towards a Reference ontology of complex economic exchanges for Accounting Information Systems</title>
		<author>
			<persName><forename type="first">I</forename><surname>Blums</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Weigand</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 20th International Conference on Enterprise Distributed Object Computing (EDOC)</title>
				<meeting>the 20th International Conference on Enterprise Distributed Object Computing (EDOC)</meeting>
		<imprint>
			<publisher>IEEE</publisher>
			<date type="published" when="2016">2016</date>
			<biblScope unit="page" from="1" to="10" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">The design of a core value ontology using ontology patterns</title>
		<author>
			<persName><forename type="first">F</forename><surname>Gailly</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Roelens</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Guizzardi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 35th International Conference on Conceptual Modeling (ER)</title>
				<meeting>the 35th International Conference on Conceptual Modeling (ER)</meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2016">2016</date>
			<biblScope unit="page" from="183" to="193" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">Towards an Ontology of Value Ascription</title>
		<author>
			<persName><forename type="first">N</forename><surname>Guarino</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Andersson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Johannesson</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Livieri</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 9th International Conferenece on Formal Ontology in Information Systems (FOIS)</title>
				<meeting>the 9th International Conferenece on Formal Ontology in Information Systems (FOIS)</meeting>
		<imprint>
			<publisher>IOS Press</publisher>
			<date type="published" when="2016">2016</date>
			<biblScope unit="page">331</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">An Ontological Analysis of Value Propositions</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">P</forename><surname>Sales</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Guarino</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Guizzardi</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Mylopoulos</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 21st International Conference on Enterprise Distributed Object Computing (EDOC)</title>
				<meeting>the 21st International Conference on Enterprise Distributed Object Computing (EDOC)</meeting>
		<imprint>
			<publisher>IEEE</publisher>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="184" to="193" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<analytic>
		<title level="a" type="main">The Development and Experimental Evaluation of a Focused Business Model Representation</title>
		<author>
			<persName><forename type="first">B</forename><surname>Roelens</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Poels</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Business &amp; Information Systems Engineering</title>
		<imprint>
			<biblScope unit="volume">57</biblScope>
			<biblScope unit="page" from="61" to="71" />
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">A Systematic Approach to Business Modeling Based on the Value Delivery Modeling Language</title>
		<author>
			<persName><forename type="first">J</forename><surname>Metzger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Kraemer</surname></persName>
		</author>
		<author>
			<persName><forename type="middle">O</forename><surname>Terzidis</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Complexity in Entrepreneurship, Innovation and Technology Research</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2016">2016</date>
			<biblScope unit="page" from="245" to="266" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<title level="m" type="main">Designing Compliance Patterns: Integrating Value Modeling, Legal Interpretation and Argument Schemes for Legal Risk Management</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">K M</forename><surname>Kiriinya</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
		<respStmt>
			<orgName>University of Luxembourg. Luxembourg</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">PhD dissertation</note>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">VDML4RS: a tool for reputation systems modeling and design</title>
		<author>
			<persName><forename type="first">L</forename><surname>Bettini</surname></persName>
		</author>
		<author>
			<persName><forename type="middle">S</forename><surname>Capecchi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 8th International Workshop on Social Software Engineering</title>
				<meeting>the 8th International Workshop on Social Software Engineering</meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2016">2016</date>
			<biblScope unit="page" from="8" to="14" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<monogr>
		<title level="m" type="main">Integrating value modeling into ArchiMate</title>
		<author>
			<persName><forename type="first">H</forename><surname>Ding</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2016">2016</date>
			<pubPlace>Enschede</pubPlace>
		</imprint>
		<respStmt>
			<orgName>University of Twente</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">Thesis</note>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Combining ArchiMate with Other Standards and Approaches</title>
		<author>
			<persName><forename type="first">M</forename><surname>Lankhorst</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Aldea</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Niehof</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Enterprise Architecture at Work</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="123" to="140" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<monogr>
		<author>
			<persName><forename type="first">S</forename><surname>Eylenbosch</surname></persName>
		</author>
		<title level="m">Een nieuwe standaard voor business modeling: Het modelleren van value delivery</title>
				<meeting><address><addrLine>Gent</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2013">2013</date>
		</imprint>
		<respStmt>
			<orgName>Ghent University</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">Thesis</note>
</biblStruct>

<biblStruct xml:id="b18">
	<monogr>
		<title level="m" type="main">The congruence between VDML and DAMIAN: A case study: In vehicle signage</title>
		<author>
			<persName><forename type="first">D</forename><surname>De Langhe</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
			<pubPlace>Gent</pubPlace>
		</imprint>
		<respStmt>
			<orgName>Ghent University</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">Thesis</note>
</biblStruct>

<biblStruct xml:id="b19">
	<monogr>
		<title level="m" type="main">Analyse van de impact van veranderingen op de telecomsector aan de hand van dynamische waardenetwerken</title>
		<author>
			<persName><forename type="first">B</forename><surname>Devocht</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
			<pubPlace>Gent</pubPlace>
		</imprint>
		<respStmt>
			<orgName>Ghent University</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">Thesis</note>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">A Design Science Research Methodology for Information Systems Research</title>
		<author>
			<persName><forename type="first">K</forename><surname>Peffers</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Tuunanen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Rothenberger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Chatterjee</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Management Information Systems</title>
		<imprint>
			<biblScope unit="volume">24</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="45" to="77" />
			<date type="published" when="2008">2008</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">Design science in Information Systems research</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">R</forename><surname>Hevner</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">T</forename><surname>March</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Park</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Ram</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">MIS Quarterly</title>
		<imprint>
			<biblScope unit="volume">28</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="75" to="105" />
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<analytic>
		<title level="a" type="main">Positioning and presenting design science research for maximum impact</title>
		<author>
			<persName><forename type="first">S</forename><surname>Gregor</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">R</forename><surname>Hevner</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">MIS Quarterly</title>
		<imprint>
			<biblScope unit="volume">37</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="337" to="355" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b23">
	<analytic>
		<title level="a" type="main">From Strategy to Business Models and onto Tactics</title>
		<author>
			<persName><forename type="first">R</forename><surname>Casadesus-Masanell</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">E</forename><surname>Ricart</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Long Range Planning</title>
		<imprint>
			<biblScope unit="volume">43</biblScope>
			<biblScope unit="page" from="195" to="215" />
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<monogr>
		<title level="m">Object Management Group: Business Motivation Model</title>
				<imprint>
			<publisher>OMG</publisher>
			<date type="published" when="2015">2015</date>
			<biblScope unit="volume">1</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b25">
	<analytic>
		<title level="a" type="main">The Business Model: Recent Developments and Future Research</title>
		<author>
			<persName><forename type="first">C</forename><surname>Zott</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Amit</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Massa</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Management</title>
		<imprint>
			<biblScope unit="volume">37</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="1019" to="1042" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b26">
	<analytic>
		<title level="a" type="main">The Business Model Cube</title>
		<author>
			<persName><forename type="first">P</forename><surname>Lindgren</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><forename type="middle">H</forename><surname>Rasmussen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Multi Business Model Innovation and Technology</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="135" to="182" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b27">
	<monogr>
		<title level="m">Object Management Group: Structured Metrics Meta-model</title>
				<imprint>
			<publisher>OMG</publisher>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
	<note>version 1.1.1</note>
</biblStruct>

<biblStruct xml:id="b28">
	<monogr>
		<title level="m" type="main">Business model generation: A handbook for visionaries, game changers, and challengers</title>
		<author>
			<persName><forename type="first">A</forename><surname>Osterwalder</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Pigneur</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2010">2010</date>
			<publisher>John Wiley &amp; Sons</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b29">
	<monogr>
		<title level="m" type="main">The business model ontology: A proposition in a design science approach</title>
		<author>
			<persName><forename type="first">A</forename><surname>Osterwalder</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2004">2004</date>
		</imprint>
		<respStmt>
			<orgName>University of Lausanne. Lausanne</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">PhD dissertation</note>
</biblStruct>

<biblStruct xml:id="b30">
	<monogr>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">S</forename><surname>Kaplan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">P</forename><surname>Norton</surname></persName>
		</author>
		<title level="m">Strategy maps: Converting intangible assets into tangible outcomes</title>
				<imprint>
			<publisher>Harvard Business Press</publisher>
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b31">
	<monogr>
		<title level="m" type="main">Incorporating Enterprise Strategic Plans into Enterprise Architecture</title>
		<author>
			<persName><forename type="first">C</forename><surname>Azevedo</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
		<respStmt>
			<orgName>University of Twente and Federal University of Espírito Santo. Enschede</orgName>
		</respStmt>
	</monogr>
	<note type="report_type">PhD dissertation</note>
</biblStruct>

<biblStruct xml:id="b32">
	<analytic>
		<title level="a" type="main">Value-Driven Strategic Sourcing Based on Service-Dominant Logic</title>
		<author>
			<persName><forename type="first">L</forename><surname>Rafati</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Poels</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Service Science</title>
		<imprint>
			<biblScope unit="volume">9</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="275" to="287" />
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

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