Orientador: Cecilia Mary Fischer Rubira / Dissertação (mestrado profissional) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-07T00:50:23Z (GMT). No. of bitstreams: 1 Pinho_HelderdeSousa_M.pdf: 1255692 bytes, checksum: 91ab06629ddbbf4b6885b93010e3511f (MD5) Previous issue date: 2006 / Resumo: O desenvolvimento baseado em componente (DBC) pennite que uma aplicação seja construída pela composição de componentes de software que já foram previamente especificados, construídos e testados, resultando em ganhos de produtividade e qualidade no software produzido. Para haver reuso de componentes, é necessário que usuários consIgam procurar e recuperar componentes previamente especificados ou implementados Um repositório de componentes é essencial para possibilitar tal reuso. Interoperabilidade é um requisito importante para repositórios, mas nem todas as ferramentas a tratam com a devida relevância. O modelo de metadados de um repositório para DBC deve contemplar características de componentes, tais como interface e separação entre especificação e implementação. Este trabalho apresentou o Rigel, um repositório de bens de software reutilizáveis com suporte para desenvolvimento baseado em componentes. O Rigel apresenta características que facilitam atividades executadas durante o desenvolvimento de sistemas baseados em componentes, tais como pesquisa, armazenamento e recuperação de bens e integração com CVS. O padrão RAS foi adotado como o fonnato de metadados e de empacotamento de bens, facilitando a integração do Rigel com outros sistemas. O modelo de metadados do RAS foi estendido para apoiar um modelo conceitual de componentes e arquitetura de software. Esta adaptação resultou na criação de quatro novos profiles RAS, para apoiar bens relacionados à DBC: componente abstrato, componente concreto, interface e configuração arquitetural. Um estudo de caso foi conduzido a fim de mostrar como o Rigel apóia um processo de desenvolvimento baseado em componentes. Conclui-se que as características do repositório Rigel facilitam um desenvolvimento baseado em componentes / Abstract: The component based development (CBD) permits an application to be built by composition of previously specified, build and tested components, resulting in increases in productivity and quality of the produced software. 1n order to make the reuse of components happen, it is necessary that users are able to search and retrieve previously specified or implemented components. A component repository is important to support this reuse. 1nteroperability is an important requirement for repositories, but not alI the tools consider it with the required relevance. The metadata model of a CBD repository must handle components features, such as interface and separation between specification and implementation. This work presents Rigel, a repository of reusable software assets with a support for component based development. Rigel presents features that make activities performed during the development of component based systems easier, such as search, storage and retrieval of assets and CVS integration. RAS standard was adopted as the asset metadata and packaging format, making Rigel integration with other systems easier. The RAS metadata model was extended to support a conceptual model of components and software architecture. This adaptation resulted in the creation of four new RAS profiles to support CBD related assets: abstract component, concrete component, interface and architectural configuration. A case study was conducted in order to show how Rigel supports a CBD processo We also conclude that Rigel repository features make the component based development easier / Mestrado / Engenharia de Computação / Mestre em Computação

