Relevant bibliographies by topics / Software engineer / Journal articles
To see the other types of publications on this topic, follow the link: Software engineer.

Journal articles on the topic 'Software engineer'

Author: Grafiati
Published: 4 June 2021
Last updated: 30 May 2022

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 engineer.'

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

Wallen, L. "Software engineer." Computer Bulletin 45, no. 5 (September 1, 2003): 29. http://dx.doi.org/10.1093/combul/45.5.29.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Whitmire, Scott A. "Engineer Your Software!" Synthesis Lectures on Algorithms and Software in Engineering 11, no. 2 (July 6, 2021): 1–143. http://dx.doi.org/10.2200/s01106ed1v01y202105ase021.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Bryden, Mark, and Doug McCorkle. "Virtual Engineering." Mechanical Engineering 127, no. 11 (November 1, 2005): 38–42. http://dx.doi.org/10.1115/1.2005-nov-4.

Full text
Abstract:
This article discusses future of virtual engineering. Not only will the plant of the future be different from the current one, but also the design tools that engineers use will be different. To reduce cost and shorten development time for the future plants, the DOE is developing virtual engineering as an enabling technology. To integrate all the parts in an intuitive manner will require a software framework, which is being developed by the Virtual Engineering Research Group at Iowa State University. The software is a virtual engineering toolkit called YE-Suite. It is composed of three main software engines—VE-CE, VE-Xplorer, and VE-Conductor—that coordinate the flow of data from the engineer to the virtual components being designed. YE-CE is responsible for the synchronization of the data among the various analysis and process models and the engineer. VE-Xplorer is the decision-making environment that allows the engineer to interact with the equipment models in a visual manner. YE-Conductor is the engineer’s mechanism to control models and other information.
APA, Harvard, Vancouver, ISO, and other styles
4

Burford, D. "CAREERS INSIDER: Software engineer." Computer Bulletin 44, no. 4 (July 1, 2002): 29. http://dx.doi.org/10.1093/combul/44.4.29.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Hall, Duncan. "The Ethical Software Engineer." IEEE Software 26, no. 4 (July 2009): 9–10. http://dx.doi.org/10.1109/ms.2009.106.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Tian, Jingbai, Jianghao Yin, and Liang Xiao. "Software Requirements Engineer’s Ability Assessment Method Based on Empirical Software Engineering." Wireless Communications and Mobile Computing 2022 (March 11, 2022): 1–10. http://dx.doi.org/10.1155/2022/3617140.

Full text
Abstract:
With the expansion of the scale and complexity of modern software systems, the failure rate of software projects remains high. One of the main reasons for the failure of software projects is the defects in processing software requirements. This paper proposes a software requirements engineer’s ability assessment method based on empirical software engineering to measure the matching degree between the software requirements engineer’s ability and industry expectations. First, collect the recruitment information of software requirements engineers from mainstream recruitment websites. Through natural language processing, the words related to the abilities of the software requirements engineer are counted. These words are summarized in the requirements acquisition, requirements analysis, and other SRE activities, then the industry expectations for various abilities are obtained. Later on, the authors collect the teaching settings of representative SRE courses, reflecting the software requirements engineer’s ability to learn the course. After that, this article defines the ratio of the industry expectation weight to the weight of each SRE activity in teaching as the software requirements engineer’s ability coefficient, which can intuitively reflect the matching degree between the software requirements engineer’s ability and industry expectations. Finally, take the national first-class undergraduate course “SRE” of Jinling Institute of Technology as an example to verify the method’s practicality to a certain extent.
APA, Harvard, Vancouver, ISO, and other styles
7

Harrison, W. "Skinner Wasn't a Software Engineer." IEEE Software 22, no. 3 (May 2005): 5–7. http://dx.doi.org/10.1109/ms.2005.76.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Dakin, K. "Software "engineer"? Time will tell." IEEE Software 14, no. 3 (1997): 105–6. http://dx.doi.org/10.1109/52.589248.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Baber, Robert L. "Portrait of a (software) engineer." Journal of Systems and Software 15, no. 1 (April 1991): 91–100. http://dx.doi.org/10.1016/0164-1212(91)90080-p.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

