Relevant bibliographies by topics / Software engineer

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature 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 lists of relevant articles, books, theses, conference reports, and other scholarly sources 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.

Journal articles on the topic "Software engineer"

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
More sources

Dissertations / Theses on the topic "Software engineer"

1

Popov, A., and N. Gudkova. "Career path for software engineer in Ukraine." Thesis, Міжнародний центр науки і досліджень, 2020. https://er.knutd.edu.ua/handle/123456789/16770.

Full text
Abstract:
Today the IT market is at a high level of its development and this system is still a work in progress. It stands to reason that the 21st century is called the age of information technology because of the huge impact of the above-mentioned technologies on people’s daily lives. It is attractive to many people for several reasons. Building a portrait of a successful IT specialist depends on many factors, such as hard and soft skills, university degree, location, age. By meeting the requirements of the market, you have to improve any chance to build a successful career in IT area.
APA, Harvard, Vancouver, ISO, and other styles
2

Zielieke, Jane. "Maximizing student software engineer productivity in hybrid commercial-educational environments." Online version, 2004. http://www.uwstout.edu/lib/thesis/2004/2004zieliekej.pdf.

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

Bruce, Bobby R. "The blind software engineer : improving the non-functional properties of software by means of genetic improvement." Thesis, University College London (University of London), 2018. http://discovery.ucl.ac.uk/10052290/.

Full text
Abstract:
Life, even in its most basic of forms, continues to amaze mankind with the complexity of its design. When analysing this complexity it is easy to see why the idea of a grand designer has been such a prevalent idea in human history. If it is assumed intelligence is required to undertake a complex engineering feat, such as developing a modern computer system, then it is logical to assume a creature, even as basic as an earthworm, is the product of an even greater intelligence. Yet, as Darwin observed, intelligence is not a requirement for the creation of complex systems. Evolution, a phenomenon without consciousness or intellect can, over time, create systems of grand complexity and order. From this observation a question arises - is it possible to develop techniques inspired by Darwinian evolution to solve engineering problems without engineers? The first to ask such a question was Alan Turing, a person considered by many to be the father of computer science. In 1948 Turing proposed three approaches he believed could solve complex problems without the need for human intervention. The first was a purely logicdriven search. This arose a decade later in the form of general problem-solving algorithms. Though successful in solving toy problems which could be sufficiently formalised, solving real-world problems was found to be infeasible. The second approach Turing called 'cultural search'. This approach would store libraries of information to then reference and provide solutions to particular problems in accordance to this information. This is similar to what we would now refer to as an expert system. Though the first expert system is hard to date due to differences in definition, the development is normally attributed to Feigenbaum, Bachanan, Lederberg, and Sutherland for their work, originating in the 1960s, on the DENRAL system. Turing's last proposal was an iterative, evolutionary technique which he later expanded on stating: "We cannot expect to find a good child-machine at the first attempt. One must experiment with teaching one machine and see how well it learns. One can then try another and see if it is better or worse. There is an obvious connection between this process and evolution". Though a primitive proposal in comparison to modern techniques, Turing clearly identified the foundation of what we now refer to as Evolutionary Computation (EC). EC borrows principles from biological evolution and adapts them for use in computer systems. Despite EC initially appearing to be an awkward melding between the two perpendicular disciplines of biology and computer science, useful ideas from evolutionary theory can be utilised in engineering processes. Just as man dreamt of flight from watching birds, EC researchers dream of self-improving systems from observing evolutionary processes. Despite these similarities, evolutionary inspired techniques in computer science have yet to build complex software systems from scratch. Though they have been successfully utilised to solve complex problems, such as classification and clustering, there is a general acceptance that, as in nature, these evolutionary processes take vast amounts of time to create complex structures from simple starting points. Even the best computer systems cannot compete with nature's ability to evaluate many millions of variants in parallel over the course of millennia. It is for this reason research into modifying and optimising already existing software, a process known as Genetic Improvement, has blossomed. Genetic Improvement (commonly referred to as 'GI') modifies existing software using search-based techniques with respect to some objective. These search-based techniques are typically evolutionary and, if not, are based on iterative improvement which we may view as a form of evolution. GI sets out to solve the 'last mile' problems of software development; problems that arise in software engineering close to completion, such as bugs or sub-optimal performance. It is the genetic improvement of non-functional properties, such as execution time and energy consumption, which we concern ourselves with in this thesis, as we find it to be the area of research which is the most interesting, and the most exciting. It is hoped that those referencing this thesis may share the same vision: that the genetic improvement of non-functional properties has the potential to transform software development, and that the work presented here is a step towards that goal. The thesis is divided into six chapters (inclusive of this 'Introduction' chapter). In Chapter 2 we explain the background material necessary to understand the content discussed later in the following chapters. From this, in Chapter 3, we highlight our investigations into the novel nonfunctional property of energy consumption which, in part, includes a study in how energy may be reduced via the approximation of output. We then expand on this in Chapter 4 by discussing our investigations into the applicability of GI in the domain of approximate computing, which covers a study into optimising the non-functional properties of software running on novel hardware - in this case, Android tablet devices. We then show, in Chapter 5, early research into how GI may be used to specialise software for specific hardware targets; in particular, how GI may automatically modify sequential code to run on GPUs. Finally, in Chapter 6 we discuss what relevant work is currently being undertaken by using the area of genetic improvement, and provide the reader with clear and concise take-away messages from this thesis.
APA, Harvard, Vancouver, ISO, and other styles
4