Orientador: Hans Kurt Edmund Liesenberg / Dissertação (mestrado) - Universidade Estadual de Campinas, Instituto de Computação / Made available in DSpace on 2018-08-11T00:52:22Z (GMT). No. of bitstreams: 1 Kollross_Diogo_M.pdf: 31909718 bytes, checksum: 107b2440c38f63fc3880fa52f54ea0d7 (MD5) Previous issue date: 2007 / Resumos: Sistemas reativos têm grande importância em muitas áreas da engenharia e da computação, mas a qualidade e maturidade das metodologias e ferramentas de apoio ao desenvolvimento deixam a desejar em relação às voltadas a sistemas transformacionais. Uma das metodologias de destaque é a Arquitetura Orientada a Modelos, onde os sistemas reativos são descritos por modelos que podem ser diretamente traduzidos em formas executáveis. A linguagem mais bem sucedida na modelagem de sistemas reativos é Statechart, que deu origem a variações como os diagramas de máquinas de estado do padrão UML e à linguagem Xchart. Essa linguagem é uma extensão de Statechart que introduz construções para controle de processos externos, história de ativações e hierarquização de eventos. Para superar as limitações da ferramenta já existente para edição de diagramas Xchart conhecida como Smart, foi desenvolvido o editor Sins (Sins 1s Not Smart), implementado como plugin para o ambiente integrado de desenvolvimento Eclipse. Com o editor Sins é possível editar os diagramas através de manipulação direta, diagramar a especificação automaticamente e gerar o código fonte correspondente na linguagem textual TEXchart. O algoritmo de layout implementado é uma variação do algoritmo de Sugiyama, modificado para melhorar a legibilidade do dia:grama ao garantir a consistência na apresentação de suas estruturas e gerar mapas semelhantes aos desenhados livremente / Abstract: Reactive systems have great importance in many areas of Engineering and Computing, but the quality and maturity of the development support methodologies and tools Iack when compared to those directed to transformational systems. One of the outstanding methodologies is Model Oriented Architecture, where the reactive systems are described by models that can be directly translated to executable form. The best succeeded language for modeling of reactive systems is Statechart, which is the origin of variations like state machine diagrams from the UML standard and the Xchart Language. This language is an extension of Statechart that introduces eIements for external process control, activation history and hierarchization of events. To overcome the limitations of the already existing tool for the edition of Xchart diagramas known as Smart, the Sins editor was developed (Sins Is Not Smart), implemented as a plugin for the Eclipse IDE. With the Sins editor it is possible to edit diagramas through direct manipulation, layout the specification automatically and generate the corresponding source code in the textual Language TEXchart. The implemented layout algorithm is a variation of the Sugiyama algorithm, modified for better legibility of the diagram by assuring consistency in the presentation of its structures and generation of layouts similar to those freely drawn / Mestrado / Sistemas de Computação / Mestre em Ciência da Computação

Nas últimas quatro décadas, métodos e algoritmos para análise e formação de arranjos físicos de máquinas, equipamentos, departamentos e serviços auxiliares vêm sendo desenvolvidos para reduzir o fluxo de materiais e o deslocamento de pessoal entre eles, objetivando diminuir custos e aumentar a eficiência do sistema produtivo. Diversos autores têm proposto algoritmos e ferramentas computacionais para aumentar a produtividade do projetista de arranjo físico, mas todos focam em um determinado conjunto de algoritmos, método, ou tipo de arranjo físico. Neste contexto, este trabalho de pesquisa buscou desenvolver um software que atue em um escopo mais amplo que o dessas ferramentas computacionais. A partir de uma estrutura baseada em um framework de aplicação orientado a objeto, o software proposto é capaz de suportar a introdução de novos métodos, algoritmos e ferramentas gráficas para análise e formação dos diversos tipos de arranjos físicos existentes, à medida que estes forem necessários, sem sofrer modificações ou gerar alterações significativas em seu código fonte. Isso permite ao desenvolvedor adaptar facilmente o software proposto às necessidades de um projeto de arranjo físico / In the last four decades, methods and algorithms have been developed to analyse and arrange the layout of machines, equipments, departments, and auxiliary services in order to minimize the movement of people and material flow. It is normally made to reduce costs and improve the production system efficiency. Several authors have proposed computational algorithms and tools to increase productivity of the layout designer, but all of them focus on a limited set of algorithms or methods, or on a particular layout type. In this research work, a computer program with a broader scope than current computational tools has been developed. By adopting a structure based on an object-oriented application framework, the proposed software supports the addition of new methods, algorithms, and graphical tools, which can be applied, as required, on several different layout design types without significant structural or source code changes. It enables the developer to adapt the proposed software for new layout design requirements easily

