Увійти

Готові списки джерел за темами / Software engineering / Статті в журналах

Статті в журналах з теми "Software engineering"

Щоб переглянути інші типи публікацій з цієї теми, перейдіть за посиланням: Software engineering.

Автор: Grafiati

Опубліковано: 4 червня 2021

Оновлено: 22 червня 2024

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями

Оберіть тип джерела:

Ознайомтеся з топ-50 статей у журналах для дослідження на тему "Software engineering".

Біля кожної праці в переліку літератури доступна кнопка «Додати до бібліографії». Скористайтеся нею – і ми автоматично оформимо бібліографічне посилання на обрану працю в потрібному вам стилі цитування: APA, MLA, «Гарвард», «Чикаго», «Ванкувер» тощо.

Також ви можете завантажити повний текст наукової публікації у форматі «.pdf» та прочитати онлайн анотацію до роботи, якщо відповідні параметри наявні в метаданих.

Переглядайте статті в журналах для різних дисциплін та оформлюйте правильно вашу бібліографію.

1

Anand, Prabhjot Singh, Deepak Chahal, and Latika Kharb. "Tools for Software Re-Engineering." International Journal of Trend in Scientific Research and Development Volume-3, Issue-1 (December 31, 2018): 600–603. http://dx.doi.org/10.31142/ijtsrd19032.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

2

Sharad, Prof Sushmitha. "The need for Software Engineering." Global Journal For Research Analysis 3, no. 1 (June 15, 2012): 45. http://dx.doi.org/10.15373/22778160/january2014/72.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

3

Notkin, David. "Software, Software Engineering and Software Engineering Research: Some Unconventional Thoughts." Journal of Computer Science and Technology 24, no. 2 (March 2009): 189–97. http://dx.doi.org/10.1007/s11390-009-9217-4.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

4

Rine, David. "A note on software engineering, software systems engineering and software design." ACM SIGSOFT Software Engineering Notes 18, no. 4 (October 1993): 16–18. http://dx.doi.org/10.1145/163626.163629.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

5

Denert, Ernst. "Software Engineering." Informatik Spektrum 44, no. 2 (February 10, 2021): 122–25. http://dx.doi.org/10.1007/s00287-021-01338-y.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

6

Parnas, David Lorge. "Software engineering." Communications of the ACM 40, no. 9 (September 1997): 128. http://dx.doi.org/10.1145/260750.260784.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

7

Christiaanse, Vance. "Software engineering." 3C ON-LINE 4, no. 3 (July 1997): 12–13. http://dx.doi.org/10.1145/270877.270881.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

8

Loka, Raghavendra Rao. "Software engineering." ACM SIGSOFT Software Engineering Notes 17, no. 3 (July 1992): 34–38. http://dx.doi.org/10.1145/140938.140941.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

9

Ellis, Heidi. "Software engineering." ACM SIGSOFT Software Engineering Notes 32, no. 1 (January 2007): 4. http://dx.doi.org/10.1145/1226816.1226822.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

10

Kazman, Rick. "Software Engineering." Computer 50, no. 7 (2017): 10–11. http://dx.doi.org/10.1109/mc.2017.184.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

11

McMillin, Bruce. "Software Engineering." Computer 51, no. 2 (February 2018): 10–12. http://dx.doi.org/10.1109/mc.2018.1451647.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

12

Maiocchi, Marco. "Software engineering." Future Generation Computer Systems 7, no. 1 (October 1991): 23–29. http://dx.doi.org/10.1016/0167-739x(91)90013-n.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

13

Broy, Manfred, and Dieter Rombach. "Software Engineering." Informatik-Spektrum 25, no. 6 (December 1, 2002): 438–51. http://dx.doi.org/10.1007/s002870200266.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

14

Holmes, Neville. "Software engineering." ACM SIGSOFT Software Engineering Notes 24, no. 3 (May 1999): 81–83. http://dx.doi.org/10.1145/311963.312025.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

15

Djordjević-Kajan, Slobodanka. "Software engineering." Microelectronics Journal 28, no. 5 (June 1997): 604–5. http://dx.doi.org/10.1016/s0026-2692(97)80961-5.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

16

Tracz, Will. "Software engineering." ACM SIGSOFT Software Engineering Notes 38, no. 6 (November 11, 2013): 46. http://dx.doi.org/10.1145/2532780.2544425.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

17

Leveson, Nancy G. "Software engineering." Communications of the ACM 40, no. 2 (February 1997): 129–31. http://dx.doi.org/10.1145/253671.253754.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

18

Ghica, Dan. "Software engineering." XRDS: Crossroads, The ACM Magazine for Students 2, no. 3 (February 1996): 3. http://dx.doi.org/10.1145/332168.332170.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

19

Gabel, D. A. "Software engineering." IEEE Spectrum 31, no. 1 (January 1994): 38–41. http://dx.doi.org/10.1109/6.249059.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

20

Comerford, R. "Software engineering." IEEE Spectrum 32, no. 1 (1995): 62–65. http://dx.doi.org/10.1109/6.366247.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

