A escolha entre o uso de metodologias ágeis ou metodologias tradicionais de desenvolvimento de software continua sendo amplamente discutida em vários aspectos, sendo um deles a presença ou ausência de certos fatores que precisam ser identificados para que as aplicações das metodologias sejam realizadas com sucesso. Neste estudo, tanto metodologias ágeis quanto tradicionais são discutidas através da literatura desde seu surgimento, histórico e evolução, até estudos comparativos entre ambas e outros com evidências empíricas, embora ainda haja a necessidade de estudos deste último tipo para o domínio. Com o intuito de avaliar as adequações dos tipos de metodologia para os diferentes cenários que uma organização ou projeto pode apresentar a partir dos fatores encontrados na literatura, foram realizadas entrevistas e questionários com pessoas envolvidas em desenvolvimento e definição de processos de desenvolvimento de software em um estudo de caso em empresa selecionada para a obtenção de mais evidências empíricas sobre o tema. Com os resultados obtidos, identifica-se então entre os fatores estudados quais são habilitadores e quais são inibidores para cada tipo de metodologia, propondo-se um modelo para a escolha de um ou de outro tipo a partir da presença ou ausência destes fatores nos cenários de aplicação das metodologias. / The choice between agile or traditional software development methodologies continues to be widely discussed in several aspects, being one of these aspects that certain factors presence or absence must be identified for methodologies usage to be successful. In this study, both agile and traditional methodologies are discussed on the domain literature from their emergence, historical facts and evolution, to comparative studies and empirical evidences obtained, despite there is still need for studies on this last subject for the domain. In order to evaluate adequacy for both types of methodologies to the different scenarios in which an organization or project may occur considering the factors appointed by literature, interviews and surveys where done with key people involved in software development or software processes in a case study in a selected company for more empirical evidence achievement. Then it is possible to identify between the factors which are enablers and which are inhibitors for each type of methodology, then purposing a model for the choice between the two types from the presence or absence of these factors in the scenarios for their uses.

Um Data Warehouse (DW) é um banco de dados centralizado, orientado por assunto, integrado, não volátil e histórico, criado com o objetivo de dar apoio ao processo de tomada de decisão e que estrutura os dados em uma arquitetura analítica bastante distinta da arquitetura relacional utilizada nos bancos de dados transacionais. Construir um DW é um projeto de engenharia bastante complexo pois envolve muitas tecnologias e muitas pessoas, de diferentes equipes, em um grande esforço conjunto para construir esta base central de informações corporativas. O processo tradicional de construção de um DW não utiliza conceitos ágeis e, pelo escopo de desenvolvimento ser grande, pode levar muito tempo até que funcionalidades sejam entregues aos clientes. Os métodos ágeis de engenharia de software são muito usados como uma alternativa aos métodos tradicionais de desenvolvimento e têm diferenciais que trazem muito valor a projetos grandes pois, além de buscar desenvolver versões funcionais em prazos curtos, defendem que todos os sistemas têm a constante necessidade de se adaptar a mudanças. Neste trabalho são aplicadas práticas ágeis no processo tradicional de engenharia de DW para que o desenvolvimento seja realizado em ciclos iterativos curtos, tornando possível o desenvolvimento rápido e evolutivo de um DW com entregas constantes de novas funcionalidades. A contínua evolução deste complexo ambiente analítico é apoiada por conceitos de banco de dados evolutivos e também por fundamentos de métodos ágeis. / A data warehouse (DW) is a central database, subject-oriented, integrated, nonvolatile, and time-variant collection of data in support of management\'s decision making process and that summarize the data in an analytic architecture quite different from the relational one, used in transactional databases. Building a DW is a complex engineering project because it involves many technologies and many people, from different teams, in a huge corporative effort to build a central database with corporative data. The traditional engineering process to build a DW does not use agile concepts and, as its scope is quite big, it might takes a long time until the customer can use its features. Agile methods of software engineering are commonly used as an alternative to the traditional methods and they have some differentials that lead a lot of value to big projects, as the continuous attempt to develop short releases in short periods of time, or the belief that every system needs to be continuously adapted to the changes on its environment. This work applies agile practices in the traditional DW engineering method, so that the development can be done in short iterative cycles, making possible a fast and evolutive DW project, with frequent delivering of new functionalities. The continuous evolution of this complex analytical environment is supported by evolutive database concepts and also for agile methods foundations.

Os métodos ágeis introduziram uma nova abordagem de desenvolvimento de software, enfatizando os indivíduos, o produto e a comunicação. Prometem alta satisfação do cliente, baixo índice de erros, tempo de desenvolvimento mais rápido e uma solução para a rápida mudança de requisitos. Por outro lado, modelos de qualidade de software, como o CMMI, prometem previsibilidade, estabilidade e segurança, melhorando a qualidade dos produtos e dos processos da empresa. O intuito desta pesquisa é unir estas duas abordagens na tentativa de aproveitar as vantagens de ambas. Como resultado, apresenta-se o framework Scrum-DR, uma extensão do Scrum, aderente às diretrizes do CMMI-DEV na categoria Suporte. O Scrum-DR possui características do desenvolvimento ágil de software e contempla a utilização de técnicas de Design Rationale, apresentando um modelo que soluciona uma importante questão nas metodologias ágeis. / Agile methods introduced a new approach to software development, emphasizing individuals, product, and communication. They promise high customer satisfaction, low error rates, faster development time and a solution for rapidly changing requirements. On the other hand, software quality models, such as CMMI, promise predictability, stability and security, improving the quality of the company\'s products and processes. The purpose of this research is to link these two approaches in an attempt to take advantage of both. As a result, the Scrum-DR framework, a Scrum extension, adhering to the CMMI-DEV guidelines in the Support category is presented. Scrum-DR has characteristics of agile software development and contemplates the use of Design Rationale techniques, presenting a model that solves an important issue in agile methodologies.

xiii, 80 p. : ill. (some col.) / The design of successful assistive technologies requires careful personalization for individual users, as well as rapid, low cost cycles for product development and testing. My research brings two modern software engineering models to meet these challenges: Personal and Contextual Requirements Engineering (PC-RE) and Agile Software Development. We adapt these models to the assistive mobile navigation domain for the blind. This dissertation demonstrates that a Virtual Environment testing can significantly reduce testing time, yield meaningful testing results by fully controlling environmental variables, alleviate logistical and safety problems, and serve as an ideal platform for deep personalization. We developed a narrative NAvigation Virtual Environment (NAVE) and compared blind subjects' performance and behavior in wayfinding tasks with tactile maps under field testing versus testing in NAVE. Our experiments showed positive results to support our hypothesis that virtual environments can be useful in replacing field testing for personalized assistive technologies in agile development. / Committee in charge: Stephen Fickas， Chairperson； Art Farley， Member； Michal Young， Member； Amy Lobben， Outside Member

In order to stay competitive in today’s overly competitive market place, businesses must be engineered to match product characteristics and customer requirements. This increased emphasis on achieving highly adaptive manufacturing with reduction in manufacturing costs, better utilization of manufacturing resources and sound environmental management practices force organisations to adopt efficient management practices in their manufacturing operations. Some of the established practices in this context belong to the Lean, Agility and Green (LAG) paradigms. Adopting these practices in order to address customer requirements may require some level of expertise and understanding of the contribution (or lack of it) of the practices in meeting those requirements. Primarily, the wide choice of LAG practices available to address customer requirements can be confusing and/or challenging for those with limited knowledge of LAG practices and their efficacy. There is currently no systematic methodology available for selecting appropriate LAG practices considering of the product life cycle (PLC). Therefore, this research provides a novel framework for selecting appropriate LAG practices based on PLC stages for reducing costs, lead time and generated waste. The methodology describes the application of analytic hierarchy process (AHP), statistical inference and regression analysis as decision support tools, ensuring a systematic approach to the analysis with appropriate performance measures. The data collected were analysed with the aid of SPSS and Excel using a variety of statistical methods. The framework was verified through a Delphi study and validated using a case study. The key findings of the research include the various contributions of lean, agile and green practices towards improving performance measures, the importance of green in improving performance measures and the importance of selecting appropriate practices based on product life cycle stages. This research makes a clear contribution to existing body of knowledge by providing a methodological framework which could serve as a guide for companies in the FMCG industry to systematically integrate and adopt lean, agile and green to better manage their processes and meet customer requirements in their organisations. However, the framework developed in this research has not been tested in other areas.

A digitalização e a evolução tecnológica experimentadas em anos recentes têm promovido mudanças na forma como as organizações se estabelecem e desenvolvem seus modelos de negócios. São exigidos intervalos de respostas cada vez mais curtos, bem como flexibilidade e dinamismo. Algumas práticas têm emergido para auxiliar empreendedores atuantes neste novo cenário, em especial aos líderes de startups e projetos de base inovadora. O presente trabalho apresenta resultados de uma pesquisa que teve como objetivo de investigar de que forma o lean startup pode auxiliar novos empreendimentos baseados em inovação a validar seus modelos de negócio, quais os fatores críticos de sucesso para a sua implementação e qual o grau de adoção de suas práticas por startups tecnológicas na região metropolitana de Porto Alegre (RS). Para isto, o estudo foi dividido em três principais etapas. A primeira etapa consistiu em uma revisão sistemática da literatura a respeito da temática, com a identificação de estudos acerca do lean startup, customer development e gestão ágil. Foram identificados principais efeitos da implementação sobre as organizações e fatores críticos de sucesso para a execução A segunda e terceira etapas compreenderam estudos de caso múltiplos, com a identificação de práticas utilizadas por startups tecnológicas para a validação de elementos de modelos de negócio, e a coleta de percepções de líderes de startups de engenharia quanto ao lean startup e os principais obstáculos e facilitadores para a sua implementação. Entre os principais resultados, destacam-se os benefícios das práticas ágeis sobre a flexibilidade das organizações, bem como a redução de custos, se comparados à gestão baseada em planos de negócios. Deve-se ressaltar que os estudos de caso possuem limitações quanto à generalização, visto que podem não representar outras realidade. De toda a forma, o presente trabalho contribui para o preenchimento de parte de uma lacuna existente na literatura quanto à temática. / Digitization and technological evolution experienced in recent years has led to changes in the way organizations establish and develop their business models. Market demands quick responses as well as flexibility and dynamism. Some practices have emerged to assist entrepreneurs in this new scenario, especially leaders behind startups and innovation-based projects. This work presents results of a research that aimed at investigating how lean startup can support the validation of business models in innovation-based ventures, what are the critical success factors for its implementation, and whether the startups in the metropolitan region of Porto Alegre (RS) are actually adopting the methodology. To achieve this objective, the study was divided into three main stages. The first stage consisted of a systematic literature review on the subject, with the identification of studies about lean startup, customer development and agile management. As main findings, we identified lean startup effects on organizations and critical success factors for its implementation. The second and third steps included multiple case studies, identifying the practices used by technological startups to validate business models elements, and the perceptions of leaders behind engineering startups regarding to lean startup, as well as main obstacles and facilitators for its implementation. Some results regard the benefits of agile practices on the flexibility of organizations, as well as the reduction of costs, when compared to plan-based management approaches. Case studies have limitations on generalization, since they may not represent other realities. In any case, the present work contributes to fill part of a literature gap on the subject.

Inom IT-projekt beskrivs kravhantering som en av de inledande aktiviteterna i systemutveckling som syftar till att specificera beställarens behov. Kravhantering har länge brottats med många problem. Ett är att krav blir låsta tidigt i ett projekt och kan därefter inte förändras, detta minskar beställarens flexibilitet. Användning av agila metoder har blivit allt vanligare bland IT-leverantörer. Agila metoder förespråkar att IT-leverantör och beställare har ett nära samarbete. Eftersom beställaren ansvar ökar under kravhantering i agila projekt fann vi det intressant att undersöka vilka faktorer som är viktiga för beställaren att beakta under kravhantering i agila projekt. I litteratur finns mycket beskrivet om agila metoder generellt, men väldigt lite kring beställarens roll, varför vi ville undersöka detta närmare. Studien genomfördes med en kvalitativ ansats. För att undersöka hur IT-leverantören ser på beställarens roll under kravhantering i agila projekt har vi intervjuat fem respondenter från fyra olika IT-företag som använder agila metoder. Intervjuerna var semistrukturerade eftersom vi sökte respondenternas uppfattningar och tolkning av kravhanteringen. Intervjumaterialet analyserades sedan med en tematisk analys. Datainsamlingen visade att det fanns flera faktorer som är viktiga för beställaren att beakta under kravhanteringen. Engagemang är viktigt för att beställaren ska ha möjlighet att påverka och ha åsikter om kraven under projektets gång. Inledningsvis samlas kraven in på en övergripande nivå och det blir därför viktigt med en kontinuerlig kommunikation mellan IT-leverantör och beställare för att detaljera kraven under projektet. För att kunna ha ett nära samarbete med IT-leverantören krävs det att beställaren är delaktig i projektet i allt större utsträckning. Det har också visat sig att IT-leverantörens användning av agila metoder inte ställer orimliga krav på beställaren. Tvärtom är de väldigt flexibla gentemot beställaren och anpassar metoden på ett sätt som passar beställaren. Studien visar att det ibland är känsligt för IT-leverantören att ställa allt för höga krav på beställaren, eftersom beställaren är en kund. Studiens resultat indikerar att när IT-företagen använder agila metoder under kravhanteringen krävs det att beställaren är engagerad under merparten av projektet, eftersom kraven samlas inledningsvis in på en övergripande nivå och detaljeras sedan. Beställarna är inte vana vid att så höga krav ställs på deras engagemang. Det har också visat sig vara svårt att motivera beställarna att vara delaktiga i projektet, beställarens måste själv inse vikten av engagemang och delaktighet. Det krävs att båda parter tar sitt ansvar under kravhanteringen för att beställaren ska kunna få det system de vill ha och betalar för. / Program: Interaktions- och kommunikationsdesignerutbildningen

While software play integral role in every aspect of the modern world, software development process still faces many problems. During development process in an organization, effective methodology has a crucial role in order to become accomplished. Agile approach is new methodologies which have been introduced recently as a new approach for developing software to increase productivity and efficacy of software development process compare to traditional methodologies. Whereas, accomplishment of this methodology is still anecdotal and deeper investigation in this area is scant in academic circles. The purposes of this research is to influence success of agile software development in subject factor of organization, people, process, technical and project dimensions under terms of quality, scope, timeless and cost. This study has conducted a survey in order to investigate important success factors of agile software development process using quantitative approach. Preliminary After sufficient literature an explanation and list of potential factors for agile methodology based on previous studies were introduced. Afterward, factor and reliability analysis were conducted to mix this primal list into a finalized list of potential critical success factors in four mentioned dimensions. For each agile success factors term of quality, scope, time, and cost has been investigated. In order to collect required data a questionnaire was conducted among employees in a famous software development company who are mostly working based on agile methodology. This survey will make the personnel’s feedback and analysis their ideas about the variety of factors of agile methodologies which they are usually implemented in software development projects. Dependent sample tests, independent test related to the gender and multiple regression techniques as in full regression model and the last one is an optimized regression model which is done via the stepwise screening procedure. Final result of this study proved and rejected selected hypotheses. These hypotheses were about relationship between factor in four dimensions and quality, scope, time, and cost by using agile process. This questionnaire and analysis of this case study has proved some of authors’ hypothesis like the fact that by using agile methodology organization dimension is related directly to quality of product instead of reduction of total cost or using team management techniques can affect timeless factor instead of cost reduction. Finally, researcher makes more suggestions in order to make success factors more effective and increase productivity during the development process and to have more accomplishment in agile base projects. / Program: Masterutbildning i Informatik

Today we are in an age of Information. The systems that effectively use the vast amount of data available all over the world and provide meaningful insight (i.e. BI systems) for the people who need it are of critical importance. The development of such systems has always been a challenge as the development is outweighed by change. The methodologies that are devised for coping with the constant change during the system development are agile methodologies. So practitioners and researchers are showing keen interest to use agile strategies for the BI projects development.The research aims to find out how well the agile strategies suit for the development of BI projects. The research considers a case study in a very big organization as BI is organization centric. There by assessing the empirical results that are collected from interviews the author is trying to generalize the results. The results for the research will give an insight of the best practices that can be considered while considering agile strategies and also the practical problems that we may encounter on the journey. The findings have implications for both business and technical managers who want to consider agile strategies for the BI/DW development projects. / Program: Masterutbildning i Informatik

Denna studie syftade till att ta fram ett ramverk för utveckling av API:er för tjänsteorienteradearkitekturer. Studien tar sin utgångspunkt i forskningsprojektet e-Me (utvecklingenav en integrationsplattform för att underlätta studenters vardag) samt en benchmarking avde i nuläget mest använda API:erna på webben. Studien har fem faser: En litteraturstudie,en benchmarking, en kvalitativ genererande intervjustudie, en teoribildande fas (framtagningav ramverket), samt en kvalitativ validerande studie. Litteraturstudien tar upp sådanafenomen som utvecklingsmetoder, systemarkitekturer (bland annat SOA) samt metautveckling.Denna studie låg till grund för den första intervjustudien, som i sin tur låg tillgrund för benchmarkingen. Resultatet av dessa två studier bildade tillsammans en grundför ramverket SOAPIF (Service-Oriented Application Programming Interface Framework),som till en början innehöll fyra olika faser: Conceptualization, där man försökerbilda sig en uppfattning om vad API:et skall exponera; Definition, där man försöker definieraett kontrakt för API:et; Testing & Implementation som tar sin utgångspunkt i testerför att implementera API:et; samt Delivery, som är den fas där API:et skall levereras. Ialla dessa faser ingick kontinuerligt dokumentation samt co-design. Efter en validering avramverket byttes de fyra faserna ut mot fem arbetsmoment, med samma namn som fasernaovan, med ett tillägg: Ett arbetsmoment som heter API Evaluation, och som syftar tillatt efter leveransen tillsammans med konsumenterna av API:et utvärdera det. Utifrån deresultat som denna studie genererat, har följande slutsatser kunnat dras: Det är oerhörtviktigt med flexibla API:er som utvecklas i samarbete med den tänkta slutkonsumenten,och att dessa API:er testas mot de förväntningar som konsumenterna har på dem. Det ärockså oerhört viktigt att API:er är väldokumenterade, för att underlätta för konsumenter.När det gäller integrationsplattformar är anledningen till att man utvecklar dessa främstett behov av flexibilitet.