Gotowe bibliografie tematyczne / Software development

Gotowa bibliografia na temat „Software development”

Autor: Grafiati
Data publikacji: 4 czerwca 2021
Data aktualizacji: 31 lipca 2024

Utwórz poprawne odniesienie w stylach APA, MLA, Chicago, Harvard i wielu innych

Wybierz rodzaj źródła:

Spis treści

Zobacz listy aktualnych artykułów, książek, rozpraw, streszczeń i innych źródeł 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.

Artykuły w czasopismach na temat "Software development"

1

Buhrer, Hans Konrad. "Software development". ACM SIGSOFT Software Engineering Notes 28, nr 2 (marzec 2003): 5. http://dx.doi.org/10.1145/638750.638777.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Gardner, Todd. "Software Development". Historical Methods: A Journal of Quantitative and Interdisciplinary History 28, nr 1 (1.01.1995): 59–62. http://dx.doi.org/10.1080/01615440.1995.9955315.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Sneed, Harry M., i Chris Verhoef. "From Software Development to Software Assembly". IEEE Software 33, nr 5 (wrzesień 2016): 80–85. http://dx.doi.org/10.1109/ms.2015.78.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Dettmer, R. "Language, truth and software [software development]". IEE Review 50, nr 1 (1.01.2004): 38–42. http://dx.doi.org/10.1049/ir:20040106.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Marcos, Esperanza. "Software engineering research versus software development". ACM SIGSOFT Software Engineering Notes 30, nr 4 (lipiec 2005): 1–7. http://dx.doi.org/10.1145/1082983.1083005.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Biju, Soly Mathew. "Agile Software Development". E-Learning and Digital Media 5, nr 1 (styczeń 2008): 97–102. http://dx.doi.org/10.2304/elea.2008.5.1.97.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Meadows, C. J. "Globalizing Software Development". Journal of Global Information Management 4, nr 1 (styczeń 1996): 5–15. http://dx.doi.org/10.4018/jgim.1996010101.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

GHEORGHE, Alina-Madalina, Ileana Daniela GHEORGHE i Ioana Laura IATAN. "Agile Software Development". Informatica Economica 24, nr 2/2020 (30.06.2020): 90–100. http://dx.doi.org/10.24818/issn14531305/24.2.2020.08.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Aramo-Immonen, Heli, Hannu Jaakkola i Harri Keto. "Multicultural Software Development". International Journal of Information Technology Project Management 2, nr 1 (styczeń 2011): 19–36. http://dx.doi.org/10.4018/jitpm.2011010102.

Pełny tekst źródła
Streszczenie:
Productivity management is a challenge for software engineering companies and, in this regard, there is a current trend toward globalization. Via acquisitions and mergers, business has become international and employs different national cultures. Therefore, the focus of this article is on the understanding of cultural differences affecting productivity in globalized software production. The relation between productivity and non coding activities in software development projects has not been proven. Software development is expert work, typically made in closely collaborating local teams and global distribution of expert work increases the degree of difficulty. In this paper, the authors analyze multicultural ICT companies from their productivity perspective through the lens of cultural differences. The purpose of this study is to report findings based on general cultural studies and reported experiences that seem to affect productivity in the software industry. Some company cases are also described and analyzed.
Style APA, Harvard, Vancouver, ISO itp.
10

Gidroets, M. O., i L. I. Grishanova. "SOFTWARE DEVELOPMENT METHODOLOGY". System analysis and logistics 4, nr 26 (17.12.2020): 45–53. http://dx.doi.org/10.31799/2007-5687-2020-4-45-53.

Pełny tekst źródła
Streszczenie:
This article discusses the main methodologies for developing software products. The most common cascading and flexible methodologies are characterized. Considered the pros and cons of each methodology. The situations of expedient application of cascade and flexible approaches to software product development are determined. Key words: development methodologies, waterfall model, agile model, project management, planning, software product development.
Style APA, Harvard, Vancouver, ISO itp.
Więcej źródeł

Rozprawy doktorskie na temat "Software development"

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
Style APA, Harvard, Vancouver, ISO itp.
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
Style APA, Harvard, Vancouver, ISO itp.
3

Hellström, Andreas, i 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ła
Streszczenie:
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.
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
Style APA, Harvard, Vancouver, ISO itp.
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ła
Streszczenie:
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.
Style APA, Harvard, Vancouver, ISO itp.
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ła
Streszczenie:
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.
Style APA, Harvard, Vancouver, ISO itp.
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ła
Streszczenie:
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.
Style APA, Harvard, Vancouver, ISO itp.
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ła
Streszczenie:
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.
Style APA, Harvard, Vancouver, ISO itp.
8

