Submitted by Silvana Teresinha Dornelles Studzinski (sstudzinski) on 2015-07-06T18:46:19Z No. of bitstreams: 1 MicheleLermen.pdf: 2970416 bytes, checksum: c3592df5d147df203246e12679dd30ea (MD5) / Made available in DSpace on 2015-07-06T18:46:19Z (GMT). No. of bitstreams: 1 MicheleLermen.pdf: 2970416 bytes, checksum: c3592df5d147df203246e12679dd30ea (MD5) Previous issue date: 2012 / Nenhuma / Esta dissertação tem por objetivo desenvolver uma ontologia que represente uma linha de produto para o gerenciamento de projetos de software com metodologias ágeis. O modelo de domínio da linha de produto é composto por conceitos formadores das metodologias ágeis eXtreme Programming (XP), Scrum, e a Feature Driven Development (FDD), bem como trata dos conceitos de gerenciamento de projetos baseados no PMBOK. Através da ontologia Molps se propõe representar este domínio, possibilitando que agentes de software realizem consultas na ontologia, inferindo as possíveis variabilidades a serem geradas no produto. A ontologia também permitirá o gerenciamento de processo de desenvolvimento de software. Para evidenciar tal flexibilidade e o gerenciamento do processo de desenvolvimento de software realizam-se testes na ontologia desenvolvida, onde os resultados são comentados e analisados. / This study aims to develop an ontology to represents a software product line to be used for project management based on agile methodologies. The product line domain model was built utilizing concepts coming from eXtreme Programming (XP), Scrum, and feature driven development (FDD), and also concepts brought from project management through PMBOK. Through the ontology Molps proposes to represent this domain, enabling software agents to perform queries on the ontology, inferring the possible variability in the product to be generated. The ontology will also allow the management process of software development. To demonstrate this flexibility and process management software development take place in the ontology developed tests, where results are discussed and analyzed.

Dagens textilbransch karaktäriseras till stor del av snabbt föränderliga trender. Det råder en hård konkurrens på marknaden och kunden besitter i stor utsträckning en god kunskap och en medvetenhet, vilket ställer högre krav på det utbud som företaget erbjuder. Vidare har hemtextilbranschen under de senaste åren präglats av en ökad konkurrensnivå. Flera aktörer så som exempelvis stormarknader, färghandlare och byggvaruhus har utökat sitt sortiment med hemtextil och är därmed med och tävlar om hemtextilkunderna. I denna situation är det viktigt att ha ett välplanerat sortiment eftersom det bland annat speglar företagets affärsidé samt kommunicerar vad affärsidén erbjuder och till vem. Vidare kan en medvetenhet kring sortimentsstrategier användas för att kommunicera rätt image till kunden och dessutom vara ett viktigt konkurrensmedel.Syftet med uppsatsen är att beskriva hur ett hemtextilföretag bör arbeta med sin sortimentsplanering för att på en strategisk nivå använda sortimentet som ett konkurrensmedel. Vidare ämnar uppsatsen även undersöka hur ett sortiment kan påverka ett hemtextilföretags image.Uppsatsen bygger på en kvalitativ studie av hemtextilföretaget Hemtex med inriktning mot företagets babysortiment. Genom semistrukturerade intervjuer med en Business area manager på Hemtex, samt potentiella kunder för sortimentet har uppsatsen kartlagt vilka avsikter Hemtex har med babysortimentet samt hur det betraktas ur ett kundperspektiv.Resultatet av studien visar att sortimentets utformning har ett starkt inflytande över hur ett hemtextilföretag betraktas av kunden. Med stöd av den teoretiska referensramen visar studien att de intervjuade kunderna bygger en stor del av sin uppfattning om Hemtex på hur sortimentet är utformat samt hur det presenteras i butik. Slutligen försöker uppsatsen finna konkreta tanke- och tillvägagångssätt som ett hemtextilföretag kan tänkas tillämpa i sin sortimentsstrategi. Bland annat presenteras modeller gällande förhållningssätt för sortimentets utformning, vilka analyseras utefter fallföretagets förutsättningar. Studien visar att Hemtex nuvarande sortimentsstrategi gynnat babysortimentet. Företagets strategi att hålla sortimentet renodlat, med färre produktvarianter, visar sig vara god då de genom detta kan minimera produktionskostnaderna och hålla ett lägre pris. Slutsatsen blir att Hemtex i sin sortimentsstrategi bör eftersträva att bevara och förstärka sin image som ett företag som tillhandahåller prisvärda produkter.The current textile industry is highly characterized by rapidly shifting trends. The market involves a high level of competition as well as consumers who possess a lot of knowledge about the products. These elements increase the demands on what a company is required to offer. Today’s home textile market has also increased its level of competition since many more companies, such as supermarkets, paint dealers and builders’ merchants are expanding their assortments to include textile products. In these circumstances a well-planned assortment is very important since it reflects the company’s business concept. The assortment communicates what is involved in the business concept and the target audience. A company may then use an awareness of different assortment strategies to communicate the right image to the appropriate audience. This may also be used as an important competitive weapon.The purpose of this essay is to describe how a home textile company can use assortment strategies in order to use their product-mix as a competitive device. This paper also intends to investigate how a company´s image will be affected by the assortment. This essay is based upon a qualitative study of the home textiles company Hemtex, with a focus towards the company´s Baby assortment. This study was carried out through semi-structured interviews with a Business Area Manager at Hemtex and a number of potential customers within the category of baby products. With the information gained from the interviews, the essay has mapped out how the Baby assortment is regarded from a customer´s perspective. The result of the study identifies that assortment strategies have a strong affect on a consumer´s perception of a home textile company. With support from the theoretical framework the study shows how the interviewed consumers build a significant part of their opinion about Hemtex upon the design and presentation of the assortment. In the final chapter of the essay, it attempts to find concrete strategies for planning and implementing favorable assortment strategies. Theoretical models relating to assortment design are evaluated according to the conditions of Hemtex. The study shows that the company´s baby assortment has performed better since implementing the present strategy. Keeping the baby assortment refined, with a smaller range of varieties, has proven to be a well-suited strategy. This is particularly important since the customers place a strong emphasis on good value for money. The conclusion is that Hemtex should strive to maintain and further strengthen their image as a company that provides a product worth its price. / Program: Textilekonomutbildningen

