Einloggen

Thematische Bibliographien / Software engineering / Zeitschriftenartikel

Um die anderen Arten von Veröffentlichungen zu diesem Thema anzuzeigen, folgen Sie diesem Link: Software engineering.

Zeitschriftenartikel zum Thema „Software engineering“

Autor: Grafiati

Veröffentlicht am 4. Juni 2021

Zuletzt aktualisiert am 5. Juli 2025

Geben Sie eine Quelle nach APA, MLA, Chicago, Harvard und anderen Zitierweisen an

Wählen Sie eine Art der Quelle aus:

Machen Sie sich mit Top-50 Zeitschriftenartikel für die Forschung zum Thema "Software engineering" bekannt.

Neben jedem Werk im Literaturverzeichnis ist die Option "Zur Bibliographie hinzufügen" verfügbar. Nutzen Sie sie, wird Ihre bibliographische Angabe des gewählten Werkes nach der nötigen Zitierweise (APA, MLA, Harvard, Chicago, Vancouver usw.) automatisch gestaltet.

Sie können auch den vollen Text der wissenschaftlichen Publikation im PDF-Format herunterladen und eine Online-Annotation der Arbeit lesen, wenn die relevanten Parameter in den Metadaten verfügbar sind.

Sehen Sie die Zeitschriftenartikel für verschiedene Spezialgebieten durch und erstellen Sie Ihre Bibliographie auf korrekte Weise.

1

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

2

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

3

Yadla, Prasanth. "Ethics in Software Engineering: Privacy." International Journal of Science and Research (IJSR) 13, no. 11 (November 5, 2024): 1850–52. https://doi.org/10.21275/sr24113092623.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

4

Kumar, Ajit. "Software Re-engineering Process Model." International Journal of Science and Research (IJSR) 10, no. 1 (January 27, 2021): 474–76. https://doi.org/10.21275/sr21101152601.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

5

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

6

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

7

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

8

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

9

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

10

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

11

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

12

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

13

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

14

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

15

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

16

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

17

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

18

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

19

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

20

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

21

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

22

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

23

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

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

24

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

25

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

26

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

27

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

28

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

29

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

30

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

31

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

32

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

33

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

34

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.

Der volle Inhalt der Quelle

Annotation:

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.

APA, Harvard, Vancouver, ISO und andere Zitierweisen

35

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

36

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

37

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

38

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

39

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

40

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.

Der volle Inhalt der Quelle

Annotation:

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.

APA, Harvard, Vancouver, ISO und andere Zitierweisen

41

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

42

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

43

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

44

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

45

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

46

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.

Der volle Inhalt der Quelle

Annotation:

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.

APA, Harvard, Vancouver, ISO und andere Zitierweisen

47

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.

Der volle Inhalt der Quelle

Annotation:

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.

APA, Harvard, Vancouver, ISO und andere Zitierweisen

48

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.

Der volle Inhalt der Quelle

Annotation:

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.

APA, Harvard, Vancouver, ISO und andere Zitierweisen

49

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

50

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.

Der volle Inhalt der Quelle

APA, Harvard, Vancouver, ISO und andere Zitierweisen

Wir bieten Rabatte auf alle Premium-Pläne für Autoren, deren Werke in thematische Literatursammlungen aufgenommen wurden. Kontaktieren Sie uns, um einen einzigartigen Promo-Code zu erhalten!