What Every Engineer Should Know about Software Engineering

What Every Engineer Should Know about Software Engineering

4.11 - 1251 ratings - Source

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.test-case generation developing tests for requirements to check testability automated consistency analysis checking the ... There is a free downloadable tool from NASA, the Automated Requirement Measurement (ARM) tool [NASA 2006].

Title:What Every Engineer Should Know about Software Engineering
Author:Philip A. Laplante
Publisher:CRC Press - 2007-04-25


You Must CONTINUE and create a free account to access unlimited downloads & streaming