L'engouement du grand public pour les applications mobiles, dont le nombre ne cessede croître, a rendu les utilisateurs de plus en plus exigeants quant à la qualité de cesapplications. Seule une procédure de test efficace permet de répondre à ces exigences.Dans le contexte des applications embarquées sur téléphones mobiles, le test est unetâche coûteuse et répétitive principalement à cause du nombre important de terminauxmobiles qui sont tous différents les uns des autres.Nous proposons dans cette thèse le langage MATeL, un DSML (Domain-Specific ModelingLanguage) qui permet de d’écrire des scénarios de test spécifiques aux applicationsmobiles. Sa syntaxe abstraite, i.e. un méta modèle et des contraintes OCL, permet auconcepteur de manipuler les concepts métier du test d'applications mobiles (testeur, mobileou encore résultats attendus et résultats obtenus). Par ailleurs, il permet d'enrichirces scénarii avec des points de variabilité qui autorisent de spécifier des variations dansle test en fonction des particularités d'un mobile ou d'un ensemble de mobiles. La syntaxeconcrète de MATeL, qui est inspirée de celle des diagrammes de séquence UML,ainsi que son environnement basé sur Eclipse permettent à l'utilisateur de concevoir desscénarii relativement facilement.Grâce à une plateforme de test en ligne construite pour les besoins de notre projet,il est possible d'exécuter les scénarii sur plusieurs téléphones différents. La démarcheest illustrée dans cette thèse à travers des cas d'utilisation et des expérimentations quiont permis de vérifier et valider notre proposition. / Mobile applications have increased substantially in volume with the emergence ofsmartphones. Ensuring high quality and successful user experience is crucial to the successof such applications. Only an efficient test procedure allows developers to meet these requirements. In the context of embedded mobile applications, the test is costly and repetitive. This is mainly due to the large number of different mobile devices. In this thesis, we describe MATeL, a Domain-Specific Modeling Language (DSML) for designing test scenarios for mobile applications. Its abstract syntax, i.e. a meta model and OCL constraints, enables the test designer to manipulate mobile applications testing concepts such as tester, mobile or outcomes and results. It also enables him/her to enrich these scenarios with variability points in the spirit of Software Product-Line engineering, that can specify variations in the test according to the characteristics of one mobile or a set of mobiles. The concrete syntax of MATeL that is inspired from UML sequence diagrams and its environment based on Eclipse allow the user to easily develop scenarios. MATeL is built upon an industrial platform (a test bed) in order to be able to run scenarios on several different phones. The approach is illustrated in this thesis through use cases and experiments that led to verify and validate our contribution.

