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
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.
(16790 views)
SOA Source Book- Van Haren Publishing
The SOA Source Book will help enterprise architects to use SOA effectively. It explains: What SOA is; How to evaluate SOA features in business terms; How to model SOA; How to use The Open Group Architecture Framework for SOA; SOA governance.
(14323 views)
The Grand Unified Theory of Software Engineeringby Mathias Ekstedt - Industrial Info Systems
This book is the result of innumerable longwinded, oftentimes unnecessarily complicated, discussions between the authors on the nature of software engineering, machines, minds, design, software, engineering, organizations and more.
(14483 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.
(16017 views)