• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 5
  • 4
  • 1
  • Tagged with
  • 12
  • 12
  • 12
  • 10
  • 7
  • 4
  • 4
  • 4
  • 4
  • 4
  • 3
  • 3
  • 3
  • 3
  • 3
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
1

Using emergent outcome controls to manage dynamic software development

Harris, Michael Loyd 01 June 2006 (has links)
Control and flexibility may appear an unlikely pair. However, I propose that effective management of dynamic environments, such as systems development under conditions of uncertainty, must still provide clear control mechanisms to manage the progress and quality of the resulting products. This dissertation presents research to understand the types of control used in the context of flexible software development processes. The dynamic capabilities extension to the resource-based view of the firm is used to understand dynamic environments. Within those environments, control theory is used to understand how activities are guided and controlled to achieve management objectives. Specifically, control theory acts as a lens to contrast the control mechanisms found in plan-driven and flexible processes. I extend current thinking to include emergent outcome controls for team coordination in a taxonomy of control mechanisms. These phenomena are studied through a qualitative field study. The results show that organizations will choose more flexible management approaches as uncertainty increases, and that more controlled-flexible approaches managed with emergent outcome controls will lead to better outcomes than uncontrolled, ad hoc approaches.
2

Software Development Methods and Usability: A Systematic Literature Review

Prem Kumar, Prabhu Raj January 2017 (has links)
This thesis provides a tour of main software development methods and their assimilation with usability. Various software development methods have been developed since the origin of software products, and with integration of usability they have achieved great heights. Software developers and researchers are also keen to integrate usability with their methods to develop a successful software product, as their product might not lose its grip over their competitors. This thesis is a preliminary literature review that provides solutions to key questions such as: Which development methods are used in projects with high demands on usability?Do agile methods positively contribute to the usability of the product? Do projects with high demands on usability use usability specialists?Which types of usability are addressed in articles relating development methods and usability? The research aim is to identify how software development methods deal with usability. This thesis clearly discusses about previous empirical studies on software development methods and usability. In this thesis, Kitchenham’s systematic literature review was followed to extract the knowledge from the databases (Inspec and ACM). Validation on the literature is performed using Cohen’s kappa value with a researcher. Four research questions mentioned above are discussed in detail to analyse the results. Agile software development methods have been widely deployed due to its iterative, incremental approach and positive contribution towards usability rather than traditional approach. The role of an usability expert has been analyzed in this thesis and their need in the development process. Futhermore, various usability types like satisfaction, efficiency and effectiveness have also been discussed in detail. Finally, this thesis suggess a solution of incorporating usability with software development methods.
3

An Evaluation of the Usage of Agile Core Practices : How they are used in industry and what we can learn from their usage

Dogs, Carsten, Klimmer, Timo January 2004 (has links)
In this thesis we investigate the usage of several agile software development methods as well as the usage of certain agile core practices. By conducting a web survey, we examine what makes these practices beneficial and what tends to make them rather less suitable for certain situations. Based on the results, we finally set up some recommendations for practitioners to reflect upon and improve their own software development process. Concerning these recommendations as well as the list of the investigated practices, we hope (and are almost sure) that there are some practices or ideas contained which are worth at least thinking about. The main findings of this thesis are: - Agile software development methods have already entered the professional market but they are still no cure-all. In many cases they also produce only middle-quality software. Nevertheless, there is – even if only little – evidence that at least XP projects meet the requirements of the customer better than traditional, non-agile methods. - For a successful software development project it is important that it has a suitable requirements engineering process, that the produced software is tested sufficiently (using automated regression testing among other types of testing), that there is a good communication between the customer and the developer side, that the risks of the project are considered, that the pros and cons of practices are considered and that processes are improved continuously. - Besides, it is important to consider the whole context when implementing a certain practice. For some contexts, certain practices do not fit for their purpose and this has to be realized. However, certain shortcomings of a specific practice might be reduced or even eliminated if implemented in combination with other practices.
4

