Top Banner

Click here to load reader

Benefits of SharePoint 2010 as a Product of SharePoint 2010 as a Product Platform For Independent Software Vendors and Enterprises Authors: Owen Allen – Principal, SharePoint Directions

May 22, 2018

ReportDownload

Documents

phamnhan

  • Benefits of SharePoint 2010 as a Product PlatformFor Independent Software Vendors and Enterprises

    Authors:

    Owen Allen Principal, SharePoint DirectionsEric Bowden Senior Consultant, ThreeWillKirk Liemohn Principal Software Engineer, ThreeWillDanny Ryan Principal, ThreeWillTommy Ryan Principal, ThreeWillPete Skelly Principal Consultant, ThreeWillJohn Underwood - Technical Evangelist, ThreeWill

    Contributors:

    Geoffrey Edge Senior Technology Specialist, Microsoft CorporationKirk Evans Developer and Platform Evangelism for Communications Sector, Microsoft CorporationChris Mitchell Technology Architect for Microsoft Technology Center, Microsoft Corporation

    Reviewers:

    Bill Arconati Product Marketing Manager, Atlassian Software SystemsTony Clark Director, Enterprise Architecture, Cox EnterprisesGeoffrey Edge Senior Technology Specialist, Microsoft CorporationBo George Senior Application Developer, Aflac Murray Gordon ISV Architect Evangelist, Microsoft CorporationAdam P. Morgan - Enterprise Sales, Digital Marketing Platform Group, Microsoft Corporation Aaron Rafus Technology Evangelist, McKesson CorporationWilliam Rogers Chief Workplace Architect, CorasWorks CorporationScott Schemmel - VP, Global Information Technology at PGi Brendon Schwartz Senior Platform Engineer, JackBe CorporationCole Shiflett Solutions Architect, EquifaxDr. Todd Stephens Senior Technical Architect, AT&TMatt Waltz Chief Technology Officer, NextDocsMichael Wilson Solution Specialist for Office and SharePoint, Microsoft Corporation

    Date published: November 2010

    SummaryDuring the 2009 SharePoint Conference, Christian Finn, Director of SharePoint Products for Microsoft, commented that given current trends, building products on the SharePoint Platform is the new black. To make his case, he cited the momentum of the SharePoint platform along with significant announcements from companies building integration with SharePoint into their products and services. This white paper, designed for Independent Software Vendors, software architects, CIOs, and other enterprise technology leaders picks up this discussion by addressing the perceived limitations that may cause development companies to discount SharePoint as a development platform when drawing up a technology roadmap and illustrating the value of leveraging SharePoint as a Web Application Development Platform for those organizations.

  • 2 3

    Contents

    Why This White Paper ..............................................................3

    SharePoint Background ...........................................................4

    Audience for this Paper............................................................6

    Making the Case for SharePoint .............................................7

    Does SharePoint Fit .........................................................................7

    Making the Case ...............................................................................8

    Leveraging the Platform ............................................................8

    Understand Your Value Proposition ......................................8

    SharePoint Platform Strategies ..............................................9

    Connect ................................................................................................9

    Extend .................................................................................................11

    Build On .............................................................................................12

    Platform Capabilities ..............................................................13

    Infrastructure ...................................................................................13

    ASP.NET HTTP Pipeline ................................................................. 13

    Application Security ....................................................................... 14

    Service Applications ....................................................................... 14

    Packaging and Deployment ....................................................... 14

    Office 365 & SharePoint Online ................................................ 14

    Content Management ..................................................................15

    External Data ..................................................................................... 15

    Business Intelligence ...................................................................... 16

    Search .................................................................................................. 16

    Workflow ............................................................................................ 17

    Data Model User Interface .......................................................... 17

    And More... ........................................................................................ 17

    User Interface ...................................................................................18

    Platform Capabilities Summary ................................................19

    Barriers to Adoption as a Development Platform ............20

    Perceived Barrier 1 - Unique Developer Skill Set .........................................................20

    Perceived Barrier 2 - Closed or Restrictive Platform Services ..................................20

    Perceived Barrier 3 - Lack of Integration with External or Relational Data ........21

    Perceived Barrier 4 - Application Lifecycle Management (ALM) and Code Isolation. .................................................................................21

    Is Perception Reality? ....................................................................22

    Misconceptions of SharePoint as an Application Platform ..............................................................23

    Misconception 1 - A SharePoint Dependency Means Closed Architecture .......................................................................23

    Misconception 2 - SharePoint Applications Are Too Restrictive ........................23

    Misconception 3 - SharePoint Is Only a Document Repository..........................24

    Misconception 4 - SharePoint Cannot Be Used to Run Line of Business Applications ..............................................................25

    Community Support and Tooling ........................................26

    Community .......................................................................................26

    Visual Studio ....................................................................................26

    Debugging ........................................................................................26

    SharePoint Designer ......................................................................27

    Third Party Tools .............................................................................27

    Office 365 & SharePoint Online Resources ...........................27

    Next Steps .................................................................................28

    Feature Mapping ............................................................................28

    Market Analysis ...............................................................................28

    Bake Off .............................................................................................28

    Pilot Project ......................................................................................28

    Consult with Others .......................................................................28

    ISV Ecosystem Map ........................................................................29

    Key Resources ..................................................................................30

    References .........................................................................................30

    Glossary of Terms ...........................................................................31

    Footnotes ..........................................................................................34

  • 3

    Why This White Paper

    As with any evolving product, there are false ceilings set due to peoples experiences with previous versions. The initial core features/capabilities for SharePoint were targeted to provide out-of-the-box features that made the product easy to use and administer for team sites and portals. The product was extensible from the beginning, but it was not architected for the mainstream developer. This focus has changed over the years and there are very compelling reasons that product companies should consider SharePoint in their technology roadmaps.

    The ability to leverage the rich features of SharePoint technologies is reason enough to consider SharePoint as a web development platform. Another key reason to consider either building on top of SharePoint or having a connection strategy with SharePoint is market opportunities that come from being associated with this popular platform (over 100 million licenses of SharePoint have been sold). The purpose of this white paper is to address the perceived limitations that typically cause product companies to discount SharePoint when determining a technology roadmap for their products.

    This white paper will dive into some of the features of the platform, including how a company could build a better product faster and take advantage of the rapid adoption and increased market interest in SharePoint as a platform. Also described in this paper are the Connect, Extend, and Build On strategies and the advantages of each approach.

  • 4 5

    SharePoint Background

    SharePoint is now in