Дисертації з теми "Software product line organisations"
Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями
Ознайомтеся з топ-50 дисертацій для дослідження на тему "Software product line organisations".
Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.
Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.
Переглядайте дисертації для різних дисциплін та оформлюйте правильно вашу бібліографію.
JUNIOR, CARLOS ROBERTO MARQUES. "COLLABORATIVE CONFIGURATION OF SOFTWARE PRODUCT LINE." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2011. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=18370@1.
Повний текст джерелаA configuração de produto é uma atividade chave para permitir a customização em massa. Ela corresponde a produção de um sistema computacional a partir de uma linha de produtos de software, respeitando as necessidades individuais dos clientes. Na prática, a atividade de configuração do produto pode se tornar uma tarefa complexa, principalmente porque envolve várias partes interessadas com diferentes competências para tomar decisões. Vários trabalhos proprõem decompor a atividade de configuração em estágios pré-estabelecidos, atravrés dos quais os interessados podem tomar suas decisões de forma separada e coerente. No entanto, quando há uma descentralização geográfica do conhecimento necessário em cada etapa e/ou quando os requisitos do cliente forem imprecisos e mudarem com frequência, essas soluções propostas não se aplicam. Para resolver essas questões, este trabalho proprõe uma abordagem de configuração dinâmica e colaborativa de produtos com base na metáfora de assistência pessoal. Os assistentes pessoais num ambiente cooperativo coordenam as decisões dos stakeholders e pró-ativamente executam tarefas, tais como o raciocínio sobre as implicaçõoes das decisões, integrando as decisões distribuídas e resolvendo os requisitos divergentes. Uma ferramenta protótipo, chamada Libertas, e dois cenários ilustrativos que avaliam a aplicabilidade da nossa abordagem também são apresentados. O primeiro cenário analisa o processo de configuração para configurar um sistema operacional para suportar os requisitos de negócio de uma empresa. O segundo aborda um cen´ario com uma linha de produtos de software para portais web.
Product configuration is a key activity for enabling mass customization. It corresponds to tailoring a software application from a software product line, respecting individual customer requirements. In practice, the product configuration activity is challenging, mainly because it involves numerous stakeholders with different expertise making decisions. Several works claim to decompose the configuration activity into pre-arranged stages, whereby stakeholders can make their decisions in a separated way and coherent fashion. However, due to the decentralization in geography of the knowledge required in each stage and that customer requirements could be imprecise and change frequently, the proposed solutions do not apply. To address these issues, this work proposes a dynamic and collaborative product configuration approach based on the personal assistant metaphor. Personal assistants in a cooperative way coordinate stakeholders´ decisions and proactively perform tasks, such as reasoning about the ramifications of decisions, integrating distributed decisions and resolving divergent requirements. A tool prototype, called Libertas, and two case studies that evaluate the applicability of our approach are also presented. The first case study analyzes the configuration process to configure an operational system to support the business requirements of an enterprise. The second one addresses a scenario of a software product line for web portals.
Ramos, Alves Vander. "Implementing software product line adoption strategies." Universidade Federal de Pernambuco, 2007. https://repositorio.ufpe.br/handle/123456789/2044.
Повний текст джерелаLinha de Produtos de Software (LPS) é uma aborgadem promissora para o desenvolvimento de um conjunto de produtos focados em um segmento de mercado e desenvolvidos a partir de um conjunto comum de artefatos. Possíveis benefícios incluem reuso em larga escala e significativa melhoria em produtividade. Um problema-chave associado, no entanto, é o tratamento de estratégias de implantação, em que uma organização decide iniciar uma LPS a partir do zero, fazer bootstrap de produtos existentes em uma LPS, ou evoluir uma LPS. Em particular, no nível de implementação e de modelo de features, métodos de desenvolvimento carecem de apoio adequado para extração e evolução de LPSs. Neste contexto, apresentamos um m´etodo original provendo diretrizes concretas para extração e evolução de LPSs no nível de implementação e de modelo de features, nos quais proporciona reuso e segurança. O método primeiro faz o bootstrap da LPS e então a evolui com uma abordagem reativa. O método se baseia em uma coleção de refatoramentos tanto na implementação (refatoramentos orientados a aspectos) como no modelo de features. O método foi avaliado no domínio altamente variável de jogos móveis
Santiago, Ferreira Felype. "MAKING SOFTWARE PRODUCT LINE EVOLUTION SAFER." Universidade Federal de Pernambuco, 2012. https://repositorio.ufpe.br/handle/123456789/2852.
Повний текст джерелаCoordenação de Aperfeiçoamento de Pessoal de Nível Superior
Desenvolvedores evoluem linhas de produtos de software (LPSs) manualmente ou usando Ferramentas típicas de refatoração de programas. No entanto, quando a evolução de uma Linha de produtos é feita para introduzir novas características, ou para melhorar o seu projeto, é importante ter a certeza de que o comportamento dos produtos existentes não é modificado. Programas típicos de refatoração de software não podem garantir isso porque o contexto de LPS vai além de código, e outros tipos de artefatos de código, e envolve artefatos adicionais, tais como modelos de feature e configuration knowledge. Além disso, em uma LPS, normalmente temos que lidar com um conjunto de possíveis artefatos de código-fonte alternativos que não constitui um programa bem formado. Como resultado, mudanças manuais e ferramentas de refatoração de software existentes podem introduzir mudanças comportamentais ou invalidar configurações de produtos existentes. Para evitar isso, propomos abordagens e implementamos ferramentas para tornar a evolução de linhas de produtos mais segura; essas ferramentas verificam se transformações em LPS são refinamentos no sentido de que preservam o comportamento dos produtos originais da LPS. Elas implementam aproximações diferentes e práticas de uma definição formal de refinamento de LPS. Avaliamos as abordagens em cenários concretos de evolução de LPS, onde o comportamento do produto existente deve ser preservado. No entanto, nossas ferramentas constataram que algumas transformações introduziram mudanças comportamentais. Além disso, avaliamos refinamentos defeituosos, e o conjunto de ferramentas detectou as mudanças de comportamento.
Hanssen, Geir Kjetil. "From Agile Software Product Line Engineering Towards Software Ecosystems." Doctoral thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2010. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-11890.
Повний текст джерелаAddy, Edward A. "Verification and validation in software product line engineering." Morgantown, W. Va. : [West Virginia University Libraries], 1999. http://etd.wvu.edu/templates/showETD.cfm?recnum=1068.
Повний текст джерелаTitle from document title page. Document formatted into pages; contains vi, 75 p. : ill. (some col.). Includes abstract. Includes bibliographical references (p. 35-39).
Holmes, Christopher Kenneth. "Generative modelling with software product line architectures." Thesis, University of York, 2007. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.503324.
Повний текст джерелаParisi, Luca. "A Knowledge Flow as a Software Product Line." Master's thesis, Alma Mater Studiorum - Università di Bologna, 2016. http://amslaurea.unibo.it/12217/.
Повний текст джерелаRahman, Asim. "Metrics for the Structural Assessment of Product Line Architecture." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3427.
Повний текст джерела+92-42-5727639
Nóbrega, Jarley Palmeira. "An integrated cost model for product line engineering." Universidade Federal de Pernambuco, 2008. https://repositorio.ufpe.br/handle/123456789/1639.
Повний текст джерелаDentro da comunidade de desenvolvimento de software, o processo de reutilizar artefatos ao invés de construí-los do zero normalmente conhecido como reuso de software tem se mostrado uma maneira efetiva de evitar os problemas associados ao estouro de orçamentos e cronogramas de projeto. Apesar do imenso potencial, a adoção de reuso em larga escala ainda não prevalece dentro das organizações. Entre os fatores que contribuem para isso, estão os obstáculos econômicos enfrentados pelas empresas, com uma clara preocupação sobre os custos para desenvolver software para e com reuso. Atualmente, as decisões relacionadas com reuso são tratadas sob um ponto de vista econômico, devido ao fato do desenvolvimento de software reutilizável ser considerado pelas organizações como um investimento. Além disso, a adoção de linhas de produto de software dentro desse contexto traz à tona alguns inibidores de reuso, como por exemplo, a aplicação dos modelos de custo para reuso de forma restrita, a falta de uma estratégia para a análise de investimentos, e o fato que poucos modelos de custo possuem uma abordagem baseada na utilização de cenários de reuso. Nesse contexto, esse trabalho apresenta um modelo integrado de custo para engenharia de linhas de produto, com o objetivo de auxiliar as organizações em seus processos de tomada de decisões na avaliação de investimentos em reuso. Os fundamentos para o modelo foram baseados em uma vasta pesquisa sobre modelos de custo para reuso e sua especialização para linhas de produto de software. O modelo apresenta a definição de funções de custo e benefícios, cenários de reuso e uma estratégia de investimento para linhas de produto. Também é apresentado um modelo de simulação baseado na técnica de Monte Carlo. Por último, um estudo de caso discute os resultados de dentro do contexto de um projeto real de desenvolvimento de software, onde o modelo foi aplicado
Eriksson, Magnus. "An approach to software product line use case modeling." Licentiate thesis, Umeå University, Computing Science, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-676.
Повний текст джерелаOrganizations developing software intensive defense systems are today faced with a number challenges related to characteristics of both the market place and the system domain:
1. Systems grow ever more complex, consisting of tightly integrated mechanical, electrical/electronic and software components.
2. Systems are often developed in short series; ranging from only a few to a few hundred units.
3. Systems have very long life spans, typically 30 years or longer.
4. Systems are developed with high commonality between different customers; however systems are always customized for specific needs.
The goal of the research presented in this thesis is to investigate methods and tools to enable efficient development and maintenance of systems in such a context. The strategy adopted in this work is to utilize the forth system characteristic, high commonality, to achieve this.
One approach to software reuse, which could be a potential solution as it enables reuse of common parts but at the same time allow for variations, is known as software product line development. The basic idea of this approach is to use domain knowledge to identify common parts within a family of related products and to separate them from the differences between the products. The commonalties are then used to create a product platform that can be used as a common baseline for all products within such a product family.
The main contribution of this licentiate thesis is a product line use case modeling approach tailored towards organizations developing software intensive defense systems. We describe how a common and complete use case model can be developed and maintained for a whole family of products, and how the variations within such a family are modeled using a feature model. Concrete use case models, for particular products within a family, can then be generated by selecting features from a feature model. We furthermore describe extensions to the commercial requirements management tool Telelogic DOORS and the UML modeling tool IBM-Rational Rose to support the proposed approach.
The approach was applied and evaluated in an industrial case study in the target domain. Based on the collected case study data we draw the conclusion that the approach performs better than modeling according to the styles and guidelines specified by the IBM-Rational Unified Process (RUP) in the current industrial context. The results however also indicate that for the approach to be successfully applied, stronger configuration management and product planning functions than traditionally found in RUP projects are needed.
Istoan, Paul. "Methodology for the derivation of product behaviour in a Software Product Line." Phd thesis, Université Rennes 1, 2013. http://tel.archives-ouvertes.fr/tel-00925479.
Повний текст джерелаRossel, Cid Pedro Osvaldo. "Software product line model for the meshing tool domain." Tesis, Universidad de Chile, 2013. http://www.repositorio.uchile.cl/handle/2250/113113.
Повний текст джерелаUna malla es una discretización de la geometría de un cierto dominio. Las mallas pueden estar compuestas de diversos elementos: triángulos, cuadriláteros, tetraedros, etc. Una herramienta para la generación de mallas es un aplicación que permite crear, refinar, desrefinar, mejorar, suavizar, visualizar y posprocesar mallas y/o una región particular de ella, como también asignar valores físicos a los elementos de la malla (temperatura, concentración, etc.). Las herramientas para la generación de mallas son complejas y sofisticadas, y construir una herramienta nueva desde cero o mantener una existente, demanda un esfuerzo enorme. Existe una necesidad y oportunidad para usar enfoques nuevos en el desarrollo de estas herramientas, de manera de reducir tanto el tiempo como los costos de desarrollo, sin comprometer la calidad. La experiencia en el desarrollo de estas herramientas provee la motivación para la construcción de otras nuevas mediante la reutilización del trabajo realizado durante los desarrollos previos. Estas herramientas comparten varias características y sus variaciones pueden ser manejadas sistemáticamente. Esto hace que el desarrollo de estas herramientas sea una buena oportunidad para aplicar el enfoque de Línea de Productos de Software (LPS). Los procesos existentes de LPS son generales y requieren usualmente una serie de pasos y documentación innecesaria en el dominio de las herramientas para la generación de mallas. Así, esta tesis propone un modelo de proceso de LPS específico para este tipo de herramientas. Un proceso de desarrollo de LPS está centrado en la reutilización de software, e involucra principalmente dos fases: la ingeniería del dominio (ID) y la ingeniería de la aplicación (IA). El proceso presentado en este trabajo está centrado en dos etapas de la ID: el análisis del dominio (AD) y el diseño del dominio (DD). En el AD se define el modelo del dominio y el alcance de la LPS. En el DD la arquitectura de la línea de productos (ALP) es creada; esta arquitectura es válida y compartida por todos los productos en la LPS. Un modelo de características es comúnmente usado para modelar el dominio. En este trabajo, el AD también ocupa un diccionario, escenarios, acciones y metas para proveer el razonamiento utilizado para la construcción del modelo de características. Esta tesis presenta un proceso riguroso para obtener el modelo del dominio. Este modelo es formalizado mediante condiciones de consistencia y completitud. El proceso de definición del alcance es presentado a través de un diagrama de actividad. Además, el enfoque presentado en esta tesis presenta explícitamente los diferentes productos de la LPS, estableciendo relaciones entre productos y las características de la LPS, lo que permite administrar el desarrollo del producto. La etapa de DD se centra en la creación de la ALP, artefacto esencial para la construcción de productos de la LPS. Para ello, este trabajo provee un proceso deductivo y otro transformacional. En el primero, una ALP explícita es desarrollada, usando los artefactos producidos en el AD. Además, tanto la vista arquitectónica estructural como la de comportamiento son establecidas. Ambas vistas son generales y permiten la representación de cualquier producto dentro del alcance de la LPS. En el proceso transformacional, una ALP implícita es desarrollada usando reglas de transformación, las que han sido creadas usando artefactos producidos en el AD. En este proceso se produce la arquitectura para productos específicos, y la ALP es definida como la suma de todas las arquitecturas de los productos. Tanto el AD como el DD son descritos en detalle, y la aplicación del modelo de la LPS es ilustrado a través de un ejemplo bien documentado en el dominio de las herramientas para la generación de mallas, el que tiene un grado relativamente alto de complejidad. En este ejemplo, un modelo del dominio formalizado es introducido, y la arquitectura es definida tanto para el proceso deductivo como para el transformacional.
Tzeremes, Vasilios. "End user software product line support for smart spaces." Thesis, George Mason University, 2017. http://pqdtopen.proquest.com/#viewpdf?dispub=10249280.
Повний текст джерелаSmart spaces are physical environments equipped with pervasive technology that sense and react to human activities and changes in the environment. End User Development (EUD) skills vary significantly among end users who want to design, develop and deploy software applications for their smart spaces. Typical end user development is opportunistic, requirements are usually unplanned and undocumented, applications are simplistic in nature, design is ad-hoc, reuse is limited, and software testing is typically haphazard, leading to many quality issues. On the other hand, technical end users with advanced EUD skills and domain expertise have the ability to create sophisticated software applications for smart spaces that are well designed and tested.
This research presents a systematic approach for adopting reuse in end user development for smart spaces by using Software Product Line (SPL) concepts. End User (EU) SPL Designers (who are technical end users and domain experts) design and develop EU SPLs for smart spaces whereas less technical end users derive their individual smart space applications from these SPLs. Incorporating SPL concepts in EUD for smart spaces makes it easier for novice end users to derive applications for their spaces without having to interface directly with devices, networks, programming logic, etc. End users only have to select and configure the EU SPL features needed for their space. Another benefit of this approach is that it promotes reuse. End user requirements are mapped to product line features that are realized by common, optional, and variant components available in smart spaces. Product line features and the corresponding component product line architecture can then be used to derive EU applications. Derived EU applications can then be deployed to different smart spaces, thereby avoiding end users having to create EU applications from scratch. Finally the proposed approach has the potential of improving software quality since testing will be an integral part of EU SPL process.
In particular, this research has: (a) defined a systematic approach for EU SPL Designers to design and develop EU SPLs, (b) provided an EU SPL application derivation approach to enable end users to derive software applications for their spaces, (c) designed an EU SPL meta-model to capture the underlying representation of EU SPL and derived application artifacts in terms of meta-classes and relationships that supports different EUD platforms, (d) designed and implemented an EUD development environment that supports EU SPL development and application derivation, and (e) provided a testing approach and framework for systematic testing of EU SPLs and derived applications.
Sousa, André Luís Sequeira de. "Traceability support in software product lines." Master's thesis, FCT - UNL, 2008. http://hdl.handle.net/10362/1798.
Повний текст джерелаTraceability is becoming a necessary quality of any modern software system. The complexity in modern systems is such that, if we cannot rely on good techniques and tools it becomes an unsustainable burden, where software artifacts can hardly be linked to their initial requirements. Modern software systems are composed by a many artifacts (models, code, etc.). Any change in one of them may have repercussions on many components. The assessment of this impact usually comes at a high cost and is highly error-prone. This complexity inherent to software development increases when it comes to Software Product Line Engineering. Traceability aims to respond to this challenge, by linking all the software artifacts that are used, in order to reason about how they influence each others. We propose to specify, design and implement an extensible Traceability Framework that will allow developers to provide traceability for a product line, or the possibility to extend it for other development scenarios. This MSc thesis work is to develop an extensible framework, using Model-Driven techniques and technologies, to provide traceability support for product lines. We also wish to provide basic and advanced traceability queries, and traceability views designed for the needs of each user.
Verdier, Frédéric. "COMpOSER : a model-driven software product line approach for an effective management of software reuse within software product families and populations." Thesis, Montpellier, 2019. http://www.theses.fr/2019MONTS117.
Повний текст джерелаSoftware systems are constantly increasing in size and complexity, forcing the software industry to migrate their hand-craft development processes, slowly realizing each product, to more systematized and automated ones, mass-producing software at lower costs. This migration process, that we call industrialization, can be achieved through the integration of systematic software reuse and automation in their development processes. Their combination results in the realization of sounder products at lower costs. Existing approaches combining Model-Driven Architecture (MDA) and Software Product Line Engineering (SPLE) partially automate development processes with systematic software reuse by capitalizing on their compatible benefits. While MDA permits developers to define highly reusable assets and automatic operations to perform on them, SPLE systematizes software reuse by relying on the commonalities and variabilities of a set of related products named a software product family. However, these approaches suffer from two major restrictions that can be a brake for companies aiming to industrialize their development processes using these solutions. Firstly, they have difficulties to fully manage variability at different levels of abstraction because of the rapidly increasing complexity of operations performed on assets alongside the addition of new variation points. Then, existing combinations of MDA and SPLE are limited to the management of variability in a software product family. But, in some contexts such as IT services companies, variability can be related to more heterogeneous sets of products than families named software product populations. Although some existing works propose to manage the variability in a software product population, these approaches, by composing independent software product lines, are limited to the composition, and by extension to reuse, of coarse-grained assets.In this PhD thesis, we propose a new approach named COMpOSER (CrOss-platform MOdel-driven Software product line EngineeRing) which defines an efficient way to compose MDA and SPLE in order to fully manages variability in a software product family but also in a software product population without reducing its reuse capabilities. To do so, COMpOSER introduces a new characterization of variability to organize reusable assets in three dimensions: the business dimension; the architecture dimension; and the technological ecosystem dimension. Additionally, this characterization distinguishes inter-domain variability, organizing the different software product families of a population, and intra-domain variability, organizing assets in a single software product family. To properly organize reusable assets, COMpOSER defines a model of fine-grained core assets which is compatible with its characterization of variability. In parallel, our approach defines partially automated operations to produce new software through systematic reuse which permit to fully manage variability without inducing scaling up issues with the addition of new variation points. Thanks to our collaboration with an industrial partner, we could experiment COMpOSER by applying our propositions to help the company industrializing its development processes. As such, we implemented a framework that supports our approach while considering the specificities of our industrial context. This framework embeds the principles of COMpOSER in a format that is easier to understand to developers with little knowledge about SPLE and MDA. In this way, we have observed that the framework facilitated the adoption of our solutions by the company's development teams. Using the COMpOSER framework, we obtained results demonstrating how our approach improves systematic software reuse when compared to concurrent approaches. These results stemmed from empirical experiments performed on concrete industrial case studies
Seidl, Christoph. "Evolution in Feature-Oriented Model-Based Software Product Line Engineering." Master's thesis, Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2012. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-81200.
Повний текст джерелаKnieke, Christoph [Verfasser]. "Managed Evolution of Automotive Software Product Line Architectures / Christoph Knieke." München : Verlag Dr. Hut, 2019. http://d-nb.info/1198542608/34.
Повний текст джерелаArriel, Juliana [Verfasser]. "Personalized recommender systems for software product line configurations / Juliana Arriel." Magdeburg : Universitätsbibliothek, 2018. http://d-nb.info/1164498398/34.
Повний текст джерелаHoxha, Armend. "Generating Members of a Software Product Line Using Combinatory Logic." Digital WPI, 2015. https://digitalcommons.wpi.edu/etd-theses/727.
Повний текст джерелаAndrade, Hugo. "Software Product Line Architectures: Reviewing the Literature and Identifying Bad Smells." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-21678.
Повний текст джерелаSoftware Product Line (SPL) paradigmet har bevisat sig vara ett effektivt sätt att uppnå storskalig återanvändning i olika domäner. Den drar nytta av gemensamma aspekter mellan olika produkter, och överväger samtidigt även produktspecifika egenskaper. Arkitekturen spelar en viktig roll i SPL tekniken, genom att tillhandahålla medel för att bättre förstå och underhålla "product-derivation" miljön. Det är dock svårt att vidareutveckla sådan arkitektur för att det inte alltid är tydligt var och hur den kan omstruktureras. Bidraget från denna avhandling är tvåfaldigt. För det första, den aktuella situationen för "software Product Line Architectures" (PLAs) undersöks genom en systematisk kartläggning. Den ger en översikt av fältet genom analys, och kategorisering av bevis. Studien identifierar luckor, trender och ger framtida riktlinjer för forskning. Vidare adresserar denna avhandling fenomenet arkitektoniska "bad smells" inom kontexten för SPLs. En fallstudie ger en utredning av implikationer av sådana strukturella egenskaper i en variabilitet-baserad miljö. Innan sökningen av "smells", är arkitekturen från en sampel SPL i textredigerar domänen återvunnen från källkoden.
Medeiros, Flávio Mota. "SOPLE-DE: an approach to design service-oriented product line architectures." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/2416.
Повний текст джерелаConselho Nacional de Desenvolvimento Científico e Tecnológico
O reuso de software é um fator extremamente importante para empresas interessadas em aumentar sua produtividade, diminuir os custos e o tempo durante o desenvolvimento de sistemas e melhorar a qualidade de seus produtos e serviços. Nesse contexto, Linhas de Produto de Software (LPS) e Arquitetura Orientada a Serviços (SOA) são duas estratégias que estão atualmente recebendo uma grande atenção, tanto na área acadêmica quanto na indústria de software. Os conceitos de linhas de produto e arquitetura orientada a serviços compartilham alguns objetivos e características que podem ser usados em conjunto para aumentar as taxas de reuso de software. No entanto, para o resultado dessa junção ser otimizado, é necessário utilizar um processo de desenvolvimento bem definido. Caso contrário, a equipe de desenvolvimento poderá produzir software de maneira não sistemática, aumentando as chances de falha, o tempo e o custo de desenvolvimento. Com essa visão, esse trabalho apresenta uma abordagem para o projeto de arquiteturas para linhas de produto orientada a serviços, constituída de um conjunto de atividades e sub atividades com entradas e saídas especificadas, sendo cada uma delas realizada por um conjunto predefinido de papéis com responsabilidades definidas. Essa abordagem visa ajudar arquitetos de software a projetar arquitetura orientada a serviços para domínios específicos. Para garantir a qualidade da abordagem desenvolvida, uma pesquisa extensiva foi realizada para analisar o atual estado da arte de processos para o desenvolvimento orientado a serviços. Foram então considerados os pontos fracos e fortes dos processos estudados com o intuito de identificar e preencher as lacunas neles existentes. Por fim, essa abordagem foi validada e refinada por meio de um estudo acadêmico experimental preliminar
Greaney, Kevin J. "Evolving a simulation model product line software architecture from heterogeneous model representations." Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2003. http://library.nps.navy.mil/uhtbin/hyperion-image/03sep%5FGreaney%5FPhD.pdf.
Повний текст джерелаMunir, Qaiser, and Muhammad Shahid. "Software Product Line:Survey of Tools." Thesis, Linköping University, Department of Computer and Information Science, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-57888.
Повний текст джерелаsoftware product line is a set of software-intensive systems that share a common, managed set of features satisfying the specificneeds of a particular market segment or mission. The main attractive part of SPL is developing a set of common assets which includes requirements, design, test plans, test cases, reusable software components and other artifacts. Tools for the development of softwareproduct line are very few in number. The purpose of these tools is to support the creation, maintenance and using different versions ofproduct line artifacts. This requires a development environment that supports the management of assets and product development,processes and sharing of assets among different products.
The objective of this master thesis is to investigate the available tools which support Software Product Line process and itsdevelopment phases. The work is carried out in two steps, in the first step available Software Product Line tools are explored and a list of tools is prepared, managed and a brief introduction of each tool is presented. The tools are classified into different categoriesaccording to their usage, relation between the tools is established for better organization and understanding. In the second step, two tools Pure::variant and MetaEdit+ are selected and the quality factors such as Usability, Performance, Reliability, MemoryConsumption and Capacity are evaluated.
Rodrigues, Elder de Macedo. "Plets : a product line of model-based testing tools." Pontifícia Universidade Católica do Rio Grande do Sul, 2013. http://hdl.handle.net/10923/5577.
Повний текст джерелаSoftware testing is recognized as a fundamental activity for assuring software quality. Furthermore, testing is also recognized as one of the most time consuming and expensive activities of software development process. A diversity of testing tools has been developed to support this activity, including tools for Model-based Testing (MBT). MBT is a testing technique to automate the generation of testing artifacts from the system model. This technique presents several advantages, such as, lower cost and less effort to generate test cases. Therefore, in the last years a diversity of commercial, academic, and open source tools to support MBT has been developed to better explore these advantages. In spite of the diversity of tools to support MBT, most of them have been individually and independently developed from scratch based on a single architecture. Thus, they face difficulties of integration, evolution, maintenance, and reuse. In another perspective, Software Product Lines (SPL) offers possibility of systematically generating software products at lower costs, in shorter time, and with higher quality. The main contribution of this Ph. D thesis is to present a SPL for testing tools that support MBT (PLeTs) and an automated environment to support the generation of these tools (PlugSPL). Furthermore, our strategy was initially applied to generate some MBT testing tools which were applied in two examples of use performed in collaboration of an IT company. Based on the feedback from the examples of use we can infer that SPL can be considered a relevant approach to improve productivity and reuse during generation of MBT testing tools. Moreover, we also performed an experimental study carried out to evaluate the effort to use an MBT tool derived from our SPL to generate test scripts and scenarios. Thus, the results point out that the effort to generate test scripts, when compared with a Capture and Replay based tool, was reduced considerably.
O teste de software é uma atividade fundamental para garantir a qualidade de software. Além disso, teste de software é uma das atividades mais caras e demoradas no processo de desenvolvimento de software. Por esta razão, diversas ferramentas de teste foram desenvolvidas para apoiar esta atividade, incluindo ferramentas para Teste Baseado em Modelos (TBM). TBM é uma técnica de teste para automatizar a geração de artefatos de teste a partir de modelos do sistema. Esta técnica apresenta diversas vantagens, tais como, menor custo e esforço para gerar casos de teste. Por este motivo, nos últimos anos, diversas ferramentas para TBM foram desenvolvidas para melhor explorar essas vantagens. Embora existam diversas ferramentas TBM, a maioria delas tem o seu desenvolvimento baseado em um esforço individual, sem a adoção de técnicas de reuso sistemático e com base em uma única arquitetura, dificultando a integração, evolução, manutenção e reutilização dessas ferramentas. Uma alternativa para mitigar estes problemas é adotar os conceitos de Linhas de Produto de Software (LPS) para desenvolver ferramentas de TBM. LPS possibilitam gerar sistematicamente produtos a custos mais baixos, em menor tempo e com maior qualidade. A principal contribuição desta tese de doutorado é apresentar uma LPS de ferramentas de teste que suportam TBM (PLeTs) e um ambiente automatizado para apoiar a geração dessas ferramentas (PlugSPL). Além disso, esta tese apresenta uma abordagem para gerar ferramentas para TBM, que foram aplicadas em dois exemplos de uso. Com base nos resultados obtidos nos exemplos de uso, podemos inferir que LPS pode ser considerada uma abordagem relevante para melhorar a produtividade e o reuso durante a geração de ferramentas de TBM. Além disso, também foi realizado um estudo experimental com o objetivo de avaliar o esforço para se utilizar uma ferramenta derivada da PLeTs para geração de scripts de teste. Os resultados apontaram que o esforço para gerar scripts de teste foi reduzido consideravelmente, quando comparado com a uma ferramenta de Capture and Replay.
Quan, Nguyen. "Distributed Game Environment : A Software Product Line for Education and Research." Thesis, Linnéuniversitetet, Institutionen för datavetenskap (DV), 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-29077.
Повний текст джерелаGOMES, ROBERTA CLAUDINO BARRETO PESSANHA. "A SOFTWARE PRODUCT LINE BASED ON AGENTS FOR PROJECT MANAGEMENT SYSTEMS." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2009. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=15976@1.
Повний текст джерелаSoftware project management faces several challenges that must be overcome throughout the development to guarantee its success. Many tools and approaches have been proposed in the literature to help project managers with these issues. Thus, it is proposed to use two promising software engineering trends barely exploited in this context, which consists of the development of a software product line of project management systems based on agents. The use of software product lines allows the derivation of customized systems based on the project size. Among the benefits of using agents it is included the system dynamic reconfiguration from the exploitation of their characteristics, such as reasoning and adaptation.
Nivoit, Jean-Baptiste (Jean-Baptiste Henri). "Issues in strategic management of large-scale software product line development." Thesis, Massachusetts Institute of Technology, 2013. http://hdl.handle.net/1721.1/90607.
Повний текст джерелаThis electronic version was submitted by the student author. The certified thesis is available in the Institute Archives and Special Collections.
Cataloged from student-submitted PDF version of thesis.
Includes bibliographical references (pages 159-163).
This thesis reflects on the issues and challenges large software product engineering managers face. Software is hard to engineer on a small scale, but at a larger scale, engineering and management tasks are even more difficult. In the context of software product line evolution, the goal of this work is to look at current managing practice, through the lens of Systems Thinking as well as my own experience. We develop a System Dynamics model to operationalize the notions examined here and run a variety of experiments representative of real situations, from which we learn some lessons and recommend policies that engineering leaders may use to manage large-scale software development organizations. During the course of this research, we found that the model developed intuitively matched experiences in the software industry. Product line engineering and tighter deadlines force software producers to require more accurate control of the production capability of their development organization. In the context of many release cycles and multiple simultaneously active releases, we present some findings about scheduling of the workload, which the engineering manager may leverage to make decisions about the allocation of work. The research presented here from the point of view of the producers of software can help other stakeholders in the software ecosystem understand the challenges these organizations face and the reasoning behind choices made by these providers.
by Jean-Baptiste Nivoit.
S.M. in Engineering and Management
Kasikci, Baris Can Cengiz. "Variability Modeling In Software Product Lines." Master's thesis, METU, 2009. http://etd.lib.metu.edu.tr/upload/12610888/index.pdf.
Повний текст джерелаSalinas, Edward Mauricio Alferez. "Derivation and consistency checking of models in early software product line engineering." Doctoral thesis, Faculdade de Ciências e Tecnologia, 2012. http://hdl.handle.net/10362/9370.
Повний текст джерелаSoftware Product Line Engineering (SPLE) should offer the ability to express the derivation of product-specific assets, while checking for their consistency. The derivation of product-specific assets is possible using general-purpose programming languages in combination with techniques such as conditional compilation and code generation. On the other hand, consistency checking can be achieved through consistency rules in the form of architectural and design guidelines, programming conventions and well-formedness rules. Current approaches present four shortcomings: (1) focus on code derivation only, (2) ignore consistency problems between the variability model and other complementary specification models used in early SPLE, (3) force developers to learn new, difficult to master, languages to encode the derivation of assets, and (4) offer no tool support. This dissertation presents solutions that contribute to tackle these four shortcomings. These solutions are integrated in the approach Derivation and Consistency Checking of models in early SPLE (DCC4SPL) and its corresponding tool support. The two main components of our approach are the Variability Modelling Language for Requirements(VML4RE), a domain-specific language and derivation infrastructure, and the Variability Consistency Checker (VCC), a verification technique and tool. We validate DCC4SPL demonstrating that it is appropriate to find inconsistencies in early SPL model-based specifications and to specify the derivation of product-specific models.
European Project AMPLE, contract IST-33710; Fundação para a Ciência e Tecnologia - SFRH/BD/46194/2008.
Eyal, Salman Hamzeh. "Recovering traceability links between artifacts of software variants in the context of software product line engineering." Thesis, Montpellier 2, 2014. http://www.theses.fr/2014MON20008/document.
Повний текст джерелаSoftware Product Line Engineering (SPLE) is a software engineering discipline providing methods to promote systematic software reuse for developing short time-to-market and quality products in a cost-efficient way. SPLE leverages what Software Product Line (SPL) members have in common and manages what varies among them. The idea behind SPLE is to builds core assets consisting of all reusable software artifacts (such as requirements, architecture, components, etc.) that can be leveraged to develop SPL's products in a prescribed way. Creating these core assets is driven by features provided by SPL products.Unfortunately, building SPL core assets from scratch is a costly task and requires a long time which leads to increasing time-to-market and up-front investment. To reduce these costs, existing similar product variants developed by ad-hoc reuse should be re-engineered to build SPLs. In this context, our thesis proposes three contributions. Firstly, we proposed an approach to recover traceability links between features and their implementing source code in a collection of product variants. This helps to understand source code of product variants and facilitate new product derivation from SPL's core assets. The proposed approach is based on Information Retrieval (IR) for recovering such traceability links. In our experimental evaluation, we showed that our approach outperforms the conventional application of IR as well as the most recent and relevant work on the subject. Secondly, we proposed an approach, based on traceability links recovered in the first contribution, to study feature-level Change Impact Analysis (CIA) for changes made to source code of features of product variants. This approach helps to conduct change management from a SPL's manager point of view. This allows him to decide which change strategy should be executed, as there is often more than one change that can solve the same problem. In our experimental evaluation, we proved the effectiveness of our approach in terms of the most used metrics on the subject. Finally, based on traceability recovered in the first contribution, we proposed an approach to contribute for building Software Product Line Architecture (SPLA) and linking its elements with features. Our focus is to identify mandatory components and variation points of components. Therefore, we proposed a set of algorithms to identify this commonality and variability across a given collection of product variants. According to the experimental evaluation, the efficiency of these algorithms mainly depends on the available product configurations
Gómez, Llana Abel. "MODEL DRIVEN SOFTWARE PRODUCT LINE ENGINEERING: SYSTEM VARIABILITY VIEW AND PROCESS IMPLICATIONS." Doctoral thesis, Universitat Politècnica de València, 2012. http://hdl.handle.net/10251/15075.
Повний текст джерелаGómez Llana, A. (2012). MODEL DRIVEN SOFTWARE PRODUCT LINE ENGINEERING: SYSTEM VARIABILITY VIEW AND PROCESS IMPLICATIONS [Tesis doctoral no publicada]. Universitat Politècnica de València. https://doi.org/10.4995/Thesis/10251/15075
Palancia
Haupt, Michael, Stefan Marr, and Robert Hirschfeld. "CSOM/PL : a virtual machine product line." Universität Potsdam, 2011. http://opus.kobv.de/ubp/volltexte/2011/5233/.
Повний текст джерелаCSOM/PL ist eine Softwareproduktfamilie (software product line, SPL), die erstellt wurde, indem Techniken der mehrdimensionalen Belangtrennung (multi-dimensional separation of concerns, MDSOC) auf die Domäne der virtuellen Maschinen (VM) für höhere Programmiersprachen angewendet wurden. Dazu wurde CSOM, eine in C implementierte Smalltalk-VM, mittels VMADL (virtual machine architecture description language) in Module zerlegt. Etliche Eigenschaften von CSOM wurden in VMADL-Module gekapselt und auf unterschiedliche Weisen komponiert. Die Auswertung des Ansatzes zeigt, dass die Anwendung von MDSOC- und SPL-Prinzipien auf die komplexe VM-Domäne nicht nur machbar ist, sondern darüber hinaus auch Vorteile mit sich bringt, da die Verständlichkeit, Wartbarkeit und Konfigurierbarkeit von VM-Implementierungen ohne Beeinträchtigung der Ausführungsgeschwindigkeit verbessert werden.
Pham, Thi-Kim-Dung. "Development of Correct-by-Construction Software using Product Lines." Thesis, Paris, CNAM, 2017. http://www.theses.fr/2017CNAM1138/document.
Повний текст джерелаWe began the thesis by survey literature on SPLE and CbyC approaches in the State of the Art. Based on the overview and the insights obtained, we have analyzed the existing problems and suggested ways to solve them for our main goal. We have proposed in Chapter 2 a methodology to develop product lines such that the generated products are correct-by-construction. Our main intention is that a user does not need to know the product generation process but can receive a correct final product from selecting a configuration of features. Using the methodology, the final products are generated automatically and their correctness is guaranteed. Following this proposal, we have moved in Chapter 3 to define the FFML language that is used for writing modules. The reuse and modification mechanism, defined for the language and applied to all kinds of artifacts (specification, code and correctness proof), reduce the programming effort. In Chapter 4, we have focused on defining the composition mechanisms for composing FFML modules and embedded them into the FFML Product Generator tool. The evaluation of our methodology is performed through the development of two software product lines, the Bank Account SPL and the Poker SPL, the latter being a bit more complex than the former. In the evaluation, we have highlighted the advantages and the limitation of our methodology
Gylterud, Snorre. "Practices of Agile Software Product-Line Engineering : A qualitative assessment of empirical studies." Thesis, Norwegian University of Science and Technology, Department of Computer and Information Science, 2009. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-9996.
Повний текст джерелаThis thesis elaborated on the how Software Product-Line Engineering is combined with Agile Software Development to improve Software Engineering, through investigating published case studies and performing interviews in several companies. This combination are often described as Agile Software Product-Line Engineering and our study aimed to describe what agility is for software product lines and find out more on how this approach could be realized. Agile Software Product-Line Engineering could reap benefits from the best of the two software engineering approaches combining long term strategic efforts with short term agility. By following a specified research method that combines qualitative research methods we were able to ensure validity in our analysis and generalize the findings of this study. We used both semi-structured interviews and textual analysis techniques. The companies under study seem to combine Software Product-Line Engineering and Agile Software Development with success, reducing initial investment and exploiting reuse, and we found several practices that are interesting for further study. Based on these practices we present our view of a top-down approach to Agile Software Product-Line Engineering starting with several characteristics and a proposal for a definition of the field. Further, a framework for implementing the approach based on our research is presented, before we describe our thoughts on how the practice areas of Software Product-Line Engineering can be combined with Agile Software Development practices. We think that this thesis could be used as a guideline for further study and implementation of Agile Software Product-Lines. We believe that the data we cover is comprehensive based on the small existing research field and covers the general ideas of both the fields included in the combination.
Gurses, Ozgur. "Non-functional Variability Management By Complementary Quality Modeling In A Software Product Line." Master's thesis, METU, 2010. http://etd.lib.metu.edu.tr/upload/12612571/index.pdf.
Повний текст джерелаOster, Sebastian [Verfasser], Andy [Akademischer Betreuer] Schürr, and Ursula [Akademischer Betreuer] Goltz. "Feature Model-based Software Product Line Testing / Sebastian Oster. Betreuer: Andy Schürr ; Ursula Goltz." Darmstadt : Universitäts- und Landesbibliothek Darmstadt, 2012. http://d-nb.info/1106113845/34.
Повний текст джерелаNieke, Michael Verfasser], Ina [Akademischer Betreuer] [Schaefer, and Bernhard [Akademischer Betreuer] Rumpe. "Consistent Feature-Model Driven Software Product Line Evolution / Michael Nieke ; Ina Schaefer, Bernhard Rumpe." Braunschweig : Technische Universität Braunschweig, 2021. http://d-nb.info/1229615598/34.
Повний текст джерелаMcEntee, Simon. "The application of intelligent software for on-line product quality monitoring in manufacturing processes." Thesis, Glasgow Caledonian University, 1996. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.295005.
Повний текст джерелаOrhan, Umut. "A Knowledge Based Product Line For Semantic Modeling Of Web Service Families." Master's thesis, METU, 2009. http://etd.lib.metu.edu.tr/upload/12610305/index.pdf.
Повний текст джерелаconcerns and end-users'
viewpoints. The main idea behind enabling a knowledge-based approach is to pursue automation and intelligence on reflecting business requirements into service descriptions via model transformations and automated reasoning. The proposed reference variability model encloses the domain-specific knowledge and is formalized by using Web Ontology Language (OWL). Adding formal semantics to feature models allows us to perform automated analysis over them such as the verification of model customizations through exploiting rule-based automated reasoners. This research was motivated due to the needs for achieving productivity gains, maintainability and better alignment of business requirements with technical capabilities in engineering service-oriented applications and systems.
Björklund, Marcus, and Jonas Hjelmar. "Adopting Software Product Lines : Guidelines based on the Maturity of Organizations." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5196.
Повний текст джерелаALMEIDA, Rodrigo Bonifácio de. "Modeling software product line variability in use case scenarios: an approach based on crosscutting mechanisms." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/1805.
Повний текст джерелаAssociação para Promoção da Excelência do Software Brasileiro
A Gerência de Variações é um desafio para a adoção de Linhas de Produtos de Software, uma vez que os desenvolvedores precisam de meios para especificar e implementar variações que ocorrem em diferentes tipos de artefatos (como requisitos, projeto e arquitetura, código fonte e casos de testes). Esta tese apresenta uma nova abordagem para gerenciar variações em cenários de casos de uso. Tal abordagem, Modeling Scenario Variabilities as Crosscutting Mechanisms (MSVCM), objetiva melhorar a separação de preocupações entre a representação de variações e as especificações de cenários, possibilitando aos engenheiros do domínio e da aplicação compreender evoluir ambas as preocupações de forma independente. MSVCM alcança tal objetivo graças ao uso extensivo de mecanismos composicionais para a derivação de produtos, idéia motivada pelo fato de que artefatos como modelos de features, configuração de produtos e modelos de conhecimento da configuração se entrecortam em relação aos membros da linha de produtos. Após a avaliação da abordagem proposta, por meio de alguns estudos de casos, identificou-se que MSVCM reduz o espalhamento de features e melhora a coesão das especificações de cenários. Estes resultados sugerem que a evolução das especificações usando a técnica proposta nesta tese requer alterações mais localizadas, quando comparada com outras abordagens existentes. Por outro lado, os resultados de três experimentos controlados apresentaram evidências de que MSVCM apenas reduz o tempo necessário para evoluir as especificações de uma LPS quando os participantes possuem grande familiaridade com a técnica proposta e com o processo de evoluir especificações de linhas de produtos.
de, Albuquerque Ribeiro Rafael. "Modeling software product line variability in use case scenarios: an approach based on crosscutting mechanisms." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/1814.
Повний текст джерелаConselho Nacional de Desenvolvimento Científico e Tecnológico
A Gerência de Variações é um desafio para a adoção de Linhas de Produtos de Software, uma vez que os desenvolvedores precisam de meios para especificar e implementar variações que ocorrem em diferentes tipos de artefatos (como requisitos, projeto e arquitetura, código fonte e casos de testes). Esta tese apresenta uma nova abordagem para gerenciar variações em cenários de casos de uso. Tal abordagem, Modeling Scenario Variabilities as Crosscutting Mechanisms (MSVCM), objetiva melhorar a separação de preocupações entre a representação de variações e as especificações de cenários, possibilitando aos engenheiros do domínio e da aplicação compreender evoluir ambas as preocupações de forma independente. MSVCM alcança tal objetivo graças ao uso extensivo de mecanismos composicionais para a derivação de produtos, idéia motivada pelo fato de que artefatos como modelos de features, configuração de produtos e modelos de conhecimento da configuração se entrecortam em relação aos membros da linha de produtos. Após a avaliação da abordagem proposta, por meio de alguns estudos de casos, identificou-se que MSVCM reduz o espalhamento de features e melhora a coesão das especificações de cenários. Estes resultados sugerem que a evolução das especificações usando a técnica proposta nesta tese requer alterações mais localizadas, quando comparada com outras abordagens existentes. Por outro lado, os resultados de três experimentos controlados apresentaram evidências de que MSVCM apenas reduz o tempo necessário para evoluir as especificações de uma LPS quando os participantes possuem grande familiaridade com a técnica proposta e com o processo de evoluir especificações de linhas de produtos
Mazo, Raul. "A Generic Approach for Automated Verification of Product Line Models." Phd thesis, Université Panthéon-Sorbonne - Paris I, 2011. http://tel.archives-ouvertes.fr/tel-00707351.
Повний текст джерелаFABRI, BRUNO FERREIRA. "FEAF: AN INFRASTRUCTURE FOR ANALYZING THE EVOLUTION OF THE FEATURES IN A SOFTWARE PRODUCT LINE." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2013. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=24837@1.
Повний текст джерелаLinhas de Produtos de Software (LPS) consistem em um paradigma de desenvolvimento de software, no qual famílias de sistemas compartilham características comuns e tornam explicitas outras características que variam de acordo com o sistema final considerado. Esta abordagem oferece benefícios ao desenvolvimento de software tais como a redução de custos e a qualidade do produto final. Como em qualquer abordagem de desenvolvimento de software, as atividades de evolução do software devem ser vistas como algo inevitável, constante e rotineiro. Dentro do cenário do desenvolvimento de LPSs, as atividades de evolução são impulsionadas pelas alterações das suas características no decorrer das versões. Visto isso, o desenvolvimento de LPSs impõem novos desafios para as atividades de análise e compreensão da evolução de suas características, considerando-se as diversas versões de uma LPS. Trabalhos de pesquisa recentes propõem estratégias visuais com suporte automatizado por ferramentas de visualização. Tais abordagens apresentam limitações visto que algumas não fornecem suporte à comparação das características em diversas versões de uma LPS e outras não dão suporte ao conceito de características presente na LPS. Esta dissertação propõe o FEAF, uma infraestrutura para auxiliar a construção de ferramentas para analisar e compreender a evolução das características nas diferentes versões de uma LPS. Com base na infraestrutura proposta, foi desenvolvida uma ferramenta visual, que auxilia nas atividades de análise e compreensão da evolução das características de uma LPS, denominada FEACP. Ela fornece uma estratégia de visualização que utiliza duas visualizações leves baseadas em representação de grafo. A ferramenta foi avaliada através de um experimento controlado que compara a sua estratégia de visualização com a estratégia de visualização da ferramenta Source Miner Evolution.
Software Products Lines (SPL) is a software engineering approach to developing software system families that share common features and differ in other features according to the requested software systems. The adoption of the SPL approach can promote several benefits such as cost reduction, product quality, productivity and time to market. As with any approach to software development, the activities of software evolution should be seen as something inevitable, constant and routine. Within the scenario of development of SPLs, evolution activities are driven by changes in its features over the releases. As such, the development of SPLs imposes new challenges to the activities of analyzing and comprehension the evolution of their features, considering the various releases of an SPL. Recent research works propose visual strategies with automated support by visualization tools. Such approaches have limitations since some do not provides support for a comparison of features in different releases of an SPL and others do not support the concept of features present in the SPL. This paper proposes the FEAF, an infrastructure to support the construction of tools for analyzing and comprehending the evolution of features in different releases of an SPL. Based on the proposed infrastructure, we developed a visual tool, which assists with the analysis and understanding of the evolution of the features of an SPL, called FEACP. It provides a visualization strategy that uses two light views based on graph representation. The tool was evaluated through a controlled experiment that compares our visualization strategy with the visualization strategy of Source Miner Evolution.
Di, Cola Simone. "A component-based approach to modelling software product families with explicit variation points." Thesis, University of Manchester, 2017. https://www.research.manchester.ac.uk/portal/en/theses/a-componentbased-approach-to-modelling-software-product-families-with-explicit-variation-points(b649eda2-8cac-46a5-888e-ee0926080ecb).html.
Повний текст джерелаMurwantara, I. Made. "The application of software product line engineering to energy management in the cloud and in virtualised environments." Thesis, University of Birmingham, 2016. http://etheses.bham.ac.uk//id/eprint/7043/.
Повний текст джерелаParlakol, Nazif Bulent. "A Test Oriented Service And Object Model For Software Product Lines." Master's thesis, METU, 2010. http://etd.lib.metu.edu.tr/upload/12611769/index.pdf.
Повний текст джерелаProduct Flow Model&rdquo
is used for the common representation of products in application engineering and the &ldquo
Domain Service and Object Model&rdquo
represents the variant based relations between products and core assets. This new approach provides a solution for avoiding unnecessary work load of regression testing using the principles of sub-service decomposition and variant based product/sub-service traceability matrices. The proposed model is adapted to a sample product line targeting the banking domain, called Loyalty and Campaign Management System, where loyalty campaigns for credit cards are the products derived from core assets. Reduced regression test scope after the realization of new requirements is demonstrated through a case study. Finally, efficiency improvement in terms of time and effort in the test process with the adaptation of the proposed model is discussed.
Salikiryaki, Aleksandra, and Iliana Petrova. "Graphical Approach for Variability Management in Safety-Critical Product Lines." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-28580.
Повний текст джерелаNascimento, Leandro Marques do. "Cores assets development in software product lines - towards a practical approach for the mobile game domain." Universidade Federal de Pernambuco, 2008. https://repositorio.ufpe.br/handle/123456789/1683.
Повний текст джерелаOs mais almejados objetivos da engenharia de software são basicamente alta produtividade, com alta qualidade a um baixo custo e uma possível forma de atingi-los é estabelecer reuso de software o processo de criar sistemas de software a partir de sistemas existentes ao invés de criar do início. Neste contexto, uma abordagem que pode habilitar reuso na prática é Linha de Produto de Software (LPS) um conjunto de sistemas de software que compartilham um conjunto comum e gerenciado de funcionalidades que satisfazem uma necessidade específica de um domínio, e que são desenvolvidas a partir de um conjunto de artefatos reusáveis. Um domínio em particular onde a adoção de tal abordagem pode trazer benefícios é o domínio de jogos móveis principalmente porque os jogos precisam executar em diversos dispositivos e existe uma grande quantidade de jogos do mesmo tipo sendo desenvolvidos com funcionalidades em comum. Entretanto, as características do domínio de jogos móveis geralmente criam barreiras para os processos de LPS na prática, tais como, restrições de memória e de tamanho da aplicação e diferentes implementações de API feitas por diferentes fabricantes. Além disso, os atuais processos de LPS ainda carecem de detalhes em fases relacionadas à implementação de artefatos reusáveis, dificultando a administração apropriada das características mencionadas. Dessa forma, este trabalho objetiva definir uma abordagem prática para implementação de artefatos reusáveis em uma LPS para o domínio de jogos móveis com base nas boas práticas do estado da arte na área. Além disso, com a intenção de avaliar a abordagem, um estudo experimental foi executado com três jogos de plataforma para construir a LPS e um quarto jogo foi derivado dela
Baum, David. "Variabilitätsextraktion aus makrobasierten Software-Generatoren." Master's thesis, Universitätsbibliothek Leipzig, 2014. http://nbn-resolving.de/urn:nbn:de:bsz:15-qucosa-132719.
Повний текст джерела