Uma das grandes dificuldades do desenvolvimento de software é adequar, de forma sistemática, os esforços na resolução de problemas e nas melhorias dos processos internos aos objetivos do negócio. O Seis Sigma é uma metodologia estruturada que incrementa a qualidade dos processos e o alinhamento com as estratégias empresariais, proporcionando altos ganhos financeiros para quem o utiliza. Surgido inicialmente na manufatura, o Seis Sigma vem sendo aplicado também noutros setores. No desenvolvimento de software, o seu uso é ainda restrito, mas há indícios de que possa ser utilizado com o mesmo sucesso. O objetivo desta dissertação de mestrado é propor um roteiro específico para a implementação do Seis Sigma nas organizações desenvolvedoras de software. Além do levantamento teórico, foi realizado um estudo de casos múltiplos para analisar as razões da sua adoção, as modalidades de seu uso, os seus benefícios e as suas limitações para os processos de software. Os resultados observados mostram que o Seis Sigma pode ser aplicado total ou parcialmente na melhoria dos processos de software. Além disso, é necessário alguma customização nos processos do Seis Sigma convencional, uma vez que os projetos de melhoria podem estar orientados para novos produtos, novos clientes ou, ainda, que os trabalhos de desenvolvimento fiquem a cargo de novas equipes, que muitas vezes são terceirizadas. O trabalho conclui que o Seis Sigma pode contribuir efetivamente para a melhoria dos processos de software, independentemente da organização objetivar níveis superiores de maturidade. O estudo sugere também um roteiro específico, chamado SW-DMAIC, para a aplicação do Seis Sigma em empresas desenvolvedoras de software. Este roteiro é composto por três etapas: implementação da filosofia do Seis Sigma, reciclagem desta filosofia, quando necessário e execução de projetos específicos. / Aligning sistematically efforts to solve problems and improve the software process with business goals is one of the challenges of software development. Six Sigma is a structured methodology that increases the process quality and aligning with enterprise strategies, providing high financial returns for those who uses it. Firstly applied in manufacturing companies, Six Sigma has been applied in other sectors too. It is not widely used in the software companies yet, but there are already some successful cases. The main objective of this master degree dissertation is to propose a specific roadmap for the Six Sigma application at software companies. Besides the theoretical research, it is accomplished a multiple case study to analyze the adoption reasons, the modalities of the use, the benefits and the limitations of Six Sigma for the software processes. The observed results show that Six Sigma could be applied totally or partially for software process improvement. Therefore it is necessary some tayloring in the Six Sigma processes, because improvement projects could refer for new products or new customers or some of the development work is in charge of new teams, specially when they are a outsoursing. The work has concluded that Six Sigma could contribute indeed to software process improvement, independently the enterprise is going to reach higher level maturity. This study suggests also a specific three-stage-roadmap, called SW-DMAIC, for the Six Sigma application at software companies containing processes for implementation of Six Sigma?s philosophy, recycling this philosophy when it?s necessary and, execution of specific Six Sigma projects.

Um crescente número de empresas produtoras de software tem adotado um modelo organizacional de Fábrica de Software (FS), que facilita a terceirização por intermédio da segmentação das atividades e adoção de um sistema de produção mais flexível, dinâmico e controlado. Uma FS pode atender a múltiplas demandas de natureza e escopos distintos com o intuito de prover as necessidades específicas de cada cliente. Em face da diversidade e complexidade deste contexto, uma das questões principais a resolver é como mapear todos os processos envolvidos, identificando claramente o que, quem e, sobretudo como cada trabalho deve ser executado e controlado, visando o alinhamento dos processos à estrutura organizacional e conceitual de FS com foco nos processos de integração, alinhamento e reuso. Este estudo tem como objetivo mapear, definir, reestruturar e estabelecer processos de Fábrica de Software, conduzidos pelo método de pesquisaação em uma organização produtora de software do setor público, considerando seu contexto operacional, técnico e cultura organizacional. O desenvolvimento, execução, acompanhamento e resultados são descritos pelos ciclos da pesquisa-ação envolvendo o estudo de estruturas organizacionais, metodologias de desenvolvimento de sistemas, e mudanças organizacionais. Para isso foram definidas uma Estrutura Organizacional de Referência de FS, uma Arquitetura de Definição de Processos para FS e uma Metodologia de Desenvolvimento de Sistemas e Integração com foco organizacional, concebidos e desenvolvidos com base na literatura, experiência profissional e pesquisa empírica, que serviram como guia de condução da pesquisa-ação, culminando na associação do estudo empírico com o estudo teórico. As contribuições empíricas e teóricas geradas referem-se à melhoria dos processos organizacionais e operacionais de uma empresa de TI do setor público com base nos conceitos de FS. / A growing number of software producing companies have adopted an organizational model of Software Factory (SF), which facilitates outsourcing by segmenting activities and by adopting a more flexible, dynamic and controlled production system. A SF can serve the multiple demands of different nature and scopes with the purpose of providing each customers specific needs. Because of the diversity and complexity of this context, one of the main issues to be solved is how to map all the processes involved, clearly identifying what, who and mainly how each work must be executed and controlled, aiming at aligning the processes to the organizational and conceptual structure of SF focusing on the integration, aligning and reuse processes. The purpose of this study is mapping, defining, restructuring and establishing the Software Factory process, conducted by the action research method in a software producing organization of the public sector, considering its operational, technical and organizational culture context. The development, execution, follow-up and results are described by the action research cycles involving the study of organizational structures, system development methodologies and organizational changes. For this, a Reference Organizational Structure of SF, and Processes Definition Architecture for SF and a Integration System Development Methodology with organizational focus were defined, conceived and developed based on the literature, professional experience and empirical research, which served as a guiding line of the action research, peaking at the association of the empirical study with the theoretical study. The generated empirical and theoretical contributions refer to the improvement of the organizational and operational processes based on the SF concepts.

A maioria das micro e pequenas empresas (MPEs) de desenvolvimento de software brasileiras são voltadas para o desenvolvimento de software on-demand. Normalmente, essas MPEs têm dificuldades em formalizar um processo de software padrão. O presente trabalho de pesquisa tem por objetivo apresentar uma proposta de integração de modelos/normas de capacidade de processo com modelos de ciclo de vida de software, em um contexto de gestão de processos de negócio. Como resultado, obteve-se o modelo de gestão do processo de venda e desenvolvimento de software on-demand para MPEs (ProcSoftVD - Gestão), composto pelo método de melhoria de processo de software (ProcSoftVD - Melhoria) e pelo modelo de processo de venda e desenvolvimento de software on-demand para MPEs (ProcSoftVD). O método de melhoria de processo de software foi criado a partir de abordagens existentes e complementares, voltadas às MPEs. O ProcSoftVD foi originado com base no framework unified process, possibilitando a visualização do processo em duas perspectivas - fases e áreas de conhecimento, e nos modelos/normas de capacidade de processo CMMI-DEV e ISO/IEC 15504-5, elaborado em um processo iterativo e evolutivo de pesquisa-ação com a participação de duas MPEs. Um diferencial dessa proposta é a consideração de atividades de comercialização do software junto ao processo de desenvolvimento de software, o que auxilia na delimitação do escopo do projeto de desenvolvimento de software para um acordo contratual. Outro diferencial é o detalhamento das atividades do processo por meio de tarefas, sugestão de papéis desempenhados pelos responsáveis das atividades e disponibilização de templates com exemplos para cada um dos artefatos elaborados na execução da atividade. / The majority of the software development micro and small companies are turned to the development of on-demand software. Usually, for these small companies the formalization of a standard process for software development is very difficult. For that reason the goal of this research is to propose an integration of capability processes models/standards within software life cycle models, in a perspective of business process management. The main result of this research is a management model of selling and on-demand software development process, which embraces the software process improvement method and the selling and on-demand software development process model. The software process improvement method was build from complementary and existents tailored approaches for micro and small companies. The selling and on-demand software development process model was created based on the models/standards of process capability CMMI-DEV and ISO/IEC 15504-5 and on the unified process framework, allowing the process view from two perspectives - phases and knowledge areas. The model was elaborated in an iterative and evolutionary action-research process carried out within two micro and small companies. The originality of this proposal is the consideration of software sale activities jointly with software development process, assisting the scope delimitation of a software development project for contractual agreement. Other aspect of this research which makes it distinctive is the detail of the process activities by mean of tasks, suggestions of people roles for each activities and provision of templates with examples for each artifact created during the activities.