Os constantes avanços técnico-científicos, nas diversas áreas da engenharia, ocasionaram grandes mudanças nos inúmeros métodos de abordagem do cotidiano e também, realizaram papel fundamental, na aproximação de novos usuários, com ou sem conhecimentos específicos, à utilização das novas técnicas. Na Cartografia, por exemplo, esses avanços e a aproximação de novos usuários, com diferentes necessidades de uso, possibilitaram o desenvolvimento de modernos modos de abordagem para problemas do dia a dia. A criação da estruturação de dados digitais geográficos permitiu o desenvolvimento de novas ferramentas computacionais que, como os Sistemas de Informação Geográficas, agilizaram as etapas referentes aos processos de pesquisas relacionados a utilização de dados geográficos. Contudo, para uma correta utilização das novas ferramentas, os conjuntos de dados geográficos, devem apresentar-se de modo estruturado, seguindo normas e técnicas bem elaboradas sobre esse assunto. Um esforço que, por muitas vezes, não ocorre por parte dos usuários finais que acabada por comprometer toda a eficiência do sistema eletrônico. Este trabalho aborda assim, os benefícios envolvidos na utilização de padrões e técnicas de desenvolvimento de softwares bem definidas e eficientes; as instituições internacionais responsáveis por estabelecerem as regras base e os esforços necessários para o desenvolvimento com qualidade de uma aplicação que utilize banco de dados espaciais. / The constant technical and scientific advances, in various areas of engineering, have led to changes in the many methods of everyday approach and played a fundamental role in attracting new users, with or without specific knowledge, to the use of these new techniques. In cartography, in special, these advances and the approximation of new users, with different skill levels, enabled the development of modern methods for resolution of problems. The creation of data structure for geographic applications allowed the development of new computational tools that, as the Geographic Information Systems, helped the development related to the research processes with geographic data. However, for a correct use of these new tools, spatial databases must be developed in a structured way, following well-developed standards and techniques. An effort that, for many times, does not occur on the part of the end users that end up compromising all the efficiency of the computational system. This work present: The benefits involved in the use of standards and techniques for developing efficient software; showing the international institutions responsible for establishing the base rules and the necessary efforts for the development with quality of an application that uses spatial databases.

Abstract A stakeholder analysis is commonly a part of the requirements engineering process in the development of software systems. It contributes to identifying, analysing, negotiating and validating requirements from multiple stakeholder viewpoints that do not necessary share the same views on a system under development and do not necessary express themselves using a similar language. Stakeholder analysis is often integrated into a used development method or practice and doesn’t necessarily appear as a separate process. The increase in software size, availability and use in different appliances, however, requires more from the stakeholder analysis than has been recognized in Software Engineering literature. The increasing scale of software systems and connections to other systems increase the number of involved stakeholders complicating the stakeholder analysis. In addition, how the actual stakeholder analysis should be implemented in large scale software development and how it supports the development effort is problematic in practice. The purpose of this thesis is to study the role and purpose of a stakeholder analysis in a large-scale software-intensive systems development. In this thesis, an empirical approach is taken to study the large-scale software-intensive systems development as phenomena in order to observe it as a whole. This approach allows this thesis to analyse the phenomena from different perspectives in order to identify and describe the nature and purpose of a stakeholder analysis in large-scale software-intensive systems development. The contribution of this thesis is the following. First, the thesis contributes to both the practical and scientific community by describing the role of stakeholder analysis in the software-intensive systems development process. Secondly, it demonstrates how a stakeholder analysis can be implemented in a large-scale software-intensive systems development process. / Tiivistelmä Sidosryhmäanalyysi on yleensä osa vaatimusmäärittelyprosessia ohjelmistojärjestelmien kehityksessä. Se edesauttaa vaatimusten tunnistamista, analysointia, sopimista ja vahvistamista useiden eri sidosryhmien näkökulmasta tilanteissa, missä eri sidosryhmät eivät välttämättä jaa samaa näkökulmaa kehitettävään järjestelmään ja eivät välttämättä käytä samaa kieltä ilmaistakseen itseään. Sidosryhmäanalyysi on usein integroitu suoraan käytettyyn kehitysmenetelmään tai käytäntöön ja ei välttämättä ilmene erillisenä prosessina. Ohjelmiston koon kasvaessa ja yhteyksien lisääntyminen yhä useampiin laitteisiin on johtanut tilanteeseen, missä sidosryhmäanalyysilta vaaditaan yhä enemmän kuin kirjallisuudessa on aiemmin tunnistettu. Ohjelmistojärjestelmien alati kasvava koko ja yhteyksien lisääntyminen muihin järjestelmiin kasvattaa sidosryhmien määrää vaikeuttaen sidosryhmäanalyysin tekemistä. Lisäksi on ongelmallista, että miten sidosryhmäanalyysin tulisi tukea suuren mittakaavan ohjelmistotuotantoa ja miten se käytännössä toteutetaan tällaisessa ympäristössä. Tämän väitöskirjan tavoitteena on tutkia sidosryhmän roolia ja tarkoitusta suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotannossa. Tutkimus on toteutettu empiirisellä lähestymistavalla tarkkailemalla suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotantoa kokonaisuutena. Tämä lähestymistapa mahdollistaa kokonaisuuden analysoinnin eri näkökulmista, jotta sidosryhmäanalyysin luonne ja tarkoitus voidaan tunnistaa ja kuvata suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotannossa. Väitöskirjan tulosten kontribuutio jakautuu kahteen osaan. Ensimmäiseksi väitöskirjan tulokset auttavat sekä tiedeyhteisöä ja käytännön työtä tekeviä kuvaamalla sidosryhmäanalyysin suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotannossa. Toiseksi tulokset havainnollistavat miten sidosryhmäanalyysi voidaan toteuttaa suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotekehitysprosessissa.

