Code Quality: The Open Source Perspective

Spinellis, Diomidis

ISBN 10: 0321166078 / ISBN 13: 9780321166074

Published by Addison-Wesley Professional, 2006

About this Item

Connecting readers with great books since 1972! Used textbooks may not include companion materials such as access codes, etc. May have some wear or writing/highlighting. We ship orders daily and Customer Service is our top priority! Seller Inventory # S_424921394

Bibliographic Details

Title: Code Quality: The Open Source Perspective

Publisher: Addison-Wesley Professional

Publication Date: 2006

Binding: Paperback

Condition: Good

About this title

Synopsis:

• Page 26: How can I avoid off-by-one errors?
• Page 143: Are Trojan Horse attacks for real?
• Page 158: Where should I look when my application can't handle its workload?
• Page 256: How can I detect memory leaks?
• Page 309: How do I target my application to international markets?
• Page 394: How should I name my code's identifiers?
• Page 441: How can I find and improve the code coverage of my tests?

Diomidis Spinellis' first book, Code Reading, showed programmers how to understand and modify key functional properties of software. Code Quality focuses on non-functional properties, demonstrating how to meet such critical requirements as reliability, security, portability, and maintainability, as well as efficiency in time and space.

Spinellis draws on hundreds of examples from open source projects--such as the Apache web and application servers, the BSD Unix systems, and the HSQLDB Java database--to illustrate concepts and techniques that every professional software developer will be able to appreciate and apply immediately.

Complete files for the open source code illustrated in this book are available online at: http://www.spinellis.gr/codequality/

Product Description:

Code Quality * Page 26: How can I avoid off-by-one errors? * Page 143: Are Trojan Horse attacks for real? * Page 158: Where should I look when my application can't handle its workload? * Page 256: How can I detect memory leaks? * Page 309: How do I target my application to international markets? * Page 394: How should I name my code's identifiers? * Page 441: How can I find and improve the code coverage of my ... Full description