LaGuardia, John Louis. "Computer Aided Parametric Screw Design and Analysis Using Pro/Engineer Solid Modeling Software." University of Akron / OhioLINK, 2009. http://rave.ohiolink.edu/etdc/view?acc_num=akron1237988201.

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

Iftikhar, Muhammad Usman. "A Model-Based Approach to Engineer Self-Adaptive Systems with Guarantees." Doctoral thesis, Linnéuniversitetet, Institutionen för datavetenskap, fysik och matematik, DFM, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-69136.

Full text
Abstract:
Modern software systems are increasingly characterized by uncertainties in the operating context and user requirements. These uncertainties are difficult to predict at design time. Achieving the quality goals of such systems depends on the ability of the software to deal with these uncertainties at runtime. A self-adaptive system employs a feedback loop to continuously monitor and adapt itself to achieve particular quality goals (i.e., adaptation goals) regardless of uncertainties. Current research applies formal techniques to provide guarantees for adaptation goals, typically using exhaustive verification techniques. Although these techniques offer strong guarantees for the goals, they suffer from well-known state explosion problem. In this thesis, we take a broader perspective and focus on two types of guarantees: (1) functional correctness of the feedback loop, and (2) guaranteeing the adaptation goals in an efficient manner. To that end, we present ActivFORMS (Active FORmal Models for Self-adaptation), a formally founded model-driven approach for engineering self-adaptive systems with guarantees. ActivFORMS achieves functional correctness by direct execution of formally verified models of the feedback loop using a reusable virtual machine. To efficiently provide guarantees for the adaptation goals with a required level of confidence, ActivFORMS applies statistical model checking at runtime. ActivFORMS supports on the fly changes of adaptation goals and updates of the verified feedback loop models that meet the changed goals. To demonstrate the applicability and effectiveness of the approach, we applied ActivFORMS in several domains: warehouse transportation, oceanic surveillance, tele assistance, and IoT building security monitoring.
Marie Curie CIG, FP7-PEOPLE-2011-CIG, Project ID: 303791
APA, Harvard, Vancouver, ISO, and other styles
6

França, Alberto César Cavalcanti. "A theory of motivation and satisfaction of software engineers." Universidade Federal de Pernambuco, 2014. https://repositorio.ufpe.br/handle/123456789/12006.

