Kliknij ten link, aby zobaczyć inne rodzaje publikacji na ten temat: Software development.
Rozprawy doktorskie na temat „Software development”
Utwórz poprawne odniesienie w stylach APA, MLA, Chicago, Harvard i wielu innych
Sprawdź 50 najlepszych rozpraw doktorskich naukowych na temat „Software development”.
Przycisk „Dodaj do bibliografii” jest dostępny obok każdej pracy w bibliografii. Użyj go – a my automatycznie utworzymy odniesienie bibliograficzne do wybranej pracy w stylu cytowania, którego potrzebujesz: APA, MLA, Harvard, Chicago, Vancouver itp.
Możesz również pobrać pełny tekst publikacji naukowej w formacie „.pdf” i przeczytać adnotację do pracy online, jeśli odpowiednie parametry są dostępne w metadanych.
Przeglądaj rozprawy doktorskie z różnych dziedzin i twórz odpowiednie bibliografie.
1
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.
Pełny tekst źródła
2
Kurdi, Suparna Carleton University Dissertation Management Studies. "Software development process and strategies used to expedite software development." Ottawa, 1997.
Znajdź pełny tekst źródła
3
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.
Pełny tekst źródłaStreszczenie:
Global Software Development is an area that has been recently highlighted. Translation is usually an issue that people associate with adapting software for a specific country but it is much more than that. Through text representation and data formatting you can go deep into cultural aspects that affect the user interface and even the core functionality. In this thesis we will discuss just how these matters can affect development of global software. To carry out the investigation we analyzed current approaches and references and build up an extended methodology with suggestions to develop global software applications.<br>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.<br>0737 305407 0708 230374
4
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.
Pełny tekst źródłaStreszczenie:
Systemutvecklingsföretag är på väg in i en turbulent period. Globaliseringen ger en total konkurrens som kräver snabba anpassningar. Detta ställer krav på reaktionssnabbhet. En framtid där vi slipper ogenomträngliga lösningar ligger nu inom räckhåll. Ett nytt synsätt har börjat ta form och konkurrerar nu ut den gamla, processorienterade synen på systemutveckling. Testdriven utveckling, refactoring och par-programmering är inslag i denna nya mera lättrörliga utvecklingsmetodiken. Detta synsätt går under namnet Agile Software Development. Den studie jag genomfört och som denna uppsats är resultatet av, syftar till att ta reda på hur systemutveckling enligt synsättet agile fungerar i verkligheten och vad det betyder för aktiva systemutvecklare. Resultatet av studien är baserad på en kvalitativ undersökning, i form av intervjuer, som gjorts med tretton systemutvecklare på olika företag runt om i Sverige. Resultatet visar att genom att utveckla mjukvara med en agilemetod, får man en snabbare utvecklingscykel med fokus på störts affärsnytta först. Det ger mer funktioner med högre kvalitet till lägre kostnad. Resultatet visar också att man har en flexiblare syn på utvecklingen och en attityd som välkomnar förändringar när helst dom dyker upp. Ett arbetssätt där förändringar är en del av planeringen.
5
TOMASSETTI, FEDERICO CESARE ARGENTINO. "Polyglot software development." Doctoral thesis, Politecnico di Torino, 2014. http://hdl.handle.net/11583/2537697.
Pełny tekst źródłaStreszczenie:
The languages we choose to design solutions influence the way we think about the problem, the words we use in discussing it with colleagues, the processes we adopt in developing the software which should solve that problem. Therefore we should strive to use the best language possible for depicting each facet of the system. To do that we have to solve two challenges: i) first of all to understand merits and issues brought by the languages we could adopt and their long reaching effects on the organizations, ii) combine them wisely, trying to reduce the overhead due to their assembling.
In the first part of this dissertation we study the adoption of modeling and domain specific languages. On the basis of an industrial survey we individuate a list of benefits attainable through these languages, how frequently they can be reached and which techniques permit to improve the chances to obtain a particular benefit. In the same way we study also the common problems which either prevent or hinder the adoption of these languages. We then analyze the processes through which these languages are employed, studying the relative frequency of the usage of the different techniques and the factors influencing it. Finally we present two case-studies performed in a small and in a very large company, with the intent of presenting the peculiarities of the adoption in different contexts.
As consequence of adopting specialized languages, many of them have to be employed to represent the complete solution. Therefore in the second part of the thesis we focus on the integration of these languages. Being this topic really new we performed preliminary studies to first understand the phenomenon, studying the different ways through which languages interact and their effects on defectivity. Later we present some prototypal solutions for i) the automatic spotting of cross-language relations, ii) the design of language integration tool support in language workbenches through the exploitation of common meta-metamodeling.
This thesis wants to offer a contribution towards the productive adoption of multiple, specific languages in the same software development project, hence polyglot software development. From this approach we should be able to reduce the complexity due to misrepresentation of solutions, offer a better facilities to think about problems and, finally to be able to solve more difficult problems with our limited brain resources.
Our results consists in a better understanding of MDD and DSLs adoption in companies. From that we can derive guidelines for practitioners, lesson learned for deploying in companies, depending on the size of the company, and implications for other actors involved in the process: company management and universities.
Regarding cross-language relations our contribution is an initial definition of the problem, supported by some empirical evidence to sustain its importance. The solutions we propose are not yet mature but we believe that from them future work can stem.
6
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.
Pełny tekst źródłaStreszczenie:
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.
7
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.
Pełny tekst źródłaStreszczenie:
The software and hardware industries are growing day by day, which makes their development environments more complex. This situation has a huge impact on the companies which have interdisciplinary development environments. To handle this situation, a common platform is required which can be acted as a bridge between hardware and software development to ease their tasks in an organized way. The research questions of the thesis aim to get information about differences and similarities in requirements handling, and their integration in current and future prospectives. The future prospect of integration is considered as a focused area. Interviews were conducted to get feedback from four different companies having complex development environments.
8
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.
Pełny tekst źródłaStreszczenie:
Lean Software Development is a new approach to provide a quality philosophy in software development companies. Lean offers a set of principles that helps companies to identify inefficient processes and waste. Therefore, by applying these principles, we can reduce costs, by shorting development time, incrementing productivity.In this study a software company with seven employees is analyzed. The company develops software and wants to increase its maturity and the quality of its processes. Currently, it has few documented processes. Furthermore, the company want a common way of working for every project. The challenge relies in adapting the set of principles provided by Lean to this particular case of study.We seek to analyze the current situation of the company to find out about the problems and limitations of the current way of working. After that we will state recommendations about the use of Lean combined with Agile practices such as Scrum and XP.As a result we present a proposal for implementation adapted from these philosophies to the needs and characteristics of the company.We have found that there are several ways in which the company can benefit from the implementation of Lean practices in combination with Scrum and XP. The result is a new framework that can be applied for other small software development companies in a similar situation.
9
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.
Pełny tekst źródłaStreszczenie:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, 2019<br>Cataloged from PDF version of thesis.<br>Includes bibliographical references (pages 157-158).<br>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.<br>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.<br>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.<br>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.<br>by Yuqing Ke.<br>S.M. in Engineering and Management<br>S.M.inEngineeringandManagement Massachusetts Institute of Technology, System Design and Management Program
10
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.
Pełny tekst źródłaStreszczenie:
A software process improvement study is presented. The literature on software
development processes and their improvement is reviewed. The current peer review
process at Software Engineering Directorate of the X Company, Ankara, Tü<br>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<br>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.
11
Abbas, Noura. "Software quality and governance in agile software development." Thesis, University of Southampton, 2009. https://eprints.soton.ac.uk/158357/.
Pełny tekst źródłaStreszczenie:
Looking at software engineering from a historical perspective, we can see how software development methodologies have evolved over the past 50 years. Using the right software development methodology with the right settings has always been a challenge. Therefore, there has always been a need for empirical evidence about what worked well and what did not, and what factors affect the different variables of the development process. Probably the most noticeable change to software development methodology in the last 15 years has been the introduction of the word “agile”. As any area matures, there is a need to understand its components and relations, as well as the need of empirical evidence about how well agile methods work in real life settings. In this thesis, we empirically investigate the impact of agile methods on different aspects of quality including product quality, process quality and stakeholders’ satisfaction as well as the different factors that affect these aspects. Quantitative and qualitative research methods were used for this research, including semi-structured interviews and surveys. Quality was studied in two projects that used agile software development. The empirical study showed that both projects were successful with multiple releases, and with improved product quality and stakeholders’ satisfaction. The data analysis produced a list of 13 refined grounded hypotheses out of which 5 were supported throughout the research. One project was studied in-depth by collecting quantitative data about the process used via a newly designed iteration monitor. The iteration monitor was used by the team over three iterations and it helped identify issues and trends within the team in order to improve the process in the following iterations. Data about other organisations collected via surveys was used to generalise the obtained results. A variety of statistical analysis techniques were applied and these suggested that when agile methods have a good impact on quality they also has a good impact on productivity and satisfaction, also when agile methods had good impact on the previous aspects they reduced cost. More importantly, the analysis clustered 58 agile practices into 15 factors including incremental and iterative development, agile quality assurance, and communication. These factors can be used as a guide for agile process improvement. The previous results raised questions about agile project governance, and to answer these questions the agile projects governance survey was conducted. This survey collected 129 responses, and its statistically significant results suggested that: retrospectives are more effective when applied properly as they had more impact when the whole team participated and comments were recorded, that organisation size has a negative relationship with success, and that good practices are related together as when a team does one aspect well, they do all aspects well. Finally, the research results supported the hypotheses: agile software development can produce good quality software, achieve stakeholders’ satisfaction, motivate teams, assures quick and effective response to stakeholder’s requests, and it goes in stages, matures, and improves over time.
12
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.
Pełny tekst źródła
13
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.
Pełny tekst źródłaStreszczenie:
<p>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.</p>
14
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.
Pełny tekst źródłaStreszczenie:
Today wireless technologies are increasing in the automation systems used in homes and buildings. More electrical devices are used in a house to save time, money, and energy because they are relatively inexpensive and easy to install; these devices even allow smart components such as mobile tablets and computer connectivity. To connect all these devices for data transmission purposes and easy access, the KNX is the best choice. The KNX standard is an open standard for home and building automation. KNX standard supports different communication media such as Twisted pairs, Power line, Radio Frequency, and tunnelling IP. KNX system is a bus system for building control, making all electrical and smart devices in a KNX system use the same transmission method and exchange telegrams via a shared bus network. To check and control all the electrical devices in a home or an apartment takes time; that is why there is a massive need for applications to make every room’s controlling process much easier and take a much shorter time. This project is about designing and implementing a visualization application for windows and .NET for managing and comparing input data with the actual data. This application is equipped with a KNX bus driver to communicate with hardware in a building. The practical part of the application is to take some raw data and then sort them in a specific way to minimize the time of controlling the process of the KNX devices in a building.
15
Marques, João Miguel Resende. ""GWB" simulation software development." Master's thesis, Universidade de Aveiro, 2009. http://hdl.handle.net/10773/1768.
Pełny tekst źródłaStreszczenie:
Mestrado em Engenharia e Gestão Industrial<br>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.
16
Rais, Aziz. "Interface-Based Software Development." Doctoral thesis, Vysoká škola ekonomická v Praze, 2017. http://www.nusl.cz/ntk/nusl-264730.
Pełny tekst źródłaStreszczenie:
Even though there are many software development and project management methodologies available, research and practice both show that IT software development projects still fail, and that the quality of software products does not always meet customers' expectations. There might be multiple causes for such failures, but some of these reasons can be seen to influence or create others. Therefore, the larger the project is, the higher its risk of failure, especially if the teams involved work remotely (distributed and outsourced). This increase in project complexity is considered the motivation for this paper. Similarly, there are other factors that can result in a project's failure and customers' dissatisfaction regarding software quality. All such factors identified by research conducted by organizations specializing in this area are analyzed in order to identify a common root of IT project failures. Once the root causes of these failures have been identified and analyzed, the goal of the Interface based software development methodology is to solve them. The solution offered by an Interface based software development methodology is to improve understanding of software requirements and to describe these requirements with interfaces in an object-oriented way. Interface based software development will support and drive development towards service-oriented architecture (SOA) and component-based development (CBD). The goal of interface based software development is to increase software testability and maintainability and to make it more easily feasible to execute various software development processes in parallel.
17
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.
Pełny tekst źródła
18
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.
Pełny tekst źródła
19
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.
Pełny tekst źródłaStreszczenie:
Everyone is talking about the software development methods but these methods are categorised into the different parts and the most important are two categories, one is agile software development methods and second is using the traditional software development methods. Agile software methods are relatively considered to be quick and for the small teams. Our main mission is to check which method is better from each other, so for that purpose we go out in the software development market to meet the professional to ask about their satisfaction on these software development methods. Our research is based on to see the suitable method for the professionals; see the challenges on the adoptability of methods and which method is quicker. To perform this study we have gone through a survey questionnaire, and results are analysed by using mixed method approach. Results shows that professionals from both types of methods are satisfied but professionals with traditional methods are more satisfy with their methods with respect to development of quality software, whereas agile professionals are more satisfied with their methods with respect of better communication with their customers. With agility point of view, our study says that both methods have characteristics which support agility but not fully support, so in such case we need to customize features from both types of methodologies.
20
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.
Pełny tekst źródłaStreszczenie:
The research described in this document represents work performed in the area of software development methodologies as it applied to quality software development in a scheduling department. It addressed traditional methods in software development, current trends in software development, in addition to quality and software development at various companies. The literature suggested a correlation between using a software development methodology and quality software. However, there was limited literature that measured quantitatively the correlation between the effectiveness of the software development methodology and quality software.
A software development methodology was developed for the scheduling department of a government contractor company in Aiken, South Carolina based on its needs and emerging technologies. An instrument was utilized to measure the effectiveness of the developed methodology. The methodology was compared with two other methodologies: a standard methodology from the literature and the current method of software development in the scheduling department. A population of computer professionals was divided into three equal groups. Each group was asked to apply the methodology to the case study. Individuals in each group were asked to review the case study and software development methodology. Then using the instrument, the individuals were asked to evaluate the effectiveness of the software development methodology, thereby providing a means for evaluated effectiveness, without conducting years of testing. The responses of the three groups were compared to one another.
The results indicated a significantly higher level of approval for those methodologies that guided the development activities, standardized the development process, and identified the development phases and deliverables. It was concluded that utilizing a software development methodology that guides, standardizes, and defines the development phases and deliverables will result in an improved software development process and software quality. Further investigation could validate the findings of this research. The results actually achieved from utilizing the methodology developed for the scheduling department compared with the results achieved from utilizing some other methodology could further validate these research findings. Additional research could examine, over an extended time period, the success of the software development process and software quality of those projects utilizing the methodology described in this dissertation.
21
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.
Pełny tekst źródłaStreszczenie:
Engineering software systems is a complex task which involves various stakeholders and requires planning and management to succeed. As the role of software in our daily life is increasing, the complexity of software systems is increasing. Throughout the short history of software engineering as a discipline, the development practises and methods have rapidly evolved to seize opportunities enabled by new technologies (e.g., the Internet) and to overcome economical challenges (e.g., the need for cheaper and faster development). Today, we are witnessing the Post-PC era. An era which is characterised by mobility and services. An era which removes organisational and geographical boundaries. An era which changes the functionality of software systems and requires alternative methods for conceiving them. In this thesis, we envision to execute software development processes in the cloud. Software processes have a software production aspect and a management aspect. To the best of our knowledge, there are no academic nor industrial solutions supporting the entire software development process life-cycle(from both production and management aspects and its tool-chain execution in the cloud. Our vision is to use the cloud economies of scale and leverage Model-Driven Engineering (MDE) to integrate production and management aspects into the development process. Since software processes are seen as workflows, we investigate using existing Workflow Management Systems to execute software processes and we find that these systems are not suitable. Therefore, we propose a reference architecture for Software Development as a Service (SDaaS). The SDaaS reference architecture is the first proposal which fully supports development of complex software systems in the cloud. In addition to the reference architecture, we investigate three specific related challenges and propose novel solutions addressing them. These challenges are: Modelling & enacting cloud-based executable software processes. Executing software processes in the cloud can bring several benefits to software develop ment. In this thesis, we discuss the benefits and considerations of cloud-based software processes and introduce a modelling language for modelling such processes. We refer to this language as EXE-SPEM. It extends the Software and Systems Process Engineering (SPEM2.0) OMG standard to support creating cloudbased executable software process models. Since EXE-SPEM is a visual modelling language, we introduce an XML notation to represent EXE-SPEM models in a machine-readable format and provide mapping rules from EXE-SPEM to this notation. We demonstrate this approach by modelling an example software process using EXE-SPEM and mapping it to the XML notation. Software process models expressed in this XML format can then be enacted in the proposed SDaaS architecture. Cost-e cient scheduling of software processes execution in the cloud. Software process models are enacted in the SDaaS architecture as workflows. We refer to them sometimes as Software Workflows. Once we have executable software process models, we need to schedule them for execution. In a setting where multiple software workflows (and their activities) compete for shared computational resources (workflow engines), scheduling workflow execution becomes important. Workflow scheduling is an NP-hard problem which refers to the allocation of su cient resources (human or computational) to workflow activities. The schedule impacts the workflow makespan (execution time) and cost as well as the computational resources utilisation. The target of the scheduling is to reduce the process execution cost in the cloud without significantly a ecting the process makespan while satisfying the special requirements of each process activity (e.g., executing on a private cloud). We adapt three workflow scheduling algorithms to fit for SDaaS and propose a fourth one; the Proportional Adaptive Task Schedule. The algorithms are then evaluated through simulation. The simulation results show that the our proposed algorithm saves between 19.74% and 45.78% of the execution cost, provides best resource (VM) utilisation and provides the second best makespan compared to the other presented algorithms. Evaluating the SDaaS architecture using a case study from the safety-critical systems domain. To evaluate the proposed SDaaS reference architecture, we instantiate a proof-of-concept implementation of the architecture. This imple mentation is then used to enact safety-critical processes as a case study. Engineering safety-critical systems is a complex task which involves multiple stakeholders. It requires shared and scalable computation to systematically involve geographically distributed teams. In this case study, we use EXE-SPEM to model a portion of a process (namely; the Preliminary System Safety Assessment - PSSA) adapted from the ARP4761 [2] aerospace standard. Then, we enact this process model in the proof-of-concept SDaaS implementation. By using the SDaaS architecture, we demonstrate the feasibility of our approach and its applicability to di erent domains and to customised processes. We also demonstrate the capability of EXE-SPEM to model cloud-based executable processes. Furthermore, we demonstrate the added value of the process models and the process execution provenance data recorded by the SDaaS architecture. This data is used to automate the generation of safety cases argument fragments. Thus, reducing the development cost and time. Finally, the case study shows that we can integrate some existing tools and create new ones as activities used in process models. The proposed SDaaS reference architecture (combined with its modelling, scheduling and enactment capabilities) brings the benefits of the cloud to software development. It can potentially save software production cost and provide an accessible platform that supports collaborating teams (potentially across di erent locations). The executable process models support unified interpretation and execution of processes across team(s) members. In addition, the use of models provide managers with global awareness and can be utilised for quality assurance and process metrics analysis and improvement. We see the contributions provided in this thesis as a first step towards an alternative development method that uses the benefits of cloud and Model-Driven Engineering to overcome existing challenges and open new opportunities. However, there are several challenges that are outside the scope of this study which need to be addressed to allow full support of the SDaaS vision (e.g., supporting interactive workflows). The solutions provided in this thesis address only part of a bigger vision. There is also a need for empirical and usability studies to study the impact of the SDaaS architecture on both the produced products (in terms of quality, cost, time, etc.) and the participating stakeholders.
22
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.
Pełny tekst źródła
23
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.
Pełny tekst źródła
24
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.
Pełny tekst źródłaStreszczenie:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO<br>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.<br>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.
25
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.
Pełny tekst źródła
26
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.
Pełny tekst źródłaStreszczenie:
Today’s software is more vulnerable to attacks due to increase in complexity, connectivity and extensibility. Securing software is usually considered as a post development activity and not much importance is given to it during the development of software. However the amount of loss that organizations have incurred over the years due to security flaws in software has invited researchers to find out better ways of securing software. In the light of research done by many researchers, this thesis presents how software can be secured by considering security in different phases of software development life cycle. A number of security activities have been identified that are needed to build secure software and it is shown that how these security activities are related with the software development activities of the software development lifecycle.
27
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.
Pełny tekst źródłaStreszczenie:
<p>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.</p>
28
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.
Pełny tekst źródłaStreszczenie:
<p>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. </p><p>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. </p><p>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.</p>
29
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.
Pełny tekst źródłaStreszczenie:
Rapid development processes and higher customer requirements lead to increasing integration
of software solutions in the automotive industry’s products. Today, several electronic
control units communicate by bus systems like CAN and provide computation of
complex algorithms. This increasingly requires a controlled timing behavior.
The following diploma thesis investigates how the timing analysis tool SymTA/S can be
used in the software development process of the ZF Friedrichshafen AG.Within the scope
of several scenarios, the benefits of using it, the difficulties in using it and the questions
that can not be answered by the timing analysis tool are examined.
(new: additional files)
30
Rathor, Shekhar. "Facilitators for Software Development Agility." FIU Digital Commons, 2016. http://digitalcommons.fiu.edu/etd/3059.
Pełny tekst źródłaStreszczenie:
Software development methodologies provide guidelines and practices for developing information systems. They have evolved over time from traditional plan-driven methodologies to incremental and iterative software development methodologies. The Agile Manifesto was released in 2001, which provides values and principles for agile software development. Over the last few years, agile software development has become popular because its values and principles focus on addressing the needs of contemporary software development. IT and Business teams need agility to deal with changes that can emerge during software development due to changing business needs. Agile software development practices claim to provide the ability to deal with such changes. Various research studies have identified many factors/variables that are important for agile software development such as team autonomy, communication, and organizational culture. Most of these empirical studies on agile software development focus on just a few variables. The relationships among the variables is still not understood. The dimensions of agility and the relationship between agility and other variables have not been studied quantitatively in the literature. Also, there is no comprehensive framework to explain agile software development. This research study addresses these research gaps.
This study analyzed a comprehensive research model that included antecedent variables (team autonomy, team competence), process variables (collaborative decision making, iterative development, communication), delivery capability, agility, and project outcomes (change satisfaction, customer satisfaction). It presents key dimensions of agility and quantitatively analyzes the relationship between agility and other variables. The PLS analysis of one hundred and sixty survey responses show that process variables mediate the relationship between antecedent variables and delivery capability and agility. The findings show that the delivery capability of the teams contributes to agility, antecedents and process variables contribute to agility, and delivery capability for better customer satisfaction. These results will help IS practitioners to understand the variables that are necessary to achieve agility for better project outcomes. Also, these quantitative findings provide better conceptual clarity about the relationship between various key variables related to agile software development.
31
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.
Pełny tekst źródłaStreszczenie:
Context: Software startups are newly created companies with no operating history and are extremely fast in producing cutting-edge technologies. These companies develop software un- der highly uncertain conditions, tackling fast growing markets with severe lack of resources. Startups present an unique combination of characteristics which pose several challenges to the software development activities, creating interesting problems for software engineers. However, despite the increasing economical importance and the high failure rate, there are only a few sci- entific studies attempting to address software engineering (SE) issues, especially for early-stages startups. In a context where a wrong decision can easily lead the entire business to failure, the support of SE can contribute to foster performances of startups and making a big impact on a large number of companies. Objective: In view of a lack of primary studies, the first step to attending the software development strategies with scientific and engineering approaches is by an understanding of the startups’ behavior. For this reason this research aims to understand how software development strategies are engineered by practitioners, in the period of time that goes from idea conception to the first open beta release of the software product. Methods: This research combines a systematic review of the state-of-the-art with a cross- sectional case study conducted in 13 web startups recently founded and distributed in di↵erent geographic areas and market sectors. A grounded theory approach guided the execution of a sys- tematic mapping study, integrated with semi-structured interviews and follow-up questionnaires to explore the state-of-practice. Results: We selected, classified and evaluated 37 relevant studies. The systematic review revealed that the studies which constitute the body of knowledge are generally not rigorously designed and executed, make use of inconsistent terminology, and cover only small samples of startups. Moreover, we extrapolated concepts from the case study to form a theoretical model, explaining the underlying phenomenon of software development in early-stage startups. The model is grounded in the empirical data and its explanatory power was further validated through a systematic procedure. Finally we proposed a multi-faceted evolutionary model to describe the dynamics of the software development after the first product release. Conclusions: The research provided a wide set of evidences fostering the understanding of how software development is structured and executed, from idea conception to the first release. The results revealed the urgent priority of startups of releasing the product as quickly as possi- ble to verify the product/market fit and to adjust the business and product trajectory according to the early collected user feedbacks. Nevertheless, the initial gain obtained in speeding-up the development by low-precision and product-centric engineering activities is counterbalanced by the need of restructuring the product and the workflows before setting o↵ for further grow. In fact, when user requests and company’s size start to increase startups face an initial and temporary drop-down in productivity, creating the need of mitigation strategies to find a sweet spot between being fast enough to enter the market early while controlling the amount of accu- mulated technical debt. The conclusions can be generalized with a good degree of confidence to the majority of early-stage software startups involved in the production of innovative products, especially for web and mobile applications.
32
Traino, Anthony J. "Automation of software development metrics." [Denver, Colo.] : Regis University, 2008. http://165.236.235.140/lib/ATraino2008.pdf.
Pełny tekst źródła
33
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.
Pełny tekst źródła
34
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.
Pełny tekst źródłaStreszczenie:
This Master thesis describes the development and modification of already existing assembler software for the DRUi 360. The DRUi is a controller unit for stabilization tasks mostly used in the military industry. The DRUi controls the stabilization platform which has the purpose to simulate a moving vehicle. The aim with this platform is for internal development of new hardware and software, evaluate new ideas and components for stabilization systems. The platform is also an internal education system for the engineers. The DRUi receives the input reference signal from the Ground Profile Generator which is a graphical interface running on a PC were the user has the ability to create or send already recorded road signals from a moving vehicle to the driver unit. In this case the DRUi. The main used software’s for this project are Code Composer Studio for programming the DRUi software and LabVIEW which is a graphical programming language used to program the Ground Profile Generator. A theoretical study of motion control is performed together with getting familiar of al the equipment. The new software for the DRUi is adapted and implemented. Filter design for the regulator unit and necessary measurements on the test stand are presented together with the results of the production run of the stabilization platform. The stabilization platform is not fully running when this thesis ended. When the production test was performed disturbances appeared in the system. The reasons for these disturbances are not yet discovered. Al safety routines needed for running the platform secure and prevent system damage are implemented to the system software.
35
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.
Pełny tekst źródłaStreszczenie:
The never-ending changes in the mineral industry environment require fast reactions on the part of governments in adapting their mining tax policies. The fiscal analysis software developed for this Master of Engineering and commissioned by the Quebec Ministry of Natural Resources provides the provincial authorities with a quick method of assessing the tax burden of a mining project located in Quebec. It also allows comparison of Quebec's tax burden with that of other Canadian mining provinces as well as the analysis of fiscal changes on a mine's profitability. The use of the software is illustrated by analyzing the effect of inflation and price cycles on the tax burden of a hypothetical mining project located in Quebec. The behavior of specific tax provisions with respect to these factors is emphasized.<br>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.
36
Lopes, Joao Sollari. "Software development in population genetics." Thesis, University of Reading, 2009. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.529977.
Pełny tekst źródła
37
Kim, Heung-Taek. "Interface-driven software development tool." Thesis, Monterey, California. Naval Postgraduate School, 1990. http://hdl.handle.net/10945/30623.
Pełny tekst źródłaStreszczenie:
Approved for public release, distribution unlimited<br>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.
38
Norman, Michael John. "SSDE : structured software development environment." Master's thesis, University of Cape Town, 1990. http://hdl.handle.net/11427/15899.
Pełny tekst źródłaStreszczenie:
Bibliography: pages 219-230.<br>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.
39
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.
Pełny tekst źródłaStreszczenie:
Background: Due to the complexity involved in robotic software development, the progress in the field has been slow. Component-based software engineering was observed to have a strong influence on the improvement of the robotic software development process and its adoption achieved good results. DevOps was seen to be compatible and produced efficient results in software engineering. Objectives: The aim of this thesis work is to present the potential usage of DevOps practices in robotic software development. 15 DevOps practices were selected from prior research from software engineering and mapped to the robotic software development process and checked for success in terms of applicability and effectiveness. Methods: By performing a research synthesis of the literature, the usage of DevOps practices in robotic software development is proposed and presented. Interview based survey was performed by approaching industry experts on robotic software development to get their response on the results of the research synthesis. Results: The applicability of the DevOps practices in robotic software development is presented and the implications of the potential usage of the practices in the proposed manner are discussed. The potential advantages and limitations of the proposed mapping are discussed and presented. Conclusions: DevOps, like other software development frameworks, has various observable advantages when applied in robotic software development. The interviews confirmed the need for DevOps to be adapted into robotic software development and the benefits it has.
40
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/.
Pełny tekst źródła
41
Dalcher, Darren. "Investigating dynamic software processes." Thesis, King's College London (University of London), 2002. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.252083.
Pełny tekst źródła
42
Á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.
Pełny tekst źródłaStreszczenie:
Context. Agile Software Development has provided a new concept of Software Development based in adaptation to changes, quick decisions, low high-level design and frequent deliveries. However, this approach ignores the value that Software Architecture provides in the long term for increasing the speed in delivery working software, which may have catastrophic consequences in the long term. Objectives. In this study, the combination of these two philosophies of Software Development is investigated. Firstly, the concept of Software Architecture in Agile Projects; then, the major challenges faced concerning Software Architecture in Agile Projects, the practices and approaches that can be used to overcome these challenges and the effects that these practices may cause on the project. Methods. The research methodologies used in this study are Systematic Literature Review for gathering the highest amount possible of contributions available in the Literature at this respect, and also the conduction of Semi-Structured Interviews with Agile Practitioners, in order to obtain empirical knowledge on the problem and support or deny the SLR findings. Results. The results of the Thesis are a unified description of the concept of Software Architecture in Agile Projects, and a collection of challenges found in agile projects, practices that overcome them and a relation of effects observed. Considering the most frequent practices/approaches followed and the empirical support, it is enabled a discussion on how to combine Software Architecture and Agile Projects. Conclusions. The main conclusion is that there is not a definite solution to this question; this is due to the relevance of the context (team, project, customer, etc.) that recommends the evaluation of each situation before deciding the best way to proceed. However, there are common trends on the best-recommended practices to integrate these two concepts. Finally, it is required more empirical work on the issue, the conduction of controlled experiments that allows to quantify the success or failure of the practices implemented would be most helpful in order to create a body of knowledge that enables the application of certain practices under certain conditions.
43
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.
Pełny tekst źródła
44
Middleton, Nigel Peter Jon. "Managing software quality." Thesis, Imperial College London, 1998. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.286299.
Pełny tekst źródła
45
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.
Pełny tekst źródłaStreszczenie:
Globally distributed software development has become an important topic for small and medium enterprises. However, the distinct requirements of small and medium enterprises (SMEs) are still not fullyunderstood. To contribute to this growing discussion, I will present an ethnographical field study of a Swedish software company engaged in a distributed development practice with its American branch. By applying a theoretical view based on communication, coordination and control over time, space and socio/cultural difference, I show to what extent a distributed software development model affects SMEs. Whereproblems related to formal and informal communication, knowledge sharing, articulation work and programming methodologies are discussed. My findings suggest that organizational adjustments are needed for SMEs in order to take advantage of distributed software development (DSD), that specialized tools supporting coordination and articulation work is not so common in practice and that certain adjustment to agile methodologies could be made in order to better support DSD.
46
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.
Pełny tekst źródłaStreszczenie:
<p> 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.</p><p>
47
Lindmark, Fanny, and Hanna Kvist. "Security in software : How software companies work with security during a software development process." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-130964.
Pełny tekst źródłaStreszczenie:
This study is conducted, due to recent interest in privacy and software security, on how a number of software development companies work during a development process to develop secure software to the possible extent. The study is based on four interviews with four software companies located in Linköping, Sweden. The interviews followed a semi-structured format to ensure the possibility to compare the given answers from the companies to each other. This structure was chosen to give each company the liberty to express what they valued and thought were important during a software development process. The aim was to analyze how and if these companies work with security when developing software, and to see what differences and similarities that could be established. We found differences between the companies' perspective of security and on their methods of working. Some valued secure software more than others and performed more measures to ensure it. We also found some similarities on their view on importance of secure software and ways to work with it. The differences and similarities were related to the size of the companies, their resources, the types of products they develop, and the types of clients they have.
48
Knapp, Chris H. "Unlocking test-driven development." [Denver, Colo.] : Regis University, 2006. http://165.236.235.140/lib/CKnapp2006.pdf.
Pełny tekst źródła
49
Sedano, Todd. "Sustainable Software Development: Evolving Extreme Programming." Research Showcase @ CMU, 2017. http://repository.cmu.edu/dissertations/837.
Pełny tekst źródłaStreszczenie:
Context: Software development is a complex socio-technical endeavor that involves coordinating different disciplines and skill sets. Practitioners experiment with and adopt processes and practices with a goal of making their work more effective. Objective: To observe, describe, and analyze software development processes and practices in an industrial setting. Our goal is to generate a descriptive theory of software engineering development, which is rooted in empirical data. Method: Following Constructivist Grounded Theory, we conducted a 2.5 year participant-observation of eight software projects at Pivotal, a software development company. We interviewed 33 software engineers, interaction designers, and product managers, and analyzed one year of retrospection topics. We iterated between data collection, data analysis and theoretical sampling until achieving theoretical saturation and generating a descriptive theory. Results: 1) This research introduces a descriptive theory of Sustainable Software Development. The theory encompasses principles, policies, and practices aiming at removing knowledge silos and improving code quality, hence leading to development sustainability. 2) At the heart of Sustainable Software Development is team code ownership. This research widens our understanding of team code ownership. Developers achieve higher team code ownership when they understand the system context, have contributed to the code in question, perceive code quality as high, believe the product will satisfy the user needs, and perceive high team cohesion. 3) This research introduces the first evidence-based waste taxonomy, identifying eight wastes along with causes and tensions, and compares it with Lean Software Development’s waste taxonomy. Conclusion: The Sustainable Software Development theory refines and extends our understanding of Extreme Programming by adding principles, policies, and practices (including Overlapping Pair Rotation) and aligning them with the business goal of sustainability. One key aspect of the theory is team code ownership, which is rooted in numerous cognitive, emotional, contextual and technical factors and cannot be achieved simply by policy. Another key dimension is waste identification and elimination, which has led to a new taxonomy of waste. Overall, this research contributes to the field of software engineering by providing new insights, rooted in empirical data, into how a software organization leverages and extends Extreme Programming to achieve software sustainability.
50
Cater-Steel, Aileen Patricia, and n/a. "An Evaluation of Software Development Practice and Assessment-Based Process Improvement in Small Software Development Firms." Griffith University. School of Computing and Information Technology, 2005. http://www4.gu.edu.au:8080/adt-root/public/adt-QGU20060110.180345.
Pełny tekst źródłaStreszczenie:
As software becomes increasingly important to all aspects of industry, there is a need to encourage practitioners to adopt best practice so as to improve the quality of the processes in use, and therefore achieve targets relating to time, budget and quality. The software development industry in Australia is dominated by a myriad of small firms. This presents a challenge in terms of determining the current practices of industry participants, and in devising improvement initiatives which are feasible for small organisations. Currently, the level of adoption of best practice among local software developers is unknown. To help improve the software industry, it is necessary to determine the current status of use of practices and techniques. Furthermore, the effectiveness of assessment-based software process improvement for small organisations needs to be evaluated. The objective of this research is to understand the extent of software development practices currently in use, and to evaluate the effectiveness of assessment-based software process improvement initiatives for small firms. To achieve this objective, an extensive mail survey of the Queensland software industry was conducted to identify and compare best practice in software development with current practice. The survey was based on the software best practice questionnaire used by the European Software Institute. Following on from this, a detailed evaluation of a process improvement program in 22 small firms was carried out. The program used the Rapid Assessments for Process Improvement for software Development (RAPID) model and method. RAPID is based on ISO/IEC 15504 (SPICE) and includes eight processes: requirements elicitation, software development, configuration management, quality assurance, project management, problem resolution, risk management, and process establishment. The evaluation analysed the process capability of the firms as reported from one-day software process assessments and also the extent of improvement as recorded at follow-up meetings held 7 to 16 months after the assessment. Both quantitative and qualitative techniques were used to analyse the assessment reports. The study confirmed that there is wide variation in the extent of adoption of software development best practice in terms of the individual practices, as well as the organisations. While project management planning and customer involvement practices are widely adopted, the use of metrics for estimating and testing are barely used by the organisations that responded to the survey. Overall, practices of a technical nature are more widely adopted compared to techniques related to support and management. Organisations involved in developing commercial off-the-shelf software have higher adoption than firms which do not develop such systems, and adoption of best practice is associated with the size of the development group. The leaders in adoption have significantly better practices when compared to the laggards for 40 of the 44 practices included in the survey. Furthermore, organisations from the finance, insurance and utilities sectors exhibited higher adoption of best practice compared to organisations from other sectors. The overall adoption of 48 percent implies that the organisations which responded have adopted, on average, almost half of the best practices in the questionnaire. While this overall adoption rate places the Queensland software industry in a competitive position compared to adoption of firms in European countries, there is scope for improvement. The process improvement assessments of 22 firms also confirmed that the capability of technical processes is higher than that of management processes; and suggested that higher capability is associated with the proportion of experienced staff and the proportion of staff with post graduate qualifications. Higher process capability is also associated with firms undertaking projects of lengthy durations. Most of the processes were rated at the lowest levels. Almost one third of all the processes were rated as incomplete (level 0) and 46 percent were rated as performed (level 1). The evaluation of the process improvement program was conducted by analysing the 22 assessment reports, and the 20 final reports from the follow-up meetings. The extent of improvement is associated with the proportion of technical staff and the proportion of formally qualified staff. The evaluation revealed that assessment-based process improvement programs are effective for small firms, regardless of the maturity of the processes at the time of the assessment. As well as detailing the process capability of 22 small software firms, this study provides an interesting insight into the actions, reasons for inaction, and reactions of the firms as far as implementing the recommendations from the assessments. Analysis of the reactions of the participants of this program suggests that for small firms, mentoring, training and organisation stability are important factors, while senior management support may not be an issue of concern. The study indicates that small firms can benefit from a low cost process improvement program with a restricted scope, a short time frame to evaluation, and mentoring from external assessors/consultants. It is also crucial that the firm is not disrupted by internal or external events during the course of the software process improvement program. Furthermore, this study provides a contribution to assessment methods by validating the RAPID model and method, and providing recommendations to improve the RAPID method. The outcomes from this research have the potential to better equip practitioners and consultants to undertake software process improvement, hence increasing the success of small software development firms in domestic and global markets.