To see the other types of publications on this topic, follow the link: Software Development Productivity.
Dissertations / Theses on the topic 'Software Development Productivity'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 26 dissertations / theses for your research on the topic 'Software Development Productivity.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Lipkin, Ilya. "Testing Software Development Project Productivity Model." University of Toledo / OhioLINK, 2011. http://rave.ohiolink.edu/etdc/view?acc_num=toledo1321593577.
Full text
2
Gupta, Shweta. "Software Development Productivity Metrics, Measurements and Implications." Thesis, University of Oregon, 2018. http://hdl.handle.net/1794/23816.
Full textAbstract:
The rapidly increasing capabilities and complexity of numerical software present a growing challenge to software development productivity. While many open source projects enable the community to share experiences, learn and collaborate; estimating individual developer productivity becomes more difficult as projects expand. In this work, we analyze some HPC software Git repositories with issue trackers and compute productivity metrics that can be used to better understand and potentially improve development processes. Evaluating productivity in these communities presents additional challenges because bug reports and feature requests are often done by using mailing lists instead of issue tracking, resulting in difficult-to-analyze unstructured data. For such data, we investigate automatic tag generation by using natural language processing techniques. We aim to produce metrics that help quantify productivity improvement or degradation over the projects lifetimes. We also provide an objective measurement of productivity based on the effort estimation for the developer's work.
3
AQUINO, JÚNIOR Gibeon Soares de. "Value-based productivity measurement in software development projects." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/1768.
Full textAbstract:
Made available in DSpace on 2014-06-12T15:52:15Z (GMT). No. of bitstreams: 2
arquivo3204_1.pdf: 2932974 bytes, checksum: ed70cb5e6dddd387ea04292de409a2f3 (MD5)
license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5)
Previous issue date: 2010<br>A fim de melhorar a sua competitividade no mercado global, as organizações de software
têm se preocupado cada vez mais com a questão de produtividade na execução de projetos.
No entanto, para melhorar a produtividade, as organizações de software devem definir
uma forma de medí-la. O problema é que a medição da produtividade apesar de parecer
ser simples, sua aplicação concreta se mostra muito complexa. Muitos são os trabalhos
de pesquisa sobre o tema, no entanto não há convergência sobre a métrica mais adequada
de produtividade para as organizações de software.
Baseado nos conceitos fundamentais relacionados à processos de produção, áreas de
conhecimento social, evidências coletadas em organizações de software reais e análise
do estado da arte em medição de produtividade em software, concluimos que a métrica
mais adequada para medir a produtividade é específica para cada contexto organizacional,
pois envolve estratégia, cultura organizacional, modus operandi, além de interesse e
conhecimento daqueles diretamente envolvidos na medição e avaliação da produtividade.
Isto explica porque não existe e nem há a possibilidade de existência de uma métrica de
produtividade para projetos de software universalmente aceita. Baseado nestas descobertas,
sugerimos a adoção de uma abordagem de medir produtividade baseada em valor. A
hipótese central que orienta nossa trabalho de pesquisa é que uma abordagem baseada
em valor pra medir a produtividade para medir a produtividade de projetos de software é
mais adequada que as medições tradicionais. Uma das consequências da validade desta
hipótese é que cada organização deve definir seu próprio modelo para a medição da
produtividade.
Com o objetivo de ajudar as organizações a definir e implementar um modelo próprio
de medição de produtividade, um processo sistemático, com uma seqüência bem definida
de etapas, entradas, saídas e diretrizes foi proposto. Ele envolve as atividades relacionadas
com a definição, implementação e aperfeiçoamento do modelo de medição de produtividade.
Além disso, foi baseado em uma extensa revisão dos principais desenvolvimentos
relacionados com a medição da produtividade, além de ser influenciado por modelos de
referência em engenharia de software, como IDEAL, CMMI, PSM e ISO/IEC 15939.
O resultado da aplicação deste processo em uma organização de software produz um
modelo de avaliação da produtividade, que considera a idéia de valor com base na visão
dos principais stakeholders da organização.
Finalmente, o conceito de medição de produtividade baseado em valor é adotado e
avaliado em um estudo de caso, envolvendo em uma organização real de desenvolvimento
de projetos de software. Em particular, o processo proposto para definição de modelos de medição de produtividade foi adotado e os benefícios, problemas e desafios foram
avaliados com o objetivo de avaliar a eficácia do processo em atendar a o seu propósito.
As análises do estudo de caso confirmaram que este tipo de abordagem foi de fato mais
adequada para a organização estudada e que potencialmente pode ser aplicado a outras
organizações de software
4
Tomaszewski, Piotr. "Software Development Productivity Issues in Large Telecommunication Applications." Licentiate thesis, Ronneby : Blekinge Institute of Technology, 2005. http://www.bth.se/fou/forskinfo.nsf/01f1d3898cbbd490c12568160037fb62/f7452f4c8d5c134ec125700d0048226b!OpenDocument.
Full text
5
Unlu, Cumhur. "The Effects Of Test Driven Development On Software Productivity And Software Quality." Master's thesis, METU, 2008. http://etd.lib.metu.edu.tr/upload/12609969/index.pdf.
Full textAbstract:
In the 1990s, software projects became larger in size and more complicated in structure. The traditional development processes were not able to answer the needs of these growing projects. Comprehensive documentation in traditional methodologies made processes slow and discouraged the developers. Testing, after all code is written, was time consuming, too costly and made error correction and debugging much harder. Fixing the code at the end of the project also affects the internal quality of the software. Agile software development processes evolved to bring quick solutions to these existing problems of the projects. Test Driven Development (TDD) is a technique, used in many agile methodologies, that suggests minimizing documentation, writing automated tests before implementing the code and frequently run tests to get immediate feedback. The aim is to increase software productivity by shortening error correction duration and increase software quality by providing rapid feedback to the developer. In this thesis work, a software project is developed with TDD and compared with a control project developed using traditional development techniques in terms of software productivity and software quality. In addition, TDD project is compared with an early work in terms of product quality. The benefits and the challenges of TDD are also investigated during the whole process.
6
Tomaszewski, Piotr. "Software development productivity : evaluation and improvement for large industrial projects /." Karlskrona : Blekinge Institute of Technology, 2006. http://www.bth.se/fou/Forskinfo.nsf/Sok/e09f2cffbbff3787c12571ca004b1232!OpenDocument.
Full text
7
Sousa, Kenia Soares. "UPi - a software development process aiming at usability, productivity and integration." Universidade de Fortaleza, 2005. http://dspace.unifor.br/handle/tede/71567.
Full textAbstract:
Made available in DSpace on 2019-04-05T23:05:13Z (GMT). No. of bitstreams: 0
Previous issue date: 2005-12-19<br>This dissertation proposes the Unified Process for Interactive Systems, called UPi, which
integrates practices from Software Engineering (SE) and Human-Computer Interaction (HCI)
with three main goals: usability, productivity, and integration. First, we intend to help
professionals from both areas in developing interactive systems with usability through the
application of a unified process. Second, we want to make HCI an essential and effective part
of SE processes by facilitating the communication and interchange of artifacts between
professionals from these two areas, thus, bringing productivity to a new working environment.
Third, we aim at describing the basis for generating User Interfaces (UI) through the
integration of HCI and SE concepts in a unified process and through the active participation
of users. In order to address the issues mentioned previously, we have defined and evaluated
the UPi and specified one artifact, the UI Definition Plan. To evaluate its efficacy, we applied
UPi in the Brazilian Digital TV Project, financed by the Brazilian Government. UPi was also
evaluated according to specific metrics to measure its Return on Investment and to monitor its
application and continuously improve it. The UI Definition Plan is an innovation for the
selection of usability patterns during UI design. UPi, the strategy to monitor its application
and evaluate the ROI, and the UI Definition Plan are our contributions for the SE and HCI
communities.<br>Essa dissertação propõe o Processo Unificado para Sistemas Interativos, chamados UPi, o qual integra práticas de Engenharia de Software (ES) e Interação Homem-Computator (IHC) com três objetivos principais: usabilidade, produtividade e integração. Primeiro, pretendemos ajudar profissionais de ambas as áreas no desenvolvimento de sistemas interativos com usabilidade através da aplicação de um processo unificado. Segundo, queremos tornar a IHC um componente essencial e efetivo de processos de ES, facilitando a comunicação e a troca de artefatos entre os profissionais das duas áreas, deste modo, trazendo produtividade para um novo ambiente de trabalho. Terceiro, pretendemos descrever o básico para gerar Interfaces de Usuário (IU) pela integração dos conceitos de IHC e ES em um processo unificado e pela participação ativa dos usuários. Para designar os assuntos mencionados anteriormente, definimos e avaliamos o UPi e especificamos um artefato: o plano de definição de IU. Para avaliar sua eficácia, aplicamos o UPi no projeto de TV digital brasileira, financiado pelo governo brasileiro. O UPi também foi avaliado de acordo com métricas específicas para medir seu Retorno de Investimento e para monitorar sua aplicação para melhorá-la continuamente. A definição do plano de IU é uma inovação para a seleção do padrão de usabilidade durante o projeto de IU. UPi, a estratégia de monitorar a aplicação e avaliar o ROI, e o plano de definição de IU são os nossos contribuintes para a comunidade de ES e IHC.
8
Dagfalk, Johanna, and Ellen Kyhle. "Listening in on Productivity : Applying the Four Key Metrics to measure productivity in a software development company." Thesis, Uppsala universitet, Avdelningen för datalogi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-440147.
Full textAbstract:
Software development is an area in which companies not only need to keep up with the latest technology, but they additionally need to continuously increase their productivity to stay competitive in the industry. One company currently facing these challenges is Storytel - one of the strongest players on the Swedish audiobook market - with about a fourth of all employees involved with software development, and a rapidly growing workforce. With the purpose of understanding how the Storytel Tech Department is performing, this thesis maps Storytel’s productivity defined through the Four Key Metrics - Deployment Frequency, Delivery Lead Time, Mean Time To Restore and Change Fail Rate. A classification is made into which performance category (Low, Medium, High, Elite) the Storytel Tech Department belongs to through a deep-dive into the raw system data existing at Storytel, mainly focusing on the case management system Jira. A survey of the Tech Department was conducted, to give insights into the connection between human and technical factors influencing productivity (categorized into Culture, Environment, and Process) and estimated productivity. Along with these data collections, interviews with Storytel employees were performed to gather further knowledge about the Tech Department, and to understand potential bottlenecks and obstacles. All Four Key Metrics could be determined based on raw system data, except the metric Mean Time To Restore which was complemented by survey estimates. The generalized findings of the Four Key Metrics conclude that Storytel can be minimally classified as a ‘medium’ performer. The factors, validated through factor analysis, found to have an impact on the Four Key Metrics were Generative Culture, Efficiency (Automation and Shared Responsibility) and Number of Projects. Lastly, the major bottlenecks found were related to Architecture, Automation, Time Fragmentation and Communication. The thesis contributes with interesting findings from an expanding, middle-sized, healthy company in the audiobook streaming industry - but the results can be beneficial for other software development companies to learn from as well. Performing a similar study with a greater sample size, and additionally enabling comparisons between teams, is suggested for future research.
9
Stone, Thomas W. "Lean Accounting Comes to Lean Software Development." Diss., Temple University Libraries, 2018. http://cdm16002.contentdm.oclc.org/cdm/ref/collection/p245801coll10/id/497799.
Full textAbstract:
Business Administration/Accounting<br>D.B.A.<br>I argue that lean software development firms become more productive if they adopt and align lean managerial accounting systems with lean software development processes. I conduct two experiments on retraining and coaching of software development teams that have used lean and agile software development practices, demonstrating that these practices significantly improve productivity compared to control groups that did not receive this retraining and coaching. In a third experiment, I expand on this theme by introducing lean accounting productivity metrics to a treatment group of software developers. Team leaders actively use these metrics as quantitative “retrospectives” in team meetings to review past performance and identify areas for process improvement. Four months after these metrics are introduced, I measure their impact on the treatment group productivity and also survey the group to determine how these metrics affect employee attitudes and productivity compared to a control group that was not trained in use of these metrics for team meetings. The results indicate that introduction of lean accounting metrics does not impact employee attitudes and understanding of processes and metrics, nor does it improve productivity in the near term. Discussions with management indicate that retraining and coaching immediately improve productivity since they are directed at remedying specific operational and process issues. Using lean accounting metrics to impact team productivity and employee attitudes is more foundational and likely requires a longer period of exposure and learning. The experimental site is a large publicly traded software firm that uses lean and agile software development practices. Key Words: Lean Accounting, Training, Coaching, Software Development, Productivity<br>Temple University--Theses
10
Brown, Mary Erin. "Data-Driven Decision Making as a Tool to Improve Software Development Productivity." Thesis, Walden University, 2013. http://pqdtopen.proquest.com/#viewpdf?dispub=3591716.
Full textAbstract:
<p> The worldwide software project failure rate, based on a survey of information technology software manager's view of user satisfaction, product quality, and staff productivity, is estimated to be between 24% and 36% and software project success has not kept pace with the advances in hardware. The problem addressed by this study was the limited information about software managers' experiences with data-driven decision making (DDD) in agile software organizations as a tool to improve software development productivity. The purpose of this phenomenological study was to explore how agile software managers view DDD as a tool to improve software development productivity and to understand how agile software development organizations may use DDD now and in the future to improve software development productivity. Research questions asked about software managers', project managers', and agile coaches' lived experiences with DDD via a set of interview questions. The conceptual framework for the research was based on the 3 critical dimensions of software organization productivity improvement: people, process, and tools, which were defined by the Software Engineering Institute's Capability Maturity Model Integrated published in 2010. Organizations focus on processes to align the people, procedures and methods, and tools and equipment to improve productivity. Positive social change could result from a better understanding of DDD in an agile software development environment; this increased understanding of DDD could enable organizations to create more products, offer more jobs, and better compete in a global economy.</p>
11
Brown, Mary Erin. "Data-Driven Decision Making as a Tool to Improve Software Development Productivity." ScholarWorks, 2011. https://scholarworks.waldenu.edu/dissertations/1075.
Full textAbstract:
The worldwide software project failure rate, based on a survey of information technology software manager's view of user satisfaction, product quality, and staff productivity, is estimated to be between 24% and 36% and software project success has not kept pace with the advances in hardware. The problem addressed by this study was the limited information about software managers' experiences with data-driven decision making (DDD) in agile software organizations as a tool to improve software development productivity. The purpose of this phenomenological study was to explore how agile software managers view DDD as a tool to improve software development productivity and to understand how agile software development organizations may use DDD now and in the future to improve software development productivity. Research questions asked about software managers', project managers', and agile coaches' lived experiences with DDD via a set of interview questions. The conceptual framework for the research was based on the 3 critical dimensions of software organization productivity improvement: people, process, and tools, which were defined by the Software Engineering Institute's Capability Maturity Model Integrated published in 2010. Organizations focus on processes to align the people, procedures and methods, and tools and equipment to improve productivity. Positive social change could result from a better understanding of DDD in an agile software development environment; this increased understanding of DDD could enable organizations to create more products, offer more jobs, and better compete in a global economy.
12
Chiang, I.-Cheng Robert. "Optimizing the productivity of development teams during software system construction : theoretical and practical considerations /." Thesis, Connect to this title online; UW restricted, 1999. http://hdl.handle.net/1773/8723.
Full text
13
Melo, Claudia de Oliveira. "Productivity of agile teams: an empirical evaluation of factors and monitoring processes." Universidade de São Paulo, 2013. http://www.teses.usp.br/teses/disponiveis/45/45134/tde-25052015-120242/.
Full textAbstract:
Lower cost and shorter time-to-market expectations are the major drivers of software productivity improvements. To manage productivity effectively, it is important to identify the most relevant difficulties and develop strategies to cope with them. Agile methods, including Extreme Programming and Scrum, have evolved as approaches to simplify software development process, potentially leading to better productivity. They aim to shorten development time and handle the inevitable changes resulting from market dynamics. Although the industry has extensively adopted agile methods, little research has empirically examined the software development agility construct regarding its dimensions, determinants, and effects on software development performance. Understanding this construct could help determine where to concentrate management efforts (and related financial resources) from a practical standpoint and where to focus research efforts from an academic perspective. Considerable research has been directed at identifying factors that have a significant impact on software development productivity. In general, the studied productivity factors were related to product, personnel, project, process, or organizational issues. Continuously evaluating productivity factors is important, as factors may change under new software engineering practices. However, little research has investigated the major factors influencing agile team productivity. ]The goal of this thesis was to explore productivity definitions, factors, and monitoring in agile teams and to improve the practice based on the collected evidence and gained knowledge. This thesis presents five novel contributions: C1 - Empirical verification of the importance of productivity for companies adopting agile methods and its perceived benefits; C2 - Rationale for the definition of productivity in the context of agile methods; C3 - Empirical verification of agile team productivity factors; C4 - A conceptual framework for agile team productivity factors and their impact; C5 - A team productivity monitoring process considering adaptability and an evaluation of the usefulness of agile team productivity metrics.<br>Menor custo e expectativa de menor time-to-market são os principais motivadores para melhorias de produtividade de software. Para gerir eficazmente a produtividade, é importante identificar as dificuldades mais relevantes e desenvolver estratégias para lidar com elas. Os métodos ágeis, incluindo Programação Extrema e Scrum, evoluíram como abordagens para simplificar o processo de desenvolvimento de software, potencialmente levando a uma melhor produtividade. Eles visam reduzir o tempo de desenvolvimento e lidar com as mudanças inevitáveis decorrentes da dinâmica do mercado. Embora a indústria tenha adotado amplamente métodos ágeis, há pouco entendimento científico do construto agilidade em desenvolvimento de software em relação às suas dimensões, determinantes e efeitos sobre o desempenho no desenvolvimento de software. Compreender esse construto poderia ajudar a determinar onde concentrar os esforços de gestão (e recursos financeiros relacionados) de um ponto de vista prático, assim como onde concentrar os esforços de investigação de uma perspectiva científica. Pesquisa considerável tem sido direcionada para identificar os fatores com impacto significativo na produtividade de desenvolvimento de software. Em geral, os fatores de produtividade estudados foram relacionadas ao produto, pessoas, projeto, processo ou questões organizacionais. Avaliar fatores de produtividade continuamente é importante, pois os fatores podem mudar quando novas práticas de engenharia de software são adotadas. No entanto, poucos estudos investigaram fatores influenciando a produtividade de times ágeis. O objetivo desta tese é explorar definições, fatores e monitoramento de produtividade em times ágeis e melhorar a prática baseada em evidência. Esta tese apresenta cinco novas contribuições: C1 - Verificação empírica da importância de produtividade para as empresas que adotam métodos ágeis e seus benefícios percebidos; C2 - Justificativa para a definição da produtividade no contexto de métodos ágeis; C3 - A verificação empírica de fatores de produtividade em times ágeis; C4 - Um arcabouço conceitual de fatores de produtividade em times ágeis e seu impacto; C5 - Um processo de acompanhamento de produtividade de times ágeis, considerando adaptabilidade e uma avaliação da utilidade de métricas de produtividade para esses times.
14
Naidu, I. Ajit. "Design and development of SINK, a software INteractions knowledge system." Master's thesis, This resource online, 1992. http://scholar.lib.vt.edu/theses/available/etd-12232009-020100/.
Full text
15
Norman, Ronald Jules. "Integrated development environments in support of information systems design methodologies and systems analysts' productivity." Diss., The University of Arizona, 1987. http://hdl.handle.net/10150/184275.
Full textAbstract:
Integrated development environment products, called CASE technology by practitioners, are being purchased by enterprises to assist systems analysts with the analysis and design of information systems. This work surveys users of a commercially available CASE product. Ninty-one users from 47 enterprises in the U.S. and Canada responded to the personal computer based survey. This work analyses the perceptions of the respondents in an attempt to determine productivity improvement over manual methods. Using the perceptions of the respondents, the component parts of the CASE product were rank ordered in terms of improved productivity. In addition to this, a psychometric preference scaling method was used to interpret the relatedness of the component parts to each other, again based on the perceptions of the respondents.
16
Wienke, Sandra [Verfasser], Matthias [Akademischer Betreuer] Müller, and Thomas [Akademischer Betreuer] Ludwig. "Productivity and Software Development Effort Estimation in High-Performance Computing / Sandra Wienke ; Matthias Müller, Thomas Ludwig." Aachen : Universitätsbibliothek der RWTH Aachen, 2018. http://d-nb.info/1162503319/34.
Full text
17
Sargut, Kamil Umut. "Application Of Statistical Process Control To Software Development Processes Via Control Charts." Master's thesis, METU, 2003. http://etd.lib.metu.edu.tr/upload/1270081/index.pdf.
Full textAbstract:
The application of Statistical Process Control (SPC) to software processes has
been a challenging issue for software engineers and researchers. Although SPC is
suggested for providing process control and achieving higher process maturity
levels, there are very few resources that describe success stories, implementation
details, and implemented guidelines for applying SPC to specific metrics.
In this thesis the findings of a case study that is performed for investigating the
applicability of SPC to software metrics in an emergent CMM Level 3 software
organization are presented. As being one of the basic and most sophisticated tools
of SPC, control charts are used for the analysis. The difficulties in application of
Statistical Process Control to a CMM Level 3 organization are observed by using
the existing data of defect density, rework percentage, productivity and review
performance metrics and relevant suggestions are provided for dealing with them.
Finally the analysis results are summarized and a guideline is prepared for
software companies who want to utilize control charts by using their existing
metric data.
18
Munir, Hussan, and Misagh Moayyed. "Systematic Literature Review and Controlled Pilot Experimental Evaluation of Test Driven Development (TDD) vs. Test-Last Development (TLD)." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4117.
Full textAbstract:
Context: Test-Driven development (TDD) is a software development approach where test cases are written before actual development of the code in iterative cycles. TDD has gained attention of many software practitioners during the last decade since it has suggested several benefits in the software development process. However, empirical evidence of its dominance in terms of internal code quality, external code quality and productivity is fairly limited. Objectives: The aim behind conducting this study is to explore what has been achieved so far in the field of Test-driven development. The study reports the benefits and limitation of TDD compared to TLD and the outcome variables in all the reported studies along with their measurement criteria. Additionally, an experiment is conducted to see the impact of Test-driven development (TDD) on internal code quality, external code quality and productivity compared to Test-Last development (TLD). Methods: In this study two research methodologies are used specifically systematic literature review according to Kitchenham guidelines and controlled pilot experiment. In systematic literature review number of article sources are considered and used, including Inspec, Compendex, ACM, IEEE Xplore, Science direct (Elsevier) and ISI web of science. A review protocol is created first to ensure the objectivity and repeatability of the whole process. Second, a controlled experiment is conducted with professional software developers to explore the assumed benefits of Test-Driven development (TDD) compared to Test-Last development (TLD). Results: 9 distinct categories related to Test-driven development (TDD) are found that are investigated and reported in the literature. All the reported experiments revealing very little or no difference in internal code quality, external code quality and productivity in Test-Driven development (TDD) over Test-Last development (TLD). However, results were found contradictory when research methods are taken into account because case studies tend to find more positive results in the favor Test-Driven development (TDD) compared to experiments possibly due to the fact that experiment are mostly conducted in artificially created software development environment and mostly with students as a test subjects. On the other hand, experimental results and statistical analysis show no statistically significant result in the favor TDD compared to TLD. All the values found related to number of acceptance test cases passed (Mann-Whitney U test Exact Sig. 0.185), McCabe’s Cyclomatic complexity (Mann-Whitney U test Exact Sig. 0.063), Branch coverage (Mann-Whitney U test Exact Sig. 0.212), Productivity in terms of number of lines of code per person hours (Independent sample Ttest Sig. 0.686), productivity in terms number of user stories implemented per person hours (Independent sample T-test Sig. 0.835) in experiment are statistically insignificant. However, static code analysis (Independent sample T-test Sig. 0.03) result was found statistically significant but due to the low statistical power of test it was not possible to reject the null hypothesis. The results of the survey revealed that the majority of developers in the experiment prefer TLD over TDD, given the lesser required level of learning curve as well as the minimum effort needed to understand and employ TLD compared to TDD Conclusion: Systematic literature review confirms that the reported benefits of TDD development compared to Test-Last development are very small. However, case studies tend to find more positive results in the favor of Test-Driven development (TDD) compared to Test-Last development (TLD). Similarly, experimental findings are also confirming the fact that TDD has small benefits over TLD. However, given the small effect size there is an indication that (Test-Driven development) TDD endorses less complex code compared to Test-Last development (TLD).<br>Systematic literature review confirms that the reported benefits of TDD development compared to Test-Last development are very small. However, case studies tend to find more positive results in the favor of Test-Driven development (TDD) compared to Test-Last development (TLD). Similarly, experimental findings are also confirming the fact that TDD has small benefits over TLD. However, given the small effect size there is an indication that (Test-Driven development) TDD endorses less complex code compared to Test-Last development (TLD).<br>hassanmunirr@hotmail.com, mm1844@gmail.com
19
Fucci, D. (Davide). "The role of process conformance and developers' skills in the context of test-driven development." Doctoral thesis, Oulun yliopisto, 2016. http://urn.fi/urn:isbn:9789526211657.
Full textAbstract:
Abstract Modern software development must adapt to demanding schedules while keeping the software at a high level of quality. Agile software development has been adopted in recent years to meet such a need. Test-driven development (TDD) is one practice that has arisen within the agile software development movement that leverages unit tests to develop software in incremental cycles. TDD supporters claim that the practice increases the productivity of the practitioners who employ it, as well as the internal and external quality of the software they develop. In order to validate or refute such claims, the software engineering research community has studied TDD for the last decade; the results of the empirical studies on the effects of TDD have been mostly inconclusive. This dissertation has studied two factors that may impact the manifestation of the claimed effects of TDD on software’s external quality and developers’ productivity: the developers’ conformance to the process (i.e., their ability to follow TDD) and their skills. The research was performed in four phases. In the first phase, the literature was reviewed to identify a set of factors that have been considered to affect TDD. In the second phase, two experiments were executed within academia. A total of 77 students at the University of Oulu, took part in the studies. These experiments investigated the quality of the software, as well as the subject’s productivity with respect to their programming and testing skills. A follow-up study, using data collected during the second experiment, explored the relation between the quality, productivity and the subjects’ process conformance. In the third phase, four industrial experiments, involving 30 professional, were performed. Process conformance and skills were investigated in relation to the TDD’s effects on external quality and productivity. The fourth phase synthesized the evidence gathered in the two previous phases. The results show that TDD is not associated with improvements in external quality, or developers’ productivity. Further, improvements in both external quality and productivity are associated with skills, rather than with the process, at least in the case of professional developers. Hence, process conformance has a negligible impact. The productivity of novice developers, on the other hand, can benefit from the test-first approach promoted by TDD<br>Tiivistelmä Modernin ohjelmistokehityksen täytyy mukautua haastaviin aikatauluihin säilyttäen ohjelmistojen korkea laatu. Ketterä ohjelmistokehitys on viime vuosina omaksuttu tähän tarpeeseen ja suuntauksessa on saanut alkunsa testivetoisen kehityksen käytäntö, joka hyödyntää yksikkötestausta ohjelmiston inkrementaalisessa, syklisessä kehityksessä. Testivetoisen kehityksen puolestapuhujat väittävät tämän käytännön lisäävän ohjelmistokehittäjien tuottavuutta sekä ohjelmiston sisäistä ja ulkoista laatua. Ohjelmistotuotannon tutkimusyhteisö on tutkinut testivetoista kehitystä viimeisen vuosikymmenen aikana vahvistaakseen tai kumotakseen nämä väitteet. Empiiriset tutkimukset testivetoisen kehityksen vaikutuksista ohjelmistotuotantoon ovat suurelta osin tuloksettomia. Tämä väitöstyö tutkii kahta tekijää, jotka voivat vaikuttaa testivetoisen kehityksen väitettyjen vaikutusten ilmentymiseen ohjelmiston ulkoisena laatuna ja ohjelmistokehittäjien tuottavuutena: ohjelmistokehittäjien taitoja ja prosessin mukaista toimintaa. Tutkimus toteutettiin neljässä vaiheessa. Ensimmäisessä vaiheessa tehtiin kirjallisuuskatsaus, jolla selvitettiin tekijöitä, joiden on katsottu vaikuttavan testivetoiseen kehitykseen. Toisessa vaiheessa tehtiin Oulun yliopistolla kaksi koetta, joihin osallistui kaikkiaan 77 opiskelijaa. Kokeissa tutkittiin ohjelmiston laadun ja osallistujien tuottavuuden suhdetta heidän ohjelmointi- ja testaustaitoihinsa. Toisen kokeen aikana kerättyä aineistoa hyödynnettiin jatkotutkimuksessa, jossa tarkasteltiin laadun, tuottavuuden ja prosessin mukaisen toiminnan suhdetta. Kolmannessa vaiheessa tehtiin neljä koetta, joihin osallistui 30 ohjelmistoalan ammattilaista. Prosessin mukaista toimintaa ja taitoja tutkittiin suhteessa testivetoisen kehityksen vaikutuksiin ohjelmiston ulkoiseen laatuun ja tuottavuuteen. Neljännessä vaiheessa syntetisoitiin kahden edellisen vaiheen löydökset. Tulokset osoittavat, ettei testivetoinen kehitys liity ulkoisen laadun parantumiseen eikä ohjelmistokehittäjien tuottavuuteen. Parannukset laadussa ja tuottavuudessa liittyvät ennemmin taitoihin kuin prosessiin, ainakin ohjelmistokehityksen ammattilaisten kohdalla. Näin ollen prosessin mukaisella toiminnalla on vähäpätöinen vaikutus. Toisaalta testivetoisen kehityksen suosiman test-first-menettelytavan hyödyntäminen voi edistää aloittelevien ohjelmistokehittäjien tuottavuutta
20
Sauma, Robin, and Milad Ziai. "Komparativ studie mellan React-Native och Flutter med avseende på utvecklarens produktivitet." Thesis, Tekniska Högskolan, Jönköping University, JTH, Datateknik och informatik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-49913.
Full textAbstract:
Utvecklingen av mobila hybrid applikationer har ökat drastiskt under det senaste årtiondet. Med tanke på mångfalden i hur stora företag börjar investera i ramverk med support för utveckling av mobila hybrid applikationer (multiplattforms ramverk), ökar nödvändigheten av aktuella studier inom detta ämnesområde. Facebook och Google är två välkända företag som har utvecklat React-Native respektive Flutter. Dessa multiplattforms ramverk utvecklas kontinuerligt och skillnader uppstår inom teknologierna hos ramverken vilket gör nya studier mer lämpliga. Syftet med denna studie är att undersöka vilket ramverk som bidrar med bäst produktivitet för utvecklaren med tanke på bristen av studier inom ämnet. Specifikt har en fallstudie utförts där studiens frågeställningar har besvarats. Respektive frågeställningarna blev uppdelade i tre delfrågeställningar där varje fråga fick angivna kriterier att följa i fallstudien och båda ramverken blev tilldelade poäng om tillhörande kriterium för varje fråga var uppfylld. I slutet av studien räknades ett medelvärde ut som tilldelades till båda ramverken. Resultaten visade att det finns små skillnader i form av dess bidrag med bäst produktivitet för utvecklaren.<br>The development of hybrid mobile applications has increased rapidly in the last decade. Considering the diversity in how big companies starts to invest in frameworks that supports hybrid application development (cross-platform framework), the necessity of contemporary studies in this subject increase. Facebook and Google are two well-known companies that have developed React-Native and Flutter, respectively. These cross-platform frameworks are continuously developing, and differences occur in their technologies which makes new studies even more appropriate. The purpose of this study is to investigate which of these two frameworks contribute the most for the developer’s productivity considering the lack of studies in this specific subject. Specifically, a case study has been conducted where the research questions were answered. The two research questions were divided into three sub questions, respectively where each question was given criteria to follow in the case study and each framework were assigned points if the associated criterion for each question were met. In the end of the study a mean value was assigned to each framework. The results showed that there are small differences in terms of its contribution for the developer’s productivity.
21
HWANG, CHEN-HSANG, and 黃呈祥. "Process-oriented software development productivity measurement model." Thesis, 1992. http://ndltd.ncl.edu.tw/handle/25539089309802822098.
Full text
22
Liu, Tien-chun, and 劉天鈞. "A Study of Agile Software Development Productivity Analysis." Thesis, 2011. http://ndltd.ncl.edu.tw/handle/45586907051055062749.
Full textAbstract:
碩士<br>中原大學<br>資訊工程研究所<br>99<br>In this thesis, we analyzed the productivity of a real world agile project and provided the productivity data on different work items and during different periods of the project. Agile development process is usually used when the scope of a project is not clearly defined. It is important for the management to monitor not only the project progress indicators but also the project productivity. Beside the line of code (LOC), function point was used to analyze the productivity of the agile project.
We estimated function point of work items from product backlog of the project, obtained work efforts of work items that were recorded using XPlanner, and then counted the line of code of work items.
We performed linear regression analysis on: 1. function point v.s. work efforts, 2. LOC v.s. work efforts, and 3. function point v.s. LOC. We found that correlations among the three are significant and thus believed that functional point can be used as a productivity indicator for agile projects.
Furthermore, we analyzed the productivity on different functions and during different stages of the project.
23
Nzou, Viola. "Development of a framework to understand the factors that influence software productivity in agile teams." Diss., 2017. http://hdl.handle.net/10500/26007.
Full textAbstract:
Productivity improvement in the software industry is one of the major challenges facing many software development companies in this century. Most companies have adopted agile methodologies in order to profit from the benefits claimed for them. Agile methodologies are characterised by frequent software delivery, short feedback loops, quicker response to change, and problem identification earlier in the development process.
The agile approach has been recognised as paving a way for companies to acquire higher software productivity, delivering good-quality and cost-effective software, enabling software development companies to respond to business challenges with their demands for high quality, high performance and high development speed in delivering the final product. For companies that adopt agile methodologies, understanding the factors that influence their teams’ software development productivity is a challenging task for management and practitioners today.
In this research, an analysis is presented that identifies productivity factors that affect agile teams. It is a study of agile methods to identify common agile practices and/or values that have impact on productivity, and describes suitable metrics that could be used to measure agile team productivity. A qualitative research approach was used, and the case study was chosen as the research strategy. Two South African companies that are located in two different provinces and that adopted agile methodologies in their software development, were selected for the case studies. Qualitative content analysis was used in the research to permit subjective interpretation of factors that influence agile team productivity, and to analyse to what extent these factors affected productivity. This research has shown that an understanding of the factors that influence an agile team’s productivity gives significant insight into the way agile teams work, motivates team members to work together, and leads to uniform metrics in tracking each team’s progress. The study indicates that tracking an agile team’s work and providing adequate tools needed to execute their tasks results in improving agile team productivity. It should be recognised that using metrics to measure performance in agile teams is helpful in creating a team’s culture and trust. In this study, it was found that the factors identified in both literature and case studies affected productivity in the two companies under study, both positively and negatively. The study also found that applying the correct metrics in assessing, analysing and reviewing an agile team’s performance is important when monitoring productivity. Successful software delivery is only possible if individuals are committed to their work, are provided with the necessary tools and have access to a stable working environment. In addition, individual factors such as knowledge, skills, abilities, personalities and experience should be considered when forming agile teams. Consideration of these factors will result in grouping people that are able to work together and achieve a common goal, which is important in improving productivity. A conceptual framework for agile team productivity was proposed. The discussion of the findings is presented in more detail in this research.<br>School of Computing<br>M.Sc. (Computing)
24
Johar, Monica S. "Essays on improving software development productivity and economic and operational analysis of content distribution networks /." 2006. http://proquest.umi.com/pqdweb?did=1179959391&sid=2&Fmt=2&clientId=10361&RQT=309&VName=PQD.
Full text
25
Costa, Manuel Eduardo Fernandes Pereira da. "e-Whip: impacto provocado pela introdução de ferramentas num processo de desenvolvimento de software." Master's thesis, 2005. http://hdl.handle.net/10451/13985.
Full textAbstract:
Tese de mestrado em Informática, apresentada à Universidade de Lisboa, através da Faculdade de Ciências, 2005<br>The software development processes evolve a complex series of factors, aiming to assure quality the final product, reached through detailed and complete planning, and fine application of the know-how and resources available in the work group, keeping the production cost as low as possible and keeping business risks under control at every moment.The team management or the organization management has to take the right decisions in every process phases and aspects. In order to do that, the management must have exact, complete and instant information available about the status of the productive process. That information must be based on real data, gathered during the development process or it can be in the form of instant communication of all execution activity between team members. The real difficulty resides in the way how that data is gathered and distributed. In this thesis a new software solution, named e-Whip, was developed from scratch. This software allows data to be gathered in a simple, complete and exact way and be transformed in information by using reports. The solution allows collective work improvement by communicating team activities between team members in real-time. In this document are discussed certain theoric and technical aspects of the software. Is also discussed how the software behaved and what its impact was like in two real-world use cases.<br>Um processo de desenvolvimento de software envolve todo um complexo conjunto de factores cujo objectivo é garantir a qualidade na entrega do produto final. Este objectivo é atingido através de um planeamento abrangente e detalhado, e de um aproveitamento óptimo do conhecimento e dos recursos disponíveis na equipa de trabalho, minimizando custos de produção e mantendo sempre controlados os riscos inerentes ao negócio. Cabe à gestão da equipa ou da organização tomar as decisões certas em todos os pontos do processo produtivo. Para que tal seja possível, é necessário existir informação ao seu dispor que lhe permita decidir acertadamente. Essa informação relativa ao processo produtivo tem de ser exacta, completa e instantânea. A informação pode ser baseada em dados reais recolhidos no decorrer do próprio processo de desenvolvimento, ou pode tomar a forma de comunicação das actividades em execução num dado instante entre os vários elementos da equipa. A dificuldade prende-se com o método empregue para recolher e distribuir esses dados fundamentais. No âmbito desta tese foi desenvolvido uma solução de software de raiz, denominado eWhip, que permite recolher dados do processo de trabalho de uma forma simples, rigorosa e completa, que depois são transformados em informação que é disponibilizada à gestão na forma de relatórios. A solução permite facilitar o esforço de trabalho colectivo, através da comunicação em tempo real das actividades de todos os elementos da equipa. Neste documento são discutidos os fundamentos teóricos e técnicos por detrás deste software. É também apresentada uma análise da sua utilização e do seu impacto em dois casos de estudo.
26
Basak, Sujit Kumar. "A model using ICT adoption and training to improve the research productivity of academics." Thesis, 2015. http://hdl.handle.net/10321/1392.
Full textAbstract:
Submitted in fulfilment of the requirement of the Doctor of Technology degree in Information Technology, Durban University of Technology, Durban, South Africa, 2015.<br>Research productivity is one of the core functions of a university and it plays a crucial role for a nation to develop and find its standing in our global world. This study examined the effect of ICT adoption and training on the research productivity of university academics. Much research has been done on using technology in research with a view to increase productivity. However, hardly any research could be found on the use of ICT combined with ICT training with a view to increase research productivity. This study addressed this gap in the literature. The study sought to design a model that can increase research productivity of academics while optimizing ICT adoption and training effects.
The study was conducted at four public universities in KwaZulu-Natal, South Africa, whilst the part of the study on ICT training was conducted at one of the four universities. This study was conducted both in the form of a survey of 103 university academics and in the form of experimental sessions, where the use of ICT (EndNote, NVivo, AMOS, SPSS, and Turnitin) with training was used for research, the use of ICT without training was used for research and, finally, a session where a manual system (without using research software/tools and training) was used for research.
The overall aim of the study was to investigate and design a model for the increase in research productivity of academics in universities after having adopted ICTs. The final results of the research revealed that the use of ICT tools (EndNote, NVivo, AMOS, SPSS, and Turnitin) with training increases research productivity as compared to using ICT tools without training, and/or using a manual system (without using research software/tools and training). A statistically proven model is recommended with a view to increase research productivity of academics.