if you think you are an engineer, you should be familiar with the broad contents of this book.
If you do not know what the IEEE you probably should not be reading this review because you are not (yet) a software engineer. This book aims to do several things. There is an appendix that lists 40 IEEE software standards. Note that none of these are computer language standards, the author assumes you would know about those. The standards listed in the appendix come under four headings (actually four volumes published by IEEE): Customer and Terminology Standards, Process Standards, Product Standards, and Resource and Technique Standards.
The body of the book starts with a chapter that seeks to motivate companies and organizations to adopt standards. This ranges from potential production benefits to the reduction of legal liability for the consequences of faults in ones products.
The second chapter is more addressed at practitioners and considers what they need to do to improve their software process.
The next four chapters consider specific aspects of using standards and should be read in reference to appendix A.
The book concludes with a chapter on practical lessons, which covers such things as 'Standard Operating Procedures', 'Project Management', 'Training' etc.
Let me be blunt: if you think you are an engineer, you should be familiar with the broad contents of this book. If you are not, for example, aware that there is a standard for Software Reviews (IEEE Std. 1028-1997) then you need to read this book. Be warned that that will only be a start, but at least you will have some idea as to where you should be looking if you want to work as an engineer rather than as a paid amateur.