Moratilla, Temprado Enrique, i 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ła
Streszczenie:
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.
Style APA, Harvard, Vancouver, ISO itp.
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ła
Streszczenie:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, 2019
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
Style APA, Harvard, Vancouver, ISO itp.
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ła
Streszczenie:
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ü
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.
Style APA, Harvard, Vancouver, ISO itp.
Więcej źródeł

Książki na temat "Software development"

1

Freedman, Jeri. Software development. New York: Cavendish Square, 2015.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Zelkowitz, Marvin V. Software development. London: Academic Press/Elsevier, 2008.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Cockburn, Alistair. Agile software development. Boston: Addison-Wesley, 2002.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Müller, Peter, i Ina Schaefer, red. Principled Software Development. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-98047-8.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Charatan, Quentin, i Aaron Kans. Formal Software Development. London: Macmillan Education UK, 2004. http://dx.doi.org/10.1007/978-0-230-00586-0.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Almeida, José Bacelar, Maria João Frade, Jorge Sousa Pinto i Simão Melo de Sousa. Rigorous Software Development. London: Springer London, 2011. http://dx.doi.org/10.1007/978-0-85729-018-2.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Stober, Thomas, i Uwe Hansmann. Agile Software Development. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-540-70832-2.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Dingsøyr, Torgeir, Tore Dybå i Nils Brede Moe, red. Agile Software Development. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12575-1.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

G, Siegel Stanley, i Donaldson Scott E, red. Successful software development. Wyd. 2. Upper Saddle River, NJ: Prentice Hall PTR, 2001.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Coad, Peter. Advanced software development. [United States]: TELOS Corp., 1988.

Znajdź pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
Więcej źródeł

Części książek na temat "Software development"

1

Paulus, Dietrich W. R., i Joachim Hornegger. "Software Development". W Pattern Recognition of Images and Speech in C++, 31–40. Wiesbaden: Vieweg+Teubner Verlag, 1997. http://dx.doi.org/10.1007/978-3-663-13991-1_3.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Paulus, Dietrich W. R., i Joachim Hornegger. "Software Development". W Pattern Recognition and Image Processing in C++, 32–41. Wiesbaden: Vieweg+Teubner Verlag, 1995. http://dx.doi.org/10.1007/978-3-322-87867-0_3.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Buchanan, W. J. "Software development". W The Complete Handbook of the Internet, 941–68. Boston, MA: Springer US, 2002. http://dx.doi.org/10.1007/978-0-306-48331-8_44.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Singh, Neeraj Kumar, Porselvan Muthukrishnan i Satyanarayana Sanpini. "Software Development". W Industrial System Engineering for Drones, 167–213. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-3534-8_6.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Lientz, Bennet P. "Software development". W Information Technology Project Management, 295–315. London: Macmillan Education UK, 2011. http://dx.doi.org/10.1007/978-0-230-34500-3_16.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Dubey, SatyaKesh, Naina Narang, Parmendra Singh Negi i Vijay Narain Ojha. "Software Development". W SpringerBriefs in Electrical and Computer Engineering, 25–34. Singapore: Springer Singapore, 2017. http://dx.doi.org/10.1007/978-981-10-6280-3_4.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Constanda, Christian, Dale Doty i William Hamill. "Software Development". W Boundary Integral Equation Methods and Numerical Solutions, 35–91. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-26309-0_4.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Hunt, Eleanor Callahan, Sara Breckenridge Sproat i Rebecca Rutherford Kitzmiller. "Software Development". W The Nursing Informatics Implementation Guide, 276–97. New York, NY: Springer New York, 2004. http://dx.doi.org/10.1007/978-1-4757-4343-2_14.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Natriello, Gary. "Software Development". W Digital-Age Innovation in Higher Education, 136–49. New York, NY : Routledge, 2021.: Routledge, 2021. http://dx.doi.org/10.4324/9781003038924-9.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Juuso, Ilkka, i Ilpo Pöyhönen. "Software Development". W Medical-Grade Software Development, 105–74. New York: Productivity Press, 2023. http://dx.doi.org/10.4324/b23403-5.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.

Streszczenia konferencji na temat "Software development"

1

Haungs, Jim, Martin Fowler, Ralph Johnson, Steve McConnell i Richard Gabriel. "Software development". W Companion to the 19th annual ACM SIGPLAN conference. New York, New York, USA: ACM Press, 2004. http://dx.doi.org/10.1145/1028664.1028720.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

DeMarco, Tom, i Tim Lister. "Software development". W the 11th international conference. New York, New York, USA: ACM Press, 1989. http://dx.doi.org/10.1145/74587.74625.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Yaeli, Avi, Alex Kofman i Yael Dubinsky. "Software development governor: Automating governance in software development environments". W 2009 31st International Conference on Software Engineering - Companion Volume. IEEE, 2009. http://dx.doi.org/10.1109/icse-companion.2009.5071038.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Kakihara, Masao. "Strategizing software development". W the 2006 international workshop. New York, New York, USA: ACM Press, 2006. http://dx.doi.org/10.1145/1137661.1137670.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Arumugam, Chamundeswari, Sriraghav Kameswaran i Baskaran Kaliamourthy. "Global Software Development". W the 7th International Conference. New York, New York, USA: ACM Press, 2017. http://dx.doi.org/10.1145/3154979.3154983.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Aguiar, Ademar, André Restivo, Filipe Figueiredo Correia, Hugo Sereno Ferreira i João Pedro Dias. "Live software development". W the 3rd International Companion Conference. New York, New York, USA: ACM Press, 2019. http://dx.doi.org/10.1145/3328433.3328456.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Northover, Mandy, Alan Northover, Stefan Gruner, Derrick G. Kourie i Andrew Boake. "Agile software development". W the 2007 annual research conference of the South African institute of computer scientists and information technologists. New York, New York, USA: ACM Press, 2007. http://dx.doi.org/10.1145/1292491.1292504.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Sedano, Todd, Paul Ralph i Cecile Peraire. "Software Development Waste". W 2017 IEEE/ACM 39th International Conference on Software Engineering (ICSE). IEEE, 2017. http://dx.doi.org/10.1109/icse.2017.20.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

Poppendieck, Mary. "Lean Software Development". W 29th International Conference on Software Engineering. IEEE, 2007. http://dx.doi.org/10.1109/icsecompanion.2007.46.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Lämmel, Ralf, Andrei Varanovich, Martin Leinberger, Thomas Schmorleiz i Jean-Marie Favre. "Declarative Software Development". W the 16th International Symposium. New York, New York, USA: ACM Press, 2014. http://dx.doi.org/10.1145/2643135.2643163.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.

Raporty organizacyjne na temat "Software development"

1

Dow, Stephen J. Trainer Software Development. Fort Belvoir, VA: Defense Technical Information Center, październik 2001. http://dx.doi.org/10.21236/ada396902.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
2

Ellison, Robert J. Software Development Environments. Fort Belvoir, VA: Defense Technical Information Center, lipiec 1986. http://dx.doi.org/10.21236/ada181742.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
3

Baskinger, Patricia J., Larry Ozarow i Mary C. Chruscicki. Speakeasy Software Development. Fort Belvoir, VA: Defense Technical Information Center, sierpień 1993. http://dx.doi.org/10.21236/ada283816.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
4

Piercey, R. B. Gammasphere software development. Office of Scientific and Technical Information (OSTI), styczeń 1993. http://dx.doi.org/10.2172/6561547.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
5

Forney, Glenn P., i Walter W. Jones. Software development tools. Gaithersburg, MD: National Institute of Standards and Technology, 1990. http://dx.doi.org/10.6028/nist.ir.4363.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
6

Dow, Stephen J. Javelin EPBST Software Development. Fort Belvoir, VA: Defense Technical Information Center, październik 2001. http://dx.doi.org/10.21236/ada396894.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
7

Manna, Zohar. Next Generation Software Development. Fort Belvoir, VA: Defense Technical Information Center, styczeń 2005. http://dx.doi.org/10.21236/ada435087.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
8

Luqi. Documentation Driven Software Development. Fort Belvoir, VA: Defense Technical Information Center, czerwiec 2010. http://dx.doi.org/10.21236/ada532459.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
9

de Vaulx, Frederic, paul Khouri Saba, Marcus Newrock i Bertrand Stivalet. Initiating mobile software development :. Gaithersburg, MD: National Institute of Standards and Technology, 2011. http://dx.doi.org/10.6028/nist.ir.7838.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
10

Hsu, Y. L., Juan F. Reynaud i Ernst W. Schwiderski. Tidal Atlas Software Development. Fort Belvoir, VA: Defense Technical Information Center, grudzień 1993. http://dx.doi.org/10.21236/ada275251.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
Możesz być także zainteresowany rozszerzonymi bibliografiami na temat „Software development” dla poszczególnych typów źródeł:
Artykuły w czasopismach Rozprawy doktorskie Książki
Oferujemy zniżki na wszystkie plany premium dla autorów, których prace zostały uwzględnione w tematycznych zestawieniach literatury. Skontaktuj się z nami, aby uzyskać unikalny kod promocyjny!

Do bibliografii