What Every Engineer Should Know about Robots

Summarizes the technology & economics of robotics.

What Every Engineer Should Know about Robots

Summarizes the technology & economics of robotics. Features: history, terminology, trends, & basic robot types; assesment of robot productivity; listing of major robot manufacturers & generic data on robot systems currently available in the U. S.

What Every Engineer Should Know About Project Management Second Edition

WHAT EVERY ENGINEER SHOULD KNOW A Series Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati , Ohio 1. What Every Engineer Should Know About Patents , William G. Konold ...

What Every Engineer Should Know About Project Management  Second Edition

Covering the roles and responsibilities of the project manager, this second edition describes requirement specifications, work breakdown structures, project control and risk management, and offers new information on motivation, matrix arrangements, and project records. Discussing the anatomy of a project planning and control and techniques, the authors describe the project manager's entire range of responsibilities from initial planning to directing personnel, controlling work, and reporting results. The appendices cover work breakdown structure paradigms, cost versus time profiles, and checklists to assess work done.

What Every Engineer Should Know about Concurrent Engineering

WHAT EVERY ENGINEER SHOULD KNOW A Series Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati, Ohio . What Every Engineer Should Know About Patents, William G. Konold, ...

What Every Engineer Should Know about Concurrent Engineering

This work offers a step-by-step approach to the overall concurrent engineering (CE) development process, presenting both fundamental principles and advanced concepts, while focusing on rapid product development and cost-effective designs. The book also provides an introduction to Cost Driven Design, with specific examples on how to minimize expenses by understanding the basis of product costs. The process of concurrent engineering is explained from initial planning to production start-up.

What Every Engineer Should Know about Microcomputers

WHAT EVERY ENGINEER SHOULD KNOW A Series Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati , Ohio Vol . 1 What Every Engineer Should Know About Patents , William G. Konold ...

What Every Engineer Should Know about Microcomputers

Revised and expanded guide demonstrates microcomputer usage by working through one simple design challenge and explaining its solution. This edition features the contributions of an Ada expert, demonstrates (in 14 new chapters) the development of a microcomputer system structured by this language, a

What Every Engineer Should Know About Modeling and Simulation

What Every Engineer Should Know About Patents, William G. Konold, Bruce Tittel, Donald F. Frei, and David S. Stallard 2. What Every Engineer Should Know About Product Liability, James F. Thorpe and William H. Middendorf 3.

What Every Engineer Should Know About Modeling and Simulation

This practical book presents fundamental concepts and issues in computer modeling and simulation (M&S) in a simple and practical way for engineers, scientists, and managers who wish to apply simulation successfully to their real-world problems. It offers a concise approach to the coverage of generic (tool-independent) M&S concepts and enables engineering practitioners to easily learn, evaluate, and apply various available simulation concepts. Worked out examples are included to illustrate the concepts and an example modeling application is continued throughout the chapters to demonstrate the techniques. The book discusses modeling purposes, scoping a model, levels of modeling abstraction, the benefits and cost of including randomness, types of simulation, and statistical techniques. It also includes a chapter on modeling and simulation projects and how to conduct them for customer and engineer benefit and covers the stages of a modeling and simulation study, including process and system investigation, data collection, modeling scoping and production, model verification and validation, experimentation, and analysis of results.

What Every Engineer Should Know About Cyber Security and Digital Forensics

What Every Engineer Should Know About Patents, William G. Konold, Bruce Tittel, Donald F. Frei, and David S. Stallard 2. ... John K. Krouse What Every Engineer Should Know About Robots, Maurice I. Zeldman What Every Engineer Should Know ...

What Every Engineer Should Know About Cyber Security and Digital Forensics

Most organizations place a high priority on keeping data secure, but not every organization invests in training its engineers or employees in understanding the security risks involved when using or developing technology. Designed for the non-security professional, What Every Engineer Should Know About Cyber Security and Digital Forensics is an overview of the field of cyber security. Exploring the cyber security topics that every engineer should understand, the book discusses: Network security Personal data security Cloud computing Mobile computing Preparing for an incident Incident response Evidence handling Internet usage Law and compliance Security and forensic certifications Application of the concepts is demonstrated through short case studies of real-world incidents chronologically delineating related events. The book also discusses certifications and reference manuals in the area of cyber security and digital forensics. By mastering the principles in this volume, engineering professionals will not only better understand how to mitigate the risk of security incidents and keep their data secure, but also understand how to break into this expanding profession.

What Every Engineer Should Know about Reliability and Risk Analysis

A Series Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati, Ohio 1. What Every Engineer Should Know About Patents, William G. Konold, Bruce Tittel, Donald F. Frei, ...

What Every Engineer Should Know about Reliability and Risk Analysis

"Examining reliability, availability, and risk analysis and reviewing in probability and statistics essential to understanding reliability methods, this outstanding volume describes day-to-day techniques used by practicing engineers -- discussing important reliability aspects of both components and complex systems. "

What Every Engineer Should Know about Ethics