The Information Technology (IT) market is growing. The number of companies and the volume of contracting in IT has increased. Because of the increasing competition, organizations need to improve their market presence and mainly seek increased efficiency and effectiveness through the implementation of software process improvement (SPI). Passos, Dias-Neto e Barreto (2012a) to believe that the results of this initiative appear when the achieved benefits are aligned with the organizational values. This study aims to verify the benefits achieved by organizations with the implementation of MPS.BR; to identify if organizational values are present in these organizations and to verify the existence of relationship between the benefits achieved by the implementation of software process models and organizational values. Data collection was conducted through questionnaires in organizations which implemented MPS.BR. The participants were 9 organizations, 47 questionnaires were answered. Benefits surveyed "clearer processes" and "processes with more quality" were the most perceived as "reduction in development time" and "reduction in the cost of development", the less checked by employees. After completing statistical analyzes, it was possible to reduce to four factors the 18 benefits studied, identifying the categories: quality, control, process and staff. Of the 10 organizational values studied, the most noted were "teamwork" and "responsibility" and the least observed were "strategy" and "information". The statistical analysis showed the relationship between the benefits and the organizational values, showed that organizational commitment and supervision values are strongly correlated of impactful on the benefits, suggesting that software development organizations that wish to achieve the benefits from the implementation of MPS.BR should focus their efforts on strengthening the supervision in their organization and develop a commitment to their team. / O mercado de Tecnologia da Informação está em ritmo crescente. Tem aumentado a quantidade de empresas e o volume de aquisições e contratações na área. Com a concorrência crescente, as organizações precisam melhorar sua presença no mercado e, principalmente, buscar aumento de eficiência e eficácia por meio da implementação de melhoria de processo de software. Segundo Passos, Dias-neto e Barreto (2012a), para que essa iniciativa traga resultados, um dos principais fatores é que os benefícios provenientes dessa implantação estejam alinhados com os valores organizacionais. Diante do exposto, este estudo pretende verificar quais os benefícios conquistados pelas organizações com a implementação da Melhoria de Processo de Software Brasileiro - MPS.BR; identificar quais valores organizacionais estão presentes nessas organizações; e verificar a existência de relações entre os benefícios alcançados pela implementação de modelos de processo de software e os valores organizacionais. O levantamento de dados foi realizado por meio de aplicação de questionários em organizações que possuem o Modelo de Processo de Software Brasileiro – MPS.BR implementado. Participaram da pesquisa 9 organizações, foram respondidos 47 questionários. Entre os benefícios pesquisados, ―processos mais claros‖ e ―processos com mais qualidade‖ foram os mais percebidos e ―redução no tempo de desenvolvimento‖ e ―redução no custo de desenvolvimento‖, os menos verificados pelos empregados. Depois de realizadas análises estatísticas, foi possível reduzir para 4 fatores os 18 benefícios estudados, identificando as categorias qualidade, controle, processo e equipe. Dos 10 valores organizacionais estudados, os mais constatados foram ―trabalho em equipe‖ e ―responsabilidade‖ e os menos observados foram ―estratégia‖ e ―informação‖. As análises estatísticas para verificar as correlações entre os benefícios e os valores organizacionais evidenciaram que os valores organizacionais, comprometimento e supervisão, se correlacionam, de forma impactante nos benefícios, sugerindo que as organizações de desenvolvimento de software que desejam alcançar os benefícios com a implementação do MPS.BR devem focar seus esforços em fortalecer a supervisão em sua organização e desenvolver o comprometimento em sua equipe. / São Cristóvão, SE

Made available in DSpace on 2015-04-11T14:03:21Z (GMT). No. of bitstreams: 1 Davi Viana dos Santos.pdf: 1879718 bytes, checksum: c5d0d7175f9d9c94ab6c07ac4434fa41 (MD5) Previous issue date: 2011-07-21 / CNPq - Conselho Nacional de Desenvolvimento Científico e Tecnológico / Several factors can influence the success of Software Process Improvement (SPI) programs. Results from previous research have shown that human and social aspects influence these programs in different ways. For this reason, it is important to analyze the human aspects involved on SPI programs to gain a better understanding about their influence on such programs. This thesis presents a research about human aspects influences in software process improvement. In this work, we analyze the major findings of a qualitative research conducted in three different phases to analyze which factors were most influential from view-point of the professionals working in the organizations. Our ultimate goal is to deepen the understanding about how human aspects can influence a SPI program in order to help in the success of future SPI implementation. / Diversos fatores podem influenciar o sucesso de um programa de Melhoria de Processo de Software (MPS). Os resultados de pesquisas anteriores mostram que vários desses fatores são de natureza humana e social. Por esta razão, é importante analisar os aspectos humanos envolvidos a fim de obter uma maior compreensão da influência destes em um programa MPS. Esta dissertação apresenta uma pesquisa sobre a influência dos aspectos humanos em Programas de MPS. Neste trabalho são analisados os principais resultados de uma pesquisa qualitativa conduzida em três diferentes fases para analisar quais fatores tiveram maior influência do ponto de vista dos colaboradores das organizações. O objetivo final é aprofundar a compreensão dos aspectos humanos que podem influenciar um programa de MPS com a finalidade de auxiliar no sucesso de futuros programas de melhoria.

Context: Software Process Improvement uses lean principles for eliminating wastes in the software development process. Waste is defined as anything that does not add value to the customer and product. The seven traditional wastes in software engineering are partially done work, extra process, extra features, waiting, motion, task switching and defects. Using the lean principles and practices, the wastes can be reduced or eliminated. It is important to know the lean practices that are widely used in software development and to know the practices, which captures the seven wastes. From the literature, the ability of waste reduction is theoretically discussed [2], but practically only little empirical evidence is available on ‘which practice is best capable in reducing specific kinds of waste.’ Objectives: Many software development organizations have adopted lean practices and agile practices for eliminating wastes of different kinds. Therefore, this study focuses on evaluating the effectiveness of lean practices in their ability to reduce the seven types of wastes associated with Lean Software Engineering. Methodology: The methodology that is used in this study is systematic literature review and industrial survey. In order to achieve the objective on evaluating the lean practices and agile practices in their ability to reduce the seven types of wastes that have more attention in research, a systematic literature review is conducted. Thereafter, to capture the effectiveness of lean practices in waste removal, a survey is designed to capture the perception of practitioners. Results: The systematic literature review has identified 53 relevant studies to the research topic. From these primary studies, the lean practices/principles, hybrid agile and lean practices, and the efficiency of agile practices in eliminating the seven wastes were identified. In addition to that, wastes that are captured by using lean practices; hybrid lean and agile practices were also identified. The reason for considering agile practices is that, agile and lean have similarities in eliminating the wastes and creating value to the customer [2][3]. Through the systematic literature review, it can be observed that researchers have not investigated all the seven wastes captured by lean practices. Thereafter, survey is the main contribution to this research where, the responses of 55 respondents from different countries were recorded. Most of the respondents are from India with 42% of the responses. We have asked the role of every respondent in their companies, and 19 respondents are Team leaders, 16 respondents are project managers and remaining people perform various other roles in software development. 38 respondents are from large-scale industry, which constitutes the majority part of the survey. The main contribution of the survey is identifying the ability of lean practices in eliminating different wastes. The respondents were asked to provide their level of agreement related to the effectiveness of each lean practices and agile practice in waste removal. A comparison between the results of SLR and survey reveals that there is a lot of variance in the perception of researchers and practitioners regarding the lean practices in eliminating wastes. Survey captures more wastes than SLR. From the results of survey, it was also identified that using the lean practices i.e. Kanban and VSM can eliminate most of the wastes. Kanban (41) and VSM (33) are mostly used and more efficient in industries. Conclusions: To conclude, the obtained results from this study will be quite useful for the real-time execution of lean practices. Team leaders, project managers, and organizations can adopt lean by choosing lean practices in accordance to the wastes that have to be eliminated from their software development process. This study has also identified the benefits and limitations of lean practices implemented in industry. This study helps researchers in providing necessary information that is very useful for further research in lean practices. The combinations of lean practices were also presented, which in terms one lean practice can compensate another in capturing all the seven wastes. In the survey, the additional wastes were identified when compared to SLR and this complements the literature. There is a considerable reach gap between the state of art and state of practice. It has been identified that VSM and Kanban practices have much attention in the literature. The remaining practices like Kotter and Kaizen are less concentrated in most of the research literature. From the literature, it is evident that none of the practices is capable of eliminating all the seven wastes in software development. VSM is capable of capturing wastes like waiting, extra process and motion. In addition, Kanban captures and eliminates wastes like partially done work, defects, task switching and extra features. With respect to the survey, Kanban and VSM practices are efficient in eliminating wastes. When the practitioners consider hybrid lean and agile practices, the combination of Kanban and Scrum, Scrum and VSM are efficient in eliminating wastes. The practitioners can consider the benefits of lean practices that are identified in this research. / V S S N R Ram Nanduri vssnrram@gmail.com

