Дисертації: "Agile software process models"

1

Sabar, Suneel. "Software Process Improvement and Lifecycle Models in Automotive Industry." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-69640.

Повний текст джерела

Анотація:

The quality of a product depends on the quality of the underlying process is a well known fact. Software development organizations have been struggling to decrease their cost, increase their ROI, reduce time-to-market, and enhance the quality of their products. This all depends upon the improvement in the processes they are following inside their organizations. A number of software process improvement models exist in market, e.g., CMMI, SPICE and Automotive SPICE. But before an organization can improve its development and management processes, it is very important to know whether it is following the right processes. There exist a number of software development process models, mainly categorized into Traditional and Agile, which provide the step-by-step guidance to develop and manage the software projects.The current thesis presents a study of software process improvement models in automotive industry, their weaknesses and strengths and presents a comparison of how do they relate to each other. This thesis also explores some software development models which are more famous in automotive industry, and the applicability of process improvement models in conjunction with the Agile software development models. A case study was performed at an automotive software supplier organization to investigate the experience of combining Agile practices with organization’s company-tailored software development model that was incorporating Automotive SPICE standards.

Стилі APA, Harvard, Vancouver, ISO та ін.

2

Ittner, Jan. "Software assisted tailoring of process descriptions." Saarbrücken VDM Verlag Dr. Müller, 2006. http://d-nb.info/987892932/04.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

3

Huo, Ming Computer Science &amp Engineering Faculty of Engineering UNSW. "A systematic framework of recovering process patterns from project enactment data as inputs to software process improvement." Publisher:University of New South Wales. Computer Science & Engineering, 2009. http://handle.unsw.edu.au/1959.4/43683.

Повний текст джерела

Анотація:

The study of the software development process is a relatively new research area but it is growing rapidly. This development process, also called 'the software life cycle' or 'the software process', is the methodology used throughout the industry for the planning, design, implementation, testing and maintenance that takes place during the creation of a software product. Over the years a variety of different process models have been developed. From the numerous process models now available, project managers need validation of the choice he/she has made for a software development model that he/she believes will provide the best results. Yet the quality software so sought after by software project managers can be enhanced by improving the development process through which it is delivered. Well tested, reliable evidence is needed to assist these project managers in choosing and planning a superior software process as well as for improving the adopted software process. While some guidelines for software process validation and improvement have been provided, such as CMMI, quantitative evidence is, in fact, scarce. The quantitative evidence sometimes may not be able to be obtained from high level processes that refer to a planned process model, such as a waterfall model. Furthermore, there has been little analysis of low level processes. These low level processes refer to the actions of how a development team follow a high level software process model to develop a software product. We describe these low level processes as project enactment. Normally there is a gap between the high level software process and the project enactment. In order to improve this software development process, this gap needs to be identified, measured and analyzed. In this dissertation, we propose an approach that examines the deviation between a planned process model and the project enactment of that plan. We measure the discrepancy from two aspects: consistency and inconsistency. The analytical results of the proposed approach, which include both qualitative and quantitative data, provide powerful and precise evidence for tailoring, planning and selecting any software process model. The entire approach is composed of four major phases: 1) re-presentation of the planned process model, 2) pre-processing the low level process data, 3) process mining, and 4) analysis and comparison of the recovered process model and planned process model. We evaluate the proposed approach in three case studies: a small, a medium, and a large-sized project obtained from an industrial software development organization. The appropriate data on low level processes is collected and our approach is then applied to these projects individually. From each case study we then performed a detailed analysis of the inconsistencies that had surfaced as well as the consistencies between the plan and the enactment models. An analysis of the inconsistencies revealed that several 'agile' practices were introduced during the project's development even though the planned process model was initially based on 'ISO-12207' instead of the 'agile' method. In addition, our analysis identifies the patterns in the process that are frequently repeated. The outcome of the case studies shows that our approach is applicable to a range of software projects. The conclusions derived from these case studies confirmed that our approach could be used to enhance the entire software development process, including tailoring and assessment.

Стилі APA, Harvard, Vancouver, ISO та ін.

4

Koutsoumpos, Vasileios, and Iker Marinelarena. "Agile Methodologies and Software Process Improvement Maturity Models, Current State of Practice in Small and Medium Enterprises." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4284.

Повний текст джерела

Анотація:

Abstract—Background: Software Process Improvement (SPI) maturity models have been developed to assist organizations to enhance software quality. Agile methodologies are used to ensure productivity and quality of a software product. Amongst others they are applied in Small and Medium – sized Enterprises (SMEs). However, little is known about the combination of Agile methodologies and SPI maturity models regarding SMEs and the results that could emerge, as all the current SPI models are addressed to larger organizations and all these improvement models are difficult to be used by Small and Medium – sized firms. Combinations of these methodologies could lead to improvement in the quality of the software products, better project management methodologies and organized software development framework. Objectives: The aim of this study is to identify the main Agile methodologies and SPI maturity models applied in SMEs, the combinations of these methodologies, and the results that could emerge. Through these combinations, new software development frameworks are proposed. What is more, the results of this study can be used as a guide with the appropriate combination for each SME, as a better project management methodology or as improvement in the current software engineering practices. Methods: A Systematic Literature Review was conducted, resulting in 71 selected relevant papers ranging from 2001 to 2013. Besides, a survey has been performed from June 2013 to October 2013, including 49 participants. Results: Seven Agile methodologies and six different SPI maturity models were identified and discussed. Furthermore, the combination of eight different Agile methodologies and Software Process Improvement maturity models is presented, and as well as their benefits and drawbacks that could emerge in Small and Medium – sized firms. Conclusion: The majority of the Agile methodologies and SPI maturity models are addressed to large or very large enterprises. Thus, little research has been conducted for SMEs. The combinations of the Agile methodologies and SPI maturity models are usually performed in experimental stages. However, it has been observed that such type of combination could present numerous benefits, which can also be applicable in SMEs as well. The combinations that are most common are the CMMI and XP, CMMI and Scrum, CMMI and Six Sigma, and the PRINCE2 and DSDM.
0034-636835645

Стилі APA, Harvard, Vancouver, ISO та ін.

5

Dreiseitel, Jiří. "Agilní metody vývoje software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2015. http://www.nusl.cz/ntk/nusl-264956.

Повний текст джерела

Анотація:

The thesis deals with basic principles of agile software development and describes their advantages compared to the traditional approach. Siemens, s.r.o in Brno uses combination of Scrum and Kanaban as part of organizational processes, therefore the thesis focuses mainly on the method Scrum, Kanban, Scrum-ban and compares these methods with each other. The thesis also analyzes the existing project and results were consulted with the representative of the Siemens company together with the proposals for improvement. JIRA plugin was designed and implemented base on our mutual agreement. This module extends the current tool for analyzing agile projects, this leads to better support of decision making in the context of agile processes. Benefits and further upgrades are consulted at the end of the thesis.

Стилі APA, Harvard, Vancouver, ISO та ін.

6

Laanti, M. (Maarit). "Agile Methods in large-scale software development organizations:applicability and model for adoption." Doctoral thesis, Oulun yliopisto, 2013. http://urn.fi/urn:isbn:9789526200347.

Повний текст джерела

Анотація:

Abstract Agile methods have proven to be beneficial in small organizations, and there has also been growing interest in using these methods in large organizations. This dissertation analyzes what agility and agile development are and creates a framework for using those methods in large organizations. The work starts with a Concept Analysis of Agile Software Development and agile-in-large. The theoretical part also reflects the necessary background of Complex Adaptive Systems, Lean Thinking, and Learning Organizations. Then a model of an Agile Enterprise is defined and a Framework for Organizational Development and putting Agile Methods into use in large software development organizations is presented. Large development organizations consist of many levels. It is not enough to use Agile Methods on a certain level only, e.g., on the lowest level, but all levels need to change and adapt to the new way of working. Failure to do so leads to several unwanted consequences, which are described. One possible large-scale Agile Framework is described and analyzed. The usage of Agile Methods on a large scale is validated by quantitative studies. The level of success of using an Agile Framework on a large scale is dictated by how much the same framework for operation is shared within the organization, as partial transformation leads to confusion. But smaller successes can lead into organizational learning. The framework that is proposed can be used to further enhance agility. In this way large-scale agility can be seen as a never-ending series of systematic improvements of the enterprises’ Agile Aspects
Tiivistelmä Tämä väitöskirja tarkastelee suurten organisaatioiden tarpeisiin sopivien ketterien prosessimallien mallinnusta ja käyttöä. Ketterät menetelmät on todettu hyödyllisiksi pienissä ohjelmistoyrityksissä, joten myös isoissa yrityksissä on herännyt kiinnostus ketteriä menetelmiä kohtaan. Työ alkaa ketterien menetelmien käsiteanalyysillä, ja jatkuu määrittelemällä mitä ketteryys laajassa mittakaavassa on. Teoriaosuus käsittelee taustatiedot kompleksisista sopeutuvista järjestelmistä, lean-ajattelusta ja oppivista organisaatioista tarvittavin osin. Tämän jälkeen määritellään ketterän yrityksen käsite ja esitetään malli laajamittaiselle ketteryydelle. Suurissa kehitysorganisaatioissa on monta tasoa. Ei riitä, että ketteriä menetelmiä käytetään vain jollakin (yleensä alimmalla) tasolla, vaan kaikkien organisaation tasojen täytyy sopeutua uuteen toimintatapaan. Mikäli näin ei tapahdu, saattaa tuloksena olla joukko ei-toivottavia seurauksia, jotka on myös kuvattu tässä työssä. Työssä on esitetty ja analysoitu mahdollinen malli suuren yrityksen ketteryyden toteuttamiseksi. Ketterien menetelmien käyttö isossa yrityksessä on validoitu kvantitatiivisin menetelmin. Isoissa yrityksissä ketteristä menetelmistä saatu hyöty on sidottu siihen miten hyvin koko organisaatio pystyy noudattamaan samaa ketterää toiminnan mallia – osittainen toimintatavan muutos johtaa toimintatapojen konflikteihin. Kuitenkin myös osittaiset onnistumiset voivat johtaa organisaation oppimiseen. Esitettyä mallia voidaan käyttää kehitettäessä toimintatapaa entisestään ketterämpään suuntaan. Tällä tavalla suuren organisaation ketteryys voidaan nähdä jatkuvana sarjana systemaattisia toimintatavan parannuksia, joista jokainen johtaa entistä ketterämpään toimintatapaan

Стилі APA, Harvard, Vancouver, ISO та ін.

7

Nascimento, Gustavo Vaz. "Um modelo de referência para o desenvolvimento ágil de software." Universidade de São Paulo, 2007. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-07052008-170413/.

Повний текст джерела

Анотація:

A crescente procura por software de qualidade vem causando grande pressão sobre as empresas que trabalham com desenvolvimento de software. As entregas de produtos de software dentro do prazo e custo previstos vêm se tornando, a cada dia, um diferencial importante nesse ramo de atividade. Nesse sentido, as empresas procuram por metodologias que propiciem o desenvolvimento de produtos com qualidade, e que respeitem o custo e prazo previstos. Em resposta a essas necessidades, surgiu uma nova classe de metodologias de desenvolvimento de software, conhecidas como metodologias ágeis. Este trabalho apresenta um estudo realizado sobre as principais características existentes nessa nova classe de metodologias. Uma análise permitiu a identificação de semelhanças e diferenças existentes entre elas, o que possibilitou a criação de um modelo de referência para o desenvolvimento ágil de software. O modelo foi utilizado em uma avaliação de processo baseada no modelo de avaliação da ISO/IEC 15504. A avaliação permitiu a identificação de forças e fraquezas no processo avaliado e possibilitou a definição de ações de melhoria para que o processo avaliado se assemelhasse à um processo de desenvolvimento ágil. Palavra-chave: Metodologia ágil de desenvolvimento. Modelo de referência. Processo de desenvolvimento de software. Avaliação de processo de software
The vast demand for software with quality is causing a great pressure on the companies which work with software development. The delivery of software products within the schedule and cost is becoming, every day, an important issue in this area. Therefore, companies are seeking for methodologies to develop products with quality, within the timetable and the cost. Considering these needs, it became a new class of software development methodologies, known as agile methodologies. This research shows a work done upon the main existing characteristics in this new class of methodologies. An analysis allowed the identification of the existing similarities and differences among them, which it made possible to create a new reference model for agile software development. The agile model was used in process assessment based on assessment model from ISO/IEC 15504. The assessment alowed a identification of power and weakness on the process and alowed a definition of improvement action to the process with the intention of to approach the agile development process

Стилі APA, Harvard, Vancouver, ISO та ін.

8

Ress, Ana Paula Pereira de Moraes. "Um estudo sobre a integração CMMI e desenvolvimento ágil." Universidade de São Paulo, 2013. http://www.teses.usp.br/teses/disponiveis/3/3136/tde-14102014-151014/.

Повний текст джерела

Анотація:

É possível notar no trabalho diário das empresas que a pressão por diminuir o prazo de entrega dos softwares ainda é uma realidade. Neste contexto, empresas adotam técnicas de desenvolvimento ágil de software, implementando entregas constantes e estabelecendo ciclos iterativos e curtos no processo de desenvolvimento de software. Mas, se por um lado estas técnicas visam inovar e reduzir tempo de desenvolvimento, por outro, as empresas sentem-se pressionadas a adotar a forma tradicional de manter a qualidade de software. Neste ponto, o CMMI se apresenta como um modelo de maturidade de reconhecimento mundial e é classificado na abordagem tradicional por pregar grande formalismo e foco no processo. A abordagem ágil coloca que os indivíduos e suas interações têm maior importância que os processos e as ferramentas e que ser adaptável às mudanças é mais importante do que seguir a rigor o planejado. Ao integrar estes dois modelos de abordagens distintas espera-se que as práticas ágeis possam ajudar organizações maduras a se tornarem mais flexíveis. Com o intuito de averiguar esta integração, utilizou-se o método de pesquisa de estudo de caso, de modo a se aprofundar nas empresas que possuem certificação CMMI e decidiram adotar o modelo de desenvolvimento ágil. O objetivo é levantar como estas empresas resolveram os pontos de conflito da abordagem tradicional e ágil, de modo a se tornarem mais eficazes. O estudo ainda contém um quadro de integração CMMI versus desenvolvimento ágil de modo a elencar os pontos que merecem maior atenção e esforço de adaptação, visando a concretização da integração.
It\'s possible to notice in the daily work of companies that pressure by decreasing the delivery of software is still a reality. It is in this context that companies adopt the techniques of agile software development, implementing and establishing constant deliveries and short iterative cycles in the process of software development. But if on the one hand these techniques aim to innovate and reduce development time, on the other, companies feel pressured to adopt the traditional way of maintaining the quality of software. At this point, the CMMI is presented as maturity model worldwide recognition, classified in the traditional approach for preaching extensive formalism and focus on the process, as the agile approach puts individuals and their interactions is more important than processes and tools, where being adaptable changes is more important than following the strict what was planned. By integrating these two models of different approaches, it is expected that agile practices can help organizations mature to become more flexible. In order to investigate this integration is that this study uses the research method of case study so as to deepen the companies that have decided to adopt CMMI and agile development model. The goal is to raise as these companies solved the trouble spots of the traditional approach and agile in order to become more effective. The study also contain a framework for integrating CMMI vs. Agile development in order to list the points that deserve more attention and effort to adapt in order to achieve integration.

Стилі APA, Harvard, Vancouver, ISO та ін.

9

Cintra, Caroline Carbonell. "A implementação de um processo de engenharia de requisitos baseado no Processo Unificado da Rational (RUP) alcançando nível 3 de Maturidade da Integração de Modelos de Capacidade e Maturidade (CMMI) incluindo a utilização de práticas de métodos ágeis." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2006. http://hdl.handle.net/10183/8128.

Повний текст джерела

Анотація:

Este trabalho descreve a definição e institucionalização de um processo de engenharia de requisitos que está em conformidade com as áreas de processo do CMMI (Capability Maturity Model) de Gerência de Requisitos e Desenvolvimento de Requisitos e cujos componentes (atividades, papéis, produtos de trabalho) são baseados em RUP (Rational Unified Process). A principal contribuição deste estudo é a definição de um processo de engenharia de requisitos baseado em abordagens de desenvolvimento diferenciadas, que foi implantado em uma organização específica, com foco em praticidade, eficiência e retorno do investimento. A implantação do processo em projetos reais permitiu sua experimentação, avaliação e refinamento, validando as alternativas de integração utilizadas para empregar as abordagens de desenvolvimento escolhidas. Complementando o processo proposto, como decorrência do foco em eficiência, são consideradas possibilidades de emprego de práticas de métodos ágeis na execução do processo, com o intuito de aumentar a produtividade do mesmo, sustentando sua garantia de qualidade. O processo proposto é descrito, do método de concepção aos passos envolvidos e artefatos gerados em cada atividade. Também são comentadas as etapas e áreas de trabalho envolvidas na institucionalização do trabalho.
This research depicts the definition and institutionalization of a requirements engineering process which is in conformance to CMMI (Capability Maturity Model) Requirements Management and Requirements Development process areas. The proposed process components (activities, roles, work products) are based on Rational Unified Process (RUP) process framework. The proposed process main contribution is the definition of a requirements engineering process, leveraging such diverse development approaches, which was implemented in a specific organization, focusing on practicality, efficiency and return on investment. Implementing such process in real projects has promoted its experimentation, evaluation and refinement, validating the integration alternatives used to bring together the chosen development approaches. The possibility of employing agile methods practices through the process execution is discussed, aiming at increasing the process productivity, while assuring product quality. The proposed process details are described, from method conception to each activity steps and generated artifacts. The process institutionalization phases and work areas are also commented.

Стилі APA, Harvard, Vancouver, ISO та ін.

10

Řezáč, Jakub. "Zdokonalování procesů vývoje software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2009. http://www.nusl.cz/ntk/nusl-236682.

Повний текст джерела

Анотація:

This master's thesis is oriented on software development processes improvement techniques. It presents modern approaches of process development and analyses problems of their management and usage in various life cycle phases. In connection with these techniques it brings draft of support tool, which increases automatization of processes development with pertinent cooperation with other tools, as one of presumptions of improvement of their quality.

Стилі APA, Harvard, Vancouver, ISO та ін.

11

Kajan, Miroslav. "Metody a organizace testování software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2015. http://www.nusl.cz/ntk/nusl-235007.

Повний текст джерела

Анотація:

This document's objective is to propose a set of methods for improvement of the organization and methodology of software testing and subsequent application of those in a real environment of the Siemens CZ company. The first part discusses the development models in terms of testing segment and the following section focuses specifically on the methodology of agile testing and development as a whole, including applicable metrics for evaluating various aspects of software exiting the testing phase. The third major section lets the reader get acquainted with the Siemens organization and methods of their software testing and by analyzing real-world project it assesses the strengths and weaknesses of the particular testing process and its management. The practical part of this thesis lies in the design and implementation of a plug-in for the JIRA environment. This tool is able to identify and quantify the long term status of the project phases of agile development and testing in a clear and interactive way, while the outputs are represented by clearly defined problems that can be more easily treated, as one can argue further progress.

Стилі APA, Harvard, Vancouver, ISO та ін.

12

Malik, Ahsan Nawaz &amp Kashif Masood. "Software Testing Process in Agile Development." Thesis, Blekinge Tekniska Högskola, Avdelningen för för interaktion och systemdesign, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4328.

Повний текст джерела

Анотація:

Software testing is the most important process to verify the quality of a product. Software testing in Agile development is very complex and controversial issue in literature and industry. Different people have different views about software testing in Agile methods, because most of Agile methods do not focus much on software testing activities. Agile strongly focus on the close customer collaboration, short iterations and frequent deliveries. But when it comes to software testing, then it is challenging, as Agile do not include many destructive testing practices, which are normally required for a quality product. This thesis covers the area of software testing process in Agile development. Agile development processes could be more beneficial and refined by adding testing practices and for this purpose; we proposed a concept of an independent integrated software testing team. This research also identifies the practices of Agile development in industry and the critical issues in industry while practicing Agile development. The issues of automated and manual testing, good practices in automation, and how to manage independent testing teams in Agile development are also high lightened. This report highlights every aspect of software testing process in Agile development. This research is based on literature reviews and an industrial survey.

Стилі APA, Harvard, Vancouver, ISO та ін.

13

Baca, Dejan. "Developing Secure Software : in an Agile Process." Doctoral thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00525.

Повний текст джерела

Анотація:

Background: Software developers are facing increased pressure to lower development time, release new software versions more frequent to customers and to adapt to a faster market. This new environment forces developers and companies to move from a plan based waterfall development process to a flexible agile process. By minimizing the pre development planning and instead increasing the communication between customers and developers, the agile process tries to create a new, more flexible way of working. This new way of working allows developers to focus their efforts on the features that customers want. With increased connectability and the faster feature release, the security of the software product is stressed. To develop secure software, many companies use security engineering processes that are plan heavy and inflexible. These two approaches are each others opposites and they directly contradict each other. Objective: The objective of the thesis is to evaluate how to develop secure software in an agile process. In particular, what existing best practices can be incorporated into an agile project and still provide the same benefit if the project was using a waterfall process. How the best practices can be incorporated and adapted to fit the process while still measuring the improvement. Some security engineering concepts are useful but the best practice is not agile compatible and would require extensive adaptation to integrate with an agile project. Method: The primary research method used throughout the thesis is case studies conducted in a real industry setting. As secondary methods for data collection a variety of approaches have been used, such as semi-structured interviews, workshops, study of literature, and use of historical data from the industry. Results: The security engineering best practices were investigated though a series of case studies. The base agile and security engineering compatibility was assessed in literature, by developers and in practical studies. The security engineering best practices were group based on their purpose and their compatibility with the agile process. One well known and popular best practice, automated static code analysis, was toughly investigated for its usefulness, deployment and risks of using as part of the process. For the risk analysis practices, a novel approach was introduced and improved. As such, a way of adapting existing practices to agile is proposed. Conclusion: With regard of agile and security engineering we did not find that any of the investigated processes was agile compatible. Agile is reaction driven that adapts to change, while the security engineering processes are proactive and try to prevent threats before they happen. To develop secure software in an agile process the developers should adopt and adapt key concepts from security engineering. These changes will affect the flexibility of the agile process but it is a necessity if developers want the same software security state as security engineering processes can provide.

Стилі APA, Harvard, Vancouver, ISO та ін.

14

McDonald, Andrew Gregory. "The Agile Web Engineering (AWE) process." Thesis, University of Glasgow, 2004. http://theses.gla.ac.uk/4065/.

Повний текст джерела

Анотація:

During the late 1990s commerce and academia voiced major concerns about the problems with development processes for Web Engineering. These concerns primarily centred upon the perceived chaotic and 'ad-hoc' approach to developing Web-based applications in extremely short time-scales when compared to traditional software development. Based on personal experience, conducting a survey of current practice, and collecting supporting evidence from the literature, I proposed a set of seven criteria that need to be addressed by a successful Web engineering process: 1. Short development life-cycle times; 2. Delivery of bespoke solutions and different business models; 3. Multidisciplinary development teams; 4. Small development teams working in parallel on similar tasks; 5. Business analysis and evaluation with end-users; 6. Requirements capture and rigorous testing; 7. Maintenance (evolution) of Web-based applications. These seven criteria are discussed in detail and the relevance of each to Web engineering is justified. They are then used to provide a framework to assess the suitability of a representative sample of well-known software engineering processes for Web engineering. The software engineering processes assessed comprise: the Unified Software Development Process; Dynamic Systems Development Method; and eXtreme Programming. These seven criteria were also used to motivate the definition of the Agile Web Engineering (AWE) process. A WE is based on the principles given in the Agile Manifesto and is specifically designed to address the major issues in Web Engineering, listed above. A number of other processes for Web Engineering have been proposed and a sample of these is systematically compared against the criteria given above. The Web engineering processes assessed are: Collaborative Web Development; Crystal Orange Web; Extensions to the Rational Unified Process; and Web OPEN. In order to assess the practical application of A WE, two commercial pilot projects were carried out in a Fortune 500 financial service sector company. The first commercial pilot of A WE increased end-user task completion on a retail Internet banking application from 47% to 79%. The second commercial pilot of A WE used by an Intranet development team won the company's global technology prize for 'value add' for 2003. In order to assess the effect of AWE within the company three surveys were carried out: an initial survey to establish current development practice within the company and two further surveys, one after each of the pilot projects. Despite the success of both pilots, AWE was not officially adopted by the company for Webbased projects. My surveys showed that this was primarily because there are significant cultural hurdles and organisational inertia to adopting different process approaches for different types of software development activity within the company. If other large companies, similar to the one discussed in this dissertation, are to adopt AWE, or other processes specific to Web engineering, then many will have to change their corporate goal of a one size fits all process approach for all software technology projects.

Стилі APA, Harvard, Vancouver, ISO та ін.

15

Saarnak, Stefan, and Björn Gustafsson. "A comparison of lifecycles : Agile software processes vs. projects in non-Agile software companies." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3251.

Повний текст джерела

Анотація:

In the software industry a number of different software processes has been used throughout the years to address known problems with software development, despite their intention complains has been raised that some of these are too bureaucratic. The Agile Alliance was formed in 2001 and aimed to solve this problem, they developed a manifesto and twelve principles which are supported by all Agile software processes. The purpose with the manifesto and its principles is to uncover better ways of developing software and these are by many intercessors of Agile seen as common sense and not completely new ideas. The aim with this master thesis is to answer the question if companies that explicitly claim that they do not use any Agile software process are already applying some of these ideas since they are thought of as obvious and common sense. The comparison in this thesis is performed between the project lifecycles used in specific projects by five non-Agile software companies and four identified lifecycle characteristics and two more general characteristics of the Agile software processes Extreme Programming (XP) and Dynamic Systems Development Method (DSDM). The result from the analysis of these interviews has shown that it is very difficult to decide if a software company really is working as described by XP or DSDM, this is due to that many different factors affect the final outcome. For example type of project and is the software company using different software processes for different kinds of projects. Since we just covered specific projects we were only able to conclude with absolute certainty actions that really were performed in just these projects. The project lifecycles of these software companies had some similarities with the above mentioned Agile software processes, but as a whole the analysis showed that they are quite different due to that two very important characteristics according to us, namely iterative development and frequent releases, were not applied by any of the software companies and that their project phases differed tremendously compared to XP and DSDM. Our common sense hypothesis for Agile software development was shown in this investigation to be incorrect since important activities were not performed by any of the software companies. Instead of using an iterative approach with frequent releases they all followed sequential waterfall like software processes.

Стилі APA, Harvard, Vancouver, ISO та ін.

16

Polavarapu, Sharen, and Amulya Sagarwal Jami. "A Framework to Integrate Software Process Improvements in Agile Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13373.

Повний текст джерела

Анотація:

Context: There has been a substantial growth of organizations adoptingAgile software development methodologies for various reasons. The requirementof improving the software processes with respect to traditional softwaredevelopment was clear and evident for different reasons. But the need forSoftware Process Improvements (SPI) in Agile context is unclear and thechallenges faced during the implementation of SPI in Agile software developmentare quite ambiguous. These two issues lie as a motivation for theobjectives of our study. Agile being a flexible way of software development,having a non-flexible framework is almost incompatible for implementingSPI in Agile software development. This acts as an inducement for buildingup our final objective. Objectives: The objectives of this research is to identify the need of Agile-SPI in software industry, challenges faced in implementing Agile-SPI atorganizational level and at team level and finally propose an approach forimplementing Agile-SPI based on improving practices. Methods: In order to achieve the objectives of our research, we initiallycarried out a survey, later cross verified and validated the data obtained inthe surveys through interviews. Literature review was performed to gainknowledge over the background and related work. Results: A total of 34 responses were obtained through survey. Theseresponses obtained through survey are further cross verified and validatedthrough 9 interviews. The data obtained through survey has been analyzedthrough descriptive statistics and the data obtained through interviews wasanalyzed using thematic coding. Conclusions: The need of Agile-SPI and the challenges faced by the organizationsand teams while implementing SPI in Agile software developmentwere identified. A total of 16 needs of Agile-SPI, 30 challenges faced byorganization and 37 challenges faced by team were drawn from survey andinterviews conducted. Finally, a conceptual framework has been proposedto implement SPI in Agile environment based on improving practices.

Стилі APA, Harvard, Vancouver, ISO та ін.

17

Leinonen, J. (Juho). "Evaluating software development effort estimation process in agile software development context." Master's thesis, University of Oulu, 2016. http://urn.fi/URN:NBN:fi:oulu-201605221862.

Повний текст джерела

Анотація:

This thesis studied effort estimation in software development, focusing on task level estimation that is done in Scrum teams. The thesis was done at Nokia Networks and the motivation for this topic came from the poor estimation accuracy that has been found to be present in software development. The aim of this thesis was to provide an overview of what is the current state of the art in effort estimation, survey the current practices present in Scrum teams working on LTE L2 software component at Nokia Networks Oulu, and then present suggestions for improvement based on the findings. On the basis of the literature review, three main categories of effort estimation methods were found: expert estimation, algorithmic models and machine learning. Universally there did not seem to be a single best method, but instead the differences come from the context of use. Algorithmic models and machine learning require data sets, whereas expert estimation methods rely on previous experiences and intuition of the experts. While model based methods have received a lot of research attention, the industry has largely relied on expert estimation. The current state of effort estimation at Nokia Networks was studied by conducting a survey. This survey was built based on previous survey studies that were found by conducting a systematic literature review. The questions found in the previous studies were formulated into a questionnaire, which was then used to survey the current effort estimation practices present in the participating teams. 41 people out of 100 in the participating teams participated in the survey. Survey results showed that like much of the software industry, the teams in LTE L2 relied on expert estimation methods. Most respondents had encountered overruns in the last sprint and the most often provided reason was that testing related effort estimation was hard. Forgotten subtasks were encountered frequently and requirements were found to be both unclear and to change often. Very few had had any training on effort estimation. There were no common practices for effort data collection and as such, it was mostly not done. By analyzing the survey results and reflecting them on the previous research, five suggestions for improvements were found. These were training in effort estimation, improving the information that is used during effort estimation by collaborating with specification personnel, improving testing related effort estimation by splitting acceptance testing into their own tasks, collecting and using effort data, and using Planning Poker as an effort estimation method, as it fit the context of estimation present in the teams. The study shed light on how effort estimation is done in software industry. Another contribution was the improvement suggestions, which could potentially improve the situation in the teams that participated in the survey. A third contribution was the questionnaire built during this study, as it could potentially be used to survey the current state of effort estimation in also other contexts.

Стилі APA, Harvard, Vancouver, ISO та ін.

18

Svetinovic, Davor. "Agile Architecture Recovery." Thesis, University of Waterloo, 2002. http://hdl.handle.net/10012/1065.

Повний текст джерела

Анотація:

Many software development projects start with an existing code base that has to be tightly integrated into a new system. In order to make a robust system that will achieve the desired business goals, developers must be able to understand the architecture of the old code base and its rationale. This thesis presents a lightweight approach for the recovery of software architecture. The main goal of the approach is to provide an efficient way for architecture recovery that works on small to mid-sized software systems, and gives a useful starting point on large ones. The emphasis of the process is on the use of well established development techniques and tools, in order to minimize adoption costs and maximize the return on investment.

Стилі APA, Harvard, Vancouver, ISO та ін.

19

Bitla, Krishna Sai, and Sairam Sagar Veesamsetty. "Measuring Process Flow using Metrics in Agile Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-18407.

Повний текст джерела

Анотація:

Context. Software Project management focuses on planning and executing the activities for developing software. Agile Software Project Management helps to plan shorter iterations and frequent changes to customer requirement. Developing the process flow metrics helps to monitor the process and to tune the process for the given context. Objectives. The main objectives in the thesis are to identify process flow metrics and frameworks that are suitable for measuring the process flow in Agile projects especially projects with significant dependence on hardware components. Apart from identified metrics from the literature, we identify the impact, challenges, and advantages of using agile models with the help of productivity and process flow metrics and implement them on a test phase project and compare the productivity of agile model with waterfall model. Methods. The thesis presents a two-step study. The first step was to perform a Systematic Literature Review (SLR) and collect the metrics from the literature study that can be used for the comparison of the productivity of both the processes. The Second step was to conduct a case study at Volvo Cars to get us a better understanding the impact of the agile and how the process flow metrics can be used in real time for measuring and comparison. Results. In the first step of SLR, 363 metrics that can be used by software teams have been identified of which 10 were suitable for the comparison of our current case study required by the second step of our thesis. In the second step, in the first iteration after the transition, an increase in productivity of 6.25% is achieved by the team following the agile process over the team following the traditional process. Several advantages and challenges faced during the transition have been identified which might have affected the achieved productivity. Conclusions. We conclude from the results achieved that metrics can be used as a tool to enhance the benefits of the Agile process. Process Flow metrics can be of good use to compare the difference of productivity between different processes and make improvements to the current processes. Use of process flow metrics increases the insight of all the team members on the progress of the project and guides them to enhance team performance and stay on track with the project schedule.

Стилі APA, Harvard, Vancouver, ISO та ін.

20

Bautista, Eduardo L. "A Front-Loaded Agile Software Process for Web Applications." NSUWorks, 2004. http://nsuworks.nova.edu/gscis_etd/406.

Повний текст джерела

Анотація:

The current state of application development for the World Wide Web is characterized by anarchy and ad hoc methodologies. In recent years, various hypermedia methodologies have been proposed to facilitate the deployment of Web applications. However, no standard has emerged to fulfill the need for a systematic and methodological approach to complex and dynamic Web application development. The primary goal of this dissertation was to elaborate a software development process for Web applications that focuses most of the developers' efforts and creativity on the phases that determine software requirements, on analysis and design, but that is, at the same time, flexible and adaptable so developers can respond to changes in requirements without major cost overruns or delays. In order to develop an effective process, the researcher examined the recommended tasks for Web development as provided by the literature. As a result, the new software process defines the following phases: Feasibility Study, Requirements Definition, System Specification, System Design, Program Design and Development, System Test, Implementation and Production, and Maintenance. The Web software process was developed for a particular initial-level organization. A statistical instrument, the Rating and Evaluation Guide (REG), which utilizes data gathered via questionnaire, was used to measure the perceived effectiveness of the developed software process. The new process was evaluated against a standard development methodology from the literature. The evaluation was performed by randomly selected teams of developers in an initial-level organization, and the evaluation revealed that the new Web application development process was perceived to be more effective than a generic software process provided by the literature. The scores for all twenty-six evaluation items in the REG were higher for the new software process than the generic methodology. Additionally, the new software process achieved an overall score of 175 points on the REG scale, a high rating score, which is substantially higher than the anticipated minimum score of 132. Furthermore, the new software process scored 41 out of 48 maximum points in the REG Properties category, which exceeds the anticipated minimum score of 40. A high score for the Properties category reveals the inherent attributes of a high quality methodology are included in FLASOFTi, and the high scores for all six distinct properties in this category indicate that the method's overall quality has been recognized by the participants as quite high. The findings of this study will be of practical value to initial-level organizations in which the corporate culture tends to require planning development projects thoroughly before working on them. Although the researcher recognizes that the "one-size-fits-all" approach is not appropriate in applying a software process to Web projects, that the factors that influence the development of a Web site are complex and vary from organization to organization, most computing environments that require small to mid-size Web application development projects will be able to use the new method with minor revisions to suit both the project and the organizational culture.

Стилі APA, Harvard, Vancouver, ISO та ін.

21

Deekonda, Rahul, and Prithvi Raj Sirigudi. "Assessment of Agile Maturity Models : A Survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13230.

Повний текст джерела

Анотація:

Context. In recent years Agile has gained lots of importance in the fieldof software development. Many organization and software practitioners hasalready adopted agile practice due to its flexibility in nature. Hence, agiledevelopment methodologies have been replaced to traditional developmentmethods. Agile is a family of several methodologies namely Scrum. eXtremeprogramming (XP) and several others. These several methods areembedded with different set of agile practices for the organizations to adoptand implement for their development process. But there is still a need forempirical research to understand the benefits of implementing the Agilepractices which contributes to the overall success of accomplishment of thesoftware project. Several agile maturity models have been published over adecade but not all of the models have been empirically validated. Hence,additional research in the context of agile maturity is essential and needed. Objectives. This study focus on providing a comprehensive knowledgeon the Agile Maturity Models which help in guiding the organizations regardingthe implementation of Agile practices. There are several maturitymodels published with different set of Agile practices that are recommendedto the industries. The primary aim is to compare the agile maturity maturitymodels and to investigate how the agile practices are implemented inthe industry Later the benefits and limitations faced by the software practitionersdue to implementation of agile practices are identified. Methods. For this particular research an industrial survey was conductedto identify the agile practices that are implemented in the industry. Inaddition, this survey aims at identifying the benefits and limitations of implementingthe agile practices. A literature review is conducted to identifythe order of agile practices recommended from the literature in agile MaturityModels. Results. From the available literature nine Maturity Models have beenextracted with their set of recommended agile practices. Then the resultsfrom the survey and literature are compared and analyzed to see if thereexist any commonalities or differences regarding the implementation of agilepractices in a certain order. From the results of the survey the benefitsand limitations of implementing the Agile practices in a particular order areidentified and reported. Conclusions. The findings from the literature review and the survey resultsin evaluating the agile maturity models regarding the implementationof agile practices.

Стилі APA, Harvard, Vancouver, ISO та ін.

22

Saks, Craig Sheldon. "Expanding software process improvement models beyond the software process itself." Master's thesis, University of Cape Town, 1999. http://hdl.handle.net/11427/16844.

Повний текст джерела

Анотація:

Bibliography: pages 182-188.
The problems besetting software development and maintenance are well recorded and numerous strategies have been adopted over the years to overcome the so-called "software crisis". One increasingly popular strategy focuses on managing the processes by which software is built, maintained and managed. As such, many software organisations see software process improvement initiatives as an important strategy to help them improve their software development and maintenance performance. Two of the more popular software process improvement (SPI) models used by the software industry to help them in this endeavour are the Capability Maturity Model for Software (SW-CMM) from the Software Engineering Institute and the Software Process Improvement and Capability determination (SPICE) model from the International Standards Organisation. This research begins with the supposition that, although these SPI models have added significant value to many organisations, they have a potential shortcoming in that they tend to focus almost exclusively on the software process itself and seem to neglect other organisational aspects that could contribute to improved software development and maintenance performance. This research is concerned with exploring this potential shortcoming and identifying complementary improvement areas that the SW -CMM and SPICE models fail to address adequately. A theoretical framework for extending the SW-CMM and SPICE models is proposed. Thereafter complementary improvement areas are identified and integrated with the SW-CMM and SPICE models to develop an Extended SPI Model. This Extended SPI Model adopts a systemic view of software process and IS organisational improvement by addressing a wide range of complementary improvement considerations. A case study of an SPI project is described, with the specific objective of testing and refining the Extended SPI Model. The results seem to indicate that the framework and Extended SPI Model are largely valid, although a few changes were made in light of the findings of the case study. Finally, the implications of the research for both theory and practice are discussed.

Стилі APA, Harvard, Vancouver, ISO та ін.

23

Malone, Michael W. "Process subversion in Agile Scrum software development| A phenomenological approach." Thesis, Capella University, 2014. http://pqdtopen.proquest.com/#viewpdf?dispub=3632735.

Повний текст джерела

Анотація:

This qualitative study examined the ways in which process subversion, defined as any attempt, conscious or unconscious, to work around, ignore, or turn to one's own purposes an established process, occurs in Scrum software development. Scrum is a software development methodology that uses self-managing teams and a well-defined process but does not dictate developer practices. It has been shown in previous research that problems with Scrum can cause issues with productivity and software quality. This descriptive phenomenological study specifically examined the ways in which process subversion was experienced by Scrum Masters. The Scrum Master is a coach and facilitator to the development team in Scrum. The study revealed a wide variety of perceptions of the Scrum Master's role as well as sources of subversion ranging from individuals on the development team to the structure of the organization. The study also revealed the creativity used by some Scrum Master in responding to such subversion. This study is important because it fills a gap in the extant literature in dealing with the problems that occur when an organization attempts to use Scrum as its development process, and provides insights that may be helpful in either mitigating the effects of such subversion or preventing it outright.

Стилі APA, Harvard, Vancouver, ISO та ін.

24

Moraes, Marcela Balbino Santos de. "RiPLE-SC: na agile scoping process for software product lines." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/2322.

Повний текст джерела

Анотація:

Made available in DSpace on 2014-06-12T15:56:44Z (GMT). No. of bitstreams: 2 arquivo2982_1.pdf: 2135820 bytes, checksum: df75cf5b4604b648bc295b0acd5b0db0 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2010
Fundação de Amparo à Ciência e Tecnologia do Estado de Pernambuco
As constantes mudanças e a busca por novos benefícios na indústria de software possibilitam o surgimento de novas áreas de pesquisa. Neste contexto, uma tendência que tem apresentado importantes benefícios é a área de desenvolvimento ágil de linhas de produtos de software. Linhas de produtos de software é uma importante estratégia de reuso para minimizar custos e tempo de entrega das aplicações, além de maximizar a qualidade e a produtividade do desenvolvimento de software. Entretanto, desenvolver linhas de produtos requer esforços e custos iniciais para apresentar resultados significativos, uma vez que envolve planejamento sistemático, gerenciamento de pontos comuns e variáveis dos produtos e design flexível e detalhado, aspectos que aumentam sua complexidade. Por outro lado, a abordagem ágil apresenta como foco o código e tem seu desenvolvimento realizado de forma iterativa. Além disso, esta metodologia encoraja práticas e valores como comunicação face a face, pequenas iterações, planejamento e design simples e incremental. Comparando linhas de produtos de software e métodos ágeis, diferentes aspectos são identificados. No entanto, pesquisas recentes mostram similaridades entre elas, como: aumento de qualidade e produtividade no desenvolvimento de software e redução de custos e tempo de entrega das aplicações. Portanto, visando diminuir custos e esforços iniciais necessários para adoção de uma linha de produtos de software, este trabalho propõe um processo de escopo ágil para linhas de produtos de software, unindo os benefícios das duas abordagens. O processo proposto é avaliado através de um estudo de caso industrial

Стилі APA, Harvard, Vancouver, ISO та ін.

25

Bodicherla, Saikumar, and Divyani Pamulapati. "Knowledge Management Maturity Model for Agile Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-17659.

Повний текст джерела

Анотація:

Context: Knowledge is the major aspect of an organization which enables the enterprise to be more productive and to deliver the high complexity services. Knowledge management plays a key role in agile software development because it supports cultural infrastructure esteems like collaboration, communication, and knowledge transfer. This research aims to explore how organizations that adopts Agile Software Development (ASD) implement knowledge management utilizing practices that supports the key process areas. Several knowledge management maturity models have been proposed over a decade ago but not all of the models that is specially stated knowledge Management Maturity Model (KMMM) for Agile software development. To fulfil this research gap, we introduce the maturity model which emphasize knowledge management in ASD among the practitioners. This maturity model helps to assess their knowledge management in organization and provides a road map to the organizations for any further improvement required in their processes. Objectives: In this thesis, we investigate the key process areas of knowledge management maturity models that could support agile software development. Through investigation about the key process areas, we found that the organizations should emphasis on key process areas and its practices in order to improve the software process. The objectives of this research include: Explore the key process areas and practices of knowledge management in the knowledge management maturity models. Identify the views of practitioners on knowledge management practices and key process areas for Agile software development. To propose the maturity model for Knowledge management in Agile software development among the practitioner’s opinions. Methods: In this research, we conducted two methods: Systematic mapping and Survey to fulfil our aim and objectives. We conducted Systematic mapping study through the snowballing process to investigate empirical literature about Knowledge management maturity models. To triangulate the systematic mapping results, we conducted a survey. From the survey results, we obtained the responses and were analyzed statistically using descriptive statistics. Results: From Systematic mapping, we identified 18 articles and analyzed 24 practices of Knowledge management maturity models. These practices are indicated in key process areas such as process, people, technology. Through the systematic mapping results, 9 KM practices that were found from KMMM literature were listed in the survey questionnaire and answered by software engineering practitioners. Moreover, 5 other new practices for agile have suggested in the survey that was not found in KMMM literature. To address the systematic mapping and survey results, we propose the maturity model which emphasize knowledge management practices in ASD among the practitioners. Conclusions: This thesis lists the main elements of practices that are utilized by the organization and also show the usage of maturity levels at each practice in detail. Furthermore, this thesis helps the organization's to assess the current levels of maturity that exist to each practice in a real process. Hence, the researchers can utilize the model from this thesis and further they can improve their Km in organizations.

Стилі APA, Harvard, Vancouver, ISO та ін.

26

Alam, Payam Norouzi. "Agile Process Recommendations for a Market-driven Company." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-6152.

Повний текст джерела

Анотація:

In this master thesis problems in a small market-driven software development company are discussed. Problems such as fast changes in the company are a result of the constantly changing market. The fast changes must be managed within the company with tailored process covering the needs like short time-to-market. Misunderstandings when managing ideas from marketing and challenging issues such as communication gaps between marketing staff and developers are discussed. These problem areas are identified by the case study through interviews of selected staff. The problems adhere from fast changes and lack of processes and structures. This paper has recommended several points influenced by agile software development with Scrum and XP. The recommendations are chosen to fit the problem areas identified by the interviews. They will work as a starting point for the company to improve the situation and to use XP and Scrum for further improvements.

Стилі APA, Harvard, Vancouver, ISO та ін.

27

Srirangarajan, Ananth Lall Pradeep Umphress David A. "The scrum process for independent programmers." Auburn, Ala, 2009. http://hdl.handle.net/10415/1617.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

28

Nikola, Luburić. "Integration of Software Security Design Analysis to the Agile Development Process." Phd thesis, Univerzitet u Novom Sadu, Fakultet tehničkih nauka u Novom Sadu, 2020. https://www.cris.uns.ac.rs/record.jsf?recordId=111796&source=NDLTD&language=en.

Повний текст джерела

Анотація:

This thesis presents research in the field of securesoftware engineering. Two methods aredeveloped that, when combined, facilitate theintegration of software security design analysisinto the agile development workflow. The firstmethod is a training framework for creatingworkshops aimed at teaching software engineerson how to perform security design analysis. Thesecond method is a process that expands on thesecurity design analysis method to facilitate betterintegration with the needs of the organization. Thefirst method is evaluated through a controlledexperiment, while the second method is evaluatedthrough comparative analysis and case studyanalysis, where the process is tailored andimplemented for two different software vendors.
U sklopu disertacije izvršeno je istraživanje uoblasti razvoja bezbednog softvera. Razvijene sudve metode koje zajedno omogućuju integracijubezbednosne analize dizajna softvera u procesagilnog razvoja. Prvi metod predstavlja radni okvirza konstruisanje radionica čija svrha je obukainženjera softvera kako da sprovode bezbednosnuanalizu dizajna. Drugi metod je proces kojiproširuje metod bezbednosne analize dizajnakako bi podržao bolju integraciju spram potrebaorganizacije. Prvi metod je evaluiran krozkontrolisan eksperiment, dok je drugi metodevaluiran upotrebom komparativne analize ianalize studija slučaja, gde je procesimplementiran u kontekstu dve organizacije kojese bave razvojem softvera.

Стилі APA, Harvard, Vancouver, ISO та ін.

29

Peldžius, Stasys. "Software process assessment using multiple process assessment models." Doctoral thesis, Lithuanian Academic Libraries Network (LABT), 2014. http://vddb.library.lt/obj/LT-eLABa-0001:E.02~2014~D_20141230_153238-51806.

Повний текст джерела

Анотація:

Many software companies face such problems as projects being behind schedule, exceeding the budget, customer dissatisfaction with product quality. Most of the problems arise due to immature software process of the company. The most popular process assessment models worldwide are ISO/IEC 15504 and CMMI. Companies seeking wider official recognition choose between these two models. Companies face the problem that different customers require process assessment according to different models. Therefore, it is important for companies to have an instrument that would transform company’s assessment results according to one process assessment model to another model without actual reassessment each time. The transitional process assessment model proposed in the dissertation allows the companies in the automotive, defence, space, medical, and other industries to have assessment results according to different process assessment models by performing only single process assessment. The presented method for TPAM development could be used developing transitional process assessment models in other domains. For example, service companies could implement a transitional model covering CMMI-SVC and ISO/IEC 15504-8 assessment models, and companies working in other areas could implement a transitional model covering Enterprise SPICE and FAA-iCMM assessment models.
Dauguma programinę įrangą kuriančių įmonių susiduria su problemomis: projektai vėluoja, viršijamas biudžetas, klientai nepatenkinti produktų kokybe. Daugelis problemų kyla dėl nebrandaus programų kūrimo proceso, pagal kurį įmonė įgyvendina projektus. Populiariausi pasaulyje programų kūrimo procesų vertinimo modeliai yra ISO/IEC 15504 ir CMMI. Įmonės, norėdamos būti oficialiai pripažintos platesnėje aplinkoje, renkasi vieną iš šių dviejų modelių. Įmonės susiduria su problema, kad skirtingi užsakovai reikalauja skirtingų procesų vertinimo modelių. Todėl įmonėms yra aktualu turėti instrumentą, kuris atvaizduotų jos vertinimo rezultatus iš vieno procesų vertinimo modelio į kitą, neatliekant kaskart realaus įmonės procesų vertinimo. Disertacijoje pateiktas tarpinis programų kūrimo procesų vertinimo modelis yra instrumentas įmonėms, siekiančioms kurti programų sistemas automobilių, krašto apsaugos, kosmoso, medicinos ir kitose pramonės šakose, gauti vertinimo rezultatus pagal įvairius procesų vertinimo modelius, atliekant vieną procesų vertinimą. Pagal pasiūlytą tarpinio programų kūrimo procesų vertinimo modelio kūrimo metodą galima kurti tarpinius modelius ir kitų sričių procesams vertinti. Pavyzdžiui, galima konstruoti tarpinį modelį paslaugas teikiančioms organizacijoms, apimantį CMMI-SVC ir ISO/IEC 15504-8 vertinimo modelius, arba tarpinį modelį bet kokia veikla užsiimančioms organizacijoms, apimantį Enterprise SPICE ir FAA-iCMM vertinimo modelius.

Стилі APA, Harvard, Vancouver, ISO та ін.

30

MANNARO, KATIUSCIA. "Adopting agile methodologies in distributed software development." Doctoral thesis, Università degli Studi di Cagliari, 2008. http://hdl.handle.net/11584/265978.

Повний текст джерела

Анотація:

From the second half of the '90s, some software engineering practitioners introduced a new group of software development methodologies called Agile Methodologies (Ams): they have been developed to overcome the limits of the traditional approaches in the software development. FLOSS (Free Libre Open Source Software) has been proposed as possible different solution to the software crisis that is afflicting the ICT worldwide business. If the AMs improve the quality code and allow to respond quickly to requirement changes, FLOSS approach decreases the development costs and increases the spreading of competences about the software products. A debate is shaping about the compatibility of these two approaches. Software development teams have been spreading around the world, with users in Europe, management in the USA and programmers in the USA and India. The scattering of team members and functions around the world introduces barriers to productivity, cultural and languages differences can lead to misunderstanding of requirements, time zone differences can delay project schedules. Agile methods can provide a competitive advantage by delivering early, simplifying communication and allowing the business to respond more quickly to the market by changing the software. Trying to distribute a development project in an agile way isn't easy and will involve compromises. The goal of this thesis is to determine the application of the AMs in several contexts so to define which of these can be used effectively in non traditional software projects as the distributed development.

Стилі APA, Harvard, Vancouver, ISO та ін.

31

NYMAN, NICK. "Threat Awareness in Agile Environments : Creating a Developer-Driven Threat Modeling Process for Agile Software Development Teams." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-276440.

Повний текст джерела

Анотація:

Agile principles for software development are now the industry standard for innovative projects. Agile is often hailed for being flexible, but there is also a commonly held 'truth' that agile principles and software security do not work well together. For this reason it is not uncommon to place all security responsibilities with a separate team, which goes against the agile principles of being team-centered and may affect flexibility or timeframe of a project. Additionally, software security is difficult and requires extensive experience and knowledge, something that varies a lot among software developers. This study presents a threat modeling process tailored for the specific needs and capabilities of the agile developer team. The process combines features of attack trees and abuser stories with other supplementary techniques in a pedagogical instruction manual to create an accessible and easy-to-get-started method intended to be driven by the developers themselves. The process has been developed through extensive review of extant threat modeling methods and the circumstances of the agile team, and trialed through user tests at an agile ITorganization in the financial services.
Agila principer för mjukvaruutveckling är nu industristandard för innovativa projekt. Agila metoder hyllas ofta för sin flexibilitet men det finns också en vidspridd uppfattning att agila metoder och mjukvarusäkerhet inte går bra ihop. Av den anledningen är det inte ovanligt att säkerhetsansvar och -uppgifter drivs av en separat säkerhetsgrupp, vilket går emot de agila principerna om fokus på utvecklarteamet. Detta kan få effekter både för projektets flexibilitet och dess tidsram. Dessutom är IT-säkerhet ett svårt ämne som kräver både erfarenhet och avsevärd kunskap, något som funnits variera mycket bland mjukvaruutvecklare. Den här studien presenterar en hotmodelleringsprocess som skräddarsytts för utvecklarteamets specifika behov och styrkor. Processen kombinerar funktioner från attackträd och abuser stories med andra, komplementära tekniker i en pedagogisk instruktionsmanual för att leverera en lättillgänglig och snabbstartad metod menad att drivas av utvecklarna själva. Processen har utvecklats genom omfattande studier av etablerade hotmodelleringsprocesser, samt den agila teammiljön, och testats och vidareutvecklats genom användartester hos en agil IT-organisation inom finansbranschen.

Стилі APA, Harvard, Vancouver, ISO та ін.

32

Nanduri, V. S. S. N. R. Ram. "Lean + Agile vs Seven Wastes in Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4057.

Повний текст джерела

Анотація:

Context: Software Process Improvement uses lean principles for eliminating wastes in the software development process. Waste is defined as anything that does not add value to the customer and product. The seven traditional wastes in software engineering are partially done work, extra process, extra features, waiting, motion, task switching and defects. Using the lean principles and practices, the wastes can be reduced or eliminated. It is important to know the lean practices that are widely used in software development and to know the practices, which captures the seven wastes. From the literature, the ability of waste reduction is theoretically discussed [2], but practically only little empirical evidence is available on ‘which practice is best capable in reducing specific kinds of waste.’ Objectives: Many software development organizations have adopted lean practices and agile practices for eliminating wastes of different kinds. Therefore, this study focuses on evaluating the effectiveness of lean practices in their ability to reduce the seven types of wastes associated with Lean Software Engineering. Methodology: The methodology that is used in this study is systematic literature review and industrial survey. In order to achieve the objective on evaluating the lean practices and agile practices in their ability to reduce the seven types of wastes that have more attention in research, a systematic literature review is conducted. Thereafter, to capture the effectiveness of lean practices in waste removal, a survey is designed to capture the perception of practitioners. Results: The systematic literature review has identified 53 relevant studies to the research topic. From these primary studies, the lean practices/principles, hybrid agile and lean practices, and the efficiency of agile practices in eliminating the seven wastes were identified. In addition to that, wastes that are captured by using lean practices; hybrid lean and agile practices were also identified. The reason for considering agile practices is that, agile and lean have similarities in eliminating the wastes and creating value to the customer [2][3]. Through the systematic literature review, it can be observed that researchers have not investigated all the seven wastes captured by lean practices. Thereafter, survey is the main contribution to this research where, the responses of 55 respondents from different countries were recorded. Most of the respondents are from India with 42% of the responses. We have asked the role of every respondent in their companies, and 19 respondents are Team leaders, 16 respondents are project managers and remaining people perform various other roles in software development. 38 respondents are from large-scale industry, which constitutes the majority part of the survey. The main contribution of the survey is identifying the ability of lean practices in eliminating different wastes. The respondents were asked to provide their level of agreement related to the effectiveness of each lean practices and agile practice in waste removal. A comparison between the results of SLR and survey reveals that there is a lot of variance in the perception of researchers and practitioners regarding the lean practices in eliminating wastes. Survey captures more wastes than SLR. From the results of survey, it was also identified that using the lean practices i.e. Kanban and VSM can eliminate most of the wastes. Kanban (41) and VSM (33) are mostly used and more efficient in industries. Conclusions: To conclude, the obtained results from this study will be quite useful for the real-time execution of lean practices. Team leaders, project managers, and organizations can adopt lean by choosing lean practices in accordance to the wastes that have to be eliminated from their software development process. This study has also identified the benefits and limitations of lean practices implemented in industry. This study helps researchers in providing necessary information that is very useful for further research in lean practices. The combinations of lean practices were also presented, which in terms one lean practice can compensate another in capturing all the seven wastes. In the survey, the additional wastes were identified when compared to SLR and this complements the literature. There is a considerable reach gap between the state of art and state of practice. It has been identified that VSM and Kanban practices have much attention in the literature. The remaining practices like Kotter and Kaizen are less concentrated in most of the research literature. From the literature, it is evident that none of the practices is capable of eliminating all the seven wastes in software development. VSM is capable of capturing wastes like waiting, extra process and motion. In addition, Kanban captures and eliminates wastes like partially done work, defects, task switching and extra features. With respect to the survey, Kanban and VSM practices are efficient in eliminating wastes. When the practitioners consider hybrid lean and agile practices, the combination of Kanban and Scrum, Scrum and VSM are efficient in eliminating wastes. The practitioners can consider the benefits of lean practices that are identified in this research.
V S S N R Ram Nanduri vssnrram@gmail.com

Стилі APA, Harvard, Vancouver, ISO та ін.

33

ERNSELL, KRISTINA. "Agile Application of the Project Processwithin Software Development : An investigation of the Agile project process, includingchallenges in practical application." Thesis, KTH, Industriell Management, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-147837.

Повний текст джерела

Анотація:

With its core in adaptability and change responsiveness, the Agile methodology has become a popular application of the project process within the often volatile environment of today’s software development projects. The Agile methodology emphasizes interaction between project roles over documentation and formal processes. This higher interaction increases the need for functioning information dissemination throughout the entire project process. The study was carried out at a small sized Swedish IT consultancy firm. The company wished to acquire a project management and planning software tool to support the entire project process and all involved project roles. However, awareness of areas in the project process in need of support was not entirely clear. Therefore, the objective of the study was to investigate the company’s application of the Agile project process and identify potential challenges. Furthermore, the objective was to investigate how a project management and planning software tool can support the Agile project process within software development. The thesis was carried out as an abductive case study, where qualitative data collection methods and literature studies were combined. As a result from the study, two main conclusions have been drawn. Firstly: requirements engineering, the customer role, communication, and knowledge transfer were concluded as prominent challenges in the project process in need of increased support. Secondly, a project management and planning software tool can support the project process by: increasing the communication and collaboration abilities, providing holistic and historical project overview, providing a single storage location, and providing structure. Furthermore, the study has also shown that the project management and planning software tool needs to interact with the Agile project process in order to provide successful support. As final contribution, the Interaction model was created. The model visualizes the main areas in which a project management and planning software tool must interact with the Agile process, in order to support the entire project process successfully.
Genom dess anpassningsförmåga och förändringsmottaglighet har den Agila metodiken blivit en populär tillämpning för projektprocessen inom mjukvaruutveckling, en miljö där snabba förändringar tillhör vardagen. Den Agila metodiken framhäver interaktion mellan projektroller framför dokumentation och formella processer, vilket ökar behovet av fungerande informationsspridning genom hela projektprocessen. Studien har utförts hos ett mindre svenskt IT-konsultföretag, vilket önskade att införskaffa en programvara för ett projektlednings- och planeringsverktyg som kan stötta hela projektprocessen och alla involverade projektroller. Medvetenheten kring de områden i projektprocessen som är i behov av stöd var däremot inte helt tydlig. Målet med studien var därför att undersöka företagets tillämpning av den Agila projektprocessen och identifiera eventuella utmaningar. Vidare var målet också att undersöka hur en programvara för ett projektlednings- och planeringsverktyg kan stödja den Agila projektprocessen inom mjukvaruutveckling. Examensarbetet utfördes som en abduktiv fallstudie där flera kvalitativa datainsamlingsmetoder användes tillsammans med litteraturstudier. Som resultat av studien har två huvudslutsatser dragits. För det första; kravhantering, kundrollen, kommunikation och kunskapsöverföring identifierades som framträdande utmaningar i projektprocessen i behov av ökat stöd. För det andra, att en programvara för ett projektlednings- och planeringsverktyg kan stödja projektprocessen genom att; förbättra kommunikations- och samarbetsmöjligheterna, ge en övergripande och historisk projektöverblick, fungera som en gemensam lagringsplats och tillhandahålla struktur. Vidare har studien visat att en programvara för ett projektlednings- och planeringsverktyg måste interagera med den Agila projektprocessen för att ge ett effektivt stöd. Som ett slutligt bidrag skapades "the Interaction model", vilken visualiserar huvudområdena inom vilka en programvara för ett projektlednings- och planeringsverktyg måste interagera med projektprocessen för att ge ett fullt stöd till processen.

Стилі APA, Harvard, Vancouver, ISO та ін.

34

Ullah, Malik Imran, and Waqar Ali Zaidi. "Quality Assurance Activities in Agile : Philosophy to Practice." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2145.

Повний текст джерела

Анотація:

Quality assurance activities, in software development, are the backbone of whole project. These activities are not only responsible of product quality, but also for process quality. In conventional software development QA is a separate group of QA experts. As the trends of software development moved towards agile development, QA activities also got changed. In agile development most of these activities are performed by developers. Close people collaboration, onsite customer and Test Driven Development are the approaches in agile development to achieve better product quality. In this thesis we have presented the philosophical as well as practical angle QA in agile development. Mindset of agile development revolves around product quality but there is much work to be done to impart quality of process in agile development to get it standardized and more organized. QA activities remain centric and focused to testing. Practices like SPI and following some standards are lacking in agile methodologies. In this thesis we have proposed to inject an extra layer of QA in agile projects. Purpose of injecting and extra layer, is to use the knowledge of QA experts to achieve quality in development process that will result in higher level of product quality.

Стилі APA, Harvard, Vancouver, ISO та ін.

35

Korraprolu, Srinivasa Abhilash. "Evaluation of the Relevance of Agile Maturity Models in the Industry : A Case Study." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-16788.

Повний текст джерела

Анотація:

Background. Over the years, agile software development has become increasingly popular in the software industry. One of the reasons is that agile development addressed the needs of the organisations better than the traditional models, such as the waterfall model. However, the textbook version of agile development still leaves something to be desired. This could be learnt by observing the implementation of agile methods/frameworks in the industry. The teams often customize agile methods to suit their context-specific needs. When teams in the industry decide to adopt the agile way of working, they are confronted by a choice¾either they have to implement all the agile practices at a time or adopt them over the time. The former choice has shown to come with risks and, therefore, was found that practitioners generally preferred the latter. However, agile practices are not independent, they have dependencies amongst them. A new approach to agile development emerged in the recent years known as Agile Maturity Models (AMMs). AMMs claim to offer a better path to agile adoption. In AMMs, the practices are typically introduced gradually in a particular order. However, these AMMs are multifarious and haven’t been sufficiently evaluated¾especially in the industry practice. Thus, they need to be evaluated in order to understand their relevance in the industry. Objectives. The goal is to evaluate the relevance of AMMs in the industry. By finding relevant AMMs, they could be used to alleviate the formation of agile teams and contribute toward their smoother functioning. By finding those that aren’t, this research could act as a cautionary to those practitioners who could potentially implement these AMMs and risk failure. The objectives are: identifying the agile practice dependencies in the AMMs; finding the agile practice dependencies in an agile team by conducting a case study in the industry; comparing the dependencies from the case study with those in the AMMs.  Methods. The agile maturity models were identified and analysed. A case study was conducted on an agile team to identify the dependencies between the agile practices in the industry practice. Semi-structured interviews were conducted with members of the agile team. Qualitative coding was used to analyse the collected data. The dependencies from the case study were compared with the AMMs to achieve the aim of this research. Results. It was found that dependencies between individual agile practices in the AMMs were almost never possible to be found. However, practices suggested in each maturity levels were derived. Hence, the dependencies were found in the maturity-level level. From the case study, 20 agile practice dependencies were found. 7/8 AMMs were found to be not relevant. 1 AMM couldn’t be evaluated as it heavily relied on the practitioner’s choices. Conclusions. The researchers could use the evaluation method presented in this thesis to conduct more such evaluations. By doing so, the dynamics present in the industry teams could be better understood. On their basis, relevant AMMs could be developed in the future. Such AMMs could help practitioners leverage agile development.

Стилі APA, Harvard, Vancouver, ISO та ін.

36

Wang, Cheng, and Changling Liu. "Adopting DevOps in Agile: Challenges and Solutions." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-16651.

Повний текст джерела

Анотація:

Background. DevOps is a hot topic in recent years. It emphasizes the combination of development and operation. Agile is one of the most popular development methods, but Agile mainly focused on software development part, there is no more involvement in deployment and operations. In this case, many companies consider adopting DevOps in Agile to attempt to improve the situation. Objectives. The combination of two diﬀerent technologies is bound to produce some challenges, whether it is for practitioners or researchers, it is very important to ﬁnd these challenges and mitigate them, so this article aims to investigate the challenges of adopting DevOps in Agile, then through the systematic literature review and survey questionnaire to determine the corresponding mitigation strategy. Then, in order to detail understand the process of adopting DevOps in Agile, we use interview to research the real process of adopting DevOps in agile. Methods. According to our research question, we used the systematic literature review(SLR), survey questionnaire and interview as our research methodology. Through literature review, we collected data of adopting DevOps in Agile, and summary the challenges and its relevant mitigation strategies. Then survey questionnaire helped us linking the content of literature to the industry, and compare their diﬀerence. Through the interview, we explored the actual process of adopting DevOps in Agile in industry, and correspond the challenges to the actual process. Results. Our study summarized the software development process of adopting DevOps based on Agile and revealed 23 challenges and corresponding mitigation strategies. The report also compares the commonalities and gaps between the results from the literature and the ﬁndings of real-life adopting of DevOps challenges and mitigation strategies. Conclusions. In this article, we introduced the challenges and corresponding mitigation strategies for adopting DevOps based on agile and summarize the corresponding software development process. The obvious challenges and mitigation strategies were divided into four categories: 1) People 2) Project 3) Process 4) Organization, after which we conducted further discussions based on the actual conditions and compared the results of systematic literature review and the results of questionnaire to detail explore their diﬀerence.

Стилі APA, Harvard, Vancouver, ISO та ін.

37

Abu, Baker Mohamed. "Agile Prototyping : A combination of different approaches into one main process." Thesis, Linköping University, PELAB - Programming Environment Laboratory, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-56463.

Повний текст джерела

Анотація:

Software prototyping is considered to be one of the most important tools that are used by software engineersnowadays to be able to understand the customer’s requirements, and develop software products that are efficient,reliable, and acceptable economically. Software engineers can choose any of the available prototyping approaches tobe used, based on the software that they intend to develop and how fast they would like to go during the softwaredevelopment. But generally speaking all prototyping approaches are aimed to help the engineers to understand thecustomer’s true needs, examine different software solutions and quality aspect, verification activities…etc, that mightaffect the quality of the software underdevelopment, as well as avoiding any potential development risks.A combination of several prototyping approaches, and brainstorming techniques which have fulfilled the aim of theknowledge extraction approach, have resulted in developing a prototyping approach that the engineers will use todevelop one and only one throwaway prototype to extract more knowledge than expected, in order to improve thequality of the software underdevelopment by spending more time studying it from different points of view.The knowledge extraction approach, then, was applied to the developed prototyping approach in which thedeveloped model was treated as software prototype, in order to gain more knowledge out of it. This activity hasresulted in several points of view, and improvements that were implemented to the developed model and as a resultAgile Prototyping AP, was developed. AP integrated more development approaches to the first developedprototyping model, such as: agile, documentation, software configuration management, and fractional factorialdesign, in which the main aim of developing one, and only one prototype, to help the engineers gaining moreknowledge, and reducing effort, time, and cost of development was accomplished but still developing softwareproducts with satisfying quality is done by developing an evolutionary prototyping and building throwawayprototypes on top of it.

Стилі APA, Harvard, Vancouver, ISO та ін.

38

Carleson, Hannes, and Marcus Lyth. "Evaluation of Problem Driven Software Process Improvement." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-189216.

Повний текст джерела

Анотація:

Software development is constantly growing in complexity and several newtools have been created with the aim to manage this. However, even with thisever evolving range of tools and methodology, organizations often struggle withhow to implement a new development-process, especially when implementingagile methods. The most common reason for this is because teams implementagile tools in an ad-hoc manner, without fully considering the effects this cancause. This leads to teams trying to correct their choice of methodologysomewhere during the post-planning phase, which can be devastating for aproject as it adds further complexity to the project by introducing new problemsduring the transition process. Moreover, with an existing range of tools aimedat managing this process transition, none of them have been thoroughlyevaluated, which in turn forms the problem that this thesis is centred around.This thesis explores a method transition scenario and evaluates a SoftwareProcess Improvement method oriented around the problems that theimprovement process is aiming to solve. The goal with this is to establish ifproblem oriented Software Process Improvement is viable as well as to providefurther data for the extensive research that is being done in this field. We wishto prove that the overall productivity of a software development team can beincreased even during a project by carefully managing the transition to newmethods using a problem driven approach.The research method used is of qualitative and inductive character. Data iscollected by performing a case study, via action research, and literature studies.The case study consists of iteratively managing a transition over to newmethods, at an organization in the middle of a project, using a problem drivenapproach to Software Process Improvement. Three iterations of methodimprovement are applied on the project and each iteration acts as an evaluationon how well Problem Driven Software Process Improvement works.By using the evaluation model created for this degree project, the researchershave found that problem driven Software Process Improvement is an effectivetool for managing and improving the processes of a development team.Productivity has increased with focus on tasks with highest priority beingfinished first. Transparency has increased with both development team andcompany having a clearer idea of work in progress and what is planned.Communication has grown with developers talking more freely about userstories and tasks during planning and stand-up meetings. The researchersacknowledge that the results of the study are of a limited scope and alsorecognize that further evaluation in form of more iterations are needed for acomplete evaluation.

Стилі APA, Harvard, Vancouver, ISO та ін.

39

Tanner, Maureen Cynthia. "Social conditions leading to Scrum process breakdowns during Global Agile Software Development: a theory of practice perspective." Doctoral thesis, University of Cape Town, 2013. http://hdl.handle.net/11427/17270.

Повний текст джерела

Анотація:

Global Software Development (GSD) and Agile are two popular software development trends that are gaining in popularity. In addition, more and more organisations are now seeking to engage in agile software development within the GSD context to reap the benefits of both ventures and achieve project success. Hence, agile methodologies adapted to fit the GSD context are commonly termed Global Agile Software Development (GASD) methodologies. However, because of geographical, temporal, and cultural challenges, collaboration is not easily realized in the GASD context. In addition, this work context is characterized by multiple overlapping fields of practice, which further hinder collaboration, and give rise to social challenges. Given the existence of these social challenges, there is a need to further investigate the human-centred aspect of collaboration during GASD. Following an extensive literature review on the application of Scrum and other agile methodologies in GASD between 2006 and 2011, it was noted that there is a lack of understanding of the social conditions giving rise to the social challenges experienced during GASD. It was noted that past studies have instead sought to describe these social challenges and to provide mitigating strategies in the form of best-practices, without detailing and theorising about the social conditions under which these social challenges emerge. One of the objective of the study was thus to investigate the use of Scrum during GASD. In particular, the Scrum process breakdowns experienced during and after Scrum's sprint planning and retrospective meetings were identified. The social conditions under which these breakdowns emerged were investigated in the light of Bourdieu's Theory of Practice. Scrum Process breakdowns were defined as any deviation from an ideal Scrum process (as per the Scrum methodology's guidelines) which yields to the emergence of social challenges, conflict or disagreements in the GASD team. The study was empirical and qualitative in nature and followed the positivist research paradigm. Two case studies, in line with Bonoma (1985)'s "drift" and "design" stages of case study design, were undertaken to investigate the phenomena of interest and answer the research questions. The first case focused on a distributed agile team executing a software project across South Africa (Cape Town) and Brazil (Sao Paulo) while the second case focused on a team executing an agile software project across India (Pune) and South Africa (Durban). The site selection was carefully thought out and the results from the first case informed the second case in order to add more richness in the data being gathered. In both case studies, data was collected through semi-structured interviews, documentation, field notes and direct observation. The underlying theoretical framework employed for the study was the Theory of Practice (Bourdieu, 1990). The study has identified various forms of Scrum process breakdowns occurring during and after sprint planning and retrospective meetings: » Different perceptions about task urgency at the software development sites » Disagreements on the suitability of software engineering practices » Low level of communication openness during meetings involving the whole GASD team compared to internal meetings at the sites » Impromptu changes to user stories' content and priorities » Product Owner's low level of authority » Disagreements on estimation mechanisms » Number of User Stories to be completed during the Sprint Is imposed on the team » Decisions on Scrum process updates not made by the development team » Selective invitation to retrospective meetings In addition, various social conditions were identified as possibly leading to the emergence of these Scrum process breakdowns in the GASD context: » GASD project stakeholders' low level of capital in the joint field » Different beliefs and values because of multiple fields Two theoretical propositions were derived to describe the social conditions and the corresponding Scrum process breakdowns which are likely to emerge under these conditions.

Стилі APA, Harvard, Vancouver, ISO та ін.

40

Lester, Neil. "Assisting the software reuse process through classification and retrieval of software models." Thesis, University of Ulster, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.311531.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

41

Mostafa, Abdelelah M. "Regression approach to software reliability models." [Tampa, Fla] : University of South Florida, 2006. http://purl.fcla.edu/usf/dc/et/SFE0001648.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

42

Turgeon, Josée. "A view-based system for eliciting software process models." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1999. http://www.collectionscanada.ca/obj/s4/f2/dsk1/tape7/PQDD_0017/NQ55388.pdf.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

43

Knodel, Jens. "Process models for the reconstruction of software architecture views." [S.l. : s.n.], 2002. http://www.bsz-bw.de/cgi-bin/xvms.cgi?SWB10252225.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

44

Wahl, Emil. "Reflecting and adjusting in large-scale Agile software development : A case study." Thesis, Blekinge Tekniska Högskola, Fakulteten för datavetenskaper, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-19676.

Повний текст джерела

Анотація:

Background. Agile software development has seen increased use in large-scale projects in recent times. Many larger corporations transition from using a traditional plan-driven approach for developing software to applying the Agile methodology within its processes. Large-scale Agile projects are inherently difficult to implement as there are many challenges associated with it. Many Agile frameworks have been developed to make it easier to apply the Agile methodology on a large-scale. The Agile principle of reflecting and adjusting at regular intervals can be used for developing these frameworks and allows practitioners to find ways to mitigate the challenges that large-scale Agile projects face. Objectives. This thesis aims to explore how a large-scale Agile project applies the Agile principle of reflecting and adjusting its work process, both at the overall and team level. The objectives of the thesis are to find out how the case organization regularly reflects on its work process and how it enables adjustments through the distribution of roles that can enforce changes. An additional objective is to find out what the perceived challenges are that are associated with performing regular reflections and adjustments in a large-scale Agile context. Methods. A field study is conducted at a large-scale Agile project. The field study includes direct observations of day-to-day work and scheduled meetings, interviewing project participants, and reading company documentation. The collected data is thematically analyzed to identify how the case organization reflects and adjust its work process and what the perceived challenges are. Results. Three different events are identified at the case organization to apply the Agile principle of reflecting and adjusting: reference groups to reflect on larger matters affecting much of the project, retrospective meetings to some extent to reflect within the different teams, and day-to-day reflections. All the identified roles can influence change for most parts of the process, but can only enforce change on their part of the process. Six themes are identified as perceived challenges associated with the Agile principle of reflecting and adjusting: Deadlines and time limits, multiple tasks within the teams, disinterest or misunderstanding the Agile principles, different levels of Agile, and established process and complacency. Conclusions. The case organization applies several different reflective events that address some of the challenges that are associated with large-scale Agile projects. The case organization has many other challenges relating to these events and they are all associated with other challenges previously discovered in related works.
Bakgrund. Agil mjukvaruutveckling har sett en ökad användning i storskaliga projekt under den senaste tiden. Många större företag övergår från att använda en traditionell plandriven strategi för att utveckla programvara till att tillämpa den Agila metodiken i sina processer. Det finns många utmaningar när man använder den Agila metodiken i ett storskaligt projekt. Agila projekt på stor skala är svårt att genomföra, och många Agila ramverk har utvecklats för att göra det lättare att tillämpa den Agila metodiken på stor skala. Den Agila principen att reflektera och justera med jämna mellanrum kan användas för att utveckla dessa ramverk och gör det möjligt för utövare att hitta sätt att tackla de utmaningar som storskaliga Agila projekt står inför. Syfte. Denna avhandling undersöker hur ett storskaligt Agilt projekt tillämpar den Agila principen att reflektera och justera sin arbetsprocess, både på en övergripande nivå och teamnivå. Målet med avhandlingen är att ta reda på hur organisationen regelbundet reflekterar över sin arbetsprocess och hur den möjliggör justeringar genom fördelning av roller som kan verkställa förändringarna. Ett ytterligare mål är att ta reda på vilka upplevda utmaningar som är förknippade med att utföra regelbundna reflektioner och justeringar i ett storskaligt Agilt sammanhang. Metod. En fältstudie genomförs på ett storskaligt Agilt projekt. Fältstudien inkluderar direkta observationer av det dagliga arbetet och schemalagda möten, intervjuer med projektdeltagare, och läsa företagetsdokumentation. Den insamlade datan analyseras tematiskt för att identifiera hur organisationen reflekterar och justerar sin arbetsprocess och de upplevda utmaningarna som relaterar till det. Resultat. Organisationen använder sig av tre olika sätt för att tillämpa den Agila principen för reflektion och justering: referensgrupper för att reflektera över större frågor som påverkar stora delar av projektet, retrospektiva möten i viss mån för att reflektera i de olika teamen, och dagliga reflektioner. Alla identifierade roller kan influera förändring på processen, men kan bara verkställa förändringar på sin del av processen. Sex teman identifieras som upplevda utmaningar förknippade med den Agila principen att reflektera och justera: Tidsfrister och tidsgränser, flera uppgifter inom teamen, ointresse eller missförståelse av de Agila principerna, olika nivåer av Agile, och etablerad process och självgodhet. Slutsatser. Organisationen tillämpar flera olika funktioner för reflektion som hanterar några av de utmaningar som är förknippade med storskaliga Agila projekt. Organisationen har många andra utmaningar relaterade till dessa funktioner och de är alla förknippade med andra utmaningar som tidigare upptäckts i relaterade arbeten.

Стилі APA, Harvard, Vancouver, ISO та ін.

45

Lake, Brandon. "An empirical evaluation of an agile modular software development approach : A case study with Ericsson." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-102397.

Повний текст джерела

Анотація:

Software development is a growing part of many businesses today. The software development approach that is used to develop new software may have a positive or negative impact on the efficiency and quality of the final software product. The objective of this thesis was to propose a refined software development approach and to test it empirically. The software development approach is comprised of three main subcomponents: development style, development architecture, and technical documentation. The software development approach was applied in a case study in cooperation with Ericsson. At the completion of the case study, questionnaires were administered to Ericsson employees to evaluate the success of the software development approach. The results showed that the quality of the software product was high and Ericsson was pleased with the result. The results indicated that the development approach helped the case study be successful in some of the researched areas. The end results suggest that the proposed software process has the potential to be successful in other projects of a similar type and structure.

Стилі APA, Harvard, Vancouver, ISO та ін.

46

Penmetsa, Jyothi Spandana. "AUTOMATION OF A CLOUD HOSTED APPLICATION : Performance, Automated Testing, Cloud Computing." Thesis, Blekinge Tekniska Högskola, Institutionen för kommunikationssystem, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-12849.

Повний текст джерела

Анотація:

Context: Software testing is the process of assessing quality of a software product to determine whether it matches with the existing requirements of the customer or not. Software testing is one of the “Verification and Validation,” or V&V, software practices. The two basic techniques of software testing are Black-box testing and White box testing. Black-box testing focuses solely on the outputs generated in response to the inputs supplied neglecting the internal components of the software. Whereas, White-box testing focuses on the internal mechanism of the software of any application. To explore the feasibility of black-box and white-box testing under a given set of conditions, a proper test automation framework needs to be deployed. Automation is deployed in order to reduce the manual effort and to perform testing continuously, thereby increasing the quality of the product. Objectives: In this research, cloud hosted application is automated using TestComplete tool. The objective of this thesis is to verify the functionality of cloud application such as test appliance library through automation and to measure the impact of the automation on release cycles of the organisation. Methods: Here automation is implemented using scrum methodology which is an agile development software process. Using scrum methodology, the product with working software can be delivered to the customers incrementally and empirically with updating functionalities in it. Test appliance library functionality is verified deploying testing device thereby keeping track of automatic software downloads into the testing device and licenses updating in the testing device. Results: Automation of test appliance functionality of cloud hosted application is made using TestComplete tool and impact of automation on release cycles is found reduced. Through automation of cloud hosted application, nearly 24% of reduction in level of release cycles can be observed thereby reducing the manual effort and increasing the quality of delivery. Conclusion: Automation of a cloud hosted application provides no manual effort thereby utilisation of time can be made effectively and application can be tested continuously increasing the efficiency and
AUTOMATION OF A CLOUD HOSTED APPLICATION

Стилі APA, Harvard, Vancouver, ISO та ін.

47

Johansson, Felix, and Samir Uppugunduri. "Measuring in an Agile System Development Process : A Case Study in Health IT." Thesis, Luleå tekniska universitet, Institutionen för ekonomi, teknik och samhälle, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:ltu:diva-63841.

Повний текст джерела

Анотація:

The basic aim for any software development organization is to maximize value creation for any given investment. To amplify and speed up value creation efforts, Agile Software Development has gained much popularity during the last decade as a response to a volatile and disruptive market. In an Agile environment, the team focuses on lightweight working practices, constant deliveries and customer collaboration rather than heavy documentation and inflexible processes. However, the Agile way of working has complicated how an organization can control and evaluate the process; allowing organizations to believe that all Agile processes is the ideal process. This master thesis was conducted as a case study at Sectra ImIT, an Agile Health IT company working with Imaging and IT solutions that is currently in an early phase of introducing metrics in the System Development process. The purpose of this thesis was to investigate and suggest how the organization could use metrics to control and evaluate value creation in the System Development process. It also aimed to provide strategic recommendations to such an organization how they could continue their work with implementing and using metrics. The descriptive and exploratory purpose of this study was realized through unstructured and semistructured interviews with people involved in the process as well as observations. One of the major findings in this thesis is related to a missing feedback loop from defects occurring at customer site to the internal System Development process. Therefore, this study developed and implemented a concept to generate this feedback. The concept builds on defect information that can be used both to generate feedback and statistics for evaluation. The second major finding in this study is related to the identification of barriers to why the organization is not using metrics in teams to control and evaluate the process. Based on these findings, the authors presented several recommendations that should be considered to create a culture where teams are using metrics to learn more about the process. The first recommendation is that the organization should set guidelines among teams of what should, and is desired to be evaluated with focus on information need. Secondly, metrics need to be higher prioritized through directives from management granting team’s resources to manage metrics, which at the same time provides incentives that the organization believe metrics could improve their work. Thirdly, based on the company context, teams should identify metrics based on an information need derived from their prioritizations, changes, decisions and what is currently left unanswered. Finally, metrics should primarily be used to provide means for discussion and provide feedback with focus on trends rather than absolute numbers.
Det huvudsakliga målet för ett godtyckligt företag inom mjukvaruutveckling är att maximera det värde som skapas i varje enskild investering. För att förstärka och snabba upp värdeskapande har Agil mjukvaruutveckling växt i popularitet som en respons mot volatila och osäkra marknader. I en Agil miljö fokuserar grupper på ”lättviktade” arbetsmetoder, kontinuerliga leveranser och kundsamarbeten över det tidigare arbetssättet som bestod av mycket dokumentation och inflexibla processer. Samtidigt har det Agila arbetssättet gjort det svårt för organisationer att kontrollera och utvärdera processen, vilket har resulterat i att organisationer antar att deras Agila process är ideal och välfungerande med avsaknad av belägg för det. Detta examensarbete genomfördes som en fallstudie på Sectra ImIT, ett Agilt företag inom medicinsk teknik med fokus på bildhanteringssystem och IT lösningar. Företaget är i en tidig fas av att undersöka och introducera mätetal i systemutvecklingsprocessen, där syftet med examensarbetet var att utvärdera och föreslå hur organisationen kunde använda mätetal för att kontrollera och utvärdera värdeskapande i processen. Därtill ämnade studien även att ge strategiska förslag på hur företaget i framtiden kan arbeta med att implementera och använda sig av mätetal. Det deskriptiva och explorativa syftet realiserades genom ostrukturerade och semi-strukturerade intervjuer samt observationer med människor som dagligen arbetade inom processen. En iakttagelse var kopplad till avsaknaden av återkoppling mellan de defekter som uppkommer ute hos kund tillbaka till systemutvecklingsprocessen. Detta resulterade i ett koncept som utvecklades och implementerades av författarna med syfte att skapa återkoppling och möjlighet till statistisk utvärdering av processen som helhet. Den andra iakttagelsen berörde ett antal anledningar till varför organisationen inte använder mätetal i teams för att kontrollera och utvärdera processen. Baserat på en analys av dessa presenterar författarna flertalet rekommendationer som företaget borde ta hänsyn till för att skapa en kultur som främjar användandet av mätetal för att skapa ytterligare förståelse för processen. Den första rekommendationen är att organisationen bör diskutera riktlinjer gemensamt för teams gällande vad som anses önskvärt att utvärdera, med fokus på informationsbehov. Därtill bör organisationen uppmana teams till att allokera mer resurser på mätetal, vilket samtidigt ger incitament att det är något företaget tror kan hjälpa teams att bli bättre. Utifrån företagets kontext bör teams själva tillåtas att identifiera mätetal baserat på deras informationsbehov som ett resultat av exempelvis prioriteringar, förändringar, beslut och vad som för tillfället är obesvarat. Slutligen ska mätetal användas i huvudsak som en grund för diskussion och feedback med fokus på trender snarare än att uppnå specifika mål.

Стилі APA, Harvard, Vancouver, ISO та ін.

48

Aslan, Ercan. "A Cots-software Requirements Elicitation Method From Business Process Models." Master's thesis, METU, 2003. http://etd.lib.metu.edu.tr/upload/260208/index.pdf.

Повний текст джерела

Анотація:

In this thesis, COTS-software requirements elicitation, which is an input for RFP in software intensive automation system&rsquo
s acquisition, is examined. Business Process Models are used for COTS-software requirements elicitation. A new method, namely CREB, is developed to meet the requirements of COTS-software. A software intensive system acquisition of a military organization is used to validate the method.

Стилі APA, Harvard, Vancouver, ISO та ін.

49

Pérez, Graciela. "A system for evaluating the fitness of software process models /." Thesis, McGill University, 1994. http://digitool.Library.McGill.CA:80/R/?func=dbin-jump-full&object_id=55523.

Повний текст джерела

Анотація:

The design, selection, reuse, improvement and customization of software process models are recognized to be important for software development, and there is an urgent need for methods and tools to assist in these tasks. This thesis describes a method and supporting tool to address these needs. The method is based on an empirically derived contingency model consisting of a definition of the characteristics of a software process model and an environment, and their inter-relationships. The tool, on the other hand, makes the method operational by accepting, as input, the characteristics of a software process and its environment and producing, as output: (i) an evaluation of how fit (or congruent) the model of the process is in the given environment, and (ii) design suggestions for building a customized process model. In this thesis, we demonstrate the usage of the tool by giving examples from three applications: fitness evaluation and improvement of a process model, selection of the fittest process model from among several models, and process reuse. The data used in the examples was gathered in a field study of fifteen software projects, and the method was validated using data from 6 of these projects.

Стилі APA, Harvard, Vancouver, ISO та ін.

50

Moneta, Francesco Maria. "State of the art techniques for creating secure software within the Agile process: a systematic literature review." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2018. http://amslaurea.unibo.it/16803/.

Повний текст джерела

Анотація:

Agile processes have become ubiquitous in the software development community, and are used by the majority of companies. At the same time, the need for secure and trustworthy software has been steadily growing. Agile software processes nonetheless have proven difficult to integrate with the preexisting security frameworks developed for the Waterfall processes. This thesis presents the results of a systematic literature review that investigates solutions to this problem. The research questions to which the researcher tried to answer are: "which are the latest solutions to enhance the security of the software developed using the Agile process??" and "Which of the solutions discussed have performed best pilot studies?". This study analyzed 39 papers published between 2011 and 2018. The results were ordered according to which exhibited the highest consensus and coded into four sets. The most salient suggestions were: increase the training of the developers, add dedicated security figures to the development team, hybridize security solution from the waterfall processes and add security artifacts such as the "security backlog" and "evil user stories" to Agile.

Стилі APA, Harvard, Vancouver, ISO та ін.

Дисертації з теми "Agile software process models"

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями