<?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">Building Software Ecosystems from a Reuse Perspective</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Cláudia</forename><forename type="middle">Maria</forename><surname>Lima</surname></persName>
							<email>werner@cos.ufrj.br</email>
							<affiliation key="aff0">
								<orgName type="department">PESC/COPPE</orgName>
								<orgName type="institution">Universidade Federal do Rio de Janeiro Rio de Janeiro</orgName>
								<address>
									<settlement>-RJ</settlement>
									<country key="BR">Brazil</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Building Software Ecosystems from a Reuse Perspective</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">F0813EC41EFE2695CC9A7BA720705A93</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T08:05+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>CBD</term>
					<term>SPL</term>
					<term>component</term>
					<term>service</term>
					<term>repository</term>
					<term>VBSE</term>
					<term>SECO</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Software Ecosystems (SECOs) involve various stakeholders interacting with a shared market for software and services, exchanging information, resources and artifacts within a common technological platform. In this context, well-known software reuse approaches such as Component-Based Development (CBD) and Software Product Lines (SPL) can lead companies to SECOs. This transition depends on decisions related to making their platforms available outside the organizational boundary, in order to explore competition and collaboration in the software industry. Since 1997, we have been building an environment for supporting software engineering activities such as modeling, construction, reuse and group interaction (contemplating software distributed development), providing an integrated set of tools and a repository of reusable components. By using the Odyssey Environment, components and architectures can be developed, according to a domain engineering process, which are made available in the Brechó repository and reused in all phases of an application development, through an application engineering process. An SPL can either be based on components or services, and Brechó provides mechanisms to support both of them. In this context, we have been trying to understand the components market movements, particularly distribution channels, through a Value-Based Software Engineering (VBSE) perspective that focuses on the historical data collection and exploration aiming to extract useful information and present it according to the various stakeholders' profiles. By evaluating its importance, considering all facets of value for component (i.e., costs, benefits, risks, time, opportunities, needs, flexibilities, and requirements) and how they change and evolve amongst the perspectives, activities and actions of stakeholders regarding value in a value chain, we realize that we have been building ecosystems based on specific architectures/components/services. Thus in this talk, we exploit a software reuse perspective on SECOs based on our group's experience.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body/>
		<back>
			<div type="references">

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