Abstract—Background: Software Process Improvement (SPI) maturity models have been developed to assist organizations to enhance software quality. Agile methodologies are used to ensure productivity and quality of a software product. Amongst others they are applied in Small and Medium – sized Enterprises (SMEs). However, little is known about the combination of Agile methodologies and SPI maturity models regarding SMEs and the results that could emerge, as all the current SPI models are addressed to larger organizations and all these improvement models are difficult to be used by Small and Medium – sized firms. Combinations of these methodologies could lead to improvement in the quality of the software products, better project management methodologies and organized software development framework. Objectives: The aim of this study is to identify the main Agile methodologies and SPI maturity models applied in SMEs, the combinations of these methodologies, and the results that could emerge. Through these combinations, new software development frameworks are proposed. What is more, the results of this study can be used as a guide with the appropriate combination for each SME, as a better project management methodology or as improvement in the current software engineering practices. Methods: A Systematic Literature Review was conducted, resulting in 71 selected relevant papers ranging from 2001 to 2013. Besides, a survey has been performed from June 2013 to October 2013, including 49 participants. Results: Seven Agile methodologies and six different SPI maturity models were identified and discussed. Furthermore, the combination of eight different Agile methodologies and Software Process Improvement maturity models is presented, and as well as their benefits and drawbacks that could emerge in Small and Medium – sized firms. Conclusion: The majority of the Agile methodologies and SPI maturity models are addressed to large or very large enterprises. Thus, little research has been conducted for SMEs. The combinations of the Agile methodologies and SPI maturity models are usually performed in experimental stages. However, it has been observed that such type of combination could present numerous benefits, which can also be applicable in SMEs as well. The combinations that are most common are the CMMI and XP, CMMI and Scrum, CMMI and Six Sigma, and the PRINCE2 and DSDM. / 0034-636835645

