Log in

Relevant bibliographies by topics / Software development / Journal articles

Journal articles on the topic 'Software development'

To see the other types of publications on this topic, follow the link: Software development.

Author: Grafiati

Published: 4 June 2021

Last updated: 31 July 2024

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the top 50 journal articles for your research on the topic 'Software development.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.

1

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

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

Full text

Abstract:

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.

APA, Harvard, Vancouver, ISO, and other styles

10

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

Full text

Abstract:

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.

APA, Harvard, Vancouver, ISO, and other styles

11

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

Full text

Abstract:

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 design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

APA, Harvard, Vancouver, ISO, and other styles

12

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

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.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

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.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

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.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

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 (August 2009): 1205–17. http://dx.doi.org/10.1109/tkde.2008.209.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

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 (December 31, 2019): 818–23. http://dx.doi.org/10.5373/jardcs/v11sp12/20193281.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

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.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

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.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

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 (October 2018): 65–78. http://dx.doi.org/10.4018/ijossp.2018100104.

Full text

Abstract:

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 an adaptive neuro-fuzzy inference system (ANFIS) model for estimating agile maintainability. Maintainability is one of the prominent quality factors in the case of agile development. The proposed model has been verified and found to be effective for assessing the maintainability of agile software.

APA, Harvard, Vancouver, ISO, and other styles

46

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Obrenovic, Zeljko. "Software Sketchifying: Bringing Innovation into Software Development." IEEE Software 30, no. 3 (May 2013): 80–86. http://dx.doi.org/10.1109/ms.2012.71.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Taylor, Richard N., Will Tracz, and Lou Coglianese. "Software development using domain-specific software architectures." ACM SIGSOFT Software Engineering Notes 20, no. 5 (December 1995): 27–38. http://dx.doi.org/10.1145/217030.217034.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Wassyng, Alan, and Mark Lawford. "Software tools for safety-critical software development." International Journal on Software Tools for Technology Transfer 8, no. 4-5 (September 23, 2005): 337–54. http://dx.doi.org/10.1007/s10009-005-0209-6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Lin, Tao. "Modern Software Development for JUNO offline software." EPJ Web of Conferences 295 (2024): 05015. http://dx.doi.org/10.1051/epjconf/202429505015.

Full text

Abstract:

The Jiangmen Underground Neutrino Observatory (JUNO), under construction in South China, primarily aims to determine the neutrino mass hierarchy and to precise measure the neutrino oscillation parameters. The data-taking is expected to start in 2024 and the detector plans to run for more than 20 years. The development of the JUNO offline software (JUNOSW) started in 2012, and it is quite challenging to maintain the JUNOSW for such a long time. In the last ten years, tools such as Subversion, Trac, and CMT had been adopted for software development. However, new stringent requirements came out, such as how to reduce the building time for the whole project, how to deploy offline algorithms to an online environment, and how to improve the code quality with code review and continuous integration. To meet the further requirements of software development, modern development tools are evaluated for JUNOSW, such as Git, GitLab, CMake, Docker, and Kubernetes. This contribution will present the software development system based on these modern tools for JUNOSW and the functionalities achieved: CMake macros are developed to simplify the build instructions for users; CMake generator expressions are used to control the build flags for the online and offline environments; a tool named git-junoenv is developed to help users partially checkout and build the software; a script is used to build and deploy the software on the CVMFS server; a Docker image with CVMFS client installed is created for continuous integration; a GitLab agent is set up to manage GitLab runners in Kubernetes with all the configurations in a GitLab repository.

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!