Kliknij ten link, aby zobaczyć inne rodzaje publikacji na ten temat: Software development.

Artykuły w czasopismach na temat „Software development”

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

Wybierz rodzaj źródła:

Sprawdź 50 najlepszych artykułów w czasopismach 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 artykuły w czasopismach z różnych dziedzin i twórz odpowiednie bibliografie.

1

Boppana, Venkat. "Secure Practices in Software Development." Global Research Review in Business and Economics 10, no. 5 (2024): 216–28. https://doi.org/10.56805/grrbe.24.10.5.75.

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

SHYNKARUK, O., O. YASHYNA, and O. ONYSHKO. "SOFTWARE QUALITY MANAGEMENT DEVELOPMENT TOOLS." Herald of Khmelnytskyi National University. Technical sciences 291, no. 6 (2020): 39–44. https://doi.org/10.31891/2307-5732-2020-291-6-39-44.

Pełny tekst źródła
Streszczenie:
At the present stage of development of software tools in the field of web development, the number of web frameworks (VFK) has increased sharply. All of them have a number of advantages and disadvantages, and therefore it is important to choose the right and appropriate framework or set for each project, because the right choice depends on the quality, implementation time and reliability of each software product being developed. Generally speaking, web frameworks have definitely changed and improved their programming capabilities and become an integral part of the development process. There is
Style APA, Harvard, Vancouver, ISO itp.
3

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

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

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

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

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

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

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

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

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

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