Num curto período de tempo, a Web tornou-se o aspecto central de muitas aplicações em diferentes áreas. Rapidamente, cresceu e diversificou seu uso, e diversos setores de negócio realizam suas operações no ambiente da Web. Entretanto, à medida que cresce a extensão de uso de aplicações Web, que se tornam mais complexas, aumenta a preocupação com a maneira como as aplicações são desenvolvidas. Freqüentemente, a abordagem de desenvolvimento é ad hoc, desprovida de técnicas sistemáticas e de metodologias sólidas, resultando em aplicações de baixa qualidade. A fim de alcançar aplicações Web bem sucedidas, há a necessidade de melhores princípios de esenvolvimento que devem considerar as características especiais dessas aplicações. Dessa forma, o objetivo do trabalho é propor Processos de Apoio ao desenvolvimento das aplicações Web, baseando-se nas características dessas aplicações e nos Processos de Apoio da ISO/IEC 12207. Os processos de Apoio visam auxiliar outros processos do ciclo de vida da aplicação a alcançar produtos de qualidade e o sucesso do projeto / Within a short period, the Web has become the central aspect of many applications in different areas. Rapidly, it has grown and diversified in its scope and use. Diverse business sectors improve their operations in Web environment. The Web application has become more complex and it has increased the concern with the way the application is developed. Frequently, the development is ad hoc, unprovide of systematic methods and methodologies, resulting in poor quality applications. In order to have successful Web applications, it is necessary better principles of development that have to consider the characteristics of these applications. The objective of this work is to propose Supporting Process for development Web applications, based on the characteristics of these applications and the Supporting Process of ISO/IEC 12207. The Supporting processes aim to assist other processes of the cycle of life of the application to reach quality products and successful projects

Context: At the core of choosing what features and level of quality to realize, and thus offer a market or customer, rests on the ability to take decisions. Decision-making is complicated by the diverse understanding of issues such as priority, consequence of realization, and interpretations of strategy as pertaining to the short-term and long-term development of software intensive products. The complexity is further compounded by the amount of decision support material that has to be taken into account, and the sheer volume of possible alternatives that have to be triaged and prioritized; thousands or even tens of thousands of requirements can be the reality facing a company. There is a need to develop the functionality that is strategically most significant, while satisfying customers and being competitive, time efficient, cost effective, and risk minimizing. In order to achieve a balance between these factors, all the stakeholders, within an organization, need to agree on the strategic aspects and value considerations to be considered, and their corresponding relative importance. Objective: The objective of this thesis is to provide enhanced decision support for product managers faced with decision-making challenges. This involves, but is not limited to, enhancing the alignment between the product and portfolio management with respect to product strategies, and enabling the use of value as a basis for product management and development related decisions. Method: A number of empirical studies, set in industry, have been performed. The research methods used span from systematic mapping, and systematic reviews to case studies, all aligned to identify possibilities for improvement, devise solutions, and incrementally evaluate said solutions. Close collaboration with industry partners was at the core of the research presented in this thesis. Result: The MASS method presented in this thesis can be used to evaluate strategic alignment and identify possible root causes for misalignment. To strengthen strategic alignment, the Software Value Map and corresponding decision support material, proposed in the thesis, can be used by product managers for making effective and efficient strategic decisions in relation to portfolios, products and process improvement, following a systematic and aligned process. Conclusions: The area of software product management, in the context of market-driven software intensive product development, is a field with unique challenges. The specifics of the solutions are based on industry case studies performed to gauge state-of-the-art, as well as identify the main challenges. The decision support developed takes the form of maps and frameworks that support software product management on product and portfolio level decisions, strategic alignment, value-based requirements selection, and value-based process improvement.

This thesis deals with software process improvement based on the deployment package Software testing, which is a guide for implementation of testing related processes of the international standard ISO/IEC 29110 Life-Cycle Profiles for Very Small Entities. The aim of this thesis is localization of the deployment package Software testing into Czech and realization of the pilot project based on this package on the real software project in a very small enterprise. Another aim is to evaluate the deployment package and to propose modifications to improve it. The real benefit of this thesis is in realization of the pilot project itself, which resulted in testing process improvement in the enterprise. Another expected benefits of this thesis based on its goals are in actual localization of the deployment package into Czech, its evaluation and suggestion of its modifications. Thesis as a whole can be used as a guide and information source for other enterprises seeking an improvement of the testing process as it provides an example of the deployment package Software testing implementation and also theoretical introduction to testing and software process improvement in a small enterprise.