Full text
Abstract:
Submitted by Nayara Passos (nayara.passos@ufpe.br) on 2015-03-11T18:03:12Z No. of bitstreams: 2 TESE Alberto César Cavalcanti França.pdf: 3788012 bytes, checksum: a84eaeee00c35211070eb3130be655f2 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
Made available in DSpace on 2015-03-11T18:03:12Z (GMT). No. of bitstreams: 2 TESE Alberto César Cavalcanti França.pdf: 3788012 bytes, checksum: a84eaeee00c35211070eb3130be655f2 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Previous issue date: 2014
CNPq
Pesquisas na área de engenharia de software indicam que o gerenciamento apropriado da motivação e satisfação no trabalho são importantes para o sucesso de projetos de software. No entanto, rara tem sido a preocupação com o uso apropriado de teorias bem estabelecidas para fundamentar tais pesquisas, o que deixa em aberto várias questões práticas sobre motivação e satisfação no contexto do desenvolvimento de softwares. Evidências apontam que o conhecimento sobre a satisfação no trabalho, neste contexto, está relativamente consolidado, mas ainda há muito a se aprender sobre as características específicas que antecedem a motivação dos engenheiros de software. Objetivo: O ponto de partida compreende teorias de Satisfação no Trabalho e das Características do Trabalho, que defendem que motivação e satisfação no trabalho referem-se a fenômenos distintos. Esta tese objetiva então clarificar quais são as características do trabalho que influenciam a motivação de engenheiros de software. Método: Este quadro teórico inicial foi evoluído baseado nos aprendizados resultantes de um estudo de múltiplos casos, executado em quatro organisações de software em Recife-PE. Durante 11 meses, dados foram coletados nestas organizações, através de entrevistas semi-estruturadas, estudos diários, e análise documental. Resultados: Os resultados apontam que (1) engenheiros de software não estão conscientes sobre a distinção entre os dois fenômenos (motivação e satisfação no trabalho), (2) motivação é caracterizada pelo engajamento e concentração, (3) motivação é afetada por diversas características da tarefa do engenheiro de software, mas também pela percepção sobre o engajamento dos colegas de trabalho e pela auto-confiança técnica do trabalhador, (4) motivação contribui para a satisfação no trabalho, moderada pela informação provida sobre a performance individual dos engenheiros, e (5) o papel mediador das características pessoais do indivíduo é universal. Conclusão: Com base nestes dados, é proposta uma nova teoria de motivação e satisfação de engenheiros de software (TMS-SE) que une elementos de teorias bem estabelecidas, expandindo-as e adaptando-as à realidade específica de engenheiros de software. A TMS-SE representa um avanço em nossa compreensão do comportamento de engenheiros de software, bem como levanta novas questões e propõe um terreno organizado para futuras investigações nesta área.
Context: Previous research work in the Software Engineering field indicates that a proper management of motivation and job satisfaction at work can help software organisations to achieve higher levels of project success. However, the little concern with the adequate use of well-established theories to underpin these researches left unclear several theoretical and practical aspects of work motivation and job satisfaction in the software context. In fact, there is enough knowledge about job satisfaction factors, but not on specific characteristics of the work that motivate software engineers. Objective: The starting point of this research comprises the Job Satisfaction and the Job Characteristics theories, which argue that job satisfaction and work motivation are distinguishable phenomena, with distinct antecedents and different outcomes. Then, this thesis aims to clarify specifically what factors drive motivation of software engineers at work. Method: The initial theoretical framework was evaluated and enhanced based on findings from a multiple case study that comprised four different software organisations from Recife, Brazil. For 11 months, rich data was collected independently in those organisations, by means of semi-structured interviews, diary studies, and document analyses, and the synthesis followed a standard procedure of cross-case analysis. Results: The results point out that (1) practitioners are not aware of the distinction between work motivation and job satisfaction, (2) work motivation is characterized by engagement and concentration, (3) work motivation is affected by software engineering tasks characteristics and by the co-workers’ engagement, workload and technical confidence, (4) work motivation improves satisfaction moderated by feedback information provided about the individual’s performance, and (5) the mediating role of individual characteristics is pervasive. Conclusion: Based on these data, it was possible to draw up a new theory of motivation and satisfaction of software engineers (TMS-SE), which unites elements from well established theories, expands and adapts them to the software engineering specific context. The TMS-SE represents an advance on our understanding of software engineers’ behaviour as well as it raises new questions and provides an organised ground for future investigations in this area.
APA, Harvard, Vancouver, ISO, and other styles
7

SANTOS, Ronnie Edson de Souza. "The Influence of Job Rotation on Motivation and Satisfaction of Software Engineers." Universidade Federal de Pernambuco, 2015. https://repositorio.ufpe.br/handle/123456789/16366.

Full text
Abstract:
Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-04-07T12:05:26Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Ronnie Edson de Souza Santos - Dissertação de Mestrado.pdf: 1606424 bytes, checksum: a113e8f9718b34411e84149694b571ce (MD5)
Made available in DSpace on 2016-04-07T12:05:26Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Ronnie Edson de Souza Santos - Dissertação de Mestrado.pdf: 1606424 bytes, checksum: a113e8f9718b34411e84149694b571ce (MD5) Previous issue date: 2015-01-22
Context. During the last decades, human factors have become of great interest for many software engineering researchers, considering there are a wide variety of human and social aspects that might affect the way software engineers perform their work. As an example of this, recent research revealed a need for the proper management of two elements, the motivation and the satisfaction of software engineers, in order to achieve higher levels of performance at work. In this context, the Theory of Motivation and Satisfaction of Software Engineers (TMS-SE), recently established, confirms this need and recognizes the difference between these two factors, demonstrating that motivated software engineers are engaged and concentrated, while satisfaction is perceived in terms of happiness at work. Goal. Although having observed a wide diversity of aspects present at the software development environment, the TMS-SE did not specifically address the practice known as Job Rotation, whereby people are constantly switching jobs or projects at the same organization, and the effects of this practice on the motivation and satisfaction of software engineers. Thus, the main goal of this research is to investigate and discuss how the practice of job rotation can influence the motivation and the satisfaction of these individuals. Method. To achieve this goal, a qualitative case study was conducted in a software organization where the practice of job rotation amongst software projects is common. A group of software engineers were interviewed in order to collect data about their experience with this practice. Results. The findings suggest that, in a context in which the rotation of software engineers is frequent, it is necessary to find the balance between the positive and negative factors affecting the engagement and the concentration of these individuals, otherwise, their motivation will be impaired by the increase in the cognitive overload at work. In addition, the lack of feedback, resultant from constant movement among projects and teams, has a direct and negative impact on job satisfaction.
Contexto. Durante as últimas décadas, os fatores humanos tem recebido grande atenção de muitos pesquisadores de área de Engenharia de Software, pois estes fatores afetam a forma como os engenheiros de software executam o seu trabalho. A exemplo disto, pesquisas recentes revelaram a necessidade de uma gestão adequada da motivação e satisfação de engenheiros de software para que se possa atingir altos níveis de desempenho. Neste contexto, a Teoria da Motivação e Satisfação dos Engenheiros de Software (TMS-SE), estabelecida recentemente, confirma esta necessidade e estabelece a diferença entre estes dois fatores, demonstrando que engenheiros de software motivados são empenhados e concentrados, enquanto a satisfação é percebida em termos de contentamento com o trabalho. Objetivo. Apesar de ter discutido uma grande variedade de aspectos relacionados com o trabalho de equipes de desenvolvimento de software, a TMS-SE não explica diretamente o impacto da prática de Job Rotation (rotações de trabalho), através da qual estes indivíduos são periodicamente mudados de equipe e de projeto de software, na motivação e satisfação dos engenheiros de software. Assim, o objetivo desta pesquisa foi investigar e discutir como as rotações de trabalho podem influenciar a motivação e a satisfação de engenheiros de software. Método. Para atingir este objetivo, um estudo de caso qualitativo foi realizado em uma organização de software que utiliza a prática de rotação de engenheiros de software, os quais foram entrevistados sobre a sua experiência neste processo. Resultados. Os resultados sugerem que, em um contexto em que a rotação de engenheiros de software é freqüente, faz-se necessário buscar o equilíbrio entre os fatores positivos e negativos que afetam o engajamento e a concentração destes indivíduos, caso contrário, sua motivação será prejudicada pelo aumento da carga cognitiva do trabalho. Além disso, a falta de feedback sobre o trabalho, tem impacto negativo direto sobre a satisfação no trabalho.
APA, Harvard, Vancouver, ISO, and other styles
8

Karlson, Max, and Fredrik Olsson. "Investigating the Newly Graduated StudentsExperience after University." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-18133.

Full text
Abstract:
Today’s labor market is teeming with software development jobs, and employeesare needed more than ever. With this statement, one would believe it is easy fora newly graduated student to start their career. However, according to severalstudies, there are specific areas where newly graduated Software Engineeringstudents struggle when beginning their first job. Currently, there is a displace-ment about what the school should focus on when teaching their students. Thiscauses various challenges to arise for newly graduated students when they areinitially starting their career. To address this issue, this study aims to iden-tify whether or not there exists a gap between the education provided by theuniversities, and what is expected from the industry. In accordance with this,the purpose is also the point out which areas might be challenging for newlygraduated students, and highlight how the school and industry can benefit fromthe results of this study.By conducting interviews with both newly graduated student with one to threeyears working experience or personnel responsible for hiring new employees atcompanies, this study will give an insight on which common areas newly grad-uates may struggle with. Although the result specifies several areas which arechallenging to newly graduated students. The greatest challenges which thenewly graduated graduated students faced were areas revolving around softskills. This was in accordance with the opinions of the recruiters. Insinuatingthat these areas are what the school should focus more on. Other differencesbetween the newly graduated interviewee’s opinions and the recruiters are alsohighlighted in the report Several subjects in school could improve its way ofteaching. Furthermore, there are possibilities for companies to better adjusttheir on-boarding of newly graduated. By addressing the challenges which newlygraduated face they can provide their new employees with a better understand-ing of how to properly work and function in the industry today.
APA, Harvard, Vancouver, ISO, and other styles
9

Ferreira, Adriane Pedroso Dias. "MetImage: uma metodologia para desenvolvimento de software para o processamento e análise de imagens." Universidade Federal de Santa Maria, 2006. http://repositorio.ufsm.br/handle/1/8243.