CROSS SECTIONAL STUDY OF AGILE SOFTWARE DEVELOPMENT METHODS AND PROJECT PERFORMANCE

Lambert, Tracy 01 January 2011 (has links)
Agile software development methods, characterized by delivering customer value via incremental and iterative time-boxed development processes, have moved into the mainstream of the Information Technology (IT) industry. However, despite a growing body of research which suggests that a predictive manufacturing approach, with big up-front specifications, detailed estimates, and speculative plans applicable to manufacturing domains, is the wrong paradigm for software development, many IT organizations are still hesitant to adopt agile approaches (Larman, 2004). This study extends research based on the Unified Theory of Acceptance and Use of Technology (Venkatesh, Morris, Davis, & Davis, 2003) into the domain of business processes. Specifically, processes related to the `behavioral intent' to adopt agile software development methods. Further, it investigated relationships between adoption and the impact on project performance attributes. A sample was obtained from a population of IT practitioners from within the IT industry. The sampling frame consisted of members from the global Software Process Improvement Network (SPIN) chapters, Agile User Groups, and I.T. industry conference promoters and presenters. Independent variables included performance expectancy, effort expectancy, social influence, and facilitating conditions, with the dependant variable being behavioral intent to adopt agile software development methods. The independent variable of agile software development adoption and dependent variables of project performance were also included as well as predictive models relating adoption to on-time delivery of project functionality and stakeholder satisfaction. The variables in the study were measured via a 65-item questionnaire based on previous scales, and tested to ensure validity and reliability. The research questions were developed to identify correlations between performance expectancy, effort expectancy, social influence, facilitating conditions, and the behavioral intent to adopt agile software development methods. Additional questions measured the correlation between adoption and key project performance attributes. The research found positive correlations between performance expectancy, effort expectancy, social influence, facilitating conditions, and behavioral intent to adopt agile software development methods, positive correlations between adoption and on-time delivery of project functionality and stakeholder satisfaction, and weak positive correlations with post delivery defects and project success rates.
5

Making Methods Work in Software Engineering : Method Deployment - as a Social Achievement

Rönkkö, Kari January 2005 (has links)
The software engineering community is concerned with improvements in existing methods and development of new and better methods. The research approaches applied to take on this challenge have hitherto focused heavily on the formal and specifying aspect of the method. This has been done for good reasons, because formalizations are the means in software projects to predict, plan, and regulate the development efforts. As formalizations have been successfully developed new challenges have been recognized. The human and social role in software development has been identified as the next area that needs to be addressed. Organizational problems need to be solved if continued progress is to be made in the field. The social element is today a little explored area in software engineering. Following with the increased interest in the social element it has been identified a need of new research approaches suitable for the study of human behaviour. The one sided focus on formalizations has had the consequence that concepts and explanation models available in the community are one sided related in method discourses. Definition of method is little explored in the software engineering community. In relation to identified definitions of method the social appears to blurring. Today the software engineering community lacks powerful concepts and explanation models explaining the social element. This thesis approaches the understanding of the social element in software engineering by applying ethnomethodologically informed ethnography and ethnography. It is demonstrated how the ethnographic inquiry contributes to software engineering. Ethnography is also combined with an industrial cooperative method development approach. The results presented demonstrate how industrial external and internal socio political contingencies both hindered a method implementation, as well as solved what the method was targeted to do. It is also presented how project members’ method deployment - as a social achievement is played out in practice. In relation to this latter contribution it is provided a conceptual apparatus and explanation model borrowed from social science, The Documentary method of interpretation. This model addresses core features in the social element from a natural language point of view that is of importance in method engineering. This model provides a coherent complement to an existing method definition emphasizing formalizations. This explanation model has also constituted the underpinning in research methodology that made possible the concrete study results.
6

Fatores de escolha entre metodologias de desenvolvimento de software tradicionais e ágeis. / Factors of choice between traditional and agile software development methodologies.

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

Fatores de escolha entre metodologias de desenvolvimento de software tradicionais e ágeis. / Factors of choice between traditional and agile software development methodologies.

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

Challenges related to the adoption of Scrum

Kanane, Aahd January 2014 (has links)
Software development projects took an important turn after the emergence of agilesoftware development methods. Indeed, this kind of projects has always been managed in atraditional way that requires an elaborate effort of planning. A way considered as inflexibleand that goes against the constantly changing and hardly predictable nature of softwaredevelopment projects. Agility offers more flexibility as far as requirements and changemanagement are concerned. In this study, the focus is placed on one of the most popularagile software development methods, namely Scrum. It investigates the challenges relatedto the adoption of Scrum, and for this the case of a company operating in the financial ITsector and that has been using Scrum for 5 years is examined. This case displays that thenature of Scrum makes that there is not a single way of adopting it. Adopting Scrum ismore a process of continuous adaptation and improvement, therefore facing challenges isan inseparable part of this process.
9

A comparative study on Traditional Software Development Methods and Agile Software Development Methods

Aslam, Gulshan, Farooq, Faisal January 2011 (has links)
Everyone is talking about the software development methods but these methods are categorised into the different parts and the most important are two categories, one is agile software development methods and second is using the traditional software development methods. Agile software methods are relatively considered to be quick and for the small teams. Our main mission is to check which method is better from each other, so for that purpose we go out in the software development market to meet the professional to ask about their satisfaction on these software development methods. Our research is based on to see the suitable method for the professionals; see the challenges on the adoptability of methods and which method is quicker. To perform this study we have gone through a survey questionnaire, and results are analysed by using mixed method approach. Results shows that professionals from both types of methods are satisfied but professionals with traditional methods are more satisfy with their methods with respect to development of quality software, whereas agile professionals are more satisfied with their methods with respect of better communication with their customers. With agility point of view, our study says that both methods have characteristics which support agility but not fully support, so in such case we need to customize features from both types of methodologies.
10

Reflexões sobre o ensino de metodologias ágeis na academia, na indústria e no governo / Reflections on teaching agile methodologies in academy, industry, and government.

Alexandre Freire da Silva 14 September 2007 (has links)
As metodologias ágeis e em especial a Programação eXtrema (XP) surgem como um contraponto aos métodos tradicionais de desenvolvimento de software. Nos encontramos em um momento no qual considera-se aceitável encontrar defeitos em programas de computador, até mesmo naqueles sistemas pelos quais temos que pagar muito dinheiro. Melhorar o ensino de técnicas para que equipes possam colaborar no desenvolvimento de software de qualidade é essencial para que esta área do conhecimento alcance a maturidade que esperamos. O ensino de XP é uma tarefa relativamente complexa pois exige que pessoas passem por uma mudança cultural, para aceitar seus valores, princípios e práticas. Diferentes organizações precisam adaptar a metodologia para que ela funcione bem em seu contexto local. Encontrar maneiras de facilitar o ensino e a adoção das práticas ágeis é fundamental para melhorar a qualidade do software desenvolvido no país. Este trabalho pesquisa o ensino de XP em contextos acadêmicos, governamentais e industriais. Três estudos de caso foram conduzidos e analisados para sugerir padrões que podem auxiliar o ensino da metodologia por um educador em qualquer contexto. / Agile methodologies, specially eXtreme Programming (XP), appear as a counterpoint to traditional software development methods. We live in a moment were it is considered acceptable to find bugs in computer programs, even those for which we pay a lot of money. It is essential to improve the way we teach techniques with which teams can collaborate on the development of quality software so that this area of knowledge reaches the maturity we wish. Teaching XP is a relatively complex task because it implies that people must go through a cultural change to accept its values, principles, and practices. Different organizations need to adapt the methodology so that it will work well in their local context. Finding ways to facilitate teaching and adopting agile practices is fundamental to improve the quality of software being developed in the country. This work researches the process of teaching XP in academic, governmental and industrial con- texts. Three case studies were conducted and analyzed so that we could suggest patterns that can support educators teaching the methodology in any context.

Page generated in 0.1829 seconds