Submitted by Geyciane Santos (geyciane_thamires@hotmail.com) on 2015-06-17T13:56:44Z No. of bitstreams: 1 Dissertação - Odette Mestrinho Passos.pdf: 11444583 bytes, checksum: 1032441dc74adfa6d647e80d33de3c6d (MD5) / Approved for entry into archive by Divisão de Documentação/BC Biblioteca Central (ddbc@ufam.edu.br) on 2015-06-17T20:05:23Z (GMT) No. of bitstreams: 1 Dissertação - Odette Mestrinho Passos.pdf: 11444583 bytes, checksum: 1032441dc74adfa6d647e80d33de3c6d (MD5) / Made available in DSpace on 2015-06-17T20:05:23Z (GMT). No. of bitstreams: 1 Dissertação - Odette Mestrinho Passos.pdf: 11444583 bytes, checksum: 1032441dc74adfa6d647e80d33de3c6d (MD5) Previous issue date: 2014-04-28 / Organizational culture is one of the most important success factors of an organization because it provides both the supporting background and the strategic direction. In the context of software organizations, organizational culture has been observed in scientific research as one of the critical factors for successful implementation of software process improvement initiatives. Therefore, it is important to analyze the impact of organizational culture on the adoption/ implementation of these initiatives. Thus, the scientific methodology adopted to conduct this research was based on secondary and primary studies. Firstly, this work identified several typological models for the analysis of organizational culture and extracted the key organizational values that comprise the selected typological models. From the results, we carried out a survey on which organizational values are important to define the organizational culture of a software organization, and the level of importance of each value to a software organization that is involved in an initiative for software process improvement. In this research, we also identified recommendations for improvement, based on organizational culture, in the context of software process improvement initiatives. Nonetheless, a new survey, conducted with experts on software process improvement, was performed to relate these recommendations for improvement with the identified organizational values. From the results obtained in these studies, we developed a conceptual framework that based on the analysis of organizational culture (through organizational values) obtained from a software organization, suggests recommendations for improvement that can be implemented in the organization aiming at positively supporting the implementation of software process improvement initiatives. Finally, to evaluate the proposed framework, we conducted a qualitative investigation with appraisers and consultants of software process improvement initiatives. The results suggest that the proposed framework contributes to understanding software organization organizational values and implementing software process improvement initiatives. / A cultura organizacional é um dos fatores mais importantes para o sucesso de uma organização, pois provê tanto as bases de sustentação quanto os rumos estratégicos. No contexto de organizações de software, a cultura organizacional tem sido observada em pesquisas científicas como sendo um dos fatores críticos para o sucesso da implementação de iniciativas de melhoria de processo de software. Diante disso, é importante analisar o impacto da cultura organizacional na adoção/implementação dessas iniciativas. Para tanto, a metodologia científica adotada para o desenvolvimento desta pesquisa foi baseada em estudos secundários e primários. Primeiramente, este trabalho identificou diversos modelos de tipologias para análise da cultura organizacional e extraiu os principais valores organizacionais abordados por cada um dos modelos selecionados. A partir dos resultados, foi realizada uma pesquisa de opinião sobre quais valores organizacionais são importantes para definir a cultura organizacional de uma organização de software e o nível de relevância de cada valor para uma organização que esteja envolvida com uma iniciativa de melhoria de processo de software. Além disso, foram identificadas recomendações de melhoria, baseadas na cultura organizacional, que estão contextualizadas com iniciativas de melhoria de processo de software. Não obstante, uma nova pesquisa de opinião, com especialistas em melhoria de processo de software, foi realizada para relacionar essas recomendações de melhorias com os valores organizacionais identificados. Com os resultados destes estudos, foi desenvolvido um framework conceitual que a partir da análise da cultura organizacional (através dos valores organizacionais) de uma organização de software, sugira recomendações de melhoria que podem ser implantadas nesta com o intuito de apoiar positivamente as implementações de iniciativas de melhoria de processo de software. Por fim, para avaliar o framework proposto, foi conduzida uma investigação qualitativa com avaliadores e consultores de iniciativas de melhoria de processo de software brasileiros. Os resultados indicam que o framework é pertinente para auxiliar a organização no entendimento dos valores organizacionais e no auxílio a implementação de iniciativas de melhoria de processo de software.