<p>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.</p><p>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.</p>

In software engineering, software reuse has been a popular topic since 1968. Nowadays, Software Product Line (SPL) engineering promotes systematic reuse throughout the whole software development process. Within SPL, reusability strongly depends on variability. In this context, variability modelling and management are crucial activities that crosscuts all development stages. Different techniques are used to model variability and one of them is Feature Diagrams (FDs). FD languages are a family of popular modelling languages used to model, and reason on, variability. Since the seminal proposal of a FD language, namely FODA, many extensions have been proposed to improve it. However, the pros and cons of these languages are difficult to evaluate for two main reasons: (1) most of them are informally defined and (2) no well defined criteria were used to justify the extensions made to FODA. As a consequence, variability modelling and management techniques proposed in the literature or used by practitioners may be suboptimal. Globally, this work underlines that the current research on FDs is fragmented and provides principles to remedy this situation. A formal approach is proposed to introduce more rigour in the motivation, definition and comparison of FD languages. Thereby, examining their qualities should be more focused and productive. A formal approach guarantees unambiguity and is a prerequisite to define formal quality criteria and to produce efficient and safe tool automation. A quality analysis is necessary to avoid the proliferation of languages and constructs that are an additional source of misinterpretations and interoperability problems. The creation or selection of a FD language should be driven and motivated by rigourous criteria. Translations from one FD language to another should be defined and carefully studied to avoid interoperability problems. The main contributions of this work are: (1) to use a quality framework to serve as a roadmap to improve the quality of FD languages, (2) to formally evaluate and compare FD language qualities according to well-defined criteria and following a clear method, (3) to formally define and motivate a new FD language that obtains the best scoring according to the quality criteria and (4) to develop tool support for this language.

A 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.

The major problem addressed in this thesis is the definition of a new SPLE methodology that covers both phases of the SPLE process and focuses on the derivation of behavioral models of SPL products. In Chapter 2 three research areas scope context of this thesis: Software Product Lines, Business Processes, and Model-Driven Engineering. Throughout Chapter 3, we propose a new SPLE methodology that focuses on the derivation of product behavior. We first describe the main flow of the methodology, and then detail the individual steps. In chapter 4 we propose a new domain specific language called CBPF created for modeling composable business process fragments. A model driven approach is followed for creating CBPF: definition of the abstract syntax, graphical concrete syntax and translational semantics. In Chapter 5 we propose several types of verifications that can be applied to business processfragments to determine their "correctness". For structural verification we definine a set of fragment consistency rules that should be valid for every business process fragment created with CBPF. To check behavioral correctness we first transform the business process fragment into an equivalent HCPN. We can then check generic properties but also define aset of fragment specific properties. In chapter 6 we exemplify the proposed SPL methodology by applying it to a case study from the crisis management system domain. We also propose a tool suite that supports our methodology. Chapter 7 describes possible improvements and extensions to the contributions of this thesis. We conclude the thesis in Chapter 8 and draw some conclusions.

Mobile applications are developed to run on fast-evolving platforms, such as Android or iOS. Respective mobile devices are heterogeneous concerning hardware (e.g., sensors, displays, communication interfaces) and software, especially operating system functions. Software vendors cope with platform evolution and various hardware configurations by abstracting from these variable assets. However, they cannot be sure about their assumptions on the inner conformance of all device parts and that the application runs reliably on each of them—in consequence, comprehensive testing is required. Thereby, in testing, variability becomes tedious due to the large number of test cases required to validate behavior on all possible device configurations. In this paper, we provide remedy to this problem by combining model-based testing with variability concepts from Software Product Line engineering. For this purpose, we use feature-based test modeling to generate test cases from variable operational models for individual application configurations and versions. Furthermore, we illustrate our concepts using the commercial mobile application “runtastic” as example application.

