What Every Engineer Should Know about Software Engineering
Phillip A. Laplante
,
Diese Seite wurde seit 5 Jahren inhaltlich nicht mehr aktualisiert.
Unter Umständen ist sie nicht mehr aktuell.
Abstracts
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.
One-to-One Computing: Artikel als Volltext (: , 124 kByte)
What Every Engineer Should Know about Software Engineering: Gesamtes Buch als Volltext (: , 2965 kByte)
Bibliographisches
Titel
Format
Bez.
Aufl.
Year
ISBN
What Every Engineer Should Know about Software Engineering
e
-
-
1
2007
0849372283
Beat and dieses Buch
Beat hat dieses Buch während seiner Zeit am Institut für Medien und Schule (IMS) ins Biblionetz aufgenommen. Beat besitzt kein physisches, aber ein digitales Exemplar. (das er aber aus Urheberrechtsgründen nicht einfach weitergeben darf). Aufgrund der wenigen Einträge im Biblionetz scheint er es nicht wirklich gelesen zu haben. Es gibt bisher auch nur wenige Objekte im Biblionetz, die dieses Werk zitieren.