The traditional definition of a dynamic web application is about a collection of programs executed at server-side to provide content for clients. These types of web applications produce content at server-side and deliver it to their clients via multiple pages. In result, the client-side has the responsibility to render the content and perform a limited amount of calculations to increase the performance and user experience.    Meteor is a web framework designed for developing Single Page Applications and compared with traditional web frameworks, it takes a new approach in which most of the computations are done at the client-side. This leads to having the server-side primarily used for data storage and secondarily performing a limited amount of computations based on the Model View View-Model pattern.    This thesis tries to examine how web development is affected by Meteor framework from different angles by performing an experimental analysis on Meteor framework. It will investigate different attributes of Meteor framework used for developing a real-world application and finally concludes by presenting the advantages and disadvantages of using it.

Every year approximately a thousand of exchange students arrive to Växjö looking forimproving their university experience. The main problem is that this amount of peopleis very difficult to handle and organize. Sometimes, students don’t have enoughsupport, missing important information, missing interesting events and so on. In consequence, the students can develop a bad feeling about the universityorganization giving a bad feedback to the future potential incoming students. This is abad aspect to Linnaeus University because it is losing future students. In order to solve the problem, different surveys have been done to the internationalstudents, and even to the Växjö International Students (VIS) organization. The findings from these surveys are very interesting, and it is possible to identify andgroup different problems in order to make the solution easier. Furthermore, a good solution is found, improving the situation we were before. The solution found will fit in the hand of each student and will bring us in a better situationfor the university and their students.

Context. Agile Software Development has provided a new concept of Software Development based in adaptation to changes, quick decisions, low high-level design and frequent deliveries. However, this approach ignores the value that Software Architecture provides in the long term for increasing the speed in delivery working software, which may have catastrophic consequences in the long term. Objectives. In this study, the combination of these two philosophies of Software Development is investigated. Firstly, the concept of Software Architecture in Agile Projects; then, the major challenges faced concerning Software Architecture in Agile Projects, the practices and approaches that can be used to overcome these challenges and the effects that these practices may cause on the project. Methods. The research methodologies used in this study are Systematic Literature Review for gathering the highest amount possible of contributions available in the Literature at this respect, and also the conduction of Semi-Structured Interviews with Agile Practitioners, in order to obtain empirical knowledge on the problem and support or deny the SLR findings. Results. The results of the Thesis are a unified description of the concept of Software Architecture in Agile Projects, and a collection of challenges found in agile projects, practices that overcome them and a relation of effects observed. Considering the most frequent practices/approaches followed and the empirical support, it is enabled a discussion on how to combine Software Architecture and Agile Projects. Conclusions. The main conclusion is that there is not a definite solution to this question; this is due to the relevance of the context (team, project, customer, etc.) that recommends the evaluation of each situation before deciding the best way to proceed. However, there are common trends on the best-recommended practices to integrate these two concepts. Finally, it is required more empirical work on the issue, the conduction of controlled experiments that allows to quantify the success or failure of the practices implemented would be most helpful in order to create a body of knowledge that enables the application of certain practices under certain conditions.

Context: Distributed software development has become a most desired way of software development. Application of agile development methodologies in distributed environments has taken a new trend in developing software due to its benefits of improved communication and collaboration. Teamwork is an important concept that agile methodologies facilitate and is one of the potential determinants of team performance which was not focused in distributed agile software development. Objectives: This research shed a light on the topic of teamwork in the context of distributed agile software development. The objectives are to identify the factors contributing teamwork of distributed agile teams along with the dependencies between the factors. And, as it is not without challenges to work with unity in a heterogeneous environment, identification of challenges related to teamwork factors of distributed agile teams along with the mitigation strategies is an another objective. Methods: A systematic literature review (SLR) was employed to identify the teamwork factors along with their dependencies and corresponding challenges and mitigation strategies of each teamwork factor from state-of-the-art literature. Quasi-gold standard method was employed as search strategy in SLR to find out the primary studies representing the objective under investigation. Further a survey was conducted with industrial practitioners working in distributed agile projects to validate the findings from state-of-the-art literature. Results: A total of 13 teamwork factors (i.e. team orientation, shared leadership, mutual performance monitoring, backup behavior, feedback, team autonomy, team learning, coordination, communication, trust, collective culture, ease of use of technology, team familiarity), a set of nine dependencies between the teamwork factors and 45 challenges and 41 mitigation strategies related to the teamwork factors were identified from state-of-the-art literature. From survey result, communication, coordination, trust and team orientation were identified as four most important teamwork factors for distributed agile teams. Out of nine dependencies, seven were supported and two were not supported by the practitioners of distributed agile projects. Additionally, nine challenges and 12 mitigation strategies were identified through survey. Conclusions: From this study, we conclude that communication is the top most important factor for successful teamwork of distributed agile teams. And, unlike its prime importance in distributed software development for getting teams work together, trust was identified with a third priority for successful teamwork of distributed agile teams. Similar to the findings of the agile teams, team autonomy was identified with least importance towards the successful teamwork of distributed agile teams. Results of dependencies show that there is need for future research to explore all the dependencies between the teamwork factors. Furthermore, there are teamwork factors with no challenges and mitigation strategies being identified in state-of-the-art literature but later, through survey it was found that practitioners are facing the challenges for that particular teamwork factor. Though, this study identified those missed challenges, due to the limited number of participants involved in the survey, we cannot conclude that these were the only challenges faced in relation to the teamwork. Hence, there is a need to have a dedicated investigation in exploring all the challenges and mitigation strategies, such that it would help the distributed agile teams in attaining the fruitful interactions between them. / H.no. 5-5-289, Prashanth Nagar, Vanasthalipuram, Hyderabad-500070, Andhra Pradesh. India

Going offshore has become a norm in current software organizations due to several benefits like availability of competent people, cost, proximity to market and customers, time and so on. Despite the fact that Global Software Engineering (GSE) offers many benefits to software organizations but it has also created several challenges/issues for practitioners and researchers like culture, communication, co-ordination and collaboration, team building and so on. As Requirements Engineering (RE) is more human intensive activity and is one of the most challenging and important phase in software development. Therefore, RE becomes even more challenging when comes to GSE context because of culture, communication, coordination, collaboration and so on. Due to the fore mentioned GSE factors, requirements’ understanding has become a challenge for software organizations involved in GSE. Furthermore, Knowledge Management (KM) is considered to be the most important asset of an organization because it not only enables organizations to efficiently share and create knowledge but also helps in resolving culture, communication and co-ordination issues especially in GSE. The aim of this study is to present how KM practices helps globally dispersed software organizations in requirements understanding. For this purpose a thorough literature study is performed along with interviews in two industries with the intent to identify useful KM practices and challenges of requirements understanding in GSE. Then based on the analysis of identified challenges of requirements understanding in GSE both from literature review and industrial interviews, useful KM practices are shown and discussed to reduce requirements understanding issues faced in GSE.