Improving Development Productivity: Static Analysis and Continuous Integration
•
1 gefällt mir•843 views
![[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],Webinar Logistics ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (8)
Ähnlich wie Improving Development Productivity: Static Analysis and Continuous Integration
Ähnlich wie Improving Development Productivity: Static Analysis and Continuous Integration (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Improving Development Productivity: Static Analysis and Continuous Integration
- 1. Improving Development Productivity with Static Analysis and Enterprise Continuous Integration A joint webinar with Klocwork and Urbancode
- 5. Introduction
- 7. Productivity Bottlenecks in the Software Development Lifecycle
- 8. Productivity Bottlenecks in the SDLC Productivity Result for Developers: More bugs reports, more fire drills Less time to write new code Peer Code Reviews Time consuming activity involving senior resources Should focus on critical code & design issues Integration Builds Critical milestone in development process Unstable integrations will slow down entire team Release Huge costs associated with bugs shipped to customers Difficult to predict stability with large code bases Testing Resources here should be focused on requirements Extended testing time can delay release and increase costs Implement Build Unit Test Check-in Integration Build System Test Release
- 9. Addressing Productivity Bottlenecks with Source Code Analysis
- 19. Addressing Productivity Bottlenecks with Continuous Integration
- 24. Builders can become bottlenecks
- 25. Deployments are similarly constrained
- 29. Quickly move from idea…
- 30. … to automation
- 32. Unified build lifecycle information Confidential
- 33. Self-service user interface Confidential
- 35. Data Aggregation and Reporting
- 36. 50+ integration across the lifecycle
- 37. Klocwork and AnthillPro Integration
- 42. Confidential
- 43. Confidential
- 46. Summary
Hinweis der Redaktion
- Speaker: Moderator
- Speaker: Moderator
- Speaker: Moderator Start with a brief introduction to explain why KW and UC are working together Discuss the productivity bottlenecks that can be solved using SCA and CI, and provide overviews of both Klocwork and Urbancode’s solutions. Followed by a look at the integration of our two solutions and how if you are a customer of KW or UC or considering either solution, how you can get the most of your investment
- Speaker: Moderator Alen is Klocwork’s Director of Product Management, responsible for setting the company’s product direction. Alen has a technical and consulting background in the telecom equipment and software tools markets, and has helped hundreds of organizations successfully deploy source code analysis technology. Jeffrey is a 17-year veteran of the software industry and has performed and managed virtually every role in the software development lifecycle, including VP of Engineering and VP of Product Management. Jeffrey has over 8 years experience at the leading edge of continuous integration and is currently Technical Evangelist at Urbancode.
- Speaker: Moderator passes to Alen
- Speaker: Alen
- Speaker: Alen
- Speaker: Alen There are a number of key milestones in software development that need to operate smoothly in order to improve overall productivity: Peer code reviews Integration builds Testing Release/deployment Unfortunately, unstable or buggy code will significantly impact productivity at all of these important milestones: Peer code reviews will be bogged down with senior dev resources discussing bugs in the code rather than critical design or requirements issues; Integration builds need to be stable – The builds are taking a long time; the more bugs that are checked into the build, the higher likelihood of unstable builds, broken regressions, and a serious drag on productivity; Testing should be focused on being customer advocates and not identifying programming bugs that could have been caught by developers; Obviously released software needs to be as secure and high quality as possible, otherwise significant costs, customer retention issues, and brand damage can occur. The result for developers is they are inundated with more fire drills and bug reports, resulting in less time to write new code which is a major productivity drain.
- Speaker: Alen
- Speaker: Alen Important to walk the audience through this quick SCA basics slide to ensure everyone is clear what SCA is all about. Source code analysis is the critical enabling technology required to meet the productivity goal of stabilizing code quality as early in the development process as possible. Rest of slide summarizes what issues can be found with SCA, where it is used in the development process (introduce importance of desktop analysis), and the automated nature of the technology vs. other testing tools.
- Speaker: Alen
- Speaker: Alen
- Speaker: Alen
- Speaker: Alen
- Speaker: Alen
- Speaker: Alen
- Speaker: Alen
- Speaker: Alen
- Speaker: Alen passes to Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff
- Speaker: Jeff passes to Moderator