Spelling suggestions: "subject:"[een] EXTREME PROGRAMMING"" "subject:"[enn] EXTREME PROGRAMMING""
31 |
Simulação multi-agente em gestão de projetos de software em ambientes de programação extremaAlves, Flávio de Oliveira January 2009 (has links)
Nesta dissertação, o autor aborda a dificuldade de prever-se o desempenho dos recursos humanos em um processo de desenvolvimento de software em um ambiente de Programação Extrema (XP) (BECK, 2000) e propõe uma solução com potencial para minimizar esse problema. Especificamente, o problema, a ser tratado neste trabalho, consiste em melhorar as previsões dos gerentes de projeto – no âmbito do ambiente mencionado - com relação ao desempenho dos recursos humanos na geração de valor para o negócio. Tal valor para o negócio é alcançado através da implementação, por parte dos programadores, das diversas funcionalidades de um sistema de software. Para a construção da solução proposta neste trabalho, o autor analisou um sistema XP de desenvolvimento de software (composto por ambiente, pessoas e processo), conforme o processo de modelagem proposto por Streit (2006) e apoiado na revisão da literatura relevante. Em seguida, o autor estruturou esse sistema em um modelo conceitual para, finalmente, desenvolver um modelo computacional do sistema analisado, baseado em múltiplos agentes inteligentes modelados conforme a arquitetura Beliefs-Desires-Intentions (BDI), ou Crenças-Desejos-Intenções. O modelo computacional da simulação multi-agente foi desenvolvido com o apoio da ferramenta SeSAm (KLÜGL, 2006). Testado através da experimentação estatística 2k Fatorial (LAW e KELTON, 2000), o modelo de simulação multi-agente de processos de desenvolvimento de software, para ambientes de Programação Extrema, demonstrou eficácia e aplicabilidade prática sobre o problema em questão. / In this research, the author adresses the difficulty to forecast the performance of the human resources in a software development process in an Extreme Programming (XP) (BECK, 2000) environment and proposes a solution that may be suitable to minimize this problem. Specifically, the main problem consists on how to improve the assumptions of the project managers - in the aforementioned environment - related with the human resources performance in generating value for the business. This value generation is reached through the implementation, by programmers, of the various functionalities of a software system. To build the solution proposed in this research, the author analysed a XP software development system (composed of environment, people and process) considering the modeling process proposed by Streit (2006) and also the relevant related works. This system was later structured in a conceptual model and, in sequence, in a computational model based on the Beliefs-Desires-Intentions (BDI) architecture of intelligent agents. The computational model of the multi-agent simulation was build with the support of the SeSAm (KLÜGL, 2006) tool. The tests of the multi-agent simulation of XP software develoment process model used the 2k Factorial statistical experimentation (LAW e KELTON, 2000) and their results demonstrated the effectiveness and practical applicability of the model for the research problem.
|
32 |
The agile methods : an analytical comparison of five agile methods and an investigation of their target environment : a thesis presented in partial fulfillment of the requirements for the degree of Master of Information Sciences in Information Systems at Massey University, Palmerston North, New ZealandStrode, Diane Elizabeth Unknown Date (has links)
This study defines the systems development methodologies named agile methods and investigates the environmental conditions where agile methods are most suitable. A definition of agile methods was developed using an analytical comparativeframework to investigate five of the earliest published agile methods; Dynamic SystemsDevelopment Method, Extreme Programming, Scrum, Adaptive Software Development,and Crystal Methods. The framework decomposed each method into its componentparts; philosophy, models, techniques, tools, scope, outputs, practice, and the extent towhich the method may be adapted to a situation. Based on this analysis and a literaturereview, a theoretical model of the target environment for agile methods was developed.This theoretical model is a proposed set of organisation, people, project, technology,and domain factors that relate to the successful use of an agile method.A mixed method research methodology was used. A qualitative design, consisting ofpositivist case studies, was used to test the theoretical model. Data was gathered fromnine software development projects, both agile and non-agile, using questionnaires andinterviews of project leaders. Then cross-case analysis was carried out on each projectfactor in the theoretical model. The relationship between environmental factors andagile method usage was investigated using non-parametric quantitative data analysis.This led to a revised model of the target environment for agile methods. The empiricaldata showed that specific organisational culture factors correlate with effective use of anagile method. These include the organisational characteristics of feedback and learning,teamwork, empowerment of people, collaboration, leadership, loyalty, and a resultsorientedculture that values entrepreneurship, innovation and risk taking.This research is significant for method users, those carrying out empirical research into agile methods, and those carrying out studies of systems development methodologies.
|
33 |
Agile Methods (Scrum, XP) Applying into Small (Micro) Enterprise Brusiness Website Development : A case study of Dalsland Travel AB website development projectShen, Bin January 2013 (has links)
No description available.
|
34 |
Dynamiska metoder för små systemutvecklingsprojektAhmed, Reham January 2003 (has links)
<p>Litteratur inom systemutvecklingsområdet visar behov av nya snabbare systemutvecklingsmetoder. Orsaken är komplexiteten både i systemutvecklings</p><p>projekten och i organisationer, där systemutveckling sker. Nu föredras små projekt, som omfattar färre än tio deltagare och genomförs på mindre än ett år. De traditionella systemutvecklingsmetoder anses vara lämpliga för stora projekt. Det finns nya systemutvecklingsmetoder, som får benämningen dynamiska metoder, för små projekt. I detta examensarbete studeras faktorer för två dynamiska metoder som gör dem lämpliga för små projekt. De två dynamiska metoderna som kommer att studeras är Extreme Programming och en specifik dokumenterad anpassning av RUP.</p><p>Syftet med detta examensarbete är att studera metoddokumentationen för två dynamiska metoder för att reda ut i vilken utsträckning de passar för små projekt. Ett ytterligare syfte är att genom analys av andras erfarenheter om tillämpningar av de två metoderna redogöra för det som styrker argumenten om deras lämplighet för små projekt.</p><p>För att besvara frågeställningen studerades litteratur och ett antal artiklar. Två telefonintervjuer genomfördes också för att besvara en av de två delfrågorna, som tillsammans utgör frågeställningen för denna studie. Resultatet visar att den specifikt dokumenterade anpassade RUP inte följer alla aspekter för små projekt. Däremot följer Extreme Programming alla de aspekterna.</p>
|
35 |
Agila metoders påverkan på testare / How agile methods affect testersChazarreta, Jasmin, Johansson, Mari January 2008 (has links)
<p>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.</p><p>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.</p><p>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.</p> / <p>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.</p><p>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.</p><p>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.</p>
|
36 |
Jdp: A Tool To Support Pair Programming In Distributed EnvironmentsKarapinar, Hasan Turan 01 July 2005 (has links) (PDF)
This thesis focuses on the development of a distributed pair programming tool that enables two programmers to generate code together in JBuilder editor over the web. First, software development processes are generally reviewed and Extreme
Programming, Distributed Extreme Programming, and Distributed Pair Programming issues are examined. The tools that enable Distributed Pair Programming are compared. This thesis also specifies the functional requirements of the newly presented tool and includes information about its design and
implementation processes. Finally, an evaluation is given by indicating the positive and negative sides of the tool.
|
37 |
Towards a philosophical understanding of agile software methodologies the case of Kuhn versus Popper /Northover, Mandy. January 2008 (has links)
Thesis (MSc (Computer science))--University of Pretoria, 2008. / Includes bibliographical references.
|
38 |
Herramientas de Software de Apoyo al Desarrollo con Metodologías Ágiles en Miras a la Certificación de ProcesosOrtega Concha, Ignacio Emilio January 2008 (has links)
Cada vez es más frecuente ver que la industria de software se base en estándares y
certificaciones de calidad. Esto ha despertado la iniciativa por parte de las empresas a
realizar esfuerzos para mejorar sus procesos de desarrollo de forma continua, con la idea de
obtener ventajas competitivas, y abarcar una mayor zona de mercado. Sin embargo, para las
empresas, el proceso de adoptar las prácticas orientadas a una mejora de procesos resulta
tener un elevado costo, que estas no siempre pueden abordar. Es aquí donde surge la idea
de utilizar algunas de las prácticas de las metodologías ágiles, principalmente gracias a su
nuevo enfoque de cómo lograr proyectos exitosos y además a la poca inversión inicial que
requieren. Con el objeto de apoyar una de las iniciativas de la Agenda Digital, ha surgido el
Proyecto Tutelkán, cuyo propósito es crear un mecanismo sustentable, que mediante un
proceso público de referencia y una comunidad activa de apoyo, permita a las empresas
nacionales contar con las herramientas y asistencia necesarias para iniciar la mejora de los
procesos de desarrollo en miras a una certificación.
Identificando necesidades reales del ambiente nacional, gracias a la inserción dentro
de la industria se construyeron herramientas para el apoyo de administración de
requerimientos y de riesgos, que reúnen tanto características provenientes de las
metodologías tradicionales como de las metodologías ágiles, formando una plataforma de
trabajo extensible e interoperable, gracias a su orientación de servicios. Todo con el fin de
apoyar con herramientas de software que agreguen valor a este mejoramiento de procesos
en el desarrollo, sin hacerlo más complejo o burocrático. La acogida desde las empresas fue
positiva, reconociendo el valor que aporta a mejorar sus procesos y el apoyo que otorga
para mejorar la imagen externa.
|
39 |
Email meets issue-tracking: a prototype implementationKwinana, Zukhanye N 11 June 2013 (has links)
The use of electronic mail (email) has evolved from sending simple messages to task delegation and management. Most mail clients, however, have not kept up with the evolution and as a result have limited task management features available. On the other hand, while issue tracking systems offer useful task management functionality, they are not as widespread as emails and also have a few drawbacks. This thesis reports on the exploration of the integration of the ubiquitous nature of email with the task management features of issue-tracking systems. We explore this using simple ad-hoc as well as semi-automated tasks. With these two working together, tasks can be delegated from email clients without needing to switch between the two environments. It brings some of the benefits of issue tracking systems closer to our email users.The system is developed using Microsoft VisuaI Studio.NET. with the code written in C#. The eXtreme Programming (XP) methodology was used during the development of the proof-of-concept prototype that demonstrates the integration of the two environments, as we were faced at first with vague requirements bound to change, as we better understood the problem domain through our development. XP allowed us to skip an extended and comprehensive initial design process and incrementally develop the system, making refinements and extensions as we encountered the need for them. This alleviated the need to make upfront decisions that were based on minimal knowledge of what to expect during development. This thesis describes the implementation of the prototype and the decisions made with each step taken towards developing an email-based issue tracking system. With the two environments working together, we can now easily track issues from our email clients without needing to switch to another system. / KMBT_363 / Adobe Acrobat 9.54 Paper Capture Plug-in
|
40 |
Simulação multi-agente em gestão de projetos de software em ambientes de programação extremaAlves, Flávio de Oliveira January 2009 (has links)
Nesta dissertação, o autor aborda a dificuldade de prever-se o desempenho dos recursos humanos em um processo de desenvolvimento de software em um ambiente de Programação Extrema (XP) (BECK, 2000) e propõe uma solução com potencial para minimizar esse problema. Especificamente, o problema, a ser tratado neste trabalho, consiste em melhorar as previsões dos gerentes de projeto – no âmbito do ambiente mencionado - com relação ao desempenho dos recursos humanos na geração de valor para o negócio. Tal valor para o negócio é alcançado através da implementação, por parte dos programadores, das diversas funcionalidades de um sistema de software. Para a construção da solução proposta neste trabalho, o autor analisou um sistema XP de desenvolvimento de software (composto por ambiente, pessoas e processo), conforme o processo de modelagem proposto por Streit (2006) e apoiado na revisão da literatura relevante. Em seguida, o autor estruturou esse sistema em um modelo conceitual para, finalmente, desenvolver um modelo computacional do sistema analisado, baseado em múltiplos agentes inteligentes modelados conforme a arquitetura Beliefs-Desires-Intentions (BDI), ou Crenças-Desejos-Intenções. O modelo computacional da simulação multi-agente foi desenvolvido com o apoio da ferramenta SeSAm (KLÜGL, 2006). Testado através da experimentação estatística 2k Fatorial (LAW e KELTON, 2000), o modelo de simulação multi-agente de processos de desenvolvimento de software, para ambientes de Programação Extrema, demonstrou eficácia e aplicabilidade prática sobre o problema em questão. / In this research, the author adresses the difficulty to forecast the performance of the human resources in a software development process in an Extreme Programming (XP) (BECK, 2000) environment and proposes a solution that may be suitable to minimize this problem. Specifically, the main problem consists on how to improve the assumptions of the project managers - in the aforementioned environment - related with the human resources performance in generating value for the business. This value generation is reached through the implementation, by programmers, of the various functionalities of a software system. To build the solution proposed in this research, the author analysed a XP software development system (composed of environment, people and process) considering the modeling process proposed by Streit (2006) and also the relevant related works. This system was later structured in a conceptual model and, in sequence, in a computational model based on the Beliefs-Desires-Intentions (BDI) architecture of intelligent agents. The computational model of the multi-agent simulation was build with the support of the SeSAm (KLÜGL, 2006) tool. The tests of the multi-agent simulation of XP software develoment process model used the 2k Factorial statistical experimentation (LAW e KELTON, 2000) and their results demonstrated the effectiveness and practical applicability of the model for the research problem.
|
Page generated in 0.035 seconds