Дисертації з теми "Duration of software development"
Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями
Ознайомтеся з топ-50 дисертацій для дослідження на тему "Duration of software development".
Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.
Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.
Переглядайте дисертації для різних дисциплін та оформлюйте правильно вашу бібліографію.
Omair, Muhammad. "Challenges in understanding software requirements in agile based offshore development." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3740.
Повний текст джерелаAhmedshareef, Zana. "Controlling schedule duration during software project execution." Thesis, University of Brighton, 2015. https://research.brighton.ac.uk/en/studentTheses/819fb81b-e3c1-40ce-bad9-f44308fdbc79.
Повний текст джерелаKaragul, Yasemin. "Factors That Affect The Duration Of Cmmi-based Software Process Improvement Initiatives." Phd thesis, METU, 2009. http://etd.lib.metu.edu.tr/upload/12610733/index.pdf.
Повний текст джерелаCMMI
Success factors
Duration factors. Enter specific words or phrases that are listed in thesis.
MacLean, Grant. "Development of a miniature, long-duration GPS tag." Thesis, Heriot-Watt University, 2008. http://hdl.handle.net/10399/2213.
Повний текст джерелаKurdi, Suparna. "Software development process and strategies used to expedite software development." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1997. http://www.collectionscanada.ca/obj/s4/f2/dsk2/ftp04/mq22136.pdf.
Повний текст джерелаKurdi, Suparna Carleton University Dissertation Management Studies. "Software development process and strategies used to expedite software development." Ottawa, 1997.
Знайти повний текст джерелаJohansson, Katrin. "Agile Software Development." Thesis, Linköpings universitet, Institutionen för teknik och naturvetenskap, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-97920.
Повний текст джерелаHellström, Andreas, and Anatoly Chervyakov. "Global Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-1687.
Повний текст джерелаUtveckling av globala programvara är ett område som den senaste tiden har uppmärksammats. Översättning är vanligtvis en fråga som människor associerar med att anpassa programvaror för ett specifikt land men det är mycket mer än det. Man kan gå djupare in i kulturella aspekter som kan påverka användargränssnitt och även mjukvarans kärna. I den här uppsatsen diskuterar vi hur dessa aspekter kan påverka utveckling av global programvara. För att genomföra vårt arbete analyserades vi först befintliga metodologier och byggde upp en utökad metodologi med förslag på hur man kan utveckla global programvara.
0737 305407 0708 230374
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.
Повний текст джерелаMoratilla, Temprado Enrique, and Bendito Enrique Ruz. "Lean Software Development and Agile Methodologies for a small Software development organization." Thesis, Högskolan i Borås, Institutionen Ingenjörshögskolan, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:hb:diva-20077.
Повний текст джерелаKe, Yuqing S. M. Massachusetts Institute of Technology. "Assessing various software development methodologies and matching software development methodologies with projects." Thesis, Massachusetts Institute of Technology, 2019. https://hdl.handle.net/1721.1/122438.
Повний текст джерелаCataloged from PDF version of thesis.
Includes bibliographical references (pages 157-158).
As the software industry evolves, various software development methodologies have become widely used in the industry. Most commonly used methodologies are Waterfall and Agile, along with less known alternatives, such as spiral and hybrid methodologies. When deciding on the methodologies, program managers tend to choose one based on the team preference or historical pattern. However, each software project is unique in its own way and has characteristics that are distinct from the previous projects the team has worked on. For each project, it is crucial to adopt a suitable methodology that help teams to produce the software that meets customer needs within schedule and budget constraints. Therefore, a practical question for every program manager is "How to find a suitable methodology for a specific project?" This thesis is aimed to help program managers answer this question.
We first explore how to evaluate each software development methodology based on the two-level decomposition of software development methodology, then analyze the project characteristics based on the situational inputs in three categories: scope, schedule and budget. Thereafter, the thesis proposes a framework to match software development methodology with a specific project. This thesis extends West's work in [1] by introducing a systems approach to assess a software project and a framework to determine the degree of compatibility between a methodology and a software project. The benefits of leveraging the systems approach are: ** The decomposition of methodologies highlights which elements in a methodology play key roles of providing the advantageous ilities over other methodologies. ** The decomposition of a project enables a program manager to evaluate the input elements of a project and gain a systems view on the project characteristics.
The framework allows program managers to compare several candidate methodologies and choose the most compatible one using the mismatch scores, weighted summations that indicate the incompatibilities between the candidate methodologies and the project based on the ilities ranking decided by the program managers. To demonstrate how to use this framework for a real world project, an example project is given. The detailed steps of calculating the mismatch scores between three methodologies and the project are shown. The proposed framework can be used as a guideline for program managers to find methodologies for different projects with the information gathered from project stakeholders. This framework has some limitations. A major one is that, since the framework is quantitative based, induvial experience is used to evaluate the elements of methodologies and factors of projects.
Further work can be done to improve the objectivity of the evaluation through the surveys of industrial experts and members of teams adopting this framework.
by Yuqing Ke.
S.M. in Engineering and Management
S.M.inEngineeringandManagement Massachusetts Institute of Technology, System Design and Management Program
Sheikh, Bilal Tahir. "Interdisciplinary Requirement Engineering for Hardware and Software Development - A Software Development Perspective." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-147886.
Повний текст джерелаKonuralp, Zeynep. "Software Process Improvement In A Software Development Environment." Master's thesis, METU, 2007. http://etd.lib.metu.edu.tr/upload/12609059/index.pdf.
Повний текст джерелаrkiye (XCOM) is studied and the static software development metrics based on a recent proposal have been evaluated. The static software metrics based improvement suggestions and the author&rsquo
s improvement suggestions discussed with the senior staff are compared. An improved peer review process is proposed. The static software development metrics have been evaluated on the improved process to see the impacts of the improvements. The improved process has been already implemented at XCOM and preliminary results have been obtained.
Abbas, Noura. "Software quality and governance in agile software development." Thesis, University of Southampton, 2009. https://eprints.soton.ac.uk/158357/.
Повний текст джерелаJohnson, Timothy Erskine. "Professional Development for Secondary School Principals: Delivery, Duration and Discernments." Diss., Virginia Tech, 2017. http://hdl.handle.net/10919/85526.
Повний текст джерелаEd. D.
Abdullahi, Abdille. "Component-based Software development." Thesis, Växjö University, School of Mathematics and Systems Engineering, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-2335.
Повний текст джерелаComponent-based Software development is a promising way to improve quality, time to market and handle the increasing complexity of software management. However, The component-based development is still a process with many problems, it is not well de_ned either from theoretical or practical point of view. This thesis gives a brief overview of Component-Based Software development and starts with brief historical evolution followed by a general explanation of the method. A detailed discussion of the underlying principles like components, component framework and compent system architecture are then presented. Some real world component stadards such as .net framework, CORBA CCM and EJB are given in detail. Finally, simple fille-sharing-program based on Apache's Avalon framework and another one based on .net framework are developed as a case study.
Nilsson, Jacob. "Development of organizer software." Thesis, University West, Department of Informatics and Mathematics, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-503.
Повний текст джерелаAlgan, Fatih Tuğlular Tuğkan. "Test driven software development/." [s.l.]: [s.n.], 2005. http://library.iyte.edu.tr/tezler/master/bilgisayaryazilimi/T000412.pdf.
Повний текст джерелаKortetjärvi, Fredrik, and Rohullah Khorami. "Software development of visualizationsystem." Thesis, Högskolan i Halmstad, Akademin för informationsteknologi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-44789.
Повний текст джерелаMarques, João Miguel Resende. ""GWB" simulation software development." Master's thesis, Universidade de Aveiro, 2009. http://hdl.handle.net/10773/1768.
Повний текст джерелаNas últimas décadas, a evolução da indústria alcançou uma extrema importância na nossa vida pessoal e também no comportamento empresarial. O conjunto de ferramentas existentes nos computadores representam um papel fundamental na comunicação, nas estratégias, nas decisões, nos sistemas de análise de processos das nossas empresas, entre outras. Os software são normalmente concebidos para permitir aos os seres humanos realizar tarefas para as quais o cérebro humano não é capaz, tais como: manipulação de grandes quantidades de informação, realização de cálculos complexos, e controlar simultâneamente muitos processos. Este projecto final foi desenvolvido exactamente sobre a disciplina de software. O presente documento mostra como uma empresa multinacional desenvolve internamente um novo software modular. Algumas técnicas serão investigadas e aplicadas a um problema real existente na empresa Robert Bosch-Bélgica, pertencente ao sector automóvel e principal responsável mundial pela produção de limpa pará-vidros. Aqui se encontrará uma sugestão para uma metodologia do ciclo de vida de um software e será explicado passo a passo todos os aspectos deste processo, desde a criação até ao desenvolvimento desta nova ferramenta de cálculo de apoio à decisão para o design. Esta metodologia foi aplicada à empresa permitindo assim a criação de um manual para o software de simulação chamado “GWB”. Mais precisamente, este projecto descreve a fase de testes, definido como a validação. Esta fase inclui um planeamento e execução de testes do software. Estes resultados foram analisados e comparados com as medições reais. Com base em conhecimentos anteriores, foi conseguido melhorar a precisão do software quer em parâmetros de produção quer em parâmetros de comportamento real dos limpa pará-brisas. Com a criação do manual e do melhoramento do software foram alcançados os dois objectivos principais envolvidos neste estágio. Este trabalho contribuiu significativamente para o desenvolvimento do software de simulação da Robert Bosch, no entanto, é sugerido um conjunto de acções futuras. Estas têm como objectivo ajudar no desenvolvimento do “GWB” para uma implementação adequada no processo de produção de limpa pará-brisas. ABSTRACT: In the last decades the evolution of software industry has reached an extreme importance in our personal daily life and also in the companies behavior. The existing sets of tools represent a vital role in our company’s communications, strategies, decisions supports, systems and process analysis, among others. Software is typically designed to enable humans to perform tasks which the human brain is not well capable, such as: handling large amounts of information, performing complex calculations, and controlling many simultaneous processes. This final project was developed based under the subject software. The present document shows how a multinational enterprise develops internally a new modulate software. Some techniques will be investigated and applied to a real life problem existing in the successful Robert Bosch-Belgium company at the automobile industry world responsible for the production of wiper blades. Here you will find a suggestion of a software life cycle methodology and an explanation step by step of all the aspects of this process from the creation to the development of a new calculation tool for design decision support. This methodology was applied to the company thus enabling to create a handbook for the simulation software called “GWB”. More precisely this project describes the testing phase, defined as validation. This phase contains the planning and execution of software tests. These results were analyzed and compared with real measurements. Based on previous knowledge, was able to improve the accuracy of the software either in production parameters or on parameters of actual behavior. With the creation of the manual and the software improvement two main objectives involved in this internship were accomplished. This work contributed significantly to the development of the Robert Bosch simulation software. However, it is suggested several future actions. To assist in the development of the “GWB” tool for a proper implementation in the wiper blade production process.
Rais, Aziz. "Interface-Based Software Development." Doctoral thesis, Vysoká škola ekonomická v Praze, 2017. http://www.nusl.cz/ntk/nusl-264730.
Повний текст джерелаSherwood, Patricia Ann. "Inspections : software development process for building defect free software applied in a small-scale software development environment /." Online version of thesis, 1990. http://hdl.handle.net/1850/10598.
Повний текст джерелаAlajrami, Sami. "Software development in the post-PC era : towards software development as a service." Thesis, University of Newcastle upon Tyne, 2017. http://hdl.handle.net/10443/3756.
Повний текст джерелаAslam, Gulshan, and Faisal Farooq. "A comparative study on Traditional Software Development Methods and Agile Software Development Methods." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH. Forskningsområde Informationsteknik, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-15383.
Повний текст джерелаMoland, Kathryn J. "An Effective Software Development Methodology for Quality Software Development in a Scheduling Department." NSUWorks, 1997. http://nsuworks.nova.edu/gscis_etd/731.
Повний текст джерелаCepa, Vasian. "Attribute enabled software development illustrated with mobile software applications." Saarbrücken VDM, Müller, 2005. http://deposit.d-nb.de/cgi-bin/dokserv?id=2939598&prov=M&dok_var=1&dok_ext=htm.
Повний текст джерелаCepa, Vasian. "Attributed enabled software development : illustrated with mobile software applications /." Saarbrücken : VDM, Verl. Dr. Müller, 2007. http://deposit.d-nb.de/cgi-bin/dokserv?id=2939598&prov=M&dok_var=1&dok_ext=htm.
Повний текст джерелаOLIVEIRA, GLORIA MARIA DE PAULA. "USING SOFTWARE ENGINEERING CONCEPTS TO DEFINE SOFTWARE DEVELOPMENT PROCESSES." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2007. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=12112@1.
Повний текст джерелаA qualidade de um produto de software depende fortemente da qualidade do processo de software utilizado em seu desenvolvimento. Para auxiliar na definição de um processo de qualidade, existem diversos modelos de processo, modelos de maturidade e normas de qualidade. Entretanto, a tarefa de elaborar ou melhorar o processo de desenvolvimento de sistemas pode se tornar árdua devido à grande quantidade de informações disponíveis e decisões a serem tomadas. Outro grande problema é o risco de definição de um processo que não seja eficaz, ou seja, não melhore a qualidade dos sistemas ou somente aumente a burocracia no desenvolvimento. Esta dissertação apresenta uma abordagem para definição de processos de desenvolvimento de sistemas baseada nos conceitos da análise de sistemas, ressaltando a analogia existente entre a elaboração de um processo e de um software. Uma das principais características da abordagem é o enfoque na área de Gerência de Riscos, visando o controle dos riscos identificados na definição do processo bem como os possíveis riscos na execução do processo de desenvolvimento.
Software quality depends heavily on the quality of the process used to develop it. In order to assist the definition of an adequate process, there are several process models, maturity models and quality standards. However, creating or improving a software development process may be tough due to the large amount of available information and decisions that have to be made. Another central problem is the risk of defining an ineffective process, that is, one that increases the bureaucracy but doesn`t improve the quality of the systems developed with its support. This dissertation presents an approach for defining software development processes based on the concepts of system analysis, based on the analogy between software and process elaboration. One of the most important attributes of this approach is the focus on Risk Management, considering the identified risks in the process definition as well the possible risks during software process execution.
Waleszonia, Nicholas W. "A SOFTWARE DEVELOPMENT DOCUMENTATION INTERNSHIP WITH BLUESPRING SOFTWARE, INC." Miami University / OhioLINK, 2011. http://rave.ohiolink.edu/etdc/view?acc_num=miami1303179151.
Повний текст джерелаOzer, Ahmet Hamdi. "Development Of An Activity Based Risk Assessment Tool Using Integrated Duration." Master's thesis, METU, 2006. http://etd.lib.metu.edu.tr/upload/12610778/index.pdf.
Повний текст джерелаeffects correctly. The aim of this thesis is to estimate the duration and cost of construction projects accurately using an activity based risk assessment method which is based on the integrated duration &ndash
cost influence network diagram model proposed by Tah and Poh (2006). Within the context of this thesis, a web based risk assessment tool using the integrated duration &ndash
cost influence network at an activity level is developed to estimate the possible cost overrun and delay in construction projects. Risk breakdown structure for construction projects is created which enables the evaluation of risk effects at an activity level. The developed tool uses Monte Carlo Simulation Technique and Risk Rating Method. The results of the developed tool are compared with those of traditional methods and the reliability of the developed tool is validated.
Williams, Robert C. "The Development of Mathematical Models for Preliminary Prediction of Highway Construction Duration." Diss., Virginia Tech, 2008. http://hdl.handle.net/10919/29483.
Повний текст джерелаPh. D.
Ahmed, Syed Rizwan. "Secure Software Development : Identification of Security Activities and Their Integration in Software Development Lifecycle." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-6170.
Повний текст джерелаDäumler, Martin. "Timing Analysis in Software Development." Master's thesis, Universitätsbibliothek Chemnitz, 2008. http://nbn-resolving.de/urn:nbn:de:bsz:ch1-200800384.
Повний текст джерелаNilsson, Jonas. "Development software for stabilization platform." Thesis, Linköpings universitet, Institutionen för teknik och naturvetenskap, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-97094.
Повний текст джерелаCuin, Henri Mathieu. "Development of tax analysis software." Thesis, McGill University, 2000. http://digitool.Library.McGill.CA:80/R/?func=dbin-jump-full&object_id=33325.
Повний текст джерелаThe report starts with a general review of mineral resource taxation and fiscal instruments available to governments. This is followed by the documentation of mineral taxation in Quebec, Ontario and British Columbia, three important Canadian mining provinces. The general design and programming of tax analysis software is then described and discussed. The thesis concludes with an analysis of two major economic factors that impact on the tax burden of a mining project, inflation and commodity price cycles.
Dumpala, Prasanth. "Software development through agile way." Thesis, University West, Department of Technology, Mathematics and Computer Science, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-568.
Повний текст джерелаThis research paper discusses the software development through agile approaches. In which we see that most of the time, agile approaches cannot use for all type of projects. But this paper is exploring the new ideas that how we can use the agile methodologies with the help of traditional approach and PSP/TSP/Software CMMI. So, the over all paper is giving the whole idea, that we can develop any type of software projects through the new agile methodology guidelines which we are describing here. As well as for solving this paper we adopted different ways in which we focused on literature study & also published research paper on agile methodology. In addition, we did this work on the base of hybrid ideology where we combined the best ways of different approaches and achieved our goals.. Where we proved that by the combination of these approaches, we can manage our projects as well as team personals in the organization successfully. And this concept for team management comes from PSP/TSP and Software CMMI. The benefit for management of this is also to get our projects with agility and personnel's training for project management.
Linder, Anders, and Johan Olsson. "Free Software For Web Development." Thesis, Linköping University, Department of Science and Technology, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-2000.
Повний текст джерелаThis thesis will look into what kind of solutions a company or a private person can use if they want to create a dynamic website using only free software. To do this we divided our work in two parts. In the first part, we developed a dynamic website for a Swedish company. On the server side we used exclusively free software with open source code. There are different meanings in how the term “free” should be used when referring to software, which we will explain in the thesis. We have also chosen to work with the XMLtechnology to see if it lives up to its expectations and to see if we could benefit from the technology. Alongside with the development of our site, another company developed a site for the same company as us, by using non-free software. We have described both implementations and compared them to see if it is possible to do the same thing with both free and non-free software.
The investigating part of our work consisted of getting information about what other people think about the free software phenomenon. To do so we created an online questionnaire where we randomly picked 100 Swedish web agencies and asked them to answer 8 questions about what kind of software they used in their company, and what they thought about free software. To get some more opinions we also interviewed two persons involved in these kinds of topics. Jan Sandred, who is a well known expert advisor in topics concerning the Information Technology area and Richard Stallman, the founder of GNU and the Free Software Movement.
The reason for dividing the thesis in two parts was to get an overall picture on the subject. We did not only want to base our results on other people’s thoughts. We wanted to make our own conclusions based on the implementation we did. This approach showed out to be very good. We got to try working with free software ourselves to see its pros and cons and build our own opinions about it. We could then proceed to compare our impressions to other people’s impressions about free software.
Traino, Anthony J. "Automation of software development metrics." [Denver, Colo.] : Regis University, 2008. http://165.236.235.140/lib/ATraino2008.pdf.
Повний текст джерелаArmstrong, Django. "A distributed software development system /." Leeds : University of Leeds, School of Computer Studies, 2008. http://www.comp.leeds.ac.uk/fyproj/reports/0708/Armstrong.pdf.
Повний текст джерелаLopes, Joao Sollari. "Software development in population genetics." Thesis, University of Reading, 2009. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.529977.
Повний текст джерелаKim, Heung-Taek. "Interface-driven software development tool." Thesis, Monterey, California. Naval Postgraduate School, 1990. http://hdl.handle.net/10945/30623.
Повний текст джерелаWe live in an age where the volume of paper-based information is steadily expanding. Personal computers have a great potential as tools for managing information. Effectiveness of using personal computers is determined by how easy it is to use them, since majority of the end-users are not computer experts. Compared with the advances in software design, the important issue of computer interface has begun to be addressed recently. There has been a research joining the database with the graphical interface to give users an easy-to-use method for accessing the database. With this, users navigate through the database by following the links from one piece of information to the next. There are several classes of softwares (languages) to build visual user interfaces: traditional, object-oriented, and interface-driven languages. This thesis, used an interface-driven software named Guide to build a prototype visual user interface to analyze the effectiveness of interface-driven software.
Baker, Wilfred G. "A software requirement development model." Master's thesis, This resource online, 1993. http://scholar.lib.vt.edu/theses/available/etd-12162009-020042/.
Повний текст джерелаRonanki, Krishna Chaitanya. "Robotic Software Development using DevOps." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-22024.
Повний текст джерелаNorman, Michael John. "SSDE : structured software development environment." Master's thesis, University of Cape Town, 1990. http://hdl.handle.net/11427/15899.
Повний текст джерелаSoftware engineers have identified many problem areas regarding the development of software. There is a need for improving system and program quality at design level, ensuring that design costs remain within the budget, and increasing the productivity of designers. Structured Software Development Environment (SSDE) provides the system designer with an interactive menu-driven environment, and a framework within which he can conveniently express and manipulate his proposed solution. This representation is in terms of both a conceptual model and a detailed software logic definition. Thus SSDE provides tools for both high-level (or logical) and low-level (or physical) design. It allows a user to follow his own preferred methodology rather than restricting him to one specific strategy. SSDE builds and maintains databases that record all design decisions. It provides the system designer with a mechanism whereby systems can easily be modified and new systems can evolve from similar existing systems. There are several auxiliary facilities as productivity aids. SSDE generates PASCAL code for low-level design constructs, ·full documentation of both the high- and low-level designs for inclusion in the project file, as well as a skeleton manual. The system was evaluated by a number of independent users. This exercise clearly demonstrated its success as an aid in expressing, understanding, manipulating and solving software development problems.
Rathor, Shekhar. "Facilitators for Software Development Agility." FIU Digital Commons, 2016. http://digitalcommons.fiu.edu/etd/3059.
Повний текст джерелаGiardino, Carmine, and Nicolò Paternoster. "Software Development in Startup Companies." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3652.
Повний текст джерелаMäkäräinen, Minna. "Software change management processes in the development of embedded software /." Espoo [Finland] : Technical Research Centre of Finland, 2000. http://www.vtt.fi/inf/pdf/publications/2000/P416.pdf.
Повний текст джерелаÁlvarez, Carlos García. "Overcoming the Limitations of Agile Software Development and Software Architecture." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-6120.
Повний текст джерелаCrunk, John. "Examining Tuckman's Team Theory in Non-collocated Software Development Teams Utilizing Collocated Software Development Methodologies." Thesis, Capella University, 2018. http://pqdtopen.proquest.com/#viewpdf?dispub=10929105.
Повний текст джерелаThe purpose of this qualitative, multi-case study was to explain Tuckman’s attributes within software development when using a collocated software designed methodology in a non-collocated setting. Agile is a software development methodology that is intended for use in a collocated setting; however, organizations are using it in a non-collocated setting, which is increasing the software errors in the final software product. The New Agile Process for Distributed Projects (NAPDiP) was developed to fix these software errors that arise when using Agile in a non-collocated setting but have not been effective. This research utilized Tuckman's team theory to explore the disparity related to why these errors still occur. The research question asked is how software development programmers explain Tuckman's attributes (i.e., forming, storming, norming, performing) on software development projects. The study adopted a qualitative model using nomothetic major and minor themes in the exploration of shared expressions of sentiments from participants. The study’s population came from seven participants located in the United States and India who met the requirement of using the Agile development methodology and work for organizations on teams with a size of at least thirty individuals from various organizations. A total of seven participants reached saturation in this multi-case study supporting the research question explored. The findings of the research demonstrated that development teams do not meet all stages and attributes of Tuckman’s team development. Future research should explore additional ways that software development teams satisfy a more significant number of Tuckman’s team development stages.
Rangevik, Alexander. "Software Development across Time Zones : A Study of Globally Distributed Software Development in Small Enterprises." Thesis, Uppsala universitet, Informationssystem, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-203325.
Повний текст джерела