Artículos de revistas sobre el tema "Software engineering"

Siga este enlace para ver otros tipos de publicaciones sobre el tema: Software engineering.

Crea una cita precisa en los estilos APA, MLA, Chicago, Harvard y otros

Elija tipo de fuente:

Consulte los 50 mejores artículos de revistas para su investigación sobre el tema "Software engineering".

Junto a cada fuente en la lista de referencias hay un botón "Agregar a la bibliografía". Pulsa este botón, y generaremos automáticamente la referencia bibliográfica para la obra elegida en el estilo de cita que necesites: APA, MLA, Harvard, Vancouver, Chicago, etc.

También puede descargar el texto completo de la publicación académica en formato pdf y leer en línea su resumen siempre que esté disponible en los metadatos.

Explore artículos de revistas sobre una amplia variedad de disciplinas y organice su bibliografía correctamente.

1

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
2

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
3

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
4

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
5

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
6

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
7

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
8

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
9

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
10

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
11

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
12

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
13

Broy, Manfred y Dieter Rombach. "Software Engineering". Informatik-Spektrum 25, n.º 6 (1 de diciembre de 2002): 438–51. http://dx.doi.org/10.1007/s002870200266.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
14

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
15

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
16

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
17

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
18

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
19

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
20

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
21

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
22

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
23

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
24

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
25

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
26

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
27

Hurlburt, George y Jeffrey Voas. "Software is Driving Software Engineering?" IEEE Software 33, n.º 1 (enero de 2016): 101–4. http://dx.doi.org/10.1109/ms.2016.22.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
28

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
29

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
30

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
31

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

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
32

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
33

Hendrickson, E. y M. Fowler. "The software engineering of internet software". IEEE Software 19, n.º 2 (marzo de 2002): 23–24. http://dx.doi.org/10.1109/ms.2002.991328.

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
34

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
35

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
36

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
37

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

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
38

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
39

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
40

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
41

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
42

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
43

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
44

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

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
45

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

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
46

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

Texto completo
Resumen
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.
Los estilos APA, Harvard, Vancouver, ISO, etc.
47

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
48

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
49

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
50

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

Texto completo
Los estilos APA, Harvard, Vancouver, ISO, etc.
Ofrecemos descuentos en todos los planes premium para autores cuyas obras están incluidas en selecciones literarias temáticas. ¡Contáctenos para obtener un código promocional único!

Pasar a la bibliografía