Android for the Enterprise and OEMs


Published on

While Android and open source software not-so-quietly revolutionized the mobile industry, Enterprise IT organizations have taken notice. “The consumerization of IT” and ubiquity of mobile devices are forcing a transformation of Enterprise IT infrastructures, something that Geoffrey Moore refers to as “Systems of Record” and “Systems of Engagement.” These new infrastructures will be built largely with open source components. But whether developing a new device or new IT infrastructure, development with open source software is not business as usual. Choosing and modifying components from external sources, integrating with proprietary code, evaluating licenses and community viability, etc., require new processes for choosing components and new ways of providing control and visibility.

In this presentation Peter Vescuso will discuss the issues of OEM development with Android and open source, where and how it impacts Enterprise IT, and for both how to provide the control and visibility required by management while giving developers the freedom they need to create and innovate.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • CPU: dual core, 1 GHZ or betterRam: 1GBStorage: 16, 32 GBCamera/Video: 8 mp , 1080p HD videoAll for < $299
  • Gartner Group ‘s lead analyst on open source, Mark Driver (data in the slide is from November 2010), summarized the benefits and key challenges of using FOSS.In addition, Mark has commented on the ubiquity of open source, that it is unavoidable and should be embraced as part of normal development process. Mark also made the following predictions:-- By 2016, OSS will be included in mission-critical software portfolios within 99% of Global 2000 enterprises, up from 75% in 2010.-- By 2014, 50% of Global 2000 organizations will experience technology, cost and security challenges through lack of open-source governance.
  • This is the Google Android Architecture diagramRun time on virtual machine External components like webkit and SSLApplication developers and device manufacturer will innovate at different places in the architecture as indicated by the yellow dots.Device Manufactures will modify lower in the architectureThe issue is depending on what you change, and what license the component is licensed under will dictate a set of obligations.
  • StrategyA strategy articulates the business objectives for using FOSSMost companies do not have a documented strategy. It’s an important tool for establishing consensus and communicating business rationale behind policies.Without a strategy, FOSS program is largely reactivePolicy & ProcessPolicy are the “rules” for using FOSSProcess is the way Policy is reliably realized on a day-to-day basisTechnology Automates the key processes for effective management and governance, allows organizations to “design in” compliance
  • Android for the Enterprise and OEMs

    1. 1. Android for the Enterprise and OEMs<br />Peter Vescuso<br />Black Duck Software<br />
    2. 2. About Black Duck SoftwareBuild better software faster by automating and managing the acquisition and governance of open source<br />OSS info, e.g. GitHub, Maven, …<br />KnowledgeBase<br />Governance<br />Approve<br />Catalog<br />Validate<br />Acquire<br />Monitor<br />Plan<br />Code<br />Build<br />Release<br />Test<br />
    3. 3. Consumerization of IT<br />My Laptop<br />
    4. 4. Agenda<br />Market Trends<br />Enterprise IT<br />OEM & Device Manufacturers<br />Summary<br />
    5. 5. Consumerization of IT<br />Processor: 1.4 GHZ<br />Storage: 32 GB<br />Video: 3D, HDMI, more<br />
    6. 6. Future of Enterprise IT<br />
    7. 7. Moore’s Model Requires IT Evolution<br />Systems of Engagement<br />Systems of Record<br />
    8. 8. Devices<br />Open Source as the Foundation for Mobility Infrastructure<br />Front End<br />Security<br />Development<br />Open SSL<br />Open SSH<br />Memcached<br />Open LDAP<br />Glassfish<br />Back End<br />
    9. 9. OSS and IT Infrastructure: Benefits and Challenges with Open Source<br />“Open source is ubiquitous, it’s unavoidable….having a policy against open source is impractical and places you at a competitive disadvantage”<br />Key Benefits<br />Flexibility<br />Modify, mix, reuse code<br />Innovation<br />Leverage OSS and community<br />Cost Optimization<br />Reduce or eliminate acquisition costs<br />Challenges<br />Technical Failure<br />Operational exposure<br />Needs to be audited, managed<br />Security Risks<br />Business exposure<br />IP Risks<br />Legal exposure<br />Source: Mark Driver, Gartner Group, November 2010<br />
    10. 10. Complexity for OEMs/Device Manufacturers<br />Components and code from many suppliers<br />Need to control and manage building software on a rapidly changing O/S<br />Multiple releases per year<br />Customize Android for:<br />The type of device (phone, tablet, TV, etc.)<br />Device drivers, power consumption, etc.<br />User experience<br />Do it all while ensuring compliance<br />
    11. 11. Android & Vendor Innovation<br />Developers<br />Typical areas of vendor/developer innovation<br />Source: Google - //<br />
    12. 12. Software Package Data Exchange™ (SPDX™)<br />Working group of the Linux Foundation<br />Charter: <br />Create data exchange standards to enable license and component information sharing (metadata)<br />Participation from over 16 organizations including software, systems and tool vendors, consultants and foundations<br />“SPDX is a crucial building block in an industry-wide system of automated license compliance administration” Eben Moglen, SFLC<br />
    13. 13. Enabling Developer Freedom (with Visibility and Control)<br />Strategy<br />Articulate the business objectives for use of OSS<br />Policy & Process<br />OSS policy & management process<br />Training & Technology<br />Automate governance and compliance<br />Design-in and automate policies<br />
    14. 14. Getting Started….<br />Black Duck Governance Fast Start<br /><ul><li>A fully functioning governance and automation platform configured with industry best practices to provide immediate returns
    15. 15. Includes:
    16. 16. Policy - initial policy implementation to get started
    17. 17. Acquisition - automated approval/request process and workflow for acquisition of open source
    18. 18. Catalog - pre-populated catalog with popular OSS components
    19. 19. Compliance - automated validation server
    20. 20. Support - optional commercial support from credativ</li></ul>For organizations that want to implement a governance solution quickly and increase sophistication and capability over time.<br />
    21. 21. Summary<br />Android has revolutionized the mobile and device landscape<br />Enterprise infrastructure is adapting to “Systems of Engagement,” open source is key enabler<br />Developers need freedom to use the best code, Management needs visibility and control<br />Solution requires training, tools, and processes<br />