STALKER, RUTH, and IAN F. C. SMITH. "Structural monitoring using engineer–computer interaction." Artificial Intelligence for Engineering Design, Analysis and Manufacturing 16, no. 3 (June 2002): 203–18. http://dx.doi.org/10.1017/s0890060402163062.

Full text
Abstract:
Engineer–computer interaction (ECI) is a new subdomain of human–computer interaction that is specifically tailored to engineers' needs. ECI uses an information classification schema, provides a modular approach to task decomposition, and integrates standard engineering characteristics and working procedures into software. A software tool kit that interprets monitoring data taken from bridges was developed according to ECI guidelines. This tool kit was given to engineers for testing and evaluation. An empirical evaluation using questionnaires was performed. The results show that this ECI software corresponds to engineers' needs and the ECI approach has potential applications to other engineering tasks.
APA, Harvard, Vancouver, ISO, and other styles
11

Bieliková, Mária, and Pavol Návrat. "An Experience with the Use of Systems Engineer Case Tool." International Journal of Software Engineering and Knowledge Engineering 07, no. 02 (June 1997): 253–59. http://dx.doi.org/10.1142/s0218194097000151.

Full text
Abstract:
Systems Engineer is a client/server CASE tool for supporting software system development on PC machines under Windows. It compares fairly satisfactorily with other similar tools of the same category. Systems Engineer offers various supporting techniques which address the full software life cycle, from planning and design to code generation, reengineering and maintenance. It supports system engineers working in a team.
APA, Harvard, Vancouver, ISO, and other styles
12

Dyba, Tore, Neil Maiden, and Robert Glass. "The Reflective Software Engineer: Reflective Practice." IEEE Software 31, no. 4 (July 2014): 32–36. http://dx.doi.org/10.1109/ms.2014.97.

Full text
APA, Harvard, Vancouver, ISO, and other styles
13

Ozkaya, Ipek. "What Should a Software Engineer Know?" IEEE Software 37, no. 1 (January 2020): 3–6. http://dx.doi.org/10.1109/ms.2019.2946668.

Full text
APA, Harvard, Vancouver, ISO, and other styles
14

Keogh, Timothy. "Commentary: Living with the Software Engineer." Journal of Technical Writing and Communication 16, no. 4 (October 1986): 363–68. http://dx.doi.org/10.2190/1tyh-1v1y-tppd-a5lb.

Full text
Abstract:
Whether they know it or not, software engineers have a great deal of power over the language we use. They may create new words, such as byte or debug, which in a remarkably short time can become commonly used far beyond their original context. The new words are accepted quickly and even eagerly as the proliferation of microcomputers and the software to run them advance so rapidly. Yet there is still a great deal of confusion and frustration among readers of software manuals about just what those manuals are trying to say. Part of the problem is that each technical field has its own jargon that any novice must learn. But in the case of software manuals, there is the additional problem of familiar words being used in unfamiliar ways. This article describes the ambiguity created for the reader when familiar words, such as function or folding, are used in the context of the software manual with new, specialized meanings.
APA, Harvard, Vancouver, ISO, and other styles
15

HIRA, RON, OSCAR DIESTE, GEORGE SPANOUDAKIS, GIUSEPPE VISAGGIO, GUIDO WIRTZ, and S. K. CHANG. "IT-OUTSOURCING AND IT-OFFSHORING: TRENDS AND IMPACTS ON SE/KE CURRICULA." International Journal of Software Engineering and Knowledge Engineering 17, no. 05 (October 2007): 663–85. http://dx.doi.org/10.1142/s0218194007003409.

Full text
Abstract:
As a result of IT outsourcing and offshoring, IT professionals and educators are faced with the following question: What SE & KE skill sets will make a software engineer or a knowledge engineer immune to the impact of outsourcing and offshoring? This article summarizes the position papers from a panel held during the 2006 International Conference on Software Engineering and Knowledge Engineering from July 5 to 7 at the Hotel Sofitel, Redwood City in California, USA. Bringing software and knowledge engineers closer to the needs of their prospective customers and providing more value than simply pure software development and maintenance, is an open challenge at least for traditional computer science and software engineering curricula.
APA, Harvard, Vancouver, ISO, and other styles
16

Wang, Zhi Ming, Yu Chao Wang, and Dong Mei Tang. "Method Study on Digital-Model Conversion of Magnetic Worm from CAD Software to ANSYS Software." Advanced Materials Research 443-444 (January 2012): 252–57. http://dx.doi.org/10.4028/www.scientific.net/amr.443-444.252.

Full text
Abstract:
In order to solve the model element-missing problem of magnetic worm during the transmission process from Pro/Engineer software to ANSYS software, the paper proposes a novel transmission method. Tooth surface point-data file is established by the MATLAB software. Then the tooth surface curve is generated by the Pro/Engineer software according to the point-data file. The curve is imported into ANSYS software to set up the finite element analysis model. Finally grids are divided by the ANSYS software. After a series of programming and related works, the finite element model of the worm is established in ANSYS software and it indicates that this method is practical and effective and successfully resolved the model element-missing problem of magnetic worm during the transmission process from Pro/Engineer software to ANSYS software.
APA, Harvard, Vancouver, ISO, and other styles
17

Brown, B. G. "Who qualifies as a software engineer? [Letters]." Computer 33, no. 1 (January 2000): 9–10. http://dx.doi.org/10.1109/mc.2000.816258.

Full text
APA, Harvard, Vancouver, ISO, and other styles
18

Johnson, D. M. "The systems engineer and the software crisis." ACM SIGSOFT Software Engineering Notes 21, no. 2 (March 1996): 64–73. http://dx.doi.org/10.1145/227531.227542.

Full text
APA, Harvard, Vancouver, ISO, and other styles
19

Kuras, Andrzej. "Scheduling programs. The software engineer at work." Electronics Education 1994, no. 2 (1994): 34–35. http://dx.doi.org/10.1049/ee.1994.0054.

Full text
APA, Harvard, Vancouver, ISO, and other styles
20

Burton, Conducted by Paul. "Interview with Scott Durow, Software Engineer, Oxford." Physics Education 33, no. 3 (May 1998): 194–96. http://dx.doi.org/10.1088/0031-9120/33/3/022.

Full text
APA, Harvard, Vancouver, ISO, and other styles
21

Hurst, Mike. "Young Software Engineer of the Year 2021." ITNOW 63, no. 4 (December 1, 2021): 32. http://dx.doi.org/10.1093/itnow/bwab111.

Full text
Abstract:
Abstract BCS-in-Scotland, a grouping of the BCS Branches and Specialist Groups in Scotland, continued its long-standing involvement with the annual ScotSoft event organised by ScotlandIS. Mike Hurst, Treasurer and Webmaster of the BCS Edinburgh Branch, reports.
APA, Harvard, Vancouver, ISO, and other styles
22

Yao, Shou Guang, Sheng Chen Zhao, and Fei Liu. "Finite Element Analysis and Multidisciplinary Design Optimization of Diesel Engine Connecting Rod Based on ISIGHT." Advanced Materials Research 479-481 (February 2012): 1863–67. http://dx.doi.org/10.4028/www.scientific.net/amr.479-481.1863.

Full text
Abstract:
Based on the multidisciplinary design optimization method and the MDO software ISIGHT, the 16PA6STC diesel engine connecting rod was taken to the model, used the Pro/engineer software to build the 3D model of connecting rod. The software ANSYS and Nastran was taken to complete the static analysis and modal analysis to get the maximum equivalent stress and the first and second modal frequencies. the software including Pro/Engineer、ANSYS、Nastran, was combined on the ISIGHT to complete the structural optimization work on the condition of restrain the stress and modal of the connecting rod, to explore the application of the MDO design method in the diesel engine connecting rod structure optimization field, offer a reference for the further improvement design study.
APA, Harvard, Vancouver, ISO, and other styles
23

Duchesne, D. P. J., and J. L. Humar. "Engineering software – a structural consultant's perspective." Canadian Journal of Civil Engineering 18, no. 2 (April 1, 1991): 303–11. http://dx.doi.org/10.1139/l91-035.

Full text
Abstract:
The advantages that automatic computing offers in structural analysis, design, and drafting are now well known. Computers offer great speed and accuracy in the process of analysis and design, relieving the engineer of the drudgery of number crunching, permitting more time for innovation and creativity, and affording the opportunity of trying out several design alternatives. However, to realize the productivity gains and the improvements in design quality that computers offer, the engineer must be aware of the many pitfalls and problems associated with computerization: the financial commitment, the need for training, the difficulty in obtaining quality software, and the risk associated with using unreliable software compounded by the inadvertent complacency that computer usage may encourage. This paper attempts to provide an overview of the issues involved in computerizing a structural engineer's office. The advantages and disadvantages of computerization are discussed. The additional management responsibilities that computerization brings are highlighted. The types of software usually needed in a structural office are outlined. The constituents of good software are discussed with reference to user interface, analysis and design procedures, output, documentation, and program architecture. Finally, the concept of computer integration in structural design is explained and an example if provided to illustrate the technique. Key words: structural, computer, software, consultants, buildings, integration.
APA, Harvard, Vancouver, ISO, and other styles
24

Lazariev, Mykola, Andrii Sushchenko, and Volodymyr Yeremieiev. "Review of the monograph by V. S. Kruglyk "The system of training of future software engineers for the professional activity at higher educational institutions"." Ukrainian Journal of Educational Studies and Information Technology 8, no. 3 (September 30, 2020): 1–6. http://dx.doi.org/10.32919/uesit.2020.03.01.

Full text
Abstract:
In the publication the scientific-theoretical and methodological monographic study of V. S. Kruglyk "The system of training of future software engineers for the professional activity at higher educational institutions" has been analyzed, the study reflects the author conceptual approach to the scientific understanding of the problem of training software engineers for professional activities. The structure and content of the monograph have been analyzed; the scientific novelty of the research which consists in the development and substantiation of the author pedagogical system of training future software engineers for their professional activity and the structure of professional competence of a software engineer has been highlighted.
APA, Harvard, Vancouver, ISO, and other styles
25

Paech, Barbara. "What Is a Requirements Engineer?" IEEE Software 25, no. 4 (July 2008): 16–17. http://dx.doi.org/10.1109/ms.2008.106.

Full text
APA, Harvard, Vancouver, ISO, and other styles
26

Thilmany, Jean. "Shaking Hands Again." Mechanical Engineering 125, no. 04 (April 1, 2003): 34–36. http://dx.doi.org/10.1115/1.2003-apr-1.

Full text
Abstract:
This article discusses that technology can ease the adversity between industrial designers and mechanical engineers. In many manufacturing organizations, engineers coexist, albeit sometimes uneasily, with the industrial designers who shape the way the product will look on the outside. While mechanical engineers take care of laying out the mechanisms inside the product’s shell, industrial designers are concerned with its external shape and appeal. At Symbol Technologies in Holtsville, NY, that uneasy alliance does not exist anymore. Symbol’s devices have to be rugged because, although they are meant to be held easily in the hand, they can just as easily be dropped. The company uses I-deas, from EDS of Plano, Texas, for CAD modeling. Before beginning to sculpt on screen, the designer now talks to the engineer about the product. The engineer might know that both a scan engine and a set of batteries must be included inside the final product. The CAID and CAD software work together in such a way that, if an industrial designer changes something about the outside shape, the mechanical features automatically update to accommodate the change. Engineers do not have to rework the internal parts each time the external changed.
APA, Harvard, Vancouver, ISO, and other styles
27

Fryer, T. "The end of the engineer? [Generative design software]." Engineering & Technology 12, no. 9 (October 1, 2017): 26–29. http://dx.doi.org/10.1049/et.2017.0900.

Full text
APA, Harvard, Vancouver, ISO, and other styles
28

Basu, Choton. "Interview with:Ravichandra GunturuSenior Software Engineer Blackthorne Capital Management." Journal of Information Privacy and Security 6, no. 4 (October 2010): 70–72. http://dx.doi.org/10.1080/15536548.2010.10855900.

Full text
APA, Harvard, Vancouver, ISO, and other styles
29

Karadsheh, Louay, Haroun Alryalat, Ja'far Alqatawna, Samer Fawaz Alhawari, and Mufleh Amin AL Jarrah. "The Impact of Social Engineer Attack Phases on Improved Security Countermeasures." International Journal of Digital Crime and Forensics 14, no. 1 (January 2022): 1–26. http://dx.doi.org/10.4018/ijdcf.286762.

Full text
Abstract:
The objective of this paper is to examine a model to identify Social Engineer Attack Phases to improve the security countermeasures by Social-Engineer Involvement. A questionnaire was developed and distributed to a sample of 243 respondents who were actively engaged in 3 Jordanian telecommunication companies. All hypotheses were tested using (PLS-SEM). The results of the study indicate that Social Engineer Attack Phases (Identification the potential target, Target Recognition, Decision approach, and Execution) have a partially mediate and significant impact on improving the security countermeasures by Social-Engineer Involvement. On the other hand, the Social Engineer Attack Phases (Information Aggregations, Analysis and Interpretation, Armament, and Influencing) have a fully mediate and significant impact on improving the security countermeasures by Social-Engineer Involvement. The findings of this study help to provide deep insight to help security professionals prepare better and implement the right and appropriate countermeasures, whether technical or soft measures.
APA, Harvard, Vancouver, ISO, and other styles
30

Abdullah, Muaz. "MOCA - Malaysia Online Coding Academy." International Journal of Informatics and Communication Technology (IJ-ICT) 4, no. 3 (December 1, 2015): 131. http://dx.doi.org/10.11591/ijict.v4i3.pp131-136.

Full text
Abstract:
<span>Programmer is one of the hottest jobs nowadays. The need of competent programmer is increasing. But the gap between expected skillful software engineer and IT graduate skills is too big. This paper is discussing how an online integrated portal can help producing good software engineers with high programming skill and matching their competencies with job opportunity.</span>
APA, Harvard, Vancouver, ISO, and other styles
31

Christensen, M. "Bluepring for the ideal requirements engineer." IEEE Software 13, no. 2 (March 1996): 12. http://dx.doi.org/10.1109/ms.1996.506457.

Full text
APA, Harvard, Vancouver, ISO, and other styles
32

Sochat, Vanessa. "The 10 best practices for remote software engineering." Communications of the ACM 64, no. 5 (May 2021): 32–36. http://dx.doi.org/10.1145/3459613.

Full text
APA, Harvard, Vancouver, ISO, and other styles
33

Estrada Guzmán, Elsa Estrada, and Adriana Peña Pérez Negrón. "Influencia de los Roles de Equipo en las Actividades del Desarrollador de Software." RECIBE, REVISTA ELECTRÓNICA DE COMPUTACIÓN, INFORMÁTICA, BIOMÉDICA Y ELECTRÓNICA 2, no. 1 (December 5, 2017): C2–1—C2–19. http://dx.doi.org/10.32870/recibe.v2i1.10.

Full text
Abstract:
Uno de los roles básicos en el proceso del software es precisamente el de desarrollador, también denominado ingeniero de software, cuyas actividades principales son: el análisis, diseño, programación y pruebas del producto a desarrollar. Estas actividades, dependiendo generalmente del tamaño del proyecto y de la metodología, pueden estar a cargo de diferentes personas o bien de un grupo de desarrolladores que en conjunto las llevan todas a cabo; en este último caso, estaríamos hablando de trabajo en equipo entre iguales o pares. Por otro lado, de acuerdo con la teoría de roles de equipo, las personas tienden a comportarse de manera regular en forma distintiva cuando colaboran, estas formas particulares de colaborar es probable que influyan en el desempeño del equipo de desarrolladores de software. En este documento se presenta un caso de estudio con la finalidad de entender la influencia de los roles de equipo en ciertas actividades involucradas en el proceso de desarrollo de software.Abstract:One of the basic roles in the software process is precisely that of a developer, also called software engineer, whose main activities are: analysis, design, programming and product testing for said product. These activities, usually based on the project size and methodology, they can be assigned to different people or to a group of developers to take care of them; in this former case we would be talking about group work among peers. On the other hand, according to the team role theory, people tend to behave in a specific way when they collaborate, these particular collaborative behaviors probably have an influence on the software developer team’s performance. This document presents a case of study, with the intention of understanding the influence of team roles in certain activities involved in the software development process.Keywords: software developer, software engineer, software engineer roles, Belbin team roles.
APA, Harvard, Vancouver, ISO, and other styles
34

Groce, Alex. "Passages." ACM SIGSOFT Software Engineering Notes 46, no. 1 (February 2021): 9–12. http://dx.doi.org/10.1145/3437479.3437481.

Full text
Abstract:
Henry Petroski's The Pencil is one of Henry Petroski's many, always both scholarly and literary, and, most importantly, always engaging, books on engineering theory, practice, and history. For the software engineer, the pencil has a special place; while software engineers are not, particularly more than anyone else, pencil- users these days, we do have a special emphasis on sketching and the development of engineering tools, and one major thread of Petroski's history of the art of pencil-making is the use of pencils as an essential tool for engineers.
APA, Harvard, Vancouver, ISO, and other styles
35

Thomas Mason, Robert. "Changing Paradigms of Technical Skills for Data Engineers." Issues in Informing Science and Information Technology 15 (2018): 035–42. http://dx.doi.org/10.28945/4033.

Full text
Abstract:
Aim/Purpose: This paper investigates the changing paradigms for technical skills that are needed by Data Engineers in 2018. Background: A decade ago, data engineers needed technical skills for Relational Database Management Systems (RDBMS), such as Oracle and Microsoft SQL Server. With the advent of Hadoop and NoSQL Databases in recent years, Data Engineers require new skills to support the large distributed datastores (Big Data) that currently exist. Job demand for Data Scientists and Data Engineers has increased over the last five years. Methodology: This research methodology leveraged the Pig programming language that used MapReduce software located on the Amazon Web Services (AWS) Cloud. Data was collected from 100 Indeed.com job advertisements during July of 2017 and then was uploaded to the AWS Cloud. Using MapReduce, phrases/words were counted and then sorted. The sorted phrase / word counts were then leveraged to create the list of the 20 top skills needed by a Data Engineer based on the job advertisements. This list was compared to the 20 top skills for a Data Engineer presented by Stitch that surveyed 6,500 Data Engineers in 2016. Contribution: This paper presents a list of the 20 top technical skills required by a Data Engineer.
APA, Harvard, Vancouver, ISO, and other styles
36

Harwood, K. "On prototyping and the role of the software engineer." ACM SIGSOFT Software Engineering Notes 12, no. 4 (October 1987): 34. http://dx.doi.org/10.1145/37537.37541.

Full text
APA, Harvard, Vancouver, ISO, and other styles
37

Ren, Manjie, Lijian He, and Chuangcun Wang. "Ways to Train Application-Oriented Software Engineer in Universities." IERI Procedia 2 (2012): 108–13. http://dx.doi.org/10.1016/j.ieri.2012.06.059.

Full text
APA, Harvard, Vancouver, ISO, and other styles
38

HOSHI, Mitsuyuki, and Hiroshi MONDEN. "Engineer Education through the ET Software Design Robot Contest." Journal of JSEE 60, no. 3 (2012): 3_92–3_98. http://dx.doi.org/10.4307/jsee.60.3_92.

Full text
APA, Harvard, Vancouver, ISO, and other styles
39

Firesmith, Donald. "Using Quality Models to Engineer Quality Requirements." Journal of Object Technology 2, no. 5 (2003): 67. http://dx.doi.org/10.5381/jot.2003.2.5.c6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
40

