Introducing: Klocwork Insight Pro | November 2009

Introducing Klocwork Insight Pro On-Demand Webinar CONFIDENTIAL

Speakers & Agenda ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],CONFIDENTIAL

Klocwork Introduction ,[object Object],[object Object],Confidential ,[object Object],Introduced Integrated Continuous Analysis, Refactoring & Code Review (Nov 2009) Passed 600 customer milestone (2009) Closed largest Q1 in company history (2009) First to market (2003) with architecture solution integrated with bug detection Awarded InfoWorld Technology of the Year Award (2007)

Over 600 customers worldwide CONFIDENTIAL Network & Telecom Finance & Insurance Spotlight Success: 3 of the top 5 computer and internet and software companies 5 of the top 10 global medical device companies 5 of the top 7 US aerospace and defense firms 5 of the top 7 global chip manufacturers 5 of the top 10 global network equipment providers “ The addition of Klocwork's best-of-breed source code analysis solution for identifying defects early in the development process will allow us to further enhance our reputation for market leadership and innovation while reducing our development costs and improving the development process.“ Orly Nicklass, Ph.D. , Head of R&D of Carrier Switches, Nokia Siemens Networks

When milestones become bottlenecks Implementation More bugs reports, more fire drills Less time to write new code ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],CONFIDENTIAL

Klocwork Insight Pro Productivity Tools for the Agile Developer CONFIDENTIAL

[object Object],[object Object],[object Object],Confidential Quality & Reliability Memory and resource leaks Using de-allocated memory Incorrect memory de-allocation Dereferencing NULL pointers Usage of uninitialized data Resource management Concurrency violations … Security Vulnerability Buffer overflow Un-validated user input SQL injection Path injection File injection Cross-site scripting Information leakage Weak encryption Vulnerable coding practices … Maintainability Architectural violations Header file structure Dead code Unreachable code Calculated values that are never used Unused function parameters Unused local variables …

CONFIDENTIAL CONFIDENTIAL CONFIDENTIAL CONFIDENTIAL Coding errors and design cleaned-up prior to check-in

CONFIDENTIAL CONFIDENTIAL CONFIDENTIAL CONFIDENTIAL ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],Frequency? Why use it? Time savings? Continuous developer desktop use Automates many time consuming tasks Developers can save many hours/week by reducing bugs reported from downstream and creating a cleaner design Coding errors and design cleaned-up prior to check-in

CONFIDENTIAL CONFIDENTIAL CONFIDENTIAL Coding errors and design cleaned-up prior to check-in Collaborative code reviews focus on critical design & requirement issues

CONFIDENTIAL CONFIDENTIAL CONFIDENTIAL Frequency? Why use it? Time savings? Daily Company mandate and/or developers want important code reviewed by peers Reading code on your own is up to 50% more effective at finding issues than group meetings; significant time is wasted attempting to schedule reviews ,[object Object],[object Object],[object Object],[object Object],Collaborative code reviews focus on critical design & requirement issues Coding errors and design cleaned-up prior to check-in

CONFIDENTIAL CONFIDENTIAL Builds are cleaner, more stable and reliable, leading to less downtime Collaborative code reviews focus on critical design & requirement issues Coding errors and design cleaned-up prior to check-in

CONFIDENTIAL CONFIDENTIAL ,[object Object],[object Object],[object Object],[object Object],Frequency? Why use it? Time savings? Daily to weekly Automated view of build-level quality ensures stable, reliable code base Unstable builds can delay a product release by weeks or months Collaborative code reviews focus on critical design & requirement issues Builds are cleaner, more stable and reliable, leading to less downtime Coding errors and design cleaned-up prior to check-in

CONFIDENTIAL Ship higher quality and more secure products on-time Test teams can focus on customer requirements not programming bugs Collaborative code reviews focus on critical design & requirement issues Builds are cleaner, more stable and reliable, leading to less downtime Coding errors and design cleaned-up prior to check-in

CONFIDENTIAL Ship higher quality and more secure products on-time Test teams can focus on customer requirements not programming bugs Ensure architecture and maintainability doesn’t erode Collaborative code reviews focus on critical design & requirement issues Builds are cleaner, more stable and reliable, leading to less downtime Coding errors and design cleaned-up prior to check-in

CONFIDENTIAL Ship higher quality and more secure products on-time Test teams can focus on customer requirements not programming bugs Ensure architecture and maintainability doesn’t erode Frequency? Why use it? Time savings? Weekly to bi-weekly Stay on top of code architecture and maintainability Re-usable, clean architecture can shrink project times by months ,[object Object],[object Object],[object Object],[object Object],Collaborative code reviews focus on critical design & requirement issues Builds are cleaner, more stable and reliable, leading to less downtime Coding errors and design cleaned-up prior to check-in

CONFIDENTIAL Ship higher quality and more secure products on-time Test teams can focus on customer requirements not programming bugs Coding errors and design cleaned-up prior to check-in Builds are cleaner, more stable and reliable, leading to less downtime Ensure architecture and maintainability doesn’t erode

Why Klocwork? CONFIDENTIAL Ship higher quality and more secure products on-time Ship higher quality and more secure products on-time Coding errors and design cleaned-up prior to check-in Test teams can focus on customer requirements not programming bugs ,[object Object],[object Object],[object Object],[object Object],Collaborative code reviews focus on critical design & requirement issues Builds are cleaner, more stable and reliable, leading to less downtime

Questions? ,[object Object],[object Object],[object Object],CONFIDENTIAL

Introducing: Klocwork Insight Pro | November 2009

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (8)

Ähnlich wie Introducing: Klocwork Insight Pro | November 2009

Ähnlich wie Introducing: Klocwork Insight Pro | November 2009 (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Introducing: Klocwork Insight Pro | November 2009

Hinweis der Redaktion