WHAT EVERY ENGINEER SHOULD KNOW A Series Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati , Ohio 1. What Every Engineer Should Know About Patents , William G. Konold ...

What Every Engineer Should Know about Ethics

This compact reference succinctly explains the engineering profession's codes of ethics using case studies drawn from decisions of the National Society of Professional Engineers' (NSPE) Board of Ethical Review, examining ethical challenges in engineering, construction, and project management. It includes study questions to supplement general engineering survey courses and a list of references to aid practicing engineers in exploring topics in depth. Concentrating primarily on situations engineers encounter on a daily basis and offering pragmatic answers to ethical questions, What Every Engineer Should Know About Ethics discusses recent headline-making disasters such as the Challenger explosion, the Chernobyl nuclear catastrophe, and the Hyatt-Regency Hotel collapse; considers the merits and drawbacks of professional codes of ethics; covers the application of the "committee approach" to specific cases; compares and contrasts ethical codes and personal values with alternative approaches to morality; defines professional licensing and registration and enumerates their prerequisites; outlines legal standards for liability; emphasizes the importance of communication, coordination, and documentation; includes a discussion of "whistleblowing;" defines the engineer's primary ethical responsibility; and more.

What Every Engineer Should Know About Excel

What Every Engineer Should Know: A Series Series Editor* Phillip A. Laplante Pennsylvania State University 1. What Every Engineer Should Know about Patents William G. Konold, Bruce Tittel, Donald F. Frei, and David S. Stallard 2.

What Every Engineer Should Know About Excel

Understanding the powerful computational and graphics capabilities of Microsoft Excel is an enormous benefit to engineers and technical professionals in almost any field and at all levels of experience. What Every Engineer Should Know About Excel is a practical guide to unlocking the features and functions of this program, using examples and screenshots to walk readers through the steps to build a strong understanding of the material. This second edition is updated to reflect the latest version of Excel (2016) and expands its scope to include data management, connectivity to external data sources, and integration with "the cloud" for optimal use of the Excel product. It also introduces the ribbon bar navigation prevalent in Microsoft products beginning with the 2007 version of MS Office. Covering a variety of topics in self-contained chapters, this handy guide will also prove useful for professionals in IT, finance, and real estate.

What Every Engineer Should Know about Software Engineering

What Every Engineer Should Know About ComputerAided Design and Computer-Aided Manufacturing: The CAD/CAM Revolution, John K. Krouse What Every Engineer Should Know About Robots, Maurice I. Zeldman What Every Engineer Should Know About ...

What Every Engineer Should Know about Software Engineering

Do you... Use a computer to perform analysis or simulations in your daily work? Write short scripts or record macros to perform repetitive tasks? Need to integrate off-the-shelf software into your systems or require multiple applications to work together? Find yourself spending too much time working the kinks out of your code? Work with software engineers on a regular basis but have difficulty communicating or collaborating? If any of these sound familiar, then you may need a quick primer in the principles of software engineering. Nearly every engineer, regardless of field, will need to develop some form of software during their career. Without exposure to the challenges, processes, and limitations of software engineering, developing software can be a burdensome and inefficient chore. In What Every Engineer Should Know about Software Engineering, Phillip Laplante introduces the profession of software engineering along with a practical approach to understanding, designing, and building sound software based on solid principles. Using a unique question-and-answer format, this book addresses the issues and misperceptions that engineers need to understand in order to successfully work with software engineers, develop specifications for quality software, and learn the basics of the most common programming languages, development approaches, and paradigms.

What Every Engineer Should Know about Data Communications

What Every Engineer Should Know A Series Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati, Ohio Vol. 1 What Every Engineer Should Know About Patents, William G. Konold, ...

What Every Engineer Should Know about Data Communications

This book discusses the fundamentals of data communications, the most important element in an engineer's daily function. It examines the technologies and methodologies now available in the marketplace to effect the exchange of information.

What Every Engineer Should Know About Business Communication

What Every Engineer Should Know About ComputerAided Design and Computer-Aided Manufacturing: The CAD/CAM Revolution, John K. Krouse What Every Engineer Should Know About Robots, Maurice I. Zeldman What Every Engineer Should Know About ...

What Every Engineer Should Know About Business Communication

Engineers must possess a range of business communication skills that enable them to effectively communicate the purpose and relevance of their idea, process, or technical design. This unique business communication text is packed with practical advice that will improve your ability to— Market ideas Write proposals Generate enthusiasm for research Deliver presentations Explain a design Organize a project team Coordinate meetings Create technical reports and specifications Focusing on the three critical communication needs of engineering professionals—speaking, writing, and listening—the book delineates critical communication strategies required in many group settings and work situations. It demonstrates how to integrate a marketing strategy into every facet of engineering communication, from presentations, visual aids, proposals, and technical reports to e-mail and phone calls. Using situational examples, the book also illustrates how to use computers, graphics, and other engineering tools to effectively communicate with other engineers and managers.

What Every Engineer Should Know about Accounting and Finance

