Abstract in English / Software project management has been less effective as a result of being focused on resource management and the completion of projects within allocated resources and other confines. There has not been much focus on improving software project management quality through improved decision-making, software project management standards and methodologies, hence the focus of this study to explore the possibility of using data analytics with project management standards and methodologies to improve software project management quality. The main question to be addressed in this study is: Can data analytics use in software project management improve decision-making and project management quality? This study, therefore, explores and provides insight on data analytics use, by means of a survey that was completed by software project managers. A questionnaire was used to collect data from software project managers. The gathered data was captured and analysed using the Statistical Package for the Social Sciences (SPSS), and the analysed data was used for validity testing, while the reliability of the measurement items was tested using Cronbach’s Alpha. A hypothesis was used to evaluate the effect of data analytics use on software project management quality. The research made use of the positivist research method. The study established that data analytics has not yet been widely adopted by software project managers and organisations alike, as both the project managers and organisations have not done enough to promote the training in, and the adoption of data analytics. The research also established that data analytics can improve software project management quality through improved decision-making and in complementing software project management standards. The study findings will be beneficial to software project managers, researchers and organisations as it reveals the factors that are necessary to effectively use data analytics in software project management, as well as highlighting how data analytics improves software project management quality / School of Computing / M.Sc. (Computing)

The aim of the thesis was to design and develop a unified application for installation and integration of the software management tools into a single comprehensive and functional unit. The application should also allow export of the project metadata via the RESTful API. The goals of the thesis were fulfilled relatively well. A set of installation scripts was created, as well as a functional web application built using the JavaEE platform. The application can be deployed in a small company after performing minor modifications. Less common deployment scenarios for CGI based applications on Apache Tomcat were also examined. Minor enhancements in the open-source project NetBeans were implemented as well. Also, a branded version of Bugzilla was created and deployed in an existing small software company.

Metric collection process and Project Management activities cannot be performed in an integrated fashion on most of the software projects. In software engineering world, there are Project Management Tools that has embedded project metrics and there are various Metric Collection Tools that collect specific metrics for satisfying requirements of different software life cycle phase activities (Configuration Management, Requirements Management, Application Development tools etc.). These tools however are not communicating with each other with any interface or any common database. This thesis focuses on the development of a tool to define, export, collect and use metrics for software project planning, tracking and oversight processes. To satisfy these objectives, POMMES with functionalities of Generic Metric Definition, Collection, Analysis, and Import, Update and Export of Project Metrics from 3rd Party Project Management Tools is developed and implemented in a software organization during this thesis work.

While software subcontracting is a common business transaction in the information technology field, metrics specifically aimed at effectiveness of software subcontracting arrangements are not commonly available. This thesis makes a review of the literature and derives such metrics from fields of software quality, COTS acquisition and IS success. A case study is performed on software subcontracting projects of a Turkish defense contractor, and the project metrics are compared according to their success. The results suggest that metrics regarding the requirements are good indicators for subcontracting success and that larger projects may enjoy more success compared to smaller ones.

