Enabling Technology Innovation using Open Source Software Black Duck Software Tammi Pirri SNHU Presentation

Agenda Black Duck Company Overview Market Dynamics & Challenges Technology Roles Black Duck Summary

About Black Duck Software Accelerate time-to-market and reduce development costs by providing products and services for which enable companies to find, manage and deploy open source software within their own development environment. Mission Founded in 2002 and backed by industry leaders Black Duck Global Distribution

620 Customers in 20 Countries Electronics Financial and Services Software Black Duck has exceeded the 600 customer mark which makes us the leader in our fast growing market space. Here is a sample of some of the more well known names. Other

Market Dynamics and Challenges

Enabling Innovation with Open Source Accelerate Time to Market Use open source software to avoid reinventing the wheel Increase Innovation & Product Capability Readily available to fill out feature list Focus internal resources on valuable new features Lower/Control Development Costs Reuse to lower development and licensing costs Improve development and group productivity Judicious use of open source can avoid reinventing the wheel and free-up resources that may otherwise be consumed in areas that don’t provide strong value to customers or differentiation against competitors. Innovate more, code less

Evolution of Software Development Development Applications Management Code Design Individual Software Developer Project Team Collaboration Application Life Cycle Management Single Enterprise Scope Focus Component-Based Development In the very early days of computing, product offerings seeking to improve developer productivity focused on tools for code design that could be used by the individual developer. For example, the first version of Turbo Pascal appeared in 1983. As the industry matured, the focus of innovation grew to facilitate the collaboration of groups of developers. For example, the (then revolutionary) revision management tool ClearCase was released by Atria software in 1992. Today, it’s the rare application that’s developed and coded from the ground up exclusively by internal resources. In the world of component-based development, where “reuse” is the mantra, developers are looking at a variety of sources of code; both internal and external. External sources of code are suppliers, partners and the open source community. We term the blending of the internal and external sources of code “the development ecosystem.” This brings us to the most recent (rightmost) stage in the history of innovation aimed at developer productivity which takes place in the era of component-based development. 1980’s 1990’s 2000’s

Software Development Today Outsourced Code Development Internally Developed Code Commercial 3rd-Party Code Open Source Software Individuals Universities Corporate Developers Most companies today, from SMB to Fortune 500, have mixed source environments for their code base. How will you know what your code is made out of? How can you replicate quickly, release and update, if you aren’t certain what your code is made out of? Software Application Mixed Source Environments

Development Organization Challenges Management Leverage the right software from many sources Increase productivity using component software Encourage standardization of components & versions Deliver timely support Compliance & Security Comply with open source policies Manage licensing and associated obligations Complying with export regulations Track security vulnerabilities The challenges arise from mixing code from different sources: partner code, open source, internal code and vendor sourced. Each of these sources could be managing its own separate version of a code component. They could be incorporating conflicting software licenses into the code base. The code could have unexpected dependencies. The software ‘integrator’ is on the hook for robust and timely support, but the support model for open source code is an area that people must think about explicitly. Code from the development ecosystem could have varying levels of quality – some of it is great, some of it, not so great. If an organization implements compliance, it may involve many approval boards. The danger of thorough compliance is that it can be time consuming, slow to react and bureaucratic. Yet, it is a necessary part of software development in today’s complex and changing landscape.

Examples of some Open Source Challenges (iPhone WIP300) Infringement Valuation Negative publicity New revenue Support costs Vulnerability (Network Attached Storage) (GPS Navigation) (Home Hub Router) (Wireless Router) (WiMax, other ) (VOIP Phone) 10

Google Security Flaws These vulnerabilities discovered within 24 hours of release Easily avoided with the right solution

The Black Duck Solves the Challenge: Enterprise architecture Modular design Customizable Extensible KnowledgeBase SDK Core & Application Frameworks UI Framework 12

Software Code Search Community Black Duck Software acquired Koders Inc, a leader in open source code search on the Internet www.koders.com – free code search Over 1.7 billion lines of code 32 languages Eclipse, Visual Studio, browser plug-ins

Technical Roles within Black Duck Software

Technical Skills: Knowledge Base Knowledge Base – Core of Black Duck’s Enterprise Products Roles within KB area: Data Collectors “Spiders” Software Automation Engineer Knowledge Base Team Leaders Technical Skills: Experience working with Linux and Perl Website navigation experience (Sourceforge.net, Rubyforge.org) Knowledge of Software Automation tools

Technical Skills: Product Development Agile Software Development Environment Roles within Application Development: Engineering Intern Software Engineer UI Engineer Sr. Software Engineer Principal Software Engineer Architect Team Lead, Product Development Proficiency within: Java RDBMS (Oracle, PostgreSQL, MySQL) Web Server Technology experience – Apache Tomcat, Hibernate, Spring/Struts Perl, XML, .Net 16

Technical Skills: Quality Assurance Manual/Automation Testing Roles within Quality Assurance: QA Intern QA Engineer Sr. QA Engineer Release/Install Engineer Skills/Proficiency within: Linux/Windows Environment Test plan creations Java Programming UI automation testing (Selenium) Regression/Performance Testing (Java/Soap) Post Build regression testing (Perl, ANT, Java, XML) Release/Install –Shell Programming Skills (BASH, Perl, Batch scripting) 17

Technical Skills: Professional Services Post Sale customer interactions Deployment/Installation Training M&A Assessment Due Diligence Infrastructure Audit Roles within Professional Services: Applications Consultant Sr. Applications Consultant Deployment Services Manager Implementation Project Manager Skills/Proficiency within: Linux/Windows Environment Some Java Programming Open Source Tools knowledge SOAP API experience 18

Summary

The Black Duck Solution Solves the three main challenges associated with open source component usage: Management (search, select, approval, monitoring) Compliance (legal, export) Security

Black Duck leads the way Leadership products for managing open source throughout the application life-cycle Pioneered open source code analysis market in 2002 Most experienced vendor with largest customer base Most comprehensive KnowledgeBase of open source software in the industry Responsive 24X7 support, global presence

Questions?