Orientador: Mario Jino / Tese (doutorado) - Universidade Estadual de Campinas, Faculdade de Engenharia Eletrica e de Computação / Made available in DSpace on 2018-08-06T08:05:26Z (GMT). No. of bitstreams: 1 Salviano_ClenioFigueiredo_D.pdf: 2111618 bytes, checksum: 1da963de455fd0587fbfd55071cd1d0f (MD5) Previous issue date: 2006 / Resumo: Melhoria de processo de software baseada nos níveis de maturidade fixos da arquitetura estagiada dos modelos SW-CMM e CMMI não atendem à diversidade de contextos e objetivos estratégicos das organizações intensivas em software. Esta pesquisa evoluí a área de melhoria de processo com a utilização da flexibilidade da arquitetura contínua da ISO/IEC 15504 para um melhor alinhamento da melhoria com o contexto e objetivos estratégicos específicos de cada organização, principalmente as micro e pequenas. São identificadas três gerações de arquiteturas de modelos de capacidade de processo (estagiada fixa, contínua fechada e contínua aberta). É proposta uma engenharia de processo, de software e de qualquer outro trabalho humano intensivo em conhecimento, dirigida por perfis de capacidade de processo. É desenvolvida uma abordagem exemplo dessa engenharia com um conjunto de propriedades, um modelo unificado, um ciclo de melhoria e um conjunto de medições, bem como um método para o estabelecimento de perfis de capacidade de processo. As propostas são validadas com análises, aplicações práticas e uma agenda de pesquisa / Abstract: Software process improvement based on the staged architecture¿s fixed maturity levels of SWCMM and CMMI models do not support the diversity of software intensive organizations context and strategic objectives. This research evolves the current process improvement area taking advantage of the flexibility of ISO/IEC 15504 continuous architecture towards a better alignment between an improvement with each organization¿s specific context and strategic objectives, especially of micro and small ones. Three generations of architectures for process capability models (fixed staged, closed continuous, open continuous) are identified. A process capability profile driven, software and any other knowledge intensive human work, process engineering is proposed. An exemplar approach for this engineering is developed, with a set of properties, a unified model, an improvement cycle and a measurement set, as well as a method for establishing process capability profile. These proposals are validated by analyses, practical applications and a research agenda / Doutorado / Engenharia de Computação / Doutor em Engenharia Elétrica

Almost everybody in the software engineering world has read about or has heard of the importance and benefits of the mature software process. This master thesis aims to answer the question why despite all the efforts; software organizations still have difficulties to achieve the mature and effective software process. The results of the literature survey and a case study performed at a real software company have shown that there is a set of factors that may cause process inefficiency in the software companies. These factors are connected with the soft aspects of the software process such as motivation of the software engineers, process understanding and the process training. / Vad är orsakerna till att programvaruföretagen har svårt att uppnå en mogen och effektiv utvecklingsprocess? Resultatet efter en fallstudie och en literaturundersökning visar att det finns ett antal faktorer som påverkar effektiviteten på processen. / Nina Dzamashvili Övre Brunnsvägen 46, SE-372 36 RONNEBY Sweden E-mail: nina.dzamashvili@bth.se

