Code Quality: The Open Source Perspective by Diomidis Spinellis

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    Code Quality: The Open Source Perspective by Diomidis Spinellis - Presentation Transcript

    1. Code Quality: The Open Source Perspective by Diomidis Spinellis Refreshingly Complete And Precise *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 cant 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 codes 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
    2. code illustrated in this book are available online at: http://www.spinellis.gr/codequality/ Personal Review: Code Quality: The Open Source Perspective by Diomidis Spinellis The book is full of hard-won experience cast nicely into prose. It's a very worthwhile read. The author doesn't shy away from explaining difficult or intricate concepts, where necessary, and each point is illustrated with example code from real systems. For example, the chapter on Maintainability opens with four attributes of a maintainable system (from ISO/IEC 9126-1:2001) that really struck a chord with me. Analysability: Finding the location of an error or the part of the software that must be analysed Changeability: Implementing the maintenance change on the system's code Stability: Not breaking anything through the change Testability: Validating the software after the change I know maintainable code when I see it -- it has a certain feel... Up until now though I've often struggled to express that feeling to non- programmers, or perhaps more importantly, to less experienced colleagues. Highly recommended. For More 5 Star Customer Reviews and Lowest Price: Code Quality: The Open Source Perspective by Diomidis Spinellis 5 Star Customer Reviews and Lowest Price!
    SlideShare Zeitgeist 2009

    + AutoSurfRestarterAutoSurfRestarter Nominate

    custom

    47 views, 0 favs, 0 embeds more stats

    The book is full of hard-won experience cast nicely more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 47
      • 47 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 0
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?