3,731 research outputs found
A Process for Engineer Domain Ontology: An Experience in Developing Business Analysis Ontology
No full textDuring the last years several works have been aimed to improve ontology technological as-pects, like representation language and inference mechanisms. This paper presents a discussion on the process and product of an experience in developing ontology for the public sector whose organization requires a strong knowledge management. This process is applied to engineer and develop ontology for Business analysis domain.Ontology, Ontology Engineering, Methodology, Protégé, Business Analysis
Biennial report of the State Engineer to the Governor of Oregon
No full textCovers OCLC #1009337973, OCLC #1089340481This archived document is maintained by the State Library of Oregon as part of the Oregon Documents Depository Program. It is for informational purposes and may not be suitable for legal purposes.Mode of access: Internet from the Oregon Government Publications Collection.Text in English
So, you wanna be an embedded engineer : the guide to embedded engineering, from consultancy to the corporate ladder /
No full textIn this new, highly practical guide, expert embedded designer and manager Lewin Edwards answers the question, How do I become an embedded engineer? Embedded professionals agree that there is a treacherous gap between graduating from school and becoming an effective engineer in the workplace, and that there are few resources available for newbies to turn to when in need of advice and direction. This book provides that much-needed guidance for engineers fresh out of school, and for the thousands of experienced engineers now migrating into the popular embedded arena. This book helps new embedded engineers to get ahead quickly by preparing them for the technical and professional challenges they will face. Detailed instructions on how to achieve successful designs using a broad spectrum of different microcontrollers and scripting languages are provided. The author shares insights from a lifetime of experience spent in-the-trenches, covering everything from small vs. large companies, and consultancy work vs. salaried positions, to which types of training will prove to be the most lucrative investments. This book provides an experts authoritative answers to questions that pop up constantly on Usenet newsgroups and in break rooms all over the world. * An approachable, friendly introduction to working in the world of embedded design * Full of design examples using the most common languages and hardware that new embedded engineers will be likely to use every day * Answers important basic questions on which are the best products to learn, trainings to get, and kinds of companies to work for.Includes bibliographical references and index.Education -- Teaching yourself, bottom-up (small embedded systems) -- Teaching Yourself, top-down (large embedded systems) -- Working for yourself as an embedded engineer -- Working for a small company -- Working for a larger company.In this new, highly practical guide, expert embedded designer and manager Lewin Edwards answers the question, How do I become an embedded engineer? Embedded professionals agree that there is a treacherous gap between graduating from school and becoming an effective engineer in the workplace, and that there are few resources available for newbies to turn to when in need of advice and direction. This book provides that much-needed guidance for engineers fresh out of school, and for the thousands of experienced engineers now migrating into the popular embedded arena. This book helps new embedded engineers to get ahead quickly by preparing them for the technical and professional challenges they will face. Detailed instructions on how to achieve successful designs using a broad spectrum of different microcontrollers and scripting languages are provided. The author shares insights from a lifetime of experience spent in-the-trenches, covering everything from small vs. large companies, and consultancy work vs. salaried positions, to which types of training will prove to be the most lucrative investments. This book provides an experts authoritative answers to questions that pop up constantly on Usenet newsgroups and in break rooms all over the world. * An approachable, friendly introduction to working in the world of embedded design * Full of design examples using the most common languages and hardware that new embedded engineers will be likely to use every day * Answers important basic questions on which are the best products to learn, trainings to get, and kinds of companies to work for.Print version record.Elsevie
Design and implementation of quasi cyclic low density parity check (QC-LDPC) code on FPGA
No full textOregon State Engineer
No full textCovers OCLC #1021864938, OCLC #1021864973Mode of access: Internet from the Oregon Government Publications Collection.Text in English
Supplier's sales engineer as a knowledge worker
No full textThe paper forms part of a multiple case study in progress that focuses on information relationships, i.e., the exchange of information and knowledge at the micro-social level between supplier and buyer firms in the fuzzy front end of product development. The micro-social level is made up of dyadic information relationships between the Design Engineer of buyer firms and the Sales Engineer of supplier firms. The case study explores the information relationship through the lens of three theoretical perspectives, namely: early supplier involvement in product development, knowledge management, and the concepts of social embeddedness and tie strengths belonging to economic sociology. The paper describes the concept of supplier’s Sales Engineer as a knowledge worker, and explains how the concept represents a specific type of supplier involvement in early product development. By using the preliminary findings of four case studies, the paper shows how the concept of the Sales Engineer as a knowledge worker has been understood and applied in practice The paper concludes with managerial implications regarding the conditions that need to be in place in order to make the knowledge transfer through the Sales Engineer robust and dependable.Product Innovation ManagementIndustrial Design Engineerin
Diary thesis of Software Engineer
No full textThe diary-based thesis explains, observes, and analyses the everyday responsibilities of a software engineer employed by a multinational software company. The thesis covers daily observation and weekly analysis entries covering eight weeks of work from September 11, 2023, to November 10, 2023. The entries include the everyday activities of a software engineer and a reflection on challenges and knowledge gained throughout the course of work.
The introduction provides an overview of the author's background and role, the purpose and extent of the thesis, the diary's methodology and resources, and the thesis's practical and ethical considerations. The chapter also outlines the primary competencies and areas of improvement for the author over the course of the eight weeks.
More information on the author's initial situations as a software engineer is provided in the description of the initial situation chapter. The chapter covers the current work and skills of the author, the stakeholders and interaction situations that the author faces, and the areas and skills that the author wants to develop for the future. The chapter gives a thorough summary of the author's experience and qualifications as a software engineer, as well as the background and environment in which the author works.
The diary part of the thesis records the daily tasks that the author performs as a software engineer. It also analyses the tasks every week to identify the challenges, learnings, and improvements that the author experiences during the eight-week period. The diary part provides a detailed and reflective account of the author's work and skills as a software engineer.
This discussion chapter describes the growth and accomplishments of the author as a software engineer throughout the eight-week observation period. The chapter compares the initial situation with the insights gained from the diary entries, highlighting the areas and skills that the author improved, the particular approaches and methodologies discovered, and the challenges and learnings that the author encountered. The chapter covers the technical and non-technical aspects of software engineering and concludes with the author's plans for continuous learning and improvement in the field of software engineering.
This thesis might be useful for anyone who is interested in learning more about the everyday tasks, responsibilities, and challenges of a software engineer in a multinational software company. The thesis might be useful for aspiring or current software engineers who want to improve their professional performance and development, as well as for researchers or educators who want to understand the real-life aspects of software engineering
Shear centre eccentricity in SCIA Engineer
No full textTorsional moments and shear stresses are not calculated correctly in the framework analysis software SCIA Engineer for cross-sections with a shear centre eccentricity. The aim of this research is to analyze and solve this problem.Civil Engineerin
Title: Software Engineer
No full textMaryse DA-PONTE joined Aerospatiale in 1989 and has worked in the electronic documentation since 1992. From 1994, she has been involved in the graphics area and has joined the ATA (Air Transport Association) /AIA (Aerospace Industry Association) Graphics Working Group which is working on the concept of Intelligent Graphics. Maryse is a graduate engineer in Computer Science from the CNAM (Conservatoire National des Arts et Métiers) (France)
Ground-water data in the Harrisburg-Halsey area, central Willamette Valley, Oregon
No full textby F.J. Frank and Nyra A. Johnson ; prepared in cooperation with the U.S. Geological Survey.Title from PDF title page (viewed on July 15, 2020).This archived document is maintained by the State Library of Oregon as part of the Oregon Documents Depository Program. It is for informational purposes and may not be suitable for legal purposes.Includes bibliographical references (page 7).Mode of access: Internet from the Oregon Government Publications Collection.Text in English
- …