WHAT EVERY ENGINEER SHOULD KNOW A Series Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati , Ohio 1. What Every Engineer Should Know About Patents , William G. Konold ...

What Every Engineer Should Know about Accounting and Finance

Presents the fundamental finance and accounting processes, methods, strategies and terminology necessary for engineers and engineering managers to interpret financial data properly - examining topics such as cost and break-even analysis, the time value of money, financial ratios and discounted cash flow techniques. The information is designed to enable engineers and project managers to prepare, appraise, evaluate and approve financial plans to accomplish specific departmental and company objectives.

What Every Engineer Should Know About Risk Engineering and Management

WHAT EVERY ENGINEER SHOULD KNOW A Series Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati , Ohio 1. What Every Engineer Should Know About Patents , William G. Konold ...

What Every Engineer Should Know About Risk Engineering and Management

"Explains how to assess and handle technical risk, schedule risk, and cost risk efficiently and effectively--enabling engineering professionals to anticipate failures regardless of system complexity--highlighting opportunities to turn failure into success."

What Every Engineer Should Know About Decision Making Under Uncertainty

WHAT EVERY ENGINEER SHOULD KNOW A Series Founding Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati , Ohio 1. What Every Engineer Should Know About Patents , William G.

What Every Engineer Should Know About Decision Making Under Uncertainty

Covering the prediction of outcomes for engineering decisions through regression analysis, this succinct and practical reference presents statistical reasoning and interpretational techniques to aid in the decision making process when faced with engineering problems. The author emphasizes the use of spreadsheet simulations and decision trees as imp

What Every Engineer Should Know about Corrosion

A Series Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati , Ohio Vol . 1 What Every Engineer Should Know About Patents , William G. Konold , Bruce Tittel , Donald F. Frei ...

What Every Engineer Should Know about Corrosion


What Every Engineer Should Know about Ceramics

WHAT EVERY ENGINEER SHOULD KNOW A Series Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati , Ohio Vol . 1 What Every Engineer Should Know About Patents , William G. Konold ...

What Every Engineer Should Know about Ceramics


What Every Engineer Should Know about Engineering Information Resources

WHAT EVERY ENGINEER SHOULD KNOW A Series Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati , Ohio Vol . 1 What Every Engineer Should Know About Patents , William G. Konold ...

What Every Engineer Should Know about Engineering Information Resources


What Every Engineer Should Know about Finite Element Analysis Second Edition

A Series Editor William H. Middendorf Department of Electrical and Computer Engineering University of Cincinnati Cincinnati , Ohio 1. What Every Engineer Should Know About Patents , William G. Konold , Bruce Tittel , Donald F. Frei ...

What Every Engineer Should Know about Finite Element Analysis  Second Edition

Summarizing the history and basic concepts of finite elements in a manner easily understood by all engineers, this concise reference describes specific finite element software applications to structural, thermal, electromagnetic and fluid analysis - detailing the latest developments in design optimization, finite element model building and results processing and future trends.;Requiring no previous knowledge of finite elements analysis, the Second Edition provides new material on: p elements; iterative solvers; design optimization; dynamic open boundary finite elements; electric circuits coupled to finite elements; anisotropic and complex materials; electromagnetic eigenvalues; and automated pre- and post-processing software.;Containing more than 120 tables and computer-drawn illustrations - and including two full-colour plates - What Every Engineer Should Know About Finite Element Analysis should be of use to engineers, engineering students and other professionals involved with product design or analysis.

What Every Engineer Should Know About Developing Real Time Embedded Products

What Every Engineer Should Know About ComputerAided Design and Computer-Aided Manufacturing: The CAD/CAM Revolution, John K. Krouse What Every Engineer Should Know About Robots, Maurice I. Zeldman What Every Engineer Should Know About ...

What Every Engineer Should Know About Developing Real Time Embedded Products

You can find them in your wristwatch or MP3 player; they perform specific functions in washing machines, traffic lights, and even pacemakers. Embedded systems are pervasive, ubiquitous, and widespread throughout our daily lives. Developing these real-time embedded products requires an understanding of the interactions between different disciplines, such as circuit design, power, cooling, packaging, software, and human interface. This volume provides the knowledge and insight engineers need to make critical design decisions and offers a clear guide for preparing and developing projects in different markets. The book begins by laying the basic groundwork for effective processes, covering smaller, self-contained devices and subsystems, ranging from handheld devices to appliances. Highly detailed case studies, which include designing instruments for space flight, implanted medical devices, and military support equipment, illustrate industry best practices and managerial issues. Each case study is detailed in terms of concept, market, standards, integration, manufacturing, and phases. With schedule and estimation templates, this highly functional text presents numerous examples of design tradeoffs critical to successful project development. Offering even coverage and clarification of the entire development process, What Every Engineer Should Know about Developing Real-Time Embedded Products provides engineers and industrial designers with practical tools to make important decisions, from deciding whether to buy or build subsystems to determining the appropriate kinds of field testing.