𝔖 Scriptorium
✦   LIBER   ✦

πŸ“

What Every Engineer Should Know about Software Engineering

✍ Scribed by Philip A. Laplante


Publisher
CRC Press
Year
2007
Tongue
English
Leaves
330
Category
Library

⬇  Acquire This Volume

No coin nor oath required. For personal study only.

✦ Synopsis


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.


πŸ“œ SIMILAR VOLUMES


What Every Engineer Should Know about So
✍ Philip A. Laplante πŸ“‚ Library πŸ“… 2007 πŸ› CRC Press 🌐 English

Do you… <li>Use a computer to perform analysis or simulations in your daily work? </li><li>Write short scripts or record macros to perform repetitive tasks? </li><li>Need to integrate off-the-shelf software into your systems or require multiple applications to work together? </li><li>Find yourself s

What Every Engineer Should Know about So
✍ Phillip A. Laplante, Mohamad Kassab πŸ“‚ Library πŸ“… 2022 πŸ› CRC Press 🌐 English

<p><span>This book offers a practical approach to understanding, designing, and building sound software based on solid principles. Using a unique Q&amp;A format, this book addresses the issues that engineers need to understand in order to successfully work with software engineers, develop specificat

What Every Engineer Should Know about So
✍ Philip A. Laplante πŸ“‚ Library πŸ“… 2007 πŸ› Taylor & Francis 🌐 English

Do you… <li>Use a computer to perform analysis or simulations in your daily work? </li><li>Write short scripts or record macros to perform repetitive tasks? </li><li>Need to integrate off-the-shelf software into your systems or require multiple applications to work together? </li><li>Find yourself s

What Every Engineer Should Know About Bu
✍ John X. Wang πŸ“‚ Library πŸ“… 2008 🌐 English

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β€”Β Β  Β Β Β Β Β Β Β Β Β Β 

What every engineer should know about co
✍ Thomas A. Salomone πŸ“‚ Library πŸ“… 1995 πŸ› M. Dekker 🌐 English

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,

What Every Engineer Should Know about Co
✍ Thomas A. Salomone (Author) πŸ“‚ Library πŸ“… 1995 πŸ› Routledge

<p>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 Desi