The Guide to the Software Engineering Body of Knowledge
by P. Bourque, R. Dupuis, A. Abran, J. W. Moore, and L. L. Tripp
Publisher: IEEE 2004
ISBN/ASIN: 0769523307
Number of pages: 204
Description:
The software engineering body of knowledge is an all-inclusive term that describes the sum of knowledge within the profession of software engineering. Since it is usually not possible to put the full body of knowledge of even an emerging discipline, such as software engineering, into a single document, there is a need for a Guide to the Software Engineering Body of Knowledge. This Guide will seek to identify and describe that subset of the body of knowledge that is generally accepted, even though software engineers must be knowledgeable not only in software engineering, but also, of course, in other related disciplines.
Download or read it online for free here:
Read online
(online html)
Similar books
The New Software Engineeringby Sue Conger - Global Text Project
The book discusses software engineer's project related knowledge and theoretical background. It covers project planning, project life cycles, methodologies, technologies, techniques, tools, languages, testing, databases, and CASE.
(19932 views)
Software Engineering for Internet Applicationsby Eve Andersson, Philip Greenspun, Andrew Grumet - The MIT Press
After completing this course on server-based Internet applications software, students who start with only the knowledge of how to write and debug a computer program will have learned how to build web-based applications on the scale of Amazon.com.
(19617 views)
Function Points Analysis Training Courseby David Longstreet - SoftwareMetrics.Com
The book introduces the basic concepts of function point analysis and unit cost estimating, describes and defines the concepts necessary to establish a boundary between applications, identifies and rates external inputs and external outputs, etc.
(15398 views)
Software Architectureby A. Bijlsma, B.J. Heeren, E.E. Roubtsova, S. Stuurman - FTA
The central theme of this book is balancing the concerns and requirements of stakeholders, combining these into an architecture proposal by employing known tactics and patterns, producing a description of the architecture that can be communicated.
(14415 views)