This master thesis describes our work with Team Sweden and how we have attempted to perform a Software Process Improvement using groupware. Team Sweden is a distributed academic software development organization doing research on artificial intelligence and robotics. Such an organization has a lot to gain from the introduction of a more structured process model. We have investigated the possibility of supporting the development processes of a small software development organization by introducing groupware. Only introducing a groupware tool or technique is not enough to improve the processes of an organization. Process improvement requires an infrastructure and groupware could be a useful tool for establishing it. Improved communication and knowledge sharing through groupware can be beneficial for establishing a process infrastructure. Groupware should be used in conjunction with other process improvement measures in order to be effective and improve the capability of the targeted organization. / This master thesis describes our work with Team Sweden and how we have attempted to perform a Software Process Improvement using groupware. / gustav@nordenskjold.com hakingma@hotmail.com

Melhoria de processo de software (SPI) é uma prática de engenharia de software motivada pela necessidade de aumentar a qualidade e a produtividade no desenvolvimento de software. Um fato amplamente reconhecido é que a qualidade do produto de software pode ser, em grande parte, determinada pela qualidade do processo utilizado para desenvolvê-lo e mantê-lo. A avaliação do processo de software ajuda as organizações de software a amadurecerem seus processos, identificando problemas críticos para estabelecer prioridades de melhoria. Essa avaliação pode ser feita por meio da comparação do estado dos processos da organização em relação a um modelo de referência que estabeleça estágios de melhoria. Uma avaliação geralmente se baseia em um modelo de processo de software que fornece um roteiro para melhorias. Este trabalho tem como objetivo estabelecer uma abordagem que: (i) define um conjunto de modelos de abstração (metamodelos) de modelos de maturidade de processo de software para apoiar uma metodologia de avaliação/melhoria de processo de software com o objetivo de certificação; e (ii) permite avaliar os processos de uma organização em comparação com um modelo de maturidade por meio de transformações desses metamodelos. A abordagem é instanciada por meio de um estudo de caso utilizando os modelos MPS.Br e CMMI para exemplificar sua aplicação. Como resultado, é apresentado um comparativo entre as limitações encontradas nas metodologias encontradas na literatura e como a abordagem sugere superá-las. / Software process improvement (SPI) is a software engineering practice motivated by the need to increase the quality and productivity in software development. A fact widely recognized is that the quality of the software product can be largely determined by the quality of the process used to develop and maintain it. The assessment of software process helps software organizations to improve themselves, identifying their critical problems to establish priorities for improvement. This assessment can take place by comparing the state of the organization on their software processes to a reference model that shows stages of improvement in scales. An assessment is usually based on a software process model that provides a roadmap for improvement. This work aims to establish an approach that: (i) defines a set of abstraction models (metamodels) of software process maturity models to support an assessment/improvement methodology aiming software process certification; and (ii) evaluates the organization processes in comparison with the maturity models through transformations of those metamodels. The approach is instantiated through a case study using the MPS.Br and CMMI models to illustrate its application. As a result, a comparison between the limitations found in the methodologies identified in the literature and how the approach suggested overcome them is presented.

The need for information systems has increased to a point where virtually all business environments require some sort of software to aid in its daily operations. This study will address the need for quality information systems by examining techniques which can potentially aid in producing consistent high-quality information systems. Two techniques in particular, namely Process Maturity Models (PMMs) and Systems Development Methodologies (SDMs) are examined. Process Maturity Models such as the Capability Maturity Model Integration (CMMI) as well as the ISO-9000 standards aid in standardising and improving an organisation’s information systems development processes. These Process Maturity Models often require either the use of certain Systems Development Methodologies or at the very least techniques used within some Systems Development Methodologies. Systems Development Methodologies refer to a set of development processes, tools, techniques etc. which can be used during software development to standardise the entire development process by offering the use of modelling techniques, tools to analyse requirements, illustration of processes etc. These techniques differ from one Systems Development Methodology to the next. This study aims to identify the relationship between Process Maturity Models and Systems Development Methodologies. During the research process a questionnaire was sent out to people within the information technology business environment. The questionnaire contained questions used to determine and measure the usage of Systems Development Methodologies and how projects were affected. The questionnaire was also used to do an informal assessment of each respondent’s Capability Maturity Model level. Furthermore the data retrieved was statistically analysed and the results were interpreted. The results indicate that a relationship exists between the use of SDMs and the success of the respondent’s development processes and developed products. A total of 73% of respondents indicated that they do use SDMs to some extent, the most common being the Systems Development Lifecycle (SDLC). The majority of organizations implementing SDMs have been doing so for three years or more. Results also show that most of the respondents are not certified in some formal Process Maturity Model; however, they do implement some of the processes required by models such as the CMMI. An informal assessment performed indicated that 65% of respondents can be grouped into a perceived CMMI level 2 category. Project outcome was measured and the relationship between PMM implementation as well as SDM use was measured. Results show no statistical evidence which indicates that an organisation’s perceived CMMI level is influenced by SDM use, both vertically and horizontally. Results do, however, indicate that organizations which have been implementing SDMs for a longer period of time are more likely to apply CMMI level 4 activities. Results also indicate that the horizontal use (number of projects/people which implement SDM knowledge) of SDMs have a significant effect on the development process- and the developed product success. Lastly the results indicated that organizations which satisfy more of the CMMI’s level 4 activities experience a higher quality development process which leads to a more successful development process. / Thesis (MSc (Computer Science))--North-West University, Potchefstroom Campus, 2013.

The need for information systems has increased to a point where virtually all business environments require some sort of software to aid in its daily operations. This study will address the need for quality information systems by examining techniques which can potentially aid in producing consistent high-quality information systems. Two techniques in particular, namely Process Maturity Models (PMMs) and Systems Development Methodologies (SDMs) are examined. Process Maturity Models such as the Capability Maturity Model Integration (CMMI) as well as the ISO-9000 standards aid in standardising and improving an organisation’s information systems development processes. These Process Maturity Models often require either the use of certain Systems Development Methodologies or at the very least techniques used within some Systems Development Methodologies. Systems Development Methodologies refer to a set of development processes, tools, techniques etc. which can be used during software development to standardise the entire development process by offering the use of modelling techniques, tools to analyse requirements, illustration of processes etc. These techniques differ from one Systems Development Methodology to the next. This study aims to identify the relationship between Process Maturity Models and Systems Development Methodologies. During the research process a questionnaire was sent out to people within the information technology business environment. The questionnaire contained questions used to determine and measure the usage of Systems Development Methodologies and how projects were affected. The questionnaire was also used to do an informal assessment of each respondent’s Capability Maturity Model level. Furthermore the data retrieved was statistically analysed and the results were interpreted. The results indicate that a relationship exists between the use of SDMs and the success of the respondent’s development processes and developed products. A total of 73% of respondents indicated that they do use SDMs to some extent, the most common being the Systems Development Lifecycle (SDLC). The majority of organizations implementing SDMs have been doing so for three years or more. Results also show that most of the respondents are not certified in some formal Process Maturity Model; however, they do implement some of the processes required by models such as the CMMI. An informal assessment performed indicated that 65% of respondents can be grouped into a perceived CMMI level 2 category. Project outcome was measured and the relationship between PMM implementation as well as SDM use was measured. Results show no statistical evidence which indicates that an organisation’s perceived CMMI level is influenced by SDM use, both vertically and horizontally. Results do, however, indicate that organizations which have been implementing SDMs for a longer period of time are more likely to apply CMMI level 4 activities. Results also indicate that the horizontal use (number of projects/people which implement SDM knowledge) of SDMs have a significant effect on the development process- and the developed product success. Lastly the results indicated that organizations which satisfy more of the CMMI’s level 4 activities experience a higher quality development process which leads to a more successful development process. / Thesis (MSc (Computer Science))--North-West University, Potchefstroom Campus, 2013.

Made available in DSpace on 2016-12-23T14:33:41Z (GMT). No. of bitstreams: 1 Dissertacao - Rodrigo Dal Moro.pdf: 1536766 bytes, checksum: ef4c5c439d91453e44612d5a0f929887 (MD5) Previous issue date: 2008-07-16 / Given the complexity of the Software Process Improvement and Assessment (SPIA) process and its strong inter-relationship with other processes in the software life cycle, we must provide automated support for it. To help identifying functional requirements, we define a SPIA process adherent to MPS.BR quality model, with the goal of guiding the establishment of tools functionalities that are able to support a quality SPIA process. To establish a consensual vision of the SPIA area to be used as a basic conceptual model, we developed an ontology of software quality with a focus on SPIA. Finally, based on the ontology and the SPIA process defined, we developed two tools: AvaliaODE, responsible for supporting software products and process evaluation, and MelhoriaODE, responsible for supporting software process improvement. This work is inserted in the context of ODE Project, a process-centered software engineering environment that is developed based on ontologies. It aims to define a conceptual basis for automating the SPIA process. / Dada a complexidade do processo de Avaliação e Melhoria de Processos de Software (AMP) e a sua forte inter-relação com outros processos do ciclo de vida de software, é preciso prover apoio automatizado para ele. Para ajudar a identificar requisitos funcionais, definiu-se um processo de AMP aderente ao MPS.BR, com o objetivo de guiar o estabelecimento de funcionalidades das ferramentas capazes de apoiar um processo de AMP de qualidade. Para estabelecer uma visão consensual sobre o domínio de AMP, a ser usada como modelo conceitual base, foi desenvolvida uma ontologia de qualidade de software com foco em AMP. Por fim, tomando por base a ontologia e o processo de AMP definidos, foram desenvolvidas duas ferramentas: AvaliaODE, responsável pelo apoio à avaliação de processos e produtos de software, e MelhoriaODE, responsável pelo apoio à melhoria de processos de software. Este trabalho está inserido no contexto do Projeto ODE, um ambiente de desenvolvimento de software centrado em processo e baseado em ontologias, e tem por objetivo a definição de uma base conceitual para apoiar a automatização do processo de Avaliação e Melhoria de Processos de Software.

Made available in DSpace on 2014-07-29T14:57:52Z (GMT). No. of bitstreams: 1 Dissertacao Patricia Gomes Fernandes.pdf: 860832 bytes, checksum: 989c4ec02ea9287d4f1a913bdb14c251 (MD5) Previous issue date: 2010-04-09 / Many organizations are applying efforts to improve their software processes, in face of the premisse that states that the quality of the processes used to develop and maintain software has a major influence over the products generated. These efforts are typicaly in the form of software process improvement (SPI) initiatives, with the general objetive defining and/or improving software processes, as well as institutionalizing them. Nevertheless, once it involves changes in the way of work of organizations, SPI provokes changes in organizational culture, and is impacted by this culture. This is reflected in SPI literature, that presents organizational culture as a critical success factor in SPI implementation. The focus of this research is the investigation of the correlation between organizational culture and the effectiveness of SPI initiatives. In order to do this, two fundamental questions were considered: (a) how the culture of an organization can influence the degree of institutionalization of a defined/improved software process, and (b) what can be done to increase the degree of institutionalization of a defined/improved software process, once this institutionalization involves a cultural change. To accomplish this, a case study was conducted in two software organizations (where only one of them institutionalized its software process) with the purpose of analysing how their cultural profiles may have influenced in these different outcomes. It was also conducted a search to identify recommendations for cultural change in Organizational Culture literature. The application of these recommendations was evaluated in a comparative way in both organizations. Additionaly, a survey with SPI implementors was also made, in order to identify the degree of application of these recommendations in the organizations they have worked. With this research, cultural elements that may have relations whit software process institutionalization were identified, as well as recommendations that can derive actions to modify the elements that are considered resistance factor to the adoption of software processes defined/improved in SPI initiatives. / Diversas organizações têm aplicado esforços para melhorar seus processos de software, diante da premissa de que qualidade dos processos utilizados para desenvolver e manter software tem grande influência na qualidade dos produtos gerados. Estes esforços tipicamente tomam a forma de iniciativas de melhoria de processos de software (MPS), cujo objetivo geralmente é o de definir e/ou aprimorar processos de software, assim como institucionalizá-los. Todavia, por envolver mudanças no modo de trabalho das organizações, a MPS provoca mudanças na cultura organizacional, e sofre impacto desta cultura. Isto é refletido na literatura de MPS que apresenta a cultura organizacional como fator crítico de sucesso na implementação de MPS. O foco da presente pesquisa é investigar a correlação entre a cultura organizacional e a efetividade das iniciativas de MPS. Para isso foram consideradas duas questões fundamentais: (a) como a cultura de uma organização pode influenciar o grau de institucionalização de um processo de software definido/ melhorado, e (b) o que pode ser feito para aumentar o grau de institucionalização de um processo de software definido/melhorado, considerando que esta institucionalização envolve uma mudança cultural. Foi conduzido um estudo de caso em duas organizações de software (tendo apenas uma conseguido institucionalizar seu processo de software) para analisar como seus perfis culturais podem ter influenciado nestes diferentes resultados. Também foi feito um levantamento de recomendações para mudança cultural na literatura de Cultura Organizacional, cuja aplicação também pôde ser avaliada de forma comparativa nas duas organizações citadas. Além disso, foi conduzida uma pesquisa de opinião com implementadores de melhoria de processos sobre a aplicação destas recomendações nas organizações em que já atuaram. Com isto, foram identificados elementos culturais que podem ter relação com a institucionalização de processos de software, assim como recomendações sobre ações que podem modificar elementos que atuam como fatores de resistência à adoção de processos definidos/melhorados em iniciativas de MPS.

Melhoria de processo de software (SPI) é uma prática de engenharia de software motivada pela necessidade de aumentar a qualidade e a produtividade no desenvolvimento de software. Um fato amplamente reconhecido é que a qualidade do produto de software pode ser, em grande parte, determinada pela qualidade do processo utilizado para desenvolvê-lo e mantê-lo. A avaliação do processo de software ajuda as organizações de software a amadurecerem seus processos, identificando problemas críticos para estabelecer prioridades de melhoria. Essa avaliação pode ser feita por meio da comparação do estado dos processos da organização em relação a um modelo de referência que estabeleça estágios de melhoria. Uma avaliação geralmente se baseia em um modelo de processo de software que fornece um roteiro para melhorias. Este trabalho tem como objetivo estabelecer uma abordagem que: (i) define um conjunto de modelos de abstração (metamodelos) de modelos de maturidade de processo de software para apoiar uma metodologia de avaliação/melhoria de processo de software com o objetivo de certificação; e (ii) permite avaliar os processos de uma organização em comparação com um modelo de maturidade por meio de transformações desses metamodelos. A abordagem é instanciada por meio de um estudo de caso utilizando os modelos MPS.Br e CMMI para exemplificar sua aplicação. Como resultado, é apresentado um comparativo entre as limitações encontradas nas metodologias encontradas na literatura e como a abordagem sugere superá-las. / Software process improvement (SPI) is a software engineering practice motivated by the need to increase the quality and productivity in software development. A fact widely recognized is that the quality of the software product can be largely determined by the quality of the process used to develop and maintain it. The assessment of software process helps software organizations to improve themselves, identifying their critical problems to establish priorities for improvement. This assessment can take place by comparing the state of the organization on their software processes to a reference model that shows stages of improvement in scales. An assessment is usually based on a software process model that provides a roadmap for improvement. This work aims to establish an approach that: (i) defines a set of abstraction models (metamodels) of software process maturity models to support an assessment/improvement methodology aiming software process certification; and (ii) evaluates the organization processes in comparison with the maturity models through transformations of those metamodels. The approach is instantiated through a case study using the MPS.Br and CMMI models to illustrate its application. As a result, a comparison between the limitations found in the methodologies identified in the literature and how the approach suggested overcome them is presented.