Submitted by Johnny Rodrigues (johnnyrodrigues@ufcg.edu.br) on 2018-06-12T16:16:04Z No. of bitstreams: 1 RICARDO DE SOUSA JOB - DISSERTAÇÃO PPGCC 2014..pdf: 17381707 bytes, checksum: e786d3893958cbeb0121a19fae52628c (MD5) / Made available in DSpace on 2018-06-12T16:16:04Z (GMT). No. of bitstreams: 1 RICARDO DE SOUSA JOB - DISSERTAÇÃO PPGCC 2014..pdf: 17381707 bytes, checksum: e786d3893958cbeb0121a19fae52628c (MD5) Previous issue date: 2014-12-05 / Capes / Padrões de Projeto são soluções consolidadas para problemas de projeto de software recorrentes. São utilizados amplamente em projetos de software orientados a objetos, tornando-se um artifício de comunicação de soluções conhecidas dentro das equipes de desenvolvimento. É importante que o projetista consiga detectar e identificar os padrões de projetos numa base de código, para compreender as relações entre as classes, como fornecer sugestões úteis para a compreensão e evolução do sistema. Para detecção automática de padrões existem basicamente duas técnicas: análise estática e dinâmica. No primeiro passo, as relações e colaborações estruturais são extraídas. Já no segundo passo monitora-se a execução do programa, rastreando o conjunto de padrões selecionados no passo anterior para identificar quais padrões comportam-se como o esperado. As técnicas de detecção atuais, no entanto, limitam-se a análises estruturais restritivas, omitindo casos em que o comportamento de um padrão está presente, mesmo que não siga a organização estrutural prevista na literatura. Chamamos de padrões emergentes estes casos em que o comportamento de um determinado padrão está presente, mesmo que certa região do código apresente estruturação livre. Por exemplo, a essência do padrão de projeto Singleton está presente em uma classe qualquer quando esta possui apenas uma única instância durante as execuções de um programa, mesmo que não haja restrição sintática para que isso seja possível; ou seja, o padrão Singleton emerge deste comportamento de um determinado elemento do programa. Ao auxiliar o desenvolvedor na detecção de situações de projeto como esta, pode-se enriquecer o seu conhecimento sobre as consequências de suas decisões, além de propiciar a estruturação explícita do padrão como conhecida, facilitando assim a documentação e comunicação do projeto. Este trabalho explora o conceito de padrões emergentes através das seguintes contribuições: (i) uma revisão sistemática sobre abordagens automáticas de detecção de padrões de projeto, (ii) conceitos de padrões emergentes para vários padrões de projeto bem conhecidos, (iii) uma proposta de abordagem semi-automática de detecção de padrões emergentes e (iv) sua utilização para uma análise de ferramentas de detecção existente acerca de sua capacidade de identificação de padrões emergentes em alguns projetos de código aberto Java. / Design Patterns are Consolidated solutions to recurring software design problems. They are widely used in object-oriented software design, as communication device of well known solutions within development teams. It is important that the software designer detects and identifies design patterns in a code base, to understand the relationships between classes, provide useful suggestions for the understanding and evolution of the system. For automatic detection of patterns there are basically two techniques: static and dynamic analysis. On the first step, relations and structural collaborations are extracted. In the second step, the program execution is monitored, tracking the selected set of patterns in the first step to identify which patterns behave as expected. However, the current detection techniques are limited to restrictive structural analysis, omitting cases where the behavior of a pattem is presente, even if not follow the structural organization provided in the literature. We call emerging patterns when the behavior of a given pattern is present, even if some code's region presents a free structure. For example, the essence of the Singleton design pattern is present in any given class when it has only a single instance during the execution of a program, even without syntactic restriction for this to be possible; that is, the Singleton pattern emerged from this program element behavior. When developers are assisted in detecting design situations like this, they can enhance their knowledge about the consequences of their decisions, as well as providing the explicit structure of the pattern, facilitating the documentation and communication of the project. This paper explores the concept of emerging patterns through the following contributions: (i) a systematic review of automatic detection approaches of design patterns, (ii) concepts of emerging patterns for several well-known design patterns, (iii) a proposal for semi-automatic detection approach of emerging patterns and (iv) its use for an analysis of existing detection tools about tíieir ability to identify emerging patterns in an open-source Java project