Diss. med. dent. Zürich. / Literaturverz.

Made available in DSpace on 2014-12-17T15:47:57Z (GMT). No. of bitstreams: 1 AnaLSO_DISSERT.pdf: 3044702 bytes, checksum: 7d5dc3b7e2aab3803ef82bbde3db6f6a (MD5) Previous issue date: 2011-05-31 / Software Product Line (SPL) consists of a software development paradigm, whose main focus is to identify features common and variability among applications in a specific domain. An LPS is designed to attend all products requirements from its product family. These requirements and LPS may have changes over time due to several factors, such as evolution of product requirements, evolution of the market, evolution of SLP process, evolution of the technologies used to develop the products. To handle these changes, LPS should be modified and evolve in order to not become obsolete, and adapt itself to new requirements. The Changes Impact Analysis is an activity that understand and identify what consequences these changes are cause on LPS. Impact Analysis on LPS may be supported by traceability relationships, which identify relationships between artefacts created during all phases of software development. Despite the solutions of change impact analysis based on traceability for software, there is a lack of solutions for assessing the change impact analysis based on traceability for LPS, since existing solutions do not include estimates specific to the artefacts of LPS. Thus, this paper proposes a process of change impact analysis and an tool for assessing the change impact through traceability of artefacts in LPS. For this purpose, we specified a process of change impact analysis that considers artifacts produced during the development of LPS. We have also implemented a tool which allows estimating and identifying artefacts and products of LPS affected from changes in other products, changes in class, changes in features, changes between releases of LPS and artefacts related to changes in core assets and variability. Finally, the results were evaluated through metrics / Linhas de Produto de Software (LPS) consistem em um paradigma de desenvolvimento de software, cujo foco principal encontra-se na identifica??o das caracter?sticas (features) comuns e vari?veis entre as aplica??es de um segmento de dom?nio espec?fico. Uma LPS ? projetada para atender todos os requisitos dos produtos de sua fam?lia de produtos. Esses requisitos e a pr?pria LPS podem sofrer mudan?as ao longo do tempo em decorr?ncia de v?rios fatores, como por exemplo, evolu??o nos requisitos dos produtos, evolu??o no dom?nio de mercado para o qual os produtos foram projetados, evolu??o no processo de constru??o da LPS, evolu??o das tecnologias usadas para desenvolver os produtos. Para lidar com essas mudan?as, a LPS deve ser modificada e evoluir, visando n?o ficar obsoleta, e se adequar aos novos requisitos que surgem. A an?lise de impacto de mudan?as consiste em uma atividade que visa compreender e identificar quais conseq??ncias essas mudan?as causam ou causar?o na LPS. A an?lise de impacto na LPS pode ser apoiada por meio de rela??es de rastreabilidade, as quais identificam relacionamentos entre artefatos criados durante todas as fases do desenvolvimento de software. Apesar de existirem solu??es de an?lise de impacto baseadas em rastreabilidade para softwares e de rastreabilidade para LPS, h? uma car?ncia de solu??es de an?lise de impacto de mudan?as baseadas em rastreabilidade para LPS, pois as solu??es existentes n?o contemplam estimativas espec?ficas para o dom?nio da LPS. Assim, este trabalho prop?e um processo de an?lise de impacto e uma ferramenta associada para an?lise de impacto de mudan?as baseada em rastreabilidade de artefatos em uma LPS. Para tal, foi especificado um processo de an?lise de impacto de mudan?as que considera artefatos produzidos durante o desenvolvimento da LPS. Foi tamb?m implementada uma ferramenta a qual permite identificar artefatos e produtos da LPS afetados a partir de mudan?as em outros produtos, mudan?as em classes, mudan?as em features, mudan?as entre vers?es (releases) da LPS e mudan?as nos artefatos relacionados ? arquitetura base e ?s variabilidades. Por ?ltimo, os resultados obtidos foram avaliados atrav?s de m?tricas