Lu, Ming. "Fan Injecting Mold Design and CNC Process Based on Pro/Engineer." Applied Mechanics and Materials 246-247 (December 2012): 948–51. http://dx.doi.org/10.4028/www.scientific.net/amm.246-247.948.

Full text
Abstract:
The method to design fan injection mold by software Pro/Engineer Wildfire has been described in the paper. And the CNC programming module has been used to the analog of producing process to verify the design and manufacturing superiority of mold by application software Pro/Engineer.
APA, Harvard, Vancouver, ISO, and other styles
41

Thilmany, Jean. "Staring Down the Divide." Mechanical Engineering 125, no. 08 (August 1, 2003): 40–43. http://dx.doi.org/10.1115/1.2003-aug-2.

Full text
Abstract:
This article highlights that electrical and mechanical engineers work together on products like cell phones; on the contrary, their software programs do not work like this anymore. Like cellular telephones and computers, all products made up of a combination of printed circuit boards and shaped materials like plastics require a rather tight degree of cooperation among mechanical engineers, electrical engineers, and finite element analysts. But today’s computer-aided design and finite element analysis technology is not advanced enough to let them work as skillfully together as they might. Engineers and analysts still need to translate their designs into a neutral file format in order to pass files between their different software systems, and much can be lost in translation. But a number of engineering software developers are refining products to break down some of those barriers. Electrical and mechanical engineers commonly use the software to work together on projects like the design of fan-cooled computer central processing units and how they are anchored using already-specified techniques that the mechanical engineer has programmed into the system.
APA, Harvard, Vancouver, ISO, and other styles
42

Kortiš, Ján. "Enhancement of the Work in Scia Engineer's Environment by Employment of XML Programming Language." Civil and Environmental Engineering 11, no. 2 (December 1, 2015): 147–51. http://dx.doi.org/10.1515/cee-2015-0019.

Full text
Abstract:
Abstract The productivity of the work of engineers in the design of building structures by applying the rules of technical standards [1] has been increasing by using different software products for recent years. The software products offer engineers new possibilities to design different structures. However, there are problems especially for design of structures with similar static schemes as it is needed to follow the same work-steps. This can be more effective if the steps are done automatically by using a programming language for leading the processes that are done by software. The design process of timber structure which is done in the environment of Scia Engineer software is presented in the article. XML Programming Language is used for automatization of the design and the XML code is modified in the Excel environment by using VBA Programming language [2], [3].
APA, Harvard, Vancouver, ISO, and other styles
43

Casella, Giovanni, and Viviana Mascardi. "West2East: exploiting WEb Service Technologies to Engineer Agent-based SofTware." International Journal of Agent-Oriented Software Engineering 1, no. 3/4 (2007): 396. http://dx.doi.org/10.1504/ijaose.2007.016267.

Full text
APA, Harvard, Vancouver, ISO, and other styles
44

Hellerstein, Joseph L., Stanley Gu, Kiri Choi, and Herbert M. Sauro. "Recent advances in biomedical simulations: a manifesto for model engineering." F1000Research 8 (March 5, 2019): 261. http://dx.doi.org/10.12688/f1000research.15997.1.

Full text
Abstract:
Biomedical simulations are widely used to understand disease, engineer cells, and model cellular processes. In this article, we explore how to improve the quality of biomedical simulations by developing simulation models using tools and practices employed in software engineering. We refer to this direction as model engineering. Not all techniques used by software engineers are directly applicable to model engineering, and so some adaptations are required. That said, we believe that simulation models can benefit from software engineering practices for requirements, design, and construction as well as from software engineering tools for version control, error checking, and testing. Here we survey current efforts to improve simulation quality and discuss promising research directions for model engineering.
APA, Harvard, Vancouver, ISO, and other styles
45

Mughal, Muhammad Hussain, and Zubair Ahmed Shaikh. "Software Atom: An approach towards software components structuring to improve reusability." Sukkur IBA Journal of Computing and Mathematical Sciences 1, no. 2 (December 31, 2017): 66. http://dx.doi.org/10.30537/sjcms.v1i2.31.

