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
Case Studies in Systematic Software Developmentby Cliff B. Jones and Robert C. F. Shaw - Prentice Hall
This book covers the case studies on the application of the most widely known formal methods in software development, the Vienna Development Method. VDM was developed in an industrial environment but has also evoked considerable academic research.
(17140 views)
Specifying Systemsby Leslie Lamport - Addison-Wesley Professional
This book shows how to write unambiguous specifications of complex computer systems. It provides a complete reference manual for the TLA+, the language developed by the author for writing simple and elegant specifications of algorithms and protocols.
(22165 views)
A Gentle Guide to Constraint Logic Programming via ECLiPSeby Antoni Niederlinski
Introductory and down-to-earth presentation of Constraint Logic Programming, an exciting software paradigm, more and more popular for solving combinatorial as well as continuous constraint satisfaction problems and constraint optimization problems.
(12889 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.
(17294 views)