21

Hines, J. R. "Software engineering." IEEE Spectrum 33, no. 1 (January 1996): 60–64. http://dx.doi.org/10.1109/6.476732.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

22

Ryan, M. "Software engineering." Information and Software Technology 32, no. 10 (December 1990): 699. http://dx.doi.org/10.1016/0950-5849(90)90105-z.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

23

West, D. "Software engineering." Computer Physics Communications 45, no. 1-3 (August 1987): 485. http://dx.doi.org/10.1016/0010-4655(87)90198-6.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

24

Petkovic, Dragutin, Gary Thompson, and Rainer Todtenhoefer. "Teaching practical software engineering and global software engineering." ACM SIGCSE Bulletin 38, no. 3 (September 26, 2006): 294–98. http://dx.doi.org/10.1145/1140123.1140202.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

25

CACM Staff. "Software engineering is engineering." Communications of the ACM 55, no. 1 (January 2012): 6–7. http://dx.doi.org/10.1145/2063176.2063178.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

26

Gupta, Karan, and Anita Goel. "Software Engineering for Tagging Software." International Journal of Software Engineering & Applications 4, no. 4 (July 31, 2013): 65–76. http://dx.doi.org/10.5121/ijsea.2013.4406.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

27

Hurlburt, George, and Jeffrey Voas. "Software is Driving Software Engineering?" IEEE Software 33, no. 1 (January 2016): 101–4. http://dx.doi.org/10.1109/ms.2016.22.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

28

Kittlaus, Dipl Inform Hans-Bernd. "Software-Engineering und Software-Fabrik." Informatik-Spektrum 26, no. 1 (January 1, 2003): 8–12. http://dx.doi.org/10.1007/s00287-002-0278-9.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

29

Broy, Manfred. "Software-Engineering und Software-Fabrik." Informatik-Spektrum 26, no. 1 (January 1, 2003): 13–16. http://dx.doi.org/10.1007/s00287-002-0279-8.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

30

Rainer, Austen, Dorota Jagielska, and Tracy Hall. "Software engineering practice versus evidence-based software engineering research." ACM SIGSOFT Software Engineering Notes 30, no. 4 (July 2005): 1–5. http://dx.doi.org/10.1145/1082983.1083177.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

31

Liu, Wen Hong, Chun Yan Wang, and Li Ge. "Software Engineering and Software Quality Management." Advanced Materials Research 926-930 (May 2014): 2642–45. http://dx.doi.org/10.4028/www.scientific.net/amr.926-930.2642.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

As the rapid development of social informatization, software reliability and security are highly required. Only applying high-quality software products can increase work efficiency. Quality is the life of software. How to enhance the quality of software products and how to use effective quality management method is an urgent need. This paper discuss the key point of software engineering and software quality management, and this is the basis of software quality ensurance model.

32

Leroy, Dorian, June Sallou, Johann Bourcier, and Benoit Combemale. "When Scientific Software Meets Software Engineering." Computer 54, no. 12 (December 2021): 60–71. http://dx.doi.org/10.1109/mc.2021.3102299.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

33

Hendrickson, E., and M. Fowler. "The software engineering of internet software." IEEE Software 19, no. 2 (March 2002): 23–24. http://dx.doi.org/10.1109/ms.2002.991328.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

34

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.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

35

Chen, Stephen. "From Software Art to Software Engineering." Engineering Management Journal 7, no. 4 (December 1995): 23–27. http://dx.doi.org/10.1080/10429247.1995.11414862.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

36

Olsen, N. C. "The software rush hour (software engineering)." IEEE Software 10, no. 5 (September 1993): 29–37. http://dx.doi.org/10.1109/52.232394.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

37

Sydorov, N. O., and N. M. Sydorova. "Software engineering and big data software." PROBLEMS IN PROGRAMMING, no. 3-4 (December 2022): 69–72. http://dx.doi.org/10.15407/pp2022.03-04.069.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Software engineering is a mature industry of human activity focused on the creation, deployment, marketing and maintenance of software. The fundamental concepts of engineering are life cycle model; three main components of life cycle phases - products, processes and resources; engineering and methodologies for creating, deployment and maintaining software. Software is the foun- dation of technological advances that lead to new high performance products. As the functionality of products grows, so does the need to efficiently and correctly create and maintain the complex software that enables this growth. Therefore, in addition to solving its own problems, software engineering serves the solution of the problems of creating and maintaining software in other domains, which are called application domains. Information technology is a well-known application domain. The basis of this domain is data. Information systems are being implemented in an organization to improve its effectiveness and efficiency. The functionality of information systems has grown dramatically when big data began to be used. This growth has led to the emergence of a wide variety of software-intensive big data information systems. At the same time, the role and importance of software engineering for solving the problems of this application domain has only intensified. Modern possibilities of software engineering are shown. The aspects of interaction between software engineering and big data systems are analyzed. The topics for the study of big data software ecosystems and big data system of systems are outlined.

38

Tchier, Fairouz, Latifa Ben Arfa Rabai, and Ali Mili. "Putting engineering into software engineering: Upholding software engineering principles in the classroom." Computers in Human Behavior 48 (July 2015): 245–54. http://dx.doi.org/10.1016/j.chb.2015.01.054.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

39

CACM Staff. "Software engineering, like electrical engineering." Communications of the ACM 58, no. 2 (January 28, 2015): 8–9. http://dx.doi.org/10.1145/2702734.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

40

Juristo, N., and S. T. Acuña. "Software Engineering and Knowledge Engineering." Expert Systems with Applications 23, no. 4 (November 2002): 345–47. http://dx.doi.org/10.1016/s0957-4174(02)00069-6.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

41

Alonso, Fernando, Jose Luis Maté, and Juan Pazos. "Knowledge engineering versus software engineering." Data & Knowledge Engineering 5, no. 2 (July 1990): 79–91. http://dx.doi.org/10.1016/0169-023x(90)90005-x.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

42

McGregor, John D. "Strategic Software Engineering." Journal of Object Technology 8, no. 3 (2009): 7. http://dx.doi.org/10.5381/jot.2009.8.3.c1.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

43

Foley, J. T., and M. Kyas. "Axiomatic Software Engineering." IOP Conference Series: Materials Science and Engineering 1174, no. 1 (August 1, 2021): 012025. http://dx.doi.org/10.1088/1757-899x/1174/1/012025.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

44

Hernández-López, Adrián, Ricardo Colomo-Palacios, Ángel García-Crespo, and Fernando Cabezas-Isla. "Software Engineering Productivity." International Journal of Information Technology Project Management 2, no. 1 (January 2011): 37–47. http://dx.doi.org/10.4018/jitpm.2011010103.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Software engineering productivity has been widely studied, but there are many issues that remain unsolved. Interesting works related to new metrics and more replications of past productivity analysis have emerged, however, in order to fulfill these unsolved issues, a consensus about influencing factors and well recognized and useful sets of inputs and outputs for using in measurements must be reached. In this regard, a clear state of the art may shed light on further research in software engineering productivity, which remains a promising research area. In this paper, general concepts of software engineering productivity along with general issues and recent challenges that need further attention from the research community are presented.

45

Khan, Khaled M. "Software Security Engineering." International Journal of Secure Software Engineering 3, no. 1 (January 2012): 62–63. http://dx.doi.org/10.4018/jsse.2012010104.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Muthu Ramachandran from Leeds Metropolitan University, UK has recently published a book entitled, Software Security Engineering: Design and Applications. The author claims that the book provides systematic approaches to engineering, building and assuring software security throughout software lifecycle, software security based requirements engineering, design for software security, software security implementation, best practice guideline on developing software security, test for software security, and quality validation for software security.

46

Marcu, Daniela, Dan Laurenţiu Milici, and Mirela Danubianu. "Software Engineering Ethics." Postmodern Openings 11, no. 4 (2020): 248–61. http://dx.doi.org/10.18662/po/11.4/233.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

Анотація:

Over the past 30 years, computer engineering has developed a lot. Currently, computer and software applications have a central role in business, medicine, security, communications, industry, education, and everyday life. Software developers, peoples who manage computer networks, data security analysts can do well, but they also have the potential to cause suffering and harm to the clients or ordinary peoples, willingly or not. For this reason, IT activities must be regulated by specific laws. From the beginning, we argue that the law is not the same thing as ethics, even if both promote the good. Certain ethical principles can be strengthened by law. In the field of computer science and technology, can exists theft, privacy violations, violence and harassment. To combat and punish such actions and behaviors, law is needed. But is software engineering a profession? If so, are there codes of professional ethics whereby specialists in the field can regulate their professional activity, as is the case, for example, in areas such as justice or medicine? In relation with that, Gibbs and Ford have identified 8 components of a professional infrastructure. Some of that is: initial vocational training, professional accreditation, licensing, continuous vocational training, the existence of code of ethics. (Ford & Gibbs, 1996). With the fact that software engineering is a profession, in this article we present the main principles of behavior. The principles are not legally binding. This are grouped by interest categories depending on who or what is involved in the interaction with software engineering.

47

Broy, Manfred, Ingolf H. Kruger, Alexander Pretschner, and Christian Salzmann. "Engineering Automotive Software." Proceedings of the IEEE 95, no. 2 (February 2007): 356–73. http://dx.doi.org/10.1109/jproc.2006.888386.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

48

Jeffery, D. R., and L. G. Votta. "Empirical Software Engineering." IEEE Transactions on Software Engineering 25, no. 4 (July 1999): 435–37. http://dx.doi.org/10.1109/tse.1999.799935.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

49

Moore, M. M. "Software engineering education." IEEE Software 19, no. 5 (September 2002): 103. http://dx.doi.org/10.1109/ms.2002.1032866.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

50

Thayer, R. H. "Glossary software engineering." IEEE Software 20, no. 4 (July 2003): 97–93. http://dx.doi.org/10.1109/ms.2003.1207487.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.