Full text
Abstract:
The development of image processing and analysis software is a complex task by using mathematical methods to solve problems, by needing multidisciplinary team and demanding high degree of software developed quality. Therefore, is very important to utilize a methodology that organizes and improves the process of development of this type of software. The existence of a methodology is pointed out as one of the first steps toward the management and improvement the process software development. Therefore, this work presents a specific methodology for the development of image processing and analysis software, called, in this work, MetImage. The goal of this methodology is to improve the deficiencies detected in existing methodologies, such as the excessive resources, bureaucracy, exaggerated control and the documentation gap, in same specific cases. The methodology proposal was implanted in the context of a research group. The main results obtained were the specification of the team activities, the inclusion of the stage of learning on the necessary mathematical methods for the implementation of the functionalities and the standardization of code. Moreover, the documentation generated can be use as a support for the agreement between specialists of the different areas that make part of the research group.
O desenvolvimento de software para processamento e análise de imagens é uma tarefa complexa por utilizar métodos matemáticos para resolver os problemas, por necessitar de uma equipe multidisciplinar e por exigir alto grau de qualidade do software desenvolvido. Portanto, fazer uso de uma metodologia que organize e melhore o processo de desenvolvimento desse tipo de software é de vital importância. A existência de uma metodologia é apontada como um dos primeiros passos em direção ao gerenciamento e a melhoria do processo de desenvolvimento de software. Assim, este trabalho apresenta uma metodologia específica para o desenvolvimento de software para processamento e análise de imagens, chamada nesse trabalho de MetImage. O objetivo dessa metodologia é suprir as deficiências detectadas nas metodologias existentes, tais como o excesso de recursos, burocracia, controle exagerado e falta de documentação, em alguns casos específicos. A metodologia proposta foi implantada no contexto de um grupo de pesquisa. Os principais resultados obtidos foram: a especificação das atividades da equipe, a inclusão de uma etapa de aprendizagem sobre os métodos matemáticos necessários para a implementação das funcionalidades requeridas pelos sistemas e a padronização de código. Além disso, a documentação gerada pode servir de apoio para o entendimento entre especialistas das diferentes áreas que fazem parte do grupo de pesquisa.
APA, Harvard, Vancouver, ISO, and other styles
10

Cyrillo, Luciano Cavallini. "GesProDS - um modelo de gestão de projetos distribuídos de software." Universidade de São Paulo, 2005. http://www.teses.usp.br/teses/disponiveis/3/3141/tde-01032006-113023/.

Full text
Abstract:
Este trabalho apresenta um modelo para gestão de projetos distribuídos de software. Inicialmente, são apresentados os principais problemas identificados na literatura em relação ao Desenvolvimento Distribuído de Software. Em seguida, são analisados alguns modelos de gestão especializados neste tipo de desenvolvimento e também modelos tradicionais de gestão. Uma comparação entre os modelos é realizada para identificação do nível de atendimento de cada um em relação aos principais problemas identificados para este contexto de desenvolvimento. As melhores práticas de gestão em ambientes de Desenvolvimento Distribuído de Software são identificadas e utilizadas para compor um modelo de Gestão de Projetos Distribuídos de Software (GesProDS). O detalhamento do modelo envolve a descrição dos papéis, responsabilidades das organizações e recursos envolvidos. Além disso, a estrutura da organização envolvida e os processos de gestão identificados são descritos.
This work shows a model for management of Global Software Development projects. Initially the main problems identified in literature for this kind of projects are presented. After that, some specialized models of project management are discussed. A comparison between the identified models and the most known models of project management in relation to the main described problems for this context is also carried through. From the described information, the best practices of project management are identified and used to compose a project management model (GesProDS) for Global Software Development Projects. This model is described including its roles, responsibilities of organizations and required resources. Further more, the structure of the virtual organization and management processes are described.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software engineer"

1

Myers, Colin, Tracy Hall, and Dave Pitt, eds. The Responsible Software Engineer. London: Springer London, 1997. http://dx.doi.org/10.1007/978-1-4471-0923-5.

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

Westfall, Linda. The certified software quality engineer handbook. Milwaukee, Wis: ASQ Quality Press, 2009.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Westfall, Linda. The certified software quality engineer handbook. Milwaukee, Wis: ASQ Quality Press, 2009.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Laplante, Phillip A. What Every Engineer Should Know about Software Engineering. London: Taylor and Francis, 2007.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Laplante, Phillip A. What every engineer should know about software engineering. Boca Raton, FL: Taylor & Francis, 2007.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Tittel, Ed. Microsoft certified systems engineer. Albany, NY: Coriolis Group, 1998.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