Full text
Abstract:
Diversity of application domain compelled to design sustainable classification scheme for significantly amassing software repository. The atomic reusable software components are articulated to improve the software component reusability in volatile industry. Numerous approaches of software classification have been proposed over past decades. Each approach has some limitations related to coupling and cohesion. In this paper, we proposed a novel approach by constituting the software based on radical functionalities to improve software reusability. We analyze the element's semantics in Periodic Table used in chemistry to design our classification approach, and present this approach using tree-based classification to curtail software repository search space complexity and further refined based on semantic search techniques. We developed a Global unique Identifier (GUID) for indexing the functions and related components. We have exploited the correlation between chemistry element and software elements to simulate one to one mapping between them. Our approach is inspired from sustainability chemical periodic table. We have proposed software periodic table (SPT) representing atomic software components extracted from real application software. Based on SPT classified repository tree parsing & extraction to enable the user to program their software by customizing the ingredients of software requirements. The classified repository of software ingredients assist user to exploits their requirements to software engineer and enable requirement engineer to develop a rapid large-scale prototype with great essence. Furthermore, we would predict the usability of the categorized repository based on feedback of users. The continuous evolution of that proposed repository will be fine-tuned based on utilization and SPT would be gradually optimized by ant colony optimization techniques. Succinctly would provoke automating the software development process.
APA, Harvard, Vancouver, ISO, and other styles
46

Cossentino, Massimo, Stephane Galland, Nicolas Gaud, Vincent Hilaire, and Abderrafiaa Koukam. "An organisational approach to engineer emergence within holarchies." International Journal of Agent-Oriented Software Engineering 4, no. 3 (2010): 304. http://dx.doi.org/10.1504/ijaose.2010.036986.

Full text
APA, Harvard, Vancouver, ISO, and other styles
47

GUO, JIANG, and LUQI. "OBJECT MODELING TO RE-ENGINEER LEGACY SYSTEMS." International Journal of Software Engineering and Knowledge Engineering 10, no. 04 (August 2000): 471–85. http://dx.doi.org/10.1142/s0218194000000225.

Full text
Abstract:
This paper summarizes our experiences in using computer-supported methods to develop a software architecture to support the re-engineering of the Janus Combat Simulation System. We have analyzed the Janus FORTRAN source code, interviewed Janus domain experts, developed an object-oriented architecture for the Janus Combat Simulation subsystem, and validated the architecture with an executable prototype. In this paper, we propose methods to facilitate the evolution of the software component of these systems by recovering the behavior of the systems using systematic methods, and illustrate their use in the context of the Janus System.
APA, Harvard, Vancouver, ISO, and other styles
48

KUCHERUK, Oksana, and Tetyana KYSIL. "APPLIED TASKS IN THE FORMATION OF MATHEMATICAL COMPETENCE SOFTWARE ENGINEER." SCIENTIFIC BULLETIN OF FLIGHT ACADEMY. Section: Pedagogical Sciences, no. 5 (March 22, 2019): 155–60. http://dx.doi.org/10.33251/2522-1477-2019-5-155-160.

Full text
APA, Harvard, Vancouver, ISO, and other styles
49

Tanaka, Koji, Chikako Morimoto, Yoshikatsu Fujita, and Kazuhiko Tsuda. "The optimal configuration method of software engineer to IT project." International Journal of Computer Applications in Technology 52, no. 2/3 (2015): 177. http://dx.doi.org/10.1504/ijcat.2015.071979.

Full text
APA, Harvard, Vancouver, ISO, and other styles
50

Sedov, V. "PECULIARITIES OF PREPARATION OF FUTURE SOFTWARE ENGINEER FOR PEDAGOGICAL ACTIVITY." Information Technologies in Education, no. 23 (July 30, 2015): 127–35. http://dx.doi.org/10.14308/ite000542.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the bibliographies on the topic 'Software engineer' for other source types:
Dissertations / Theses Books
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!

To the bibliography