• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 35
  • 28
  • 22
  • 6
  • 2
  • 2
  • 2
  • 1
  • 1
  • 1
  • Tagged with
  • 109
  • 109
  • 52
  • 52
  • 48
  • 35
  • 35
  • 25
  • 22
  • 22
  • 21
  • 16
  • 14
  • 12
  • 12
  • 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.
51

XWEBPROCESS : um processo ágil para o desenvolvimento de aplicações web

Tadeu Falcone Sampaio, Americo January 2004 (has links)
Made available in DSpace on 2014-06-12T15:58:28Z (GMT). No. of bitstreams: 2 arquivo4574_1.pdf: 1993524 bytes, checksum: 8bd7ac8823b7cd26d61ac1882bf03321 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2004 / O crescimento da internet e da World Wide Web provocou mudanças em muitos aspectos da nossa sociedade. A Web veio a oferecer novas maneiras de fazer negócio e muitas organizações passaram a oferecer seus serviços e migrar seus sistemas para este ambiente. As aplicações Web apresentam características importantes que devem ser tratadas adequadamente por técnicas, métodos e processos da engenharia de software. Na maioria dos casos, as restrições envolvidas nos prazos de entrega de sistemas Web são críticas por se tratar de uma questão estratégica do negócio do cliente. Neste trabalho apresentamos um processo ágil de desenvolvimento de aplicações Web, XWebProcess, que é baseado em Extreme Programming (XP) e cujo foco é a construção de sistemas Web de qualidade de forma eficiente e rápida. O processo é descrito usando a meta linguagem SPEM para facilitar seu entendimento e melhorias futuras. Um experimento foi conduzido com um grupo de quarenta estudantes de graduação para avaliar a eficiência e qualidade do processo proposto. Os resultados mostraram que XWebProcess foi tão ágil quanto XP e também que o processo é bastante adequado para o desenvolvimento Web considerando questões como análise de requisitos, projeto de navegação e interface gráfica, e testes
52

XP-CMM : uma guia para utilização de Extreme Programming em um ambiente nível do CMM

Endriss Carneiro Campelo, Renata January 2003 (has links)
Made available in DSpace on 2014-06-12T15:58:59Z (GMT). No. of bitstreams: 2 arquivo4794_1.pdf: 2683672 bytes, checksum: ea816cfe4cb13fb4f70bae7d4e2876eb (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2003 / Recentemente a comunidade de software vem se deparando com um grupo de novas metodologias de desenvolvimento de software, classificadas como metodologias ágeis . Algumas das metodologias que fazem parte deste grupo são Extreme Programming (XP) e SCRUM, sendo XP a mais conhecida e utilizada. Estas metodologias possuem em comum um conjunto de valores para o desenvolvimento de software, priorizando: indivíduos e iterações sobre processos e ferramentas; software funcionando sobre documentação compreensiva; colaboração do cliente sobre negociação de contrato; resposta à mudança sobre seguir um plano. Em paralelo à disseminação das metodologias ágeis, os investimentos em qualidade de software vêm aumentando a cada ano. Pesquisas realizadas sobre o setor de software, indicam um crescimento na adoção de modelos de qualidade como ISO 9000 e Capability Maturity Model for Software (CMM). Modelos de qualidade e metodologias ágeis possuem fundamentos opostos, como é possível notar nos valores definidos por essas metodologias. Autores de metodologias ágeis freqüentemente criticam modelos como o CMM. Em contra partida, alguns trabalhos indicam que é possível utilizar as duas abordagens em um mesmo ambiente. Este trabalho apresenta o Guia XP-CMM2, que tem como objetivo apoiar as organizações no uso da metodologia ágil XP em um ambiente nível 2 do CMM. Com o uso do Guia XP-CMM2, as organizações deverão se beneficiar da agilidade proposta por XP e da maturidade adquirida com o nível 2 do modelo de qualidade de software mais respeitado do mundo, o CMM. Para a elaboração do Guia XP-CMM2, foi realizado inicialmente um diagnóstico da satisfação de XP ao nível 2 do CMM e, depois, para cada problema identificado, uma solução foi proposta. Finalmente o Guia XP-CMM2 foi aplicado em dois ambientes distintos visando avaliação dos resultados obtidos
53

Uso eficaz de métricas em métodos ágeis de desenvolvimento de software / Effective use of metrics on agile software development methods

Danilo Toshiaki Sato 29 June 2007 (has links)
Os Métodos Ágeis surgiram no final da década passada como uma alternativa aos métodos tradicionais de desenvolvimento de software. Eles propõem uma nova abordagem para o desenvolvimento, eliminando gastos com documentação excessiva e burocrática, enfatizando a comunicação, colaboração com o cliente e as atividades que trazem valor imediato na produção de software com qualidade. Por meio de um processo empírico, com ciclos constantes de inspeção e adaptação, a equipe trabalha sempre num ambiente de melhoria contínua. Uma das atividades propostas pela Programação Extrema (XP) para guiar a equipe em direção à melhoria é conhecida como tracking. O papel do tracker é coletar métricas para auxiliar a equipe a entender o andamento do projeto. Encontrar maneiras eficazes de avaliar o processo e a equipe de desenvolvimento não é uma tarefa simples. Além disso, alguns dos possíveis problemas não são facilmente reconhecidos a partir de dados quantitativos. Este trabalho investiga o uso de métricas no acompanhamento de projetos utilizando Métodos Ágeis de desenvolvimento de software. Um estudo de caso da aplicação de XP em sete projetos acadêmicos e governamentais foi conduzido para validar algumas dessas métricas e para avaliar o nível de aderência às práticas propostas, com o objetivo de auxiliar o tracker de uma equipe ágil. / Agile Methods appeared at the end of the last decade as an alternative to traditional software development methods. They propose a new style of development, eliminating the cost of excessive and bureaucratic documentation, and emphasizing the interactions between people collaborating to achieve high productivity and deliver high-quality software. With an empirical process, based on constant inspect-and-adapt cycles, the team works towards an environment of continuous improvement. One of the practices proposed by Extreme Programming (XP) to enable the creation of such environment is called tracking. The role of a tracker is to collect metrics that support the team on understanding their current process. Finding effective ways to evaluate the team and the development process is not an easy task. Also, some of the possible problems are not always easily recognizable from quantitative data alone. This work investigates the use of metrics for tracking projects using Agile Methods for software development. A case study on the adoption of XP in seven academic and governmental projects was conducted to validate some of these metrics and to evaluate the level of adherence to the proposed practices, with the goal of assisting and supporting the tracker of an agile team.
54

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.
55

Test-lists Utilization in Test Driven Development : The Role of test-lists in Requirements Traceability / Test-lists Utilization in Test Driven Development : The Role of test-lists in Requirements Traceability

Khan, Hassan Mahmood, Arshad, Ibrar January 2012 (has links)
Context: In recent times, many organizations have started using agile software development methodologies instead of using traditional methodologies. The main reason for this shift is the ability of agile approaches to cope with changes in the requirements, customer satisfaction and assurance of on-time delivery of quality products [19]. Test-Driven Development (TDD) is a software development methodology that is considered to be one of the most prominent practices of eXtreme Programming (XP) (an agile methodology) [1][9][10]. Test-list in TDD is considered as a temporary repository in which test items are stored and later by using those items test cases are developed. Requirements Traceability is also a major problem in agile development mainly because of lack of formal requirements specification and frequent requirements change. Objectives: This study explores the utilization of test-list and possibility of using test-list for requirements traceability in TDD. This study describes concept of test-list, its formation and exploring its utilization in TDD. Methods for implementing requirements traceability in and identification of possibility of utilizing test-list for requirements traceability in TDD is also explored. Methods: Methods used in this study are systematic literature review, surveys and interviews. Systematic literature review was done using seven electronic databases, including Inspec, IEEE Xplore, ACM Digital Library, Springer, Science Direct and Scopus. Studies were selected on the bases of preliminary, basic and advanced developed criteria. Survey was conducted using online questionnaire from TDD practitioners. Findings from literature review and surveys were used to develop interview questionnaires. Interviews were conducted from the same practitioners that were involved in surveys. Results: Based on the findings of literature review, questionnaire and interviews, we obtained TDD practices for test-list development and requirements traceability. Analysis was performed on results of SLR and questionnaire and possibility of using test-list for requirements traceability was identified. Based on the analysis of literature review and surveys, interview questionnaire were developed to further investigate the area of interest. We have found that in literature there is no defined method to develop test-list. and survey participants also confirms it. Majority of survey participants create test-list temporarily and informal. On question of whether test-list can be use for requirements traceability around 70% of participants are agree for its use. Interview respondents also confirm the findings of survey. Conclusions: Literature has not provided any test-list development method and practitioners also have no clear guideline to develop test-list prior to Test development. Systematic literature review and practitioner’s survey and interviews confirm it. Literature is also silent for any specific requirements change management or requirements traceability method in TDD. We identified requirements traceability practices in agile and management through literature and survey. After analysis of gathered data we found TDD lacks in test-list formalization, none of the study focuses on requirements traceability in TDD. In this study our contribution is exploration of test-list creation and utilization through literature and state of the practice; after practitioners feedback we also explored that test-list can be used for requirements traceability. / hasmkh@gmail.com, ibrararshad@gmail.com
56

Combining eXtreme Programming with ISO 9000:2000 to Improve Nigerian Software Development Processes / Combining eXtreme Programming with ISO 9000:2000 to Improve Nigerian Software Development Processes

Erharuyi, Edison January 2007 (has links)
The aim of this research work is to study how eXtreme programming could be combined with ISO 9000:2000 standards to improve Nigerian software development processes. The combination of these models will enable organizations take advantage of models’ strengths and compensate for their weaknesses in enhancing continuous software process improvement and rapidly responding customer’s changing needs. This was achieved by adopting a model in balancing ISO and eXtreme programming in software projects. This allows organization to determine whether to choose a pure method (eXtreme programming or ISO) or mixed methods (eXtreme programming and ISO) that will be most successful in executing software projects. Also developed was another strategy in modifying eXtreme programming practices to reflect ISO 9001:2000 standard requirements. / The aim of this research work is to study how eXtreme programming could be combined with ISO 9000:2000 standards to improve Nigerian software development processes / C/o Patrick O. Nordkapsgatan 8,Kista, 164 36, Stockholm Tel:+46-704214035, e- mail address: edisonerhas@yahoo.com
57

Utvärdering av agila systemutvecklingsmetoder : Småskalig agil systemutveckling

Sundberg, André, Torkkeli, Ted January 2016 (has links)
Inom systemutveckling är det viktigt att man använder den eller de metoder som lämpar sig bäst till projektet. De mest populära systemutvecklingsmetoderna är de agila metoderna. Att utveckla agilt innebär att man jobbar iterativt och inkrementellt och följer tolv grundprinciper för att skapa värde till kunden. Författarna till denna uppsats har utvecklat ett informationssystem under en månad där de tillämpat agila principer samt metodelement från SCRUM och Extreme Programming, och dokumenterat processen för att undersöka för- och nackdelarna med detta inom ett mikroprojekt.
58

Vilka nödvändiga kompetenser krävs av systemutvecklare som använder XP? : en kvalitativ studie bland svenska systemutvecklare

Velic, Haris January 2008 (has links)
Examensarbetet har sin ansats i utvecklingsmetoder närmare bestämt den lättrörliga utvecklingsmetoden Extreme Programming (XP). Beståndsdelen i en utvecklingsmetod är människorna, deras erfarenheter och kunnande samt deras förmåga att skapa idéer och lösa problem såväl enskilt som tillsammans. Utan nödvändig kompetens inom utvecklingsteamen ökar risken att utvecklingsprojekten misslyckas eller försenas. Syftet med detta arbete är att utifrån intervjuer med systemutvecklare undersöka vilka nödvändiga kompetenser som är nödvändiga för att XP skall kunna användas på ett effektivt sätt, även att uppmärksamma vilka problem som kan uppstå då den sociala kompetensen saknas. Metoden som har använts för att undersöka vilka faktorer som är nödvändiga i avseende till kompetenser är baserad på en kvalitativ ansats. Undersökningen har gjorts på två medelstora företag som använder XP vid utveckling av programvara. I stora drag har resultatet från denna undersökning utifrån intervjuer visat att social kompetens är viktig hos medarbetarna för att uppnå ett lyckat resultat. I ett projekt där samarbete med kunden sker kontinuerligt är det nödvändigt att systemutvecklarna har en god kommunikation vilken grundar sig på den sociala kompetensen. Slutsatser som kan dras från denna undersökning utifrån det empiriska materialet visar att social kompetens utgör en central roll inom XP. Systemutvecklare som använder XP behöver kunna kommunicera på ett klart och tydligt sätt, samt kunna samarbeta med övriga gruppmedlemmar för att projekten skall drivas framåt. I resultaten berörs även ytterligare kompetenser som kan vara till nytta vid användning av XP. Vidare redogörs för faktorer som kan vidtas för att uppnå kraven.
59

Agila metoders påverkan på testare / How agile methods affect testers

Chazarreta, Jasmin, Johansson, Mari January 2008 (has links)
To assure good quality the software needs to be tested to find errors and to verify that the programme meets the customer’s expectations. Traditional methods are usually used in software development and means that a number of predetermined steps are followed. By using agile methods the development can more easily be adapted to the changes on the market. With these methods the testing is carried out continuously throughout the project. This may affect both developers and testers in different ways. Most studies focus on how agile methods affect developers but there are no studies on how testers are affected by these methods. The purpose of this master thesis is therefore to study how the testers are affected when adopting the agile methods. The study was based on a theoretical and an empirical study consisting of interviews. These studies indicate five areas to investigate further, these areas were: test process, collaboration and communication, psychological effects, exchange of knowledge and education. After contacting a number of interviewees a decision was made to only study the agile methods Extreme programming and Scrum. Interviews were carried out at six different companies, where all interviewees had experience of testing in agile projects. The questions were open-ended questions and the answers were compiled to be compared with the theory in an analysis. The result showed that tests are carried out early and continuously throughout the entire development process. Since the testing is carried out parallel to the development the tester gains a better understanding for the product and there is a smaller risk for unnecessary tests to be written. The documentation produced during the test process is not affected by the agile methods but is rather dependent on other factors. These factors could be demands or the company’s business area. Collaboration and communication between testers and developers is improved since they are sitting together and have daily meetings. This also results in an increased exchange of knowledge within the team and that the team members are more informed about each others work. The result also showed that agile methods have psychological effects on the tester. Since the tester often has a unique role in the team the feeling of loneliness is larger and the opportunities to discuss tests are less than if there would have been other testers in the team. The role as a tester means to work independently with both developers and product owners to satisfy the interests of both sides. Finally, the study showed that the team needs an education when adopting agile methods to make sure that all team members have the same understanding of the methods. / För att kunna säkerställa god kvalité på mjukvara krävs att den testas för att hitta fel och visa att programmet uppfyller kundens förväntningar. Vanligen sker mjukvaruutveckling enligt så kallade traditionella metoder som innebär att ett antal förutbestämda steg följs. För att kunna anpassa mjukvaruutvecklingen efter förändringar som ständigt uppstår på marknaden används i stället agila metoder. Dessa metoder innebär bland annat att testningen sker parallellt med utvecklingen vilket kan komma att påverka utvecklarna och testarna på flera olika sätt. De flesta studier kring agila metoders påverkan fokuserar på utvecklarna och studier som visar hur testarna påverkas saknas. Syftet med examensarbetet var därför att undersöka hur testarna påverkas av införandet av agila metoder. Undersökningen baserades på teoristudier och en empirisk studie bestående av intervjuer. Dessa studier visade på fem områden att undersöka närmare, dessa var: testprocessen, samarbete och kommunikation, psykologiska effekter, kunskapsutbyte samt utbildning. Efter kontakt med ett antal intervjuobjekt beslöts att avgränsa studien till att endast studera de agila metoderna Extreme programming och Scrum. Personer från sex olika företag intervjuades, där alla intervjuobjekt hade erfarenhet av test inom agila projekt. Intervjufrågorna var fasta med öppna svarsalternativ och svaren sammanställdes sedan för att, i en analys, jämföras med den teoretiska bakgrunden. Resultatet visade att testaren utför tester tidigt och kontinuerligt genom hela utvecklingsprocessen. Genom att testningen sker parallellt med utvecklingen får testaren en ökad förståelse för produkten och risken minskar för att onödiga tester skrivs. Dokumentationen som produceras under testprocessen påverkas inte av de agila metoderna utan beror i stället på andra faktorer. Dessa faktorer kan vara efterfrågan eller vilken bransch företaget är verksam i. Samarbete och kommunikation mellan testare och utvecklare förbättras då de sitter tillsammans och har dagliga möten. Detta leder även till att kunskapsutbytet inom teamet ökar och att teammedlemmarna blir mer insatta i varandras arbeten. Resultatet visade även att agila metoder har vissa psykologiska effekter på testaren. Eftersom testaren oftast har en unik roll i teamet känner denne i större grad ensamhet i sitt arbete och tillfällena att diskutera test blir färre än om det hade varit fler testare i teamet. Rollen som testare innebär att arbeta oberoende med både utvecklare och produktägare samtidigt som båda parter ska bli nöjda. Slutligen visade undersökningen att teamet behöver utbildning vid införandet av agila metoder. Utbildningen ska ge en korrekt bild av metoderna för att alla i teamet ska få samma syn på dessa.
60

Investigating the Suitability of Extreme Programming for Global Software Development : A Systematic Review and Industrial Survey

Shah, Syed Mudassir, Amin, Muhammad January 2013 (has links)
Context: Over the past few years, Global Software Development (GSD) has emerged as an evolving trend in the software industry. The reasons behind this evolution are globalization, economic benefits, time to market, organizational and strategic location, access to skilled labor and reduction of costs. But despite its benefits, GSD also has challenges associated with communication, coordination and control. The challenges are mainly due to temporal, geographical and socio-cultural distances. Due to flexibility, and emphasis on frequent communication in agile methods, researchers have shown interest in incorporating agile methods in GSD. Extreme Programming (XP) is one of the most widely known agile methodologies that values simplicity, communication, courage and feedback. In this research study, we have investigated the suitability of XP in GSD by exploring its benefits and challenges in the state of art and state of practice. Objectives: This study aims at investigating the benefits and challenges associated with the combination of XP and GSD both in the research literature and in practice. The study also explores practices or solutions adopted in order to address the challenges of XP-GSD combination. Moreover, this study compares challenges of XP-GSD combination with the traditional GSD challenges. Methods: This research study has been accomplished with the help of a systematic literature review (SLR) and an industrial survey. For the systematic review, the snowballing approach was applied, and an initial set of papers was selected from IEEE Xplore and Google Scholar. After selecting the initial set of papers, backward snowballing was conducted by searching the reference list of the selected articles. Then, forward snowballing was conducted by looking for the citations of the selected articles. After completing the systematic review, the industrial survey was conducted to complement the findings of the literature review. The data collected from both SLR and survey was analyzed both separately and collectively. Results: Through SLR, we have identified 21 benefits, 17 challenges, and 18 solutions to the identified challenges. The benefits and challenges have been classified according to communication, coordination and control in correspondence with temporal, socio-cultural and geographical distance. From the survey, we have identified 19 benefits, 20 challenges, and 17 solutions to the identified challenges. However, 13 benefits, 9 challenges, and 8 solutions were in common. The majority of challenges found in both literature review and survey were however traditional GSD challenges. Conclusions: The scarcity of research literature in the area suggests that more work needs to be done to successfully implement XP in GSD projects. The benefits and challenges extracted from literature and industry suggest that the application of XP can be beneficial for GSD since the majority of the reported challenges are traditional GSD challenges. Nevertheless, application of XP practices can alleviate these challenges. Based on the results, we conclude that XP can be successfully adopted in GSD projects.

Page generated in 0.1246 seconds