RHCE: Red Hat Certified Engineer. San Francisco: Sybex, 2001.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Palmer, Michael J. Microsoft certified systems engineer. Albany, NY: Coriolis Group Books, 1998.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Microsoft certified systems engineer. Indianapolis, IN: Que, 1997.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Cohen, Judith Love. You can be a woman engineer. Culver City, CA: Cascade Pass, Inc., 1995.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software engineer"

1

Foster, Elvis C. "The Role of the Software Engineer." In Software Engineering, 21–40. Berkeley, CA: Apress, 2014. http://dx.doi.org/10.1007/978-1-4842-0847-2_2.

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

Foster, Elvis C. "The Role of the Software Engineer." In Software Engineering, 21–37. 2nd ed. Boca Raton: Auerbach Publications, 2021. http://dx.doi.org/10.1201/9780367746025-3.

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

Myers, Colin, Tracy Hall, and Dave Pitt. "Software Project Management Ethics." In The Responsible Software Engineer, 100–106. London: Springer London, 1997. http://dx.doi.org/10.1007/978-1-4471-0923-5_11.

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

Habermann, A. Nico. "The Environment for the Software Engineer." In Software Engineering Education, 78–86. New York, NY: Springer New York, 1987. http://dx.doi.org/10.1007/978-1-4612-4720-3_8.

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

Smith, David J., and Kenneth B. Wood. "The Role of the Software Engineer." In Engineering Quality Software, 200–204. Dordrecht: Springer Netherlands, 1989. http://dx.doi.org/10.1007/978-94-009-1121-5_13.

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

Myers, Colin, Tracy Hall, and Dave Pitt. "Software Engineering: A New Professionalism." In The Responsible Software Engineer, 21–31. London: Springer London, 1997. http://dx.doi.org/10.1007/978-1-4471-0923-5_2.

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

Myers, Colin, Tracy Hall, and Dave Pitt. "Selling, Marketing and Procuring Software." In The Responsible Software Engineer, 277–84. London: Springer London, 1997. http://dx.doi.org/10.1007/978-1-4471-0923-5_29.

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

Myers, Colin, Tracy Hall, and Dave Pitt. "Who should License Software Engineers?" In The Responsible Software Engineer, 72–77. London: Springer London, 1997. http://dx.doi.org/10.1007/978-1-4471-0923-5_8.

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

Myers, Colin, Tracy Hall, and Dave Pitt. "Introduction." In The Responsible Software Engineer, 7–16. London: Springer London, 1997. http://dx.doi.org/10.1007/978-1-4471-0923-5_1.

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

Myers, Colin, Tracy Hall, and Dave Pitt. "Can a Software Engineer Afford to be Ethical?" In The Responsible Software Engineer, 92–99. London: Springer London, 1997. http://dx.doi.org/10.1007/978-1-4471-0923-5_10.

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

Conference papers on the topic "Software engineer"

1

Belady, Laszlo A. "Software engineer, the system designer." In the 1986 ACM fourteenth annual conference. New York, New York, USA: ACM Press, 1986. http://dx.doi.org/10.1145/324634.325189.

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

Orsted, Martin. "Software development engineer in Microsoft." In the 22nd international conference. New York, New York, USA: ACM Press, 2000. http://dx.doi.org/10.1145/337180.337445.

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

Peters, Anne-Kathrin, Waqar Hussain, Asa Cajander, Tony Clear, and Mats Daniels. "Preparing the Global Software Engineer." In 2015 IEEE 10th International Conference on Global Software Engineering (ICGSE). IEEE, 2015. http://dx.doi.org/10.1109/icgse.2015.20.

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

Guelfi, Nicolas. "Please ... . draw me a Software Engineer." In Hawaii International Conference on System Sciences. Hawaii International Conference on System Sciences, 2018. http://dx.doi.org/10.24251/hicss.2018.701.

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

"What makes a good software engineer?" In the conference, chair J. Bamberger. New York, New York, USA: ACM Press, 1989. http://dx.doi.org/10.1145/74261.74289.

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

Li, Paul Luo, Andrew J. Ko, and Jiamin Zhu. "What Makes a Great Software Engineer?" In 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering (ICSE). IEEE, 2015. http://dx.doi.org/10.1109/icse.2015.335.

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

Ren, Wei, Stephen Barrett, and Sourojit Das. "Toward Gamification to Software Engineering and Contribution of Software Engineer." In ICMSS 2020: 2020 4th International Conference on Management Engineering, Software Engineering and Service Sciences. New York, NY, USA: ACM, 2020. http://dx.doi.org/10.1145/3380625.3380628.

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

Rothermel, Gregg. "Helping End-User Programmers "Engineer' Dependable Software." In Proceedings of the 6th International Conference on Quality Software. IEEE, 2006. http://dx.doi.org/10.1109/qsic.2006.33.

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

Jayaram, K. R. "Exploiting Causality to Engineer Elastic Distributed Software." In 2016 IEEE 36th International Conference on Distributed Computing Systems (ICDCS). IEEE, 2016. http://dx.doi.org/10.1109/icdcs.2016.102.

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

Shin, Michael E., Snehadeep Sethia, and Nipul Patel. "Component-Based Malicious Software Engineer Intrusion Detection." In 2011 International Conference on Secure Software Integration and Reliability Improvement (SSIRI). IEEE, 2011. http://dx.doi.org/10.1109/ssiri.2011.33.

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

Reports on the topic "Software engineer"

1

Vakaliuk, Tetiana A., Valerii V. Kontsedailo, Dmytro S. Antoniuk, Olha V. Korotun, Iryna S. Mintii, and Andrey V. Pikilnyak. Using game simulator Software Inc in the Software Engineering education. [б. в.], February 2020. http://dx.doi.org/10.31812/123456789/3762.

Full text
Abstract:
The article presents the possibilities of using game simulator Sotware Inc in the training of future software engineer in higher education. Attention is drawn to some specific settings that need to be taken into account when training in the course of training future software engineers. More and more educational institutions are introducing new teaching methods, which result in the use of engineering students, in particular, future software engineers, to deal with real professional situations in the learning process. The use of modern ICT, including game simulators, in the educational process, allows to improve the quality of educational material and to enhance the educational effects from the use of innovative pedagogical programs and methods, as it gives teachers additional opportunities for constructing individual educational trajectories of students. The use of ICT allows for a differentiated approach to students with different levels of readiness to study. A feature of any software engineer is the need to understand the related subject area for which the software is being developed. An important condition for the preparation of a highly qualified specialist is the independent fulfillment by the student of scientific research, the generation, and implementation of his idea into a finished commercial product. In the process of research, students gain knowledge, skills of the future IT specialist and competences of the legal protection of the results of intellectual activity, technological audit, marketing, product realization in the market of innovations. Note that when the real-world practice is impossible for students, game simulators that simulate real software development processes are an alternative.
APA, Harvard, Vancouver, ISO, and other styles
2

Shaw, Mary, Dario Giuse, and Raj Reddy. What a Software Engineer Needs to Know: 1. Program Vocabulary. Fort Belvoir, VA: Defense Technical Information Center, August 1989. http://dx.doi.org/10.21236/ada219064.

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

Golish, Michael L., Carrie J. McCunn, and Beth A. Symonds. The Use of Design Automation Software by Government-Contracted Architect/Engineer Firms: A Status Report. Fort Belvoir, VA: Defense Technical Information Center, September 1993. http://dx.doi.org/10.21236/ada273181.

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

Bruder, Brittany L., Katherine L. Brodie, Tyler J. Hesser, Nicholas J. Spore, Matthew W. Farthing, and Alexander D. Renaud. guiBath y : A Graphical User Interface to Estimate Nearshore Bathymetry from Hovering Unmanned Aerial System Imagery. Engineer Research and Development Center (U.S.), February 2021. http://dx.doi.org/10.21079/11681/39700.

Full text
Abstract:
This US Army Engineer Research and Development Center, Coastal and Hydraulics Laboratory, technical report details guiBathy, a graphical user interface to estimate nearshore bathymetry from imagery collected via a hovering Unmanned Aerial System (UAS). guiBathy provides an end-to-end solution for non-subject-matter-experts to utilize commercia-off-the-shelf UAS to collect quantitative imagery of the nearshore by packaging robust photogrammetric and signal-processing algorithms into an easy-to-use software interface. This report begins by providing brief background on coastal imaging and the photogrammetry and bathymetric inversion algorithms guiBathy utilizes, as well as UAS data collection requirements. The report then describes guiBathy software specifications, features, and workflow. Example guiBathy applications conclude the report with UAS bathymetry measurements taken during the 2020 Atlantic Hurricane Season, which compare favorably (root mean square error = 0.44 to 0.72 m; bias = -0.35 to -0.11 m) with in situ survey measurements. guiBathy is a standalone executable software for Windows 10 platforms and will be freely available at www.github.com/erdc.
APA, Harvard, Vancouver, ISO, and other styles
5

Levine, Linda, Linda H. Pesante, and Susan B. Dunkle. Technical Writing for Software Engineers. Fort Belvoir, VA: Defense Technical Information Center, November 1991. http://dx.doi.org/10.21236/ada636493.

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

Osadcha, Kateryna P., and Viacheslav V. Osadchyi. The use of cloud computing technology in professional training of future programmers. [б. в.], June 2021. http://dx.doi.org/10.31812/123456789/4435.

Full text
Abstract:
The article provides a brief analysis of the current state of the study of cloud technologies by future software engineers at foreign and Ukrainian universities. The author experience in the application of cloud technologies in the training of future software engineers in Ukraine is presented. The application of cloud business automation systems, online services to monitor the implementation of the software projects, Google services for collaboration, planning and productivity while studying professional disciplines and carrying out diploma projects is described. Based on the survey conducted at Stackoverflow, the state of application of cloud technologies by software engineers around the world has been analyzed. The cloud technologies that are not studied at the analyzed universities of Ukraine and those that are not popular with software developers in the world, but studied at Ukrainian universities by future software engineers are outlined. Conclusions are made on the modernization of training programs for future software engineers. Topics for the study of cloud technologies by future software engineers in the content of professional disciplines are proposed.
APA, Harvard, Vancouver, ISO, and other styles
7

Striuk, Andrii M., and Serhiy O. Semerikov. The Dawn of Software Engineering Education. [б. в.], February 2020. http://dx.doi.org/10.31812/123456789/3671.

Full text
Abstract:
Designing a mobile-oriented environment for professional and practical training requires determining the stable (fundamental) and mobile (technological) components of its content and determining the appropriate model for specialist training. In order to determine the ratio of fundamental and technological in the content of software engineers’ training, a retrospective analysis of the first model of training software engineers developed in the early 1970s was carried out and its compliance with the current state of software engineering development as a field of knowledge and a new the standard of higher education in Ukraine, specialty 121 “Software Engineering”. It is determined that the consistency and scalability inherent in the historically first training program are largely consistent with the ideas of evolutionary software design. An analysis of its content also provided an opportunity to identify the links between the training for software engineers and training for computer science, computer engineering, cybersecurity, information systems and technologies. It has been established that the fundamental core of software engineers’ training should ensure that students achieve such leading learning outcomes: to know and put into practice the fundamental concepts, paradigms and basic principles of the functioning of language, instrumental and computational tools for software engineering; know and apply the appropriate mathematical concepts, domain methods, system and object-oriented analysis and mathematical modeling for software development; put into practice the software tools for domain analysis, design, testing, visualization, measurement and documentation of software. It is shown that the formation of the relevant competencies of future software engineers must be carried out in the training of all disciplines of professional and practical training.
APA, Harvard, Vancouver, ISO, and other styles
8

Tkachuk, Viktoriia V., Vadym P. Shchokin, and Vitaliy V. Tron. The Model of Use of Mobile Information and Communication Technologies in Learning Computer Sciences to Future Professionals in Engineering Pedagogy. [б. в.], November 2018. http://dx.doi.org/10.31812/123456789/2668.

Full text
Abstract:
Research goal: the research is aimed at developing a model of use of mobile ICT in learning Computer Sciences to future professionals in Engineering Pedagogy. Object of research is the model of use of mobile ICT in learning Computer Sciences to future professionals in Engineering Pedagogy. Results of the research: the developed model of use of mobile ICT as tools of learning Computer Sciences to future professionals in Engineering Pedagogy is based on the competency-based, person-centered and systemic approaches considering principles of vocational education, general didactic principles, principles of Computer Science learning, and principles of mobile learning. It also takes into account current conditions and trends of mobile ICT development. The model comprises four blocks: the purpose-oriented block, the content-technological block, the diagnostic block and the result-oriented block. According to the model, the learning content of Computer Sciences consists of 5 main units: 1) Fundamentals of Computer Science; 2) Architecture of Modern Computers; 3) Fundamentals of Algorithmization and Programming; 4) Software of Computing Systems; 5) Computer Technologies in the Professional Activity of Engineer-pedagogues.
APA, Harvard, Vancouver, ISO, and other styles
9

Wiegand, Chiu, Rick Mullinix, and Justin Boblitt. Software Engineers' Perspective on Open Source Projects at NASA/GSFC. Washington, D.C.: National Academies Press, December 2018. http://dx.doi.org/10.17226/25217_9.

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

PARAMAX SYSTEMS CORP RESTON VA. Integrating Domain-Specific Reuse for System/Software Engineers Course Description. Fort Belvoir, VA: Defense Technical Information Center, June 1992. http://dx.doi.org/10.21236/ada257637.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software engineer' for particular source types:
Journal articles 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