Gotowa bibliografia na temat „Software development”
Utwórz poprawne odniesienie w stylach APA, MLA, Chicago, Harvard i wielu innych
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"
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łaGardner, 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łaSneed, 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łaDettmer, 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łaMarcos, 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łaBiju, 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łaMeadows, 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łaGHEORGHE, 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łaAramo-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łaGidroets, 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łaRozprawy doktorskie na temat "Software development"
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łaKurdi, Suparna Carleton University Dissertation Management Studies. "Software development process and strategies used to expedite software development". Ottawa, 1997.
Znajdź pełny tekst źródłaHellströ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łaUtveckling 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
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łaTOMASSETTI, FEDERICO CESARE ARGENTINO. "Polyglot software development". Doctoral thesis, Politecnico di Torino, 2014. http://hdl.handle.net/11583/2537697.
Pełny tekst źródłaLeinonen, 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łaSheikh, 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łaMoratilla, 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łaKe, 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łaCataloged 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
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łarkiye (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.
Książki na temat "Software development"
Freedman, Jeri. Software development. New York: Cavendish Square, 2015.
Znajdź pełny tekst źródłaZelkowitz, Marvin V. Software development. London: Academic Press/Elsevier, 2008.
Znajdź pełny tekst źródłaCockburn, Alistair. Agile software development. Boston: Addison-Wesley, 2002.
Znajdź pełny tekst źródłaMü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łaCharatan, 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łaAlmeida, 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łaStober, 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łaDingsø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łaG, 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łaCoad, Peter. Advanced software development. [United States]: TELOS Corp., 1988.
Znajdź pełny tekst źródłaCzęści książek na temat "Software development"
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łaPaulus, 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łaBuchanan, 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łaSingh, 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łaLientz, 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łaDubey, 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łaConstanda, 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łaHunt, 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łaNatriello, 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łaJuuso, 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łaStreszczenia konferencji na temat "Software development"
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łaDeMarco, 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łaYaeli, 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łaKakihara, 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łaArumugam, 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łaAguiar, 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łaNorthover, 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łaSedano, 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łaPoppendieck, 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łaLä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łaRaporty organizacyjne na temat "Software development"
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łaEllison, 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łaBaskinger, 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łaPiercey, 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łaForney, 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łaDow, 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łaManna, 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łaLuqi. 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łade 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łaHsu, 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