Biju, Soly Mathew. "Agile Software Development." E-Learning and Digital Media 5, no. 1 (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.
9

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

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

GHEORGHE, Alina-Madalina, Ileana Daniela GHEORGHE, and Ioana Laura IATAN. "Agile Software Development." Informatica Economica 24, no. 2/2020 (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.
11

Aramo-Immonen, Heli, Hannu Jaakkola, and Harri Keto. "Multicultural Software Development." International Journal of Information Technology Project Management 2, no. 1 (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 glo
Style APA, Harvard, Vancouver, ISO itp.
12

Gidroets, M. O., and L. I. Grishanova. "SOFTWARE DEVELOPMENT METHODOLOGY." System analysis and logistics 4, no. 26 (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.
13

Nicolaysen, Torstein, Richard Sassoon, Maria B. Line, and Martin Gilje Jaatun. "Agile Software Development." International Journal of Secure Software Engineering 1, no. 3 (2010): 71–85. http://dx.doi.org/10.4018/jsse.2010070105.

Pełny tekst źródła
Streszczenie:
In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security des
Style APA, Harvard, Vancouver, ISO itp.
14

Hargreaves, Elizabeth, Daniela Damian, Filippo Lanubile, and James Chisan. "Global software development." ACM SIGSOFT Software Engineering Notes 29, no. 5 (2004): 1–5. http://dx.doi.org/10.1145/1022494.1022502.

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

Ebert, Christof, Pekka Abrahamsson, and Nilay Oza. "Lean Software Development." IEEE Software 29, no. 5 (2012): 22–25. http://dx.doi.org/10.1109/ms.2012.116.

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

Thomson, Alistair C. "Software Development Procedures." Educational Media International 22, no. 3 (1985): 2–4. http://dx.doi.org/10.1080/09523988508548813.

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

Fayad, Mohamed E. "Software development process." Communications of the ACM 40, no. 9 (1997): 101–3. http://dx.doi.org/10.1145/260750.260783.

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

Hall, Patrick A. V. "Software development standards." Software Engineering Journal 4, no. 3 (1989): 143. http://dx.doi.org/10.1049/sej.1989.0017.

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

Herbsleb, J. D., and D. Moitra. "Global software development." IEEE Software 18, no. 2 (2001): 16–20. http://dx.doi.org/10.1109/52.914732.

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

Filman, R. E. "Postmodern Software Development." IEEE Internet Computing 9, no. 1 (2005): 4–6. http://dx.doi.org/10.1109/mic.2005.20.

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

Henderson, P. B. "Software development environments." ACM SIGSOFT Software Engineering Notes 12, no. 1 (1987): 51–52. http://dx.doi.org/10.1145/24574.24582.

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

Blackburn, Joseph, Gary Scudder, and Luk N. Van Wassenhove. "Concurrent software development." Communications of the ACM 43, no. 11es (2000): 4. http://dx.doi.org/10.1145/352515.352519.

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

Matsudaira, Kate. "Lean software development." Communications of the ACM 58, no. 12 (2015): 56–58. http://dx.doi.org/10.1145/2814346.

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

Williams, Laurie, and James Tomayko. "Agile Software Development." Computer Science Education 12, no. 3 (2002): 167–68. http://dx.doi.org/10.1076/csed.12.3.167.8613.

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

McCallum, Tom. "Secure Software Development." ITNOW 60, no. 4 (2018): 42–43. http://dx.doi.org/10.1093/itnow/bwy101.

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

Sagheb-Tehrani, Mehdi, and Arbi Ghazarian. "Software development process." ACM SIGSOFT Software Engineering Notes 27, no. 2 (2002): 58–62. http://dx.doi.org/10.1145/511152.511162.

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

Shotton, M. W., R. C. Denny, and V. T. Forsyth. "CCP13 Software Development." Fibre Diffraction Review 7, no. 7 (1998): 40. http://dx.doi.org/10.1382/s19980740.

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

Shotton, M. W., and R. C. Denny. "CCP13 Software Development." Fibre Diffraction Review 8, no. 8 (1999): 14. http://dx.doi.org/10.1382/s19999014.

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

Conchúir, Eoin Ó., Pär J. Ågerfalk, Helena H. Olsson, and Brian Fitzgerald. "Global software development." Communications of the ACM 52, no. 8 (2009): 127–31. http://dx.doi.org/10.1145/1536616.1536648.

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

Robinson, H. "Postmodern Software Development." Computer Journal 41, no. 6 (1998): 363–75. http://dx.doi.org/10.1093/comjnl/41.6.363.

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

Lanubile, Filippo, Daniela Damian, and Heather L. Oppenheimer. "Global software development." ACM SIGSOFT Software Engineering Notes 28, no. 6 (2003): 2. http://dx.doi.org/10.1145/966221.966224.

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

Yilmaz, Murat, Rory V. O'Connor, and Paul Clarke. "Software Development Roles." ACM SIGSOFT Software Engineering Notes 40, no. 1 (2015): 1–5. http://dx.doi.org/10.1145/2693208.2693239.

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

Dart, Ellison, Feiler, and Habermann. "Software Development Environments." Computer 20, no. 11 (1987): 18–28. http://dx.doi.org/10.1109/mc.1987.1663413.

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

Topper, A. "Automating software development." IEEE Spectrum 28, no. 11 (1991): 56. http://dx.doi.org/10.1109/6.99018.

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

Sawyer, Steve. "Software development teams." Communications of the ACM 47, no. 12 (2004): 95–99. http://dx.doi.org/10.1145/1035134.1035140.

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

Mazza, C. "Controlling software development." Nuclear Instruments and Methods in Physics Research Section A: Accelerators, Spectrometers, Detectors and Associated Equipment 352, no. 1-2 (1994): 370–74. http://dx.doi.org/10.1016/0168-9002(94)91546-6.

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

Eder, Klaus, Jürgen Meyer, and Siegfried Hörfarter. "Efficient software development." ATZelektronik worldwide 4, no. 2 (2009): 50–54. http://dx.doi.org/10.1007/bf03242217.

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

Greer, Des, and Yann Hamon. "Agile Software Development." Software: Practice and Experience 41, no. 9 (2011): 943–44. http://dx.doi.org/10.1002/spe.1100.

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

Tarasova, Yu A. "SECURE SOFTWARE DEVELOPMENT." Научное обозрение. Технические науки (Scientific Review. Technical Sciences), no. 5 2023 (2023): 31–35. http://dx.doi.org/10.17513/srts.1450.

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

Wongthongtham, P., E. Chang, T. Dillon, and I. Sommerville. "Development of a Software Engineering Ontology for Multisite Software Development." IEEE Transactions on Knowledge and Data Engineering 21, no. 8 (2009): 1205–17. http://dx.doi.org/10.1109/tkde.2008.209.

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

Fabrianti Kusumasari, Tien, Bambang Riyanto Trilaksono, Atya Nur Aisha, and Fitria . "Software Development Team Competencies to Support Software Development Project Success." International Journal of Engineering & Technology 7, no. 4.40 (2018): 156–61. http://dx.doi.org/10.14419/ijet.v7i4.40.24424.

Pełny tekst źródła
Streszczenie:
Software development projects have relatively low success rates compared to other projects. One of the causes is human factors, lack of competence from the development team. The competency of the existing development team cannot meet project needs. Therefore, this research has analyzed the list of competencies that have an important role in the software development team. The list of competencies analyzed was obtained from the results of the literature review and evaluations from 17 practitioners in software development. From the literature review, 57 competency elements were obtained in the co
Style APA, Harvard, Vancouver, ISO itp.
42

Alfaro, Iván, and Ranganathan Chandrasekaran. "Software Quality and Development Speed in Global Software Development Teams." Business & Information Systems Engineering 57, no. 2 (2015): 91–102. http://dx.doi.org/10.1007/s12599-015-0372-6.

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

Dargham, J. A., N. Barsoum, A. Chekima, and R. K. Y. Chin. "Software Development of a Smart Irrigation System." Journal of Advanced Research in Dynamical and Control Systems 11, no. 12-SPECIAL ISSUE (2019): 818–23. http://dx.doi.org/10.5373/jardcs/v11sp12/20193281.

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

Liu, Yinlong, and Yong Wang. "A Study on Software Development Month Effort." Journal of Software 10, no. 7 (2015): 798–804. http://dx.doi.org/10.17706//jsw.10.7.798-804.

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

Tanaka, Sei, and Hiromi Kobayashi. "Trigger Based Assertion Tool in Software Development." Lecture Notes on Software Engineering 3, no. 2 (2015): 73–77. http://dx.doi.org/10.7763/lnse.2015.v3.169.

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

Nadeem, Muhammad Asgher, and Scott Uk-Jin Lee. "Requirement Elicitation Framework for Global Software Development." Indian Journal of Science and Technology 12, no. 43 (2019): 1–6. http://dx.doi.org/10.17485/ijst/2019/v12i43/146882.

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

Gupta, Naveen Kumar. "Impact of Flutter Technology in Software Development." International Journal of Research Publication and Reviews 5, no. 7 (2024): 3749–52. http://dx.doi.org/10.55248/gengpi.5.0724.1928.

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

Kaur, Kirandeep. "Imprecise Software Requirements: A Software Development Risk." IOSR Journal of Computer Engineering 7, no. 1 (2012): 10–12. http://dx.doi.org/10.9790/0661-0711012.

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

Jain, Parita, Arun Sharma, and Laxmi Ahuja. "Software Maintainability Estimation in Agile Software Development." International Journal of Open Source Software and Processes 9, no. 4 (2018): 65–78. http://dx.doi.org/10.4018/ijossp.2018100104.

Pełny tekst źródła
Streszczenie:
Agile methodologies have gained wide acceptance for developing high-quality products with a quick and flexible approach. However, until now, the quality of the agile process has not been validated quantitatively. Quality being important for the software system, there is a need for measurement. Estimating different quality factors will lead to a quality product. Also, agile software development does not provide any precise models to evaluate maintainability. Therefore, there is a need for an algorithmic approach that can serve as the basis for estimation of maintainability. The article proposes
Style APA, Harvard, Vancouver, ISO itp.
50

Kaur, Pawanpreet, and Sumit Sharma. "Agile Software Development in Global Software Engineering." International Journal of Computer Applications 97, no. 4 (2014): 39–43. http://dx.doi.org/10.5120/16999-7181.

Pełny tekst źródła
Style APA, Harvard, Vancouver, ISO itp.
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!