Background. Management is an essential factor in any organization let alone its kind and size. Project management is the art and science of planning and implementing a project to achieve the desired outcome. Project Management (PM) plays a crucial role in businesses which are bound to function in a team-based environment regardless of the type of business. Although a variety of project management practices are employed in different kinds of industries, it is well understood that the style and level of employment of these project management practices have a significant impact on the project success. The software engineering industry has its own project management practices and the employment of these practices depends on the project manager who thus plays a key role in project management. Project manager has been a ubiquitous feature of traditional software projects. Project managers are a merger of personal characteristics and areas of competency that act together to integrate the various components of a project. In this study, the author discusses about the concept of software engineering management, various characteristics and key competencies of a project manager and also the factors influencing the overall success of a project. The authors also discuss about the current state and importance of PM education and its influence in the real time industry. Objectives. This research study is to analyze and make conclusions about the ideal features of a project manager and therefore attempt to understand its association with critical factors of PM for a project’s success in terms of delivering the product as scheduled and also understand various non-PM factors that are critical for project success. The study also attempts to show the significance of studying PM specifically in the context of Software Engineering as different from other contexts and the importance of PM education in academics and teaching PM in the industry. Methods. To achieve the objectives of this research, we attempt to study project management in the context of Software Engineering by conducting a literature review followed with a descriptive Survey as our research methods for this study to show how far literature complies to the present-day views and overall form a common opinion on this subject by comparing both the findings. Results. The results yielded by conducting a literature review conclude that Project Management or Software Engineering Management plays a vital role in software projects. Various factors that contribute towards successful project management were identified. Also, relevant literature was reviewed to identify the characteristics and competencies of an effective project manager and the status of project management education in academics and in the software engineering industry. The results obtained from the literature review were used in designing a survey and were further used to compare with and validate the results of this survey. A thorough analysis of these results yielded in capturing the current status and views with a snapshot of the situation in the present Software Engineering industry. A clear view on the subject area and results from a sample population of 73 software engineering professionals consisting of up to 41 experienced managers were analyzed, commented and documented. Conclusions. Various conclusions were drawn including discussions on the compliances and contradictions between present literature and software professionals in the present industry have been made. It was found that the majority of software professionals believe that project management in software engineering is unique from project management in other disciplines. It was found that professionals believe project management to be highly to very highly crucial for the overall success of software projects and that the most important key factors for successful project management were team motivation, communication and risk management. It was found that ‘Ability to foresee a problem’, ‘Decision making’ and ‘Inspires a shared vision’ were among the top three characteristics and ‘Team management’, ‘Leadership’ and ‘Ability to work under pressure’ were among the top three competencies of an effective project manager. It was found that managers feel the need to be taught about project management standards and that the ‘PMBoK’ and ‘ISO 9001’ were the most popular standards implemented. It was found that there are very contrasting views among companies on training project managers before promoting them to managerial positions whereas managers expect to be trained. Keywords: Software Engineering Management, Software Project Management, Project Manager, Project Success, Project Management Education, Software Engineering.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2017-04-19T14:49:21Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) TeseDoutorado_JoseAdsonOliveiraGuedesCunha_CInUFPE_vFinal.pdf: 2184943 bytes, checksum: 928987ce07e4113b3596a20086cbc4c7 (MD5) / Made available in DSpace on 2017-04-19T14:49:21Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) TeseDoutorado_JoseAdsonOliveiraGuedesCunha_CInUFPE_vFinal.pdf: 2184943 bytes, checksum: 928987ce07e4113b3596a20086cbc4c7 (MD5) Previous issue date: 2016-09-15 / Background: In software project management, the decision-making process is a complex set of tasks mainly based on human relations, individual knowledge, and cultural background. The factors that affect the decisions of Software Project Managers (SPMs), as well as their potential consequences, require attention because project delays and failures might be related to a series of poor decisions. Aims: To understand how SPMs make decisions based on how they interpret their experiences in the workplace. Further, to identify antecedents, moderators and consequences of those decisions to increase the effectiveness of project management. Method: Firstly, an exploratory study based on semi-structured interviews was conducted with SPMs from a large Brazilian governmental organization and from a small Portuguese private organization to shed light on the causal factors of SPMs’ cognitive biases and how they deal with them, including techniques and tools they used to minimize the cognitive biases’ adverse effects. The initial findings suggested that we needed a more grounded understanding of the mechanisms of decision-making. Thus, a broader research protocol based on semi-structured interviews was carried out with SPMs within a large Brazilian governmental organization and a large Brazilian private organization. We also conducted interviews with software engineers and PMO managers to triangulate the data, which was analyzed using techniques from grounded theory. Data from observations, document analysis and selected studies from a systematic literature review were also used. Results: We found that decision-making in software project management is based on knowledge sharing in which the SPM acts as a facilitator. This phenomenon is influenced by individual factors, such as experience, knowledge, leadership style, and skills, and by situational factors such as the autonomy of the SPM, task complexity and team members' technical competence. Conclusions: Due to the uncertainty and dynamism inherent to software projects, the SPMs focus on making, monitoring and adjusting decisions in na argument-driven way. Also, the involvement of the team members in decision-making aims to minimize the SPM's decision regret and cognitive biases as well as to maximize the team member's commitment. / Contexto: No gerenciamento de projetos de software, o processo de tomada de decisão refere-se a um conjunto complexo de tarefas baseadas, principalmente, nas relações humanas e no conhecimento e background de cada indivíduo. Os fatores que afetam as decisões dos gerentes de projeto de software (GPs), bem como as suas consequências potenciais necessitam de atenção uma vez que atrasos e falhas de projeto estão relacionados a uma série de más decisões. Objetivos: Entender como os GPs tomam decisões com base em como eles interpretam suas experiências no ambiente de trabalho. Além disso, pretende-se identificar os antecedentes, moderadores e consequências dessas decisões para aumentar a eficácia no gerenciamento de projetos. Método: Primeiramente foi realizado um estudo exploratório com base em entrevistas semi-estruturadas com GPs de uma organização governamental brasileira de grande porte e de uma organização privada portuguesa de pequeno porte para analisar os fatores causais dos vieses cognitivos dos GPs e como estes lidam com eles, incluindo técnicas e as ferramentas utilizadas para minimizar os efeitos adversos dos vieses cognitivos. Os resultados iniciais sugeriram uma compreensão mais fundamentada dos mecanismos de tomada de decisão. Dessa forma, um protocolo mais amplo de pesquisa baseado em entrevistas semi-estruturadas foi realizado com GPs de uma organização governamental e de uma organização privada, ambas brasileiras e de grande porte. Foram realizadas entrevistas com engenheiros de software e gerentes de escritório de projetos para triangular os dados, que foram analisados usando técnicas de teoria fundamentada. Também foram utilizados dados de observações, análise de documentos e estudos selecionados a partir de uma revisão sistemática da literatura. Resultados: Verificou-se que a tomada de decisão no gerenciamento de projetos de software é baseada no compartilhamento de conhecimento em que o gerente de projetos de software atua como um facilitador. Este fenômeno é influenciado por fatores individuais, como experiência, conhecimento, estilo de liderança, e habilidades, e por fatores situacionais, tais como a autonomia, complexidade da tarefa, e competência técnica dos membros de equipe. Conclusões: Devido à incerteza e dinamismo inerente aos projetos de software, os GPs concentram-se em agir, monitorar e ajustar as decisões com base em argumentos. Além disso, o envolvimento dos membros da equipe na tomada de decisão visa minimizar o arrependimento de decisões e influência de vieses cognitivos por parte dos GPs, bem como maximizar o comprometimento dos membros da equipe.

Submitted by Marcia Silva (marcia@latec.uff.br) on 2016-10-24T19:01:36Z No. of bitstreams: 1 Dissert Luiz Augusto Cescon Tavares.pdf: 2000584 bytes, checksum: 8a2e3d63b83415e6a821fa41e28059df (MD5) / Rejected by Biblioteca da Escola de Engenharia (bee@ndc.uff.br), reason: Favor incluir no trabalho a folha de rosto (elemento obrigatório), antes da ficha catalográfica. Atenciosamente, Catarina Ribeiro Bibliotecária BEE - Ramal 5992 on 2017-01-27T11:51:16Z (GMT) / Submitted by Marcia Silva (marcia@latec.uff.br) on 2017-02-08T17:38:28Z No. of bitstreams: 1 Dissert Luiz Augusto Cescon Tavares.pdf: 2000584 bytes, checksum: 8a2e3d63b83415e6a821fa41e28059df (MD5) / Rejected by Biblioteca da Escola de Engenharia (bee@ndc.uff.br), reason: Favor incluir no trabalho a folha de rosto (elemento obrigatório), antes da ficha catalográfica. Atenciosamente, Catarina Ribeiro Bibliotecária BEE - Ramal 5992 on 2017-02-15T12:03:25Z (GMT) / Submitted by Marcia Silva (marcia@latec.uff.br) on 2017-05-09T19:56:05Z No. of bitstreams: 1 Dissert Luiz Augusto Cescon Tavares.pdf: 2000584 bytes, checksum: 8a2e3d63b83415e6a821fa41e28059df (MD5) / Approved for entry into archive by Biblioteca da Escola de Engenharia (bee@ndc.uff.br) on 2017-05-15T12:09:26Z (GMT) No. of bitstreams: 1 Dissert Luiz Augusto Cescon Tavares.pdf: 2000584 bytes, checksum: 8a2e3d63b83415e6a821fa41e28059df (MD5) / Made available in DSpace on 2017-05-15T12:09:27Z (GMT). No. of bitstreams: 1 Dissert Luiz Augusto Cescon Tavares.pdf: 2000584 bytes, checksum: 8a2e3d63b83415e6a821fa41e28059df (MD5) Previous issue date: 2015-12-21 / Este estudo investiga o grau de utilização do framework SCRUM na empresa Dclick desenvolvimento de software LTDA, empresa nacional do setor de tecnologia da informação que foi estudada no ano de 2015. Com o objetivo geral de analisar por meio de um survey, o nível de utilização das ferramentas e técnicas ágeis em que os profissionais de desenvolvimento de software atuam em equipe na empresa descrita. A revisão da literatura foi efetuada entre os artigos selecionados como mais relevantes para o tema na base de dados da CAPES, o framework SCRUM foi exaustivamente estudado e também foram revisados os frameworks que tratam do assunto maturidade, o CMMI e o OPM3. A metodologia foi baseada na proposta de Gil (1999), e em um questionário que utiliza escala de Likert como referência, essas abordagens foram importantes para ajudar a listar as ferramentas e técnicas ágeis contidas no framework SCRUM de forma organizada gerando assim, as perguntas em um modelo fechado para que com esse questionário se possa aferir o seu grau de utilização e com isso, averiguar a maturidade e se ela contribuirá para o sucesso do gerenciamento de projetos de software / This study investigates the utilization of the SCRUM framework in the Dclick desenvolvimento de software company, a Brazilian company in the information technology sector that was studied in 2015. With the overall aim of identifying through a survey, the level of use the tools and techniques that agile software development professionals work as a team in the company described above. The literature review was conducted among the articles selected as most relevant to the topic in the CAPES database, the SCRUM framework has been thoroughly studied and were also reviewed the frameworks dealing with the subject maturity, CMMI and OPM3. The methodology was based on the proposal of Gil (1999), and a questionnaire using the Likert scale, Likert (1932) as a reference, these approaches were important in helping us to list and organize the tools and agile techniques contained in the framework SCRUM in an organized manner thus generating questions in a model closed so that with this questionnaire is to measure the degree of use and thereby ascertain the maturity and it will contribute to the successful management of software projects

The aim of this thesis is to determine possibilities and real use of project management tools in event management, in sphere built on project bases, but that is also very dynamic and changing even in realisation. The thesis focuses on software support for managing projects and project teams, that are applicable in event management. The research was made for the selection of optimal tool for realization of leasure time, public event Ladronkafest. Selection is based on multi-criteria decision evaluation process, that is implemented after consultation with professionals in event management. The chosen software was tested on some smaller event. During the test users realized some negatives about this program and decided not use it.

Background. Effort estimation is today a crucial part of software development planning. However, much of the earlier research has been focused on the general conditions of effort estimation. Little to no effort has been spent on solution verification (SV) of the projects. It is not surprising considering that SV becomes more relevant, the larger the project. To improve effort estimation, it is key to consider the uncertainties from the assumptions and conditions it relies on. Objectives. The main objective of this study is to identify differences and similarities between general effort estimation and effort estimation in SV in order to find potential improvements to software project planning of large projects. More specifically, this thesis aims to identify what and how activities and factors affect effort uncertainty and what theory and methods can be applied to increase the accuracy of effort estimation in SV. Methods. An exploratory case study was conducted to reach the objectives. It was designed accordingly to the triangulation method and consisted of unstructured interviews, a questionnaire, and archival research. The analysis followed a four steps procedure. First, it aimed to identify each SV activity’s contribution to effort and effort uncertainty. Secondly, identify and analyze which and how factors impact the identified activities. Third, investigate the factors that impact effort uncertainty. Fourth and last, an analysis of how the factors and sources of uncertainty could be used to improve software project planning. Results. The result shows that the activities could be divided into two different groups, based on their difference in contribution to effort and effort uncertainty. The two activities showing a higher uncertainty than effort were trouble report handling& troubleshooting, which is by far the most uncertainty-causing, and fault correction lead-time. The fault-related factors were both collectively and non-collectively found to be the most uncertainty-causing. Furthermore, it showed that the type of product and what type of objective the employee has influenced the cause of uncertainty. Conclusions. The SV process shifts from a proactive and structured way to a more reactive and unstructured way of working with the project life cycle. Moreover, size is not a cause of uncertainty of effort, but the differences in products create different causes. It was concluded that to most effectively address inaccuracy in effort estimation, one should address the activities that constitute a minority in effort but the majority of uncertainty. The most straightforward approach to increase the performance of effort estimation in SV would be to evaluate the inclusion of fault prediction and fault correction. Consequently, the implementation of uncertainty identification and prevention methods such as the six Ws framework and the bottom-up/top-down effort estimation practices. / Bakgrund. Ansträngningsuppskattning är idag en viktig del av planeringen avmjukvaruutveckling. Mycket av den tidigare forskningen har fokuserat på demgenerella förhållandena av ansträngningsuppskattning. Lite till ingen energi har lagts på lösningverifiering av projekten. Det är inte förvånande med tanke på lösningsverifiering (LV) blir mer relevant, desto större projekt. För att förbättra ansträngninguppskattningen så är det viktigt att ta hänsyn till dem osäkerheter som härstammar från dem antaganden och förhållanden som den vilar på. Syfte. Huvudmålet av studien är att identifiera likheter och skillnader mellan den generella teorin om ansträngninguppskattning gentemot ansträngninguppskattning inom LV i avsikt att identifiera potentiella förbättringar av mjukvaruutvecklings planering för större projekt. Mer specifikt, åsyftade studien till att identifiera vilka och hur aktiviteter och faktorer påverkar ansträngnings osäkerheter, samt vilken redan existerande teori och modeller som skulle kunna appliceras för att öka noggrannheten i ansträngninguppskattningen av lösningverifieringen. Metod. En utforskande fallstudie genomfördes för att uppfylla målen. Den designades i enlighet med trianguleringsmetoden och bestod av ostrukturerade intervjuer, ett frågeformulär, samt en arkivstudie. Analysen följde en procedur på fyra steg. Det första steget hade i avsikt att identifiera varje aktivitets, i LV proccessen, tillförande av ansträngning och osäkerhet. Det andra steget avsåg att identifiera och analysera vilka och hur faktorer påverkade dem identifierade aktiviteterna. Det tredje steget åsyftade att undersöka dem faktorer som påverkar ansträngningsosäkerheten. Och slutligen, det fjärde steget avsåg att analysera hur dem identifierade faktorerna och källorna till osäkerhet kan användas för att förbättra mjukvaruprojekts planering. Resultat. Resultatet visar att aktiviteterna kunde kategoriseras i två olika grupper baserat på differensen mellan ansträngningen och den relaterade osäkerheten. Dem två aktiviteter som visade en högre osäkerhet än ansträngning var felrapports hantering & felsökning, som visade sig orsaka mest osäkerhet, samt ledtid till följd av felkorrigering. De felrelaterade faktorerna var både självständigt och kollektivt dem som skapar mest osäkerhetsgrundande. Samtidigt visade det sig att typ av produkt och vilken typ av arbete influerade grunden till osäkerhet. Slutsatser. LV proccesen skiftar med projekt livscykeln, från en proaktiv och strukturerad process, till en mer reaktiv och ostrukturerad process. Storlek är inte en grund för osäkerhet av ansträngning, däremot skapar skillnader mellan produkterna olika osäkerhetsgrunder. För att på ett så effektivt sätt som möjligt adressera felaktigheter i ansträngningsuppskattningarna, bör fokus lika på dem aktiviteter som utgör en minoritet av ansträngning och samtidigt utgör en majoritet i osäkerhet. Den mest självklara tillvägagångssättet för att öka prestandan av anstängningsuppskatningarna av LV är att evaluera införandet av fel deterktering och fel korrektion i modelen. Följaktligen, att implementera osäkerhetsidentifications och förhindrande metoder, till exempel "the six Ws framework" och "bottom-up/top-down" ansträningningsuppskattnings metoderna.