Your SlideShare is downloading. ×
0
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Sharepoint 2010   composites
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Sharepoint 2010 composites

1,608

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,608
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
50
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • We will talk about how SharePoint can help you redefine your platform with capabilities that help you deliver solutions that are composite, people-centric and collaborative on a single platform that can be centrally managed. We will learn what makes SP apps special, what tools and developer services are available, how SP solutions are deployed on a centrally managed platform and finally see how the ecosystem of partners may help you find even more specific solutions for your area or industry.The most important message is how SP helps you close the value gap between non differentiating solutions like infrastructure software and solutions ONLY YOU can build and that because they incorporate your intellectual property are differentiating.
  • Describe the overall value of SharePoint. This deck assumes that this has been covered. In particular though, we will be discussing the role of SharePoint in helping organizations rapidly respond to business needs, as well as how SharePoint Composites is a differentiating aspect for applications built using SharePoint.
  • These are the typical questions we hear from people and which we address in this deck:What is the role of SharePoint in my app dev strategy (by a CIO or VP of App Dev)Should I develop a specific app on SharePoint?How can SharePoint help me deal with the backlog of applications I can never seem to have resources to build?How should I think about solutions built by end users or power users?
  • We will talk about how:SharePoint applications are differentiated from traditional appsHow SharePoint provides a spectrum of tools and platform services to build appsHow SharePoint’s central platform helps with manageability of applicationsHow SharePoint has evolved into a thriving ecosystem for vertical solutions as well as partner solutions that extend SharePoint
  • Here are the actors we will talk about:The end user (“business side”): the most important role in our discussion. We are solving a problem for this audienceThe developer (“app dev team”): the role that enables or creates a solution as a response to some business requirementThe IT Pro (“operations team”): the team that is tasked with managing the platform and applications produced by (“thrown over the fence by”) the development team
  • The challenge to most orgs is four words: more demands, less resources.Individuals and organizations are being asked to do more IT resources are scarceTherefore unsolved problems (“backlog”) continue to pile up This increases business dissatisfaction with ITOn top of that, organizations operate in a regulatory environment, rules and governance rules that can change and require governance in terms of security of data, authentication/authorization rules, etc.
  • So we need to recognize this creates tension between IT and the business because they each want something that the other seemingly does not want: the business users want to be empowered, while IT wants to keep some sense of control.This is the paradox, and the question is: how can we break this paradox?
  • There is a value gap between what the business wants and what technology delivers. Most technology from software vendors (everybody, including Microsoft) is sold to all customers. Much of it is standard and therefore not differentiating (it is not differentiating because everybody gets the same technology).It is in those applications YOU (the customer) build that you find the innovation and differentiation that your business requires. Those apps are the ones that ONLY YOU CAN BUILD through custom applications. You can always hire system integrator or consultants, but in general apps incorporate differentiation for your company.That is the business gap you want to close and that SharePoint can help close.
  • Geoffrey Moore, author of “Crossing the Chasm” talks about this in his book “Dealing with Darwin.”In this matrix, the are two columns: on the left are solutions that are “Core” and on the right solutions that are “Context.” Core solutions are those that create differentiation, while Context is everything else. Note “Core” does not mean “Core Competence.” A core competence is something you do very well, but it may or may not be “Core” in Moore’s terminology. For example, one of the core competences of an airline is flying airplanes. But that is not “Core” because it does not create differentiation: all airlines need to be good a flying airplanes.On the rows, we have Mission Critical apps on the top row. These are apps that carry significant risk to the organization if something was to malfunction. At the bottom you have the non mission critical apps.Most interesting processes in companies start in Quadrant I as non mission critical applications that add some differentiation. They are some project that a department implements, but they are still not mission critical because they have not been launched to scale.Over time, the solution evolves to becoming mission critical. IT takes it over and deploys it across the organization.However, everything becomes Context. Other companies probably copy your process or it ceases to be Core. Think of accounting or accounts payable in many organizations. They are not differentiating. Some vendors like ERP sell them as “packaged apps.”Over time, many processes actually become even less important that you actually outsource them (quadrant IV).The thing with Quadrant III (packaged apps) is that they are very important to support mission critical custom solutions of Quadrant 3. For example, a catalog or payment system is very important for a new ecommerce system because it allows it to be developed faster. So all Quadrant II solutions require some form of connectivity to Quadrant III solutions. We will talk about Business Connectivity Services in SharePoint later.
  • If we think about SharePoint applications, you can see that they are different from apps built on other platforms:First, they are people-centric, they surface in the familiar UX of SP and OfficeSecond, they are collaborative. They help people participate in ad-hoc processes that happen outside of enterprise systemsThird, they are composite. They are assembled, not built. Many apps can be built without code.
  • SharePoint Composites also helps apps differentiate from other apps built on alternative platforms:First, Composites helps you build solutions without code. Using SharePoint Designer, Access Services, Visio Services, etc. More importantly, many things can be done directly on the browserSecond, they help you unlock the value of your enterprise data. BCS (Business Connectivity Services) allows for that connection from “Quadrant III” to “Quadrant II” applications that we talked about before. With BCS, you can surface enterprise data in Word, Outlook and Workspace, with full CRUD (create, read, update, and delete) and Search-enabled.Third, Composites allows you to maintain control over the solutions with Sandboxed Solutions, centralization of Access and Visio investments, and health monitoring
  • They key in SharePoint is all the investments you see here at the bottom. From Forms and Wikis to Tags and Blogs to Offline access and Metadata. SharePoint comes with a lot of out of the box capabilities.These capabilities can be used across many frequent scenarios that occur in enterprise and web applications. From creating custom or standard app experiences, or processing documents, or connecting to other systems, or automating workflows, or analyzing and reporting on data, or creating sites.And as we saw before, these are fundamental scenarios that occur in many applications, from payroll portals to .com sites overviews, to many others you see here on top of this slide.
  • Application experiences are a key scenario. Many companies have created strange UX. Well, in SharePoint you can create standard user experiences that minimize training for people.Or you can customize the UX for very specific and unique requirements. In the end, it is the richness of the building blocks available in SharePoint that makes the difference.
  • In these applications, you can leverage your desktop skills in Access or Visio and share these apps or diagrams with others.
  • Many applications have unstructured document requirements, but they are typically “outside” of the app. We think that unstructured documents should be considered to be part of the relational data model of an app. With SharePoint you get document sets, records management, metadata and you can implement retention policies for documents.You can also use document generation techniques on the server with Excel Services or Word Automation Services for, for example, reports or bill production or generation of PDF files.
  • Connecting to external systems is something most applications need. No app that is not trivial really stands in isolation.This is useful to extend LOB systems that tend to have difficult to use user experiences and extend these apps to more users via Office and SharePoint.
  • We connect to external systems in SharePoint via BCS. With BCS, you first create what is called an “External Content Type” which you see here in the middle. This is used to describe to SharePoint how to read, update, delete, etc., against an external source. The beauty of that is that once that is done, you many things “automatically”:You get to search that dataYou can use it in SharePoint listsYou can use it in Workspace or InfoPathYou can use it in Outlook or Word
  • Human workflow is also another common task need in apps that SharePoint supports. Here, we see a few layers of sophistication from simple diagramming at the bottom to Biztalk integration on top.Using SharePoint you can use a number of out of the box workflows for simple document tasks like approvals. You can also edit them, or you can create your own custom ones using SharePoint Designer. You can also use WF in Visual Studio and use these tasks in SharePoint.BizTalk integration falls beyond the scope of SharePoint but it is something that can be done with code.
  • What application does not have or does not generate data? Using SharePoint you can also leverage increasingly sophisticated solutions. From simple chart web parts (bottom) to mash-ups using Excel Services or Visio. Or if you need to implement BI solutions you can use PerformancePoint Services.The idea is to empower users to create their own reports and visualizations of data. You should produce less “canned reports” since they tend to be less useful.
  • Finally, every application has stakeholders. These are people who live inside or outside of the organization but that are not the actual users of the app. For example, for an HR recruiting system there are stakeholders like the hiring managers, the interviewing team, the actual candidate, etc. The managing team (in this case the HR recruiting team) can use SharePoint to publish information via sites to these stakeholders. A lot of these customizations can be done on the browser.
  • Now let’s talk a little about developer services and how SP helps them be more productive.
  • If you are not a developer, here is the one thing you want to remember. Many platforms are “opaque.” What this means is that you can only write on the platform but not use the underlying layers. They tend to be black boxes. The problem with this is that there is always that point where you start pushing the limits of the platform. In these opaque platforms you hit the wall and those problems become VERY complex to solve.Because SP is built on .NET, the complexity of your solution increase more smoothly as the problem’s complexity increases. There is no “WALL.”
  • In terms of tools, you have also increasing sophistication tools:The browserSharePoint Designer and the Office tools like Access and VisioVisual StudioThey are useful for increasingly complex problems, from simple customization using web parts (bottom) to major enterprise integration (top), for example.
  • Visual Studio 2010 has the most sophisticated tools for SharePoint with very rich templates for modules, content types, workflows, lists, etc., that you see here, and more.
  • There is support for Silverlight, XSLT views, support for Standards and even for Multilingual UXs.
  • In SP 2010, there is more support for referential integrity (cascade and transactional deletion, for example)as well as validations for things like required fields, uniqueness, etc.
  • The programmability platform has also been enhanced dramatically, with support for SPLinq, REST services, client APIs (with Object Models for Javascript, .NET, and Silverlight), better workflow and richer event support.
  • While this slide is a little busy, let’s use it to provide a single place where we can have a conversation about your business problems and application issues by highlighting the attributes that makes SharePoint a great platform for custom applications and how they may relate to your application needs. We are combining a number of the value elements of SharePoint with a base of technical detail that can help us have the right conversation both across the business side and those of you who are from IT.SharePoint 2010 is the business collaboration platform that unifies platforms that have previously been silos into a single people-ready infrastructure. Most times people think about SharePoint as an application, but SharePoint is also a platform upon which to build your proprietary innovations. FOCUS ON THE END USER: One of the issues with traditional application platforms has been that the functionality (and as a result) the applications that are made possible are primarily focus on back end issues to the detriment of the end user. With SharePoint, the end user is considered the focal point of all application value. End users are able to connect with each other in very rich ways, from the browser, to the rich experience of Office, or when they are mobile or disconnected. Users feel empowered to perform their jobs and business in ways that was not possible before because they interact with the application through a familiar user experience that can span all the situations a user may find himself in.All of this is possible through increasing levels of functionality that is layered on each other. Let’s discuss this from the bottoms up.ENTERPRISE LOB AND EXTERNAL SYSTEMS: Any non trivial solution cannot stand in isolation. They typically require access to the system of records that are the backbone of an enterprise. These systems are typically more static and change less frequently, but they are important nonetheless. One of the problems that these systems face is a very rigid and unfriendly user interface. What SharePoint and the rest of the Microsoft platform do is to help users connect to this data seamlessly. SharePoint provides the capabilities to connect to this data while respecting the security and policies in place to ensure that only the appropriate rights are granted to users. More importantly, SharePoint makes it possible for users to work with this data just as if the data were store in SharePoint. In addition to LOB data, companies are becoming more used to leveraging cloud services in their applications. Connecting to these external systems, LOB applications and cloud services is done in SharePoint primarily through the Business Connectivity Services.REST OF MICROSOFT PLATFORM: One of the greatest strengths of SharePoint is that is built on the most successful enterprise-class application platforms: the Microsoft Application Platform. SharePoint is built on Windows, SQL Server, and .NET. As a result, it inherits all of their benefits. All of the great capabilities of SharePoint are possible because we did not have to spend resources building those capabilities and are able instead to leverage them to create a very scalable, robust, and manageable platform. In addition, SharePoint is a “transparent” platform, meaning that developers have line of sight to these underlying technologies and are able to leverage those capabilities directly in their code if necessary (their object models, their APIs, etc.) and use the advanced tools in Visual Studio to create sophisticated applications.KEY SHAREPOINT PLATFORM SERVICES: On top of the Microsoft application platform, SharePoint built a number of platform services that serve as the foundation for both SharePoint and an enterprise applications. This is not an exhaustive list but it includes the major areas of investments that are relevant to those who are considering building solutions on SharePoint. Of course, a great platform has to have great programmability in the forms of object models. Most people are familiar with the traditional SharePoint server object model, but something new is the object models that are available on the client tier, including a .NET, Silverlight, and JavaScript, for example. There is also great support for web based standards such as REST and Web Services.The application model is what makes SharePoint so usable. It is the foundation of what an application in SharePoint is. Here we define the UX framework, the list and libraries, the model for the sites and pages, the web part framework, security, etc. We also provide the infrastructure to connect to external data and to provide connectors for Search.Deployment is important because it is the linkage between development and the operations sides. In SharePoint 2010 we are unifying all deployment technologies under a common deployment framework (the WSP).Finally, Security and Manageability are key services in the platform. SharePoint defines a framework for users, roles, and groups that is used throughout the platform. In SharePoint 2010 we have also made great investments in Claims-based authentication and pluggable provides to integrate with other ways to authenticate users. For Manageability, the platform provides also with great scripting capabilities through PowerShell and also administration and monitoring functionality to ensure that the infrastructure is operating at its best.OUT OF THE BOX CAPABILITIES: It is likely that you are already familiar with these capabilities. In SharePoint, we have leveraged our own platform services to build the applications that make up SharePoint. These are the “six slices” of the SharePoint pie, from Sites and Communities, to Content and Insights, as well as the Search capabilities. The power of the SharePoint platform is that you can create your own applications using the same foundation we did, just like we were able to create the applications that come in SharePoint out of the box.SHAREPOINT COMPOSITE APPLICATIONS: A composite application in the industry is one that is built using previously existing building blocks. That is exactly what SharePoint Composite applications are. However, the key difference in SharePoint is that we place the end user in the center of the interaction, and built a unified platform to make the vision of Composition a reality across many different domains. So in SharePoint you are able to create Composite Applications that span scenarios of people, LOB data, data analytics and business intelligence, Search, workflow and documents, and of course the Web. All of these scenarios can come to live in your application. We are already seeing many customers doing just that: they build data tracking applications, of integrate with LOB data in Office Business Applications (OBAs). We have seen many applications that also empower decision making and enable business insight, combining unstructured and structured information making it easily usable, accessible, and discoverable with rich, self-service capabilities that enable the creation of business intelligence content in scorecards and dashboards. Or applications that implement human workflow over forms and documents to reduce errors and make a process more efficient. We also have seen search-based applications that create very dynamic and engaging experiences based on search, helping people navigate all of the information they have without having to codify that navigation rigidly into the application. And finally, we have seen applications that exploit the interactivity available on the web through Rich Internet Applications in public facing sites.MANAGEMENT: In other platforms, all of these applications would have created a great amount of issues for the IT Pros who are in charge of keeping the platform working. Not in SharePoint. Our platform gives you the flexibility to deploy these applications on premise or online, or to create a Shared Services infrastructure that you can leverage across your business units or across your applications. One important aspect of our platform in 2010 is the concept of Sandbox Solutions. This capability enables End Users to upload their own solutions to SharePoint and to run them in their own sandbox, meaning that they won’t negatively affect the infrastructure. Your IT personnel can set the right parameters in terms of resource consumption and utilization that will bound these solutions. If the solution starts going beyond these limits that you define, then SharePoint is able to manage it and block it. Imagine for example an application that for some reason starts taking up a lot of CPU. Well, your other applications won’t suffer because SharePoint will manage that faulty application down to where the application no longer works and the problem is fixed. The benefit is that you don’t have to baby sit these applications: you basically set the parameters of resources you are comfortable with, and then SharePoint does the rest.IN CLOSING: We hope that you are able to see how SharePoint can be the used for your own internal proprietary innovations and not just in what it brings you out of the box. It is a great platform for end users because they are the center of your application, enabling them to work as they want to. Your developers are more productive because of the great tools and programmability capabilities in the platform, and because they will be using the same tools they are used to in Visual Studio. And finally, your operations team and IT Pros will be able to do their job and keep the platform up and working and have the flexibility to deploy the solutions in the model that is the most appropriate for the need.MORE INFORMATION: There is also more information available on the web. You can certainly find more at sharepoint.microsoft.com in the SHAREPOINT COMPOSITES section, with white papers on our platform, videos, and other useful links to SharePoint developer content, end user content, etc.
  • While this slide is a little busy, let’s use it to provide a single place where we can have a conversation about your business problems and application issues by highlighting the attributes that makes SharePoint a great platform for custom applications and how they may relate to your application needs. We are combining a number of the value elements of SharePoint with a base of technical detail that can help us have the right conversation both across the business side and those of you who are from IT.SharePoint 2010 is the business collaboration platform that unifies platforms that have previously been silos into a single people-ready infrastructure. Most times people think about SharePoint as an application, but SharePoint is also a platform upon which to build your proprietary innovations. FOCUS ON THE END USER: One of the issues with traditional application platforms has been that the functionality (and as a result) the applications that are made possible are primarily focus on back end issues to the detriment of the end user. With SharePoint, the end user is considered the focal point of all application value. End users are able to connect with each other in very rich ways, from the browser, to the rich experience of Office, or when they are mobile or disconnected. Users feel empowered to perform their jobs and business in ways that was not possible before because they interact with the application through a familiar user experience that can span all the situations a user may find himself in.All of this is possible through increasing levels of functionality that is layered on each other. Let’s discuss this from the bottoms up.ENTERPRISE LOB AND EXTERNAL SYSTEMS: Any non trivial solution cannot stand in isolation. They typically require access to the system of records that are the backbone of an enterprise. These systems are typically more static and change less frequently, but they are important nonetheless. One of the problems that these systems face is a very rigid and unfriendly user interface. What SharePoint and the rest of the Microsoft platform do is to help users connect to this data seamlessly. SharePoint provides the capabilities to connect to this data while respecting the security and policies in place to ensure that only the appropriate rights are granted to users. More importantly, SharePoint makes it possible for users to work with this data just as if the data were store in SharePoint. In addition to LOB data, companies are becoming more used to leveraging cloud services in their applications. Connecting to these external systems, LOB applications and cloud services is done in SharePoint primarily through the Business Connectivity Services.REST OF MICROSOFT PLATFORM: One of the greatest strengths of SharePoint is that is built on the most successful enterprise-class application platforms: the Microsoft Application Platform. SharePoint is built on Windows, SQL Server, and .NET. As a result, it inherits all of their benefits. All of the great capabilities of SharePoint are possible because we did not have to spend resources building those capabilities and are able instead to leverage them to create a very scalable, robust, and manageable platform. In addition, SharePoint is a “transparent” platform, meaning that developers have line of sight to these underlying technologies and are able to leverage those capabilities directly in their code if necessary (their object models, their APIs, etc.) and use the advanced tools in Visual Studio to create sophisticated applications.KEY SHAREPOINT PLATFORM SERVICES: On top of the Microsoft application platform, SharePoint built a number of platform services that serve as the foundation for both SharePoint and an enterprise applications. This is not an exhaustive list but it includes the major areas of investments that are relevant to those who are considering building solutions on SharePoint. Of course, a great platform has to have great programmability in the forms of object models. Most people are familiar with the traditional SharePoint server object model, but something new is the object models that are available on the client tier, including a .NET, Silverlight, and JavaScript, for example. There is also great support for web based standards such as REST and Web Services.The application model is what makes SharePoint so usable. It is the foundation of what an application in SharePoint is. Here we define the UX framework, the list and libraries, the model for the sites and pages, the web part framework, security, etc. We also provide the infrastructure to connect to external data and to provide connectors for Search.Deployment is important because it is the linkage between development and the operations sides. In SharePoint 2010 we are unifying all deployment technologies under a common deployment framework (the WSP).Finally, Security and Manageability are key services in the platform. SharePoint defines a framework for users, roles, and groups that is used throughout the platform. In SharePoint 2010 we have also made great investments in Claims-based authentication and pluggable provides to integrate with other ways to authenticate users. For Manageability, the platform provides also with great scripting capabilities through PowerShell and also administration and monitoring functionality to ensure that the infrastructure is operating at its best.OUT OF THE BOX CAPABILITIES: It is likely that you are already familiar with these capabilities. In SharePoint, we have leveraged our own platform services to build the applications that make up SharePoint. These are the “six slices” of the SharePoint pie, from Sites and Communities, to Content and Insights, as well as the Search capabilities. The power of the SharePoint platform is that you can create your own applications using the same foundation we did, just like we were able to create the applications that come in SharePoint out of the box.SHAREPOINT COMPOSITE APPLICATIONS: A composite application in the industry is one that is built using previously existing building blocks. That is exactly what SharePoint Composite applications are. However, the key difference in SharePoint is that we place the end user in the center of the interaction, and built a unified platform to make the vision of Composition a reality across many different domains. So in SharePoint you are able to create Composite Applications that span scenarios of people, LOB data, data analytics and business intelligence, Search, workflow and documents, and of course the Web. All of these scenarios can come to live in your application. We are already seeing many customers doing just that: they build data tracking applications, of integrate with LOB data in Office Business Applications (OBAs). We have seen many applications that also empower decision making and enable business insight, combining unstructured and structured information making it easily usable, accessible, and discoverable with rich, self-service capabilities that enable the creation of business intelligence content in scorecards and dashboards. Or applications that implement human workflow over forms and documents to reduce errors and make a process more efficient. We also have seen search-based applications that create very dynamic and engaging experiences based on search, helping people navigate all of the information they have without having to codify that navigation rigidly into the application. And finally, we have seen applications that exploit the interactivity available on the web through Rich Internet Applications in public facing sites.MANAGEMENT: In other platforms, all of these applications would have created a great amount of issues for the IT Pros who are in charge of keeping the platform working. Not in SharePoint. Our platform gives you the flexibility to deploy these applications on premise or online, or to create a Shared Services infrastructure that you can leverage across your business units or across your applications. One important aspect of our platform in 2010 is the concept of Sandbox Solutions. This capability enables End Users to upload their own solutions to SharePoint and to run them in their own sandbox, meaning that they won’t negatively affect the infrastructure. Your IT personnel can set the right parameters in terms of resource consumption and utilization that will bound these solutions. If the solution starts going beyond these limits that you define, then SharePoint is able to manage it and block it. Imagine for example an application that for some reason starts taking up a lot of CPU. Well, your other applications won’t suffer because SharePoint will manage that faulty application down to where the application no longer works and the problem is fixed. The benefit is that you don’t have to baby sit these applications: you basically set the parameters of resources you are comfortable with, and then SharePoint does the rest.IN CLOSING: We hope that you are able to see how SharePoint can be the used for your own internal proprietary innovations and not just in what it brings you out of the box. It is a great platform for end users because they are the center of your application, enabling them to work as they want to. Your developers are more productive because of the great tools and programmability capabilities in the platform, and because they will be using the same tools they are used to in Visual Studio. And finally, your operations team and IT Pros will be able to do their job and keep the platform up and working and have the flexibility to deploy the solutions in the model that is the most appropriate for the need.MORE INFORMATION: There is also more information available on the web. You can certainly find more at sharepoint.microsoft.com in the SHAREPOINT COMPOSITES section, with white papers on our platform, videos, and other useful links to SharePoint developer content, end user content, etc.
  • In many cases customers have web services that we need to integrate to. This is an advanced scenario but here are some screenshots that show the simplest scenario overall. Again, this will require WCF expertise.In this case, we have a service that does a simple “calculator.” you can think of services your company may already have like calculating shipping charges or something like that. With SharePoint, you can create a web part to provide users access to those web services.
  • We are moving now to the issues that matter to the operations teams (IT Pros) and they can be summarized in terms of maintaining control and flexibility of deployment.
  • Sandboxed Solutions help safe deployments of code solutions. They are basically running on a subset of the object model. Sandboxed Solutions help users upload code solutions to their sites, while helping admins retain control of the site. Admins only have to set policies once.
  • In SharePoint 2010 we also have a unified packaging format that helps across Visual Studio, SharePoint Designer and browser solutions. This facilitates upgrades.
  • Here is a subset of these partners. There is one for your need.
  • Here is your call to action. The main one is to involve your technical experts and managers to learn about the value of SharePoint for .net developers and identify new apps that can benefit from SP’s collaborative and composite capabilities.We have content specifically for IT Pros and for Developers.
  • Transcript

    • 1. SharePoint Composites
      Redefining Your Application Platform With SharePoint Composites
    • 2. Redefine your platform with capabilities that help you deliver solutions that are composite, people-centric and collaborative on a single platform that can be centrally managed
    • 3. Story of the software
      Some needs
      Small program
      More needs
      More functionality
      More needs
      More programs/ new functionalities
      Expectations
      Infrastructure Improvements
      Enhanced features
      Demands
      Complex software
      …..
      Security ?
      Information sanctity ?
      Reliability ?
      Optimization ?
      Identity ?
      …..
    • 4. Enterprise Software Hierarchy of Needs
      Sophistication
      !
      Data
      Automating Legacy
      Redundancy
    • 5. Problems are transforming one form to another ,
      but they are converging into “I.T”
      But better Governance can convert these converging
      problems to opportunity
    • 6. Microsoft SharePoint 2010TheBusiness Collaboration Platform for the Enterprise and the Internet
      Sites
      Deliver the Best Productivity Experience
      Communities
      Composites
      Cut Costs with a Unified Infrastructure
      Content
      Insights
      Rapidly Respond to Business Needs
      Search
    • 7. SharePoint as an Application PlatformWhat questions do we hear?
    • 8. SharePoint as an Application PlatformContent
    • 9. The actors
    • 10. Challenges of IT development organizationsMore demands, less resources
      Increasing demands on individual and organizational productivity
      IncreasingIT backlog of unmet needs
      Limited resources and funds for IT
      More difficult to improve businesssatisfaction
      Organization’s need for governance
    • 11. Tension between business and IT The paradox of empowerment vs. control
      How do we break this paradox?
      CONTROL
      Governance
      Management
      Centralization
      Consolidation
      Cost controls
      EMPOWERMENT
      Access
      Agility
      Adaptability
      Self-service
      Innovation
      2
    • 12. The “Value Gap”Impacting innovation and satisfaction on the business side
      The value traditionallyseen from infrastructure
      What is required by the business need
      Innovation
      Business value
      Differentiation
      Standardized activities
      Utility
      Non differentiating
      The value gap
    • 13. The different classes of solutions/processes Balancing innovation and mission criticality
      Types of business applications
      Core: Driving differentiation
      Innovative, proprietary I.P.
      Not “codified” initially
      Mission critical when it scales
      Context: Standard activities
      No longer differentiating activities
      “Packaged” (ERP)
      Still mission critical
      Just not differentiating
      Supports innovations
      Context
      Solution implementsnon differentiating activities
      Core
      Solution drives differentiation
      Custom Solution is Deployed at Scale
      “Packaged” or Out of the Boxstandard solution
      MissionCritical
      II
      III
      Innovation
      Solution is Outsourced
      Non MissionCritical
      IV
      I
      Source: “Dealing with Darwin: how great companies innovate at every phase of their evolutions,” by Geoffrey Moore
    • 14. SharePoint applicationsHow are they different from those built on alternative platforms?
    • 15. SharePoint CompositesDo-It-Yourself SharePoint solutions
      Empower business users with browser-based customizations
      Build declarative sophisticated solutions with SharePoint Designer
      Create human workflows and visualizations with Visio Services
      Share and publish databases with Access Services
      Rapidly create SharePoint solutions without code
      Leverage enterprise data through Business Connectivity Services
      Surface enterprise data in Outlook, Word, and Workspace
      Provide full read and writeaccess, offline or while connected
      Easily enable Search across these systems
      Unlock the value of your enterprise data
      Manage custom code with Sandboxed Solutions
      Manage desktop solutions with Visio, Forms and Access Services
      Maintain flexibility with deployment online or on premise
      Maintain operational insight with health monitoring
      Maintain control over end user solutions
    • 16. SharePoint applicationsLeveraging a rich set of building blocks across a broad set of scenarios
      Employee payroll portal
      Offline order entry
      Personal profile site
      Executive dashboard
      Job candidate applications
      .com site
      Conference planning
      Pricing analysis
      Insurance process
      Delivery scheduling
      Product catalog
      Compliance reviews
      Contract generation
      Expertise finder
      Sales reports
      IT service portal
      Request for proposals
      Human workflow
      LOBintegration
      Reportingand Analysis
      Documentprocessing
      SharePoint
      Portal Wikis Doc Sets BCS Forms Workflows KPIs People search Visio Services
      Web part framework Blogs Tags Doc ID SharePoint Designer Reporting Dashboards Access Services Enterprise search
      List relationships Web edit Managed taxonomy External lists
      Navigators Folksonomies Expertise Silverlight integration
      Excel Services Offline Tag cloud Metadata
      InfoPath web part Org chart browser BI slicers Conditional formatting
      Applicationexperience
      Web sites
    • 17. The application experience: “Work Areas” A standard yet configurable framework for your application
      Microsoft’s very own Autogroup
      (One strange experience)
      Standard or custom UX
      Usability vs. Uniqueness
      Personalized by user
      Right on the browser
      Rich building blocks
      You can create your own galleries of web parts
      It can surface in Office
    • 18. The application experience: “Work Areas” Leveraging users skills in Office tools: Visio and Access
      Access Services
      Visio Services
    • 19. Documents processingDocuments ARE part of the data model
      Expanding the notion of the data model to include unstructured content
      Samples capabilities
      Document Sets
      Records Management
      Metadata
      Retention policies
      Document generation
      Excel Services
      Word Automation Services
    • 20. LOB and external system integrationUnlocking the value of your enterprise data with Business Connectivity Services
      Traditional packaged or legacy solutions lack in user experience
      Derive more value from those investments
      Extend it to more users
      Put the rules in place, then let users “discover and use” the data
      Extend it to Office
    • 21. LOB and external system integrationUnlocking the value of your enterprise data with Business Connectivity Services
      My Artists
      Artist Tracker > Artists
      SharePoint Workspace with InfoPath Forms
      Artist
      Contracts
      Artist Name
      Address
      City
      State
      Artist Name:
      Mandible
      Outlook Forms andTask panes
      Deathrattle
      SharePoint lists
      Artists
      Concourse
      Jay Hamlin Trio
      Down on the Bayou
      Andrew Datars Quartet
      Agent:
      Concourse
      Stuck in the Mud
      Jay Hamlin Trio
      Tastes like chicken
      Down on the Bayou
      Mandible
      Concourse
      Search results
      Office Word
    • 22. Human workflowAutomate activities and tasks across people
      Leverage the knowledge of your business analysts
      Visio
      Collaborate with dev team
      Export to SharePoint
      Extend w/Visual Studio
      Levels of WF sophistication
      Out of the box
      Customized OOB
      Declarative custom
      Custom action
      Code-based custom
      BizTalk integration
      WF in Visual Studio
      Custom actions
      In SPD
      SharePoint Designerdeclarative workflows
      Custom OOB Workflows
      Out of the BoxWorkflows
      Visio processdiagrams
    • 23. Reporting and AnalysisEmpowering decision makers to create, access and share information
      The user drives the insights
      Access and Discoverability
      Self-service and Collaboration
      Forming insights
      App should empower users by exposing data
      Users form insights w/Excel
      Share with Excel Services
      Custom dashboards w/Visio
      Strategic scorecards with PPS
      Increasing level of sophistication
      Less “canned” reports, more dynamic and strategic insights
      PerformancePointServices
      Excel
      Excel Svcs
      Visio
      Charts and
      Web parts
    • 24. Web sitesCommunicating with the application’s internal and external stakeholders
      Most applications need some form of web publishing
      Even if not built on SharePoint
      Employees, Partners, Customers
      Leverage SharePoint’s authoring, publishing andreview process
      Theming, Web editing
      AJAX and Silverlight
      Rich media
      Publishing processes
      Hosted or On Premise
    • 25. Developer productivityPlatform services
      Productivity
      andPlatform services
    • 26. Transparent vs. OpaqueThe flexibility of the “escape option” to .NET
      Application
      Application
      “Opaque” platform
      SharePoint
      .NET
      ?
      Complexity of solution
      Complexity of solution
      An “opaque” platform
      A “transparent” platform
      “Hitting the wall”
      Complexity of problem
      Complexity of problem
    • 27. A sliding scale of solution sophisticationDifferent tools for different roles
      Highest sophistication
      Visual Studio
      SharePoint Designer
      Office
      Browser
      Larger team development
      ALM
      Enterprise application integration
      Across the firewall integration
      Web services and components
      Manageability
      Declarative integration to external data
      Relatively sophisticated workflows
      Rich forms-based applications
      Web design
      Some VS-based (WF activities, web parts)
      BU reporting, tracking Access DBs
      User customized sites
      Ad-hoc solutions
      Browser-based SharePoint data definition
      Using galleries of web parts
      Sophisticated enterprise applications
      Enable
      Declarativesolutions, some code
      Enable
      No-code solutions
      Highest empowerment
    • 28. Visual Studio 2010 Tools for SharePoint
    • 29. Modern User ExperienceDynamic, standard and multilingual end user experiences
      SILVERLIGHTEasier dynamic Silverlight experiences in SharePoint
      • Simplified upload of Silverlight packages
      • 30. Client Object Model in Silverlight
      • 31. Support for remotely hosting Silverlight apps
      XSLT ViewsStandard UX by default
      • Replaces CAML
      • 32. Improved performance
      • 33. Integration with SharePoint Designer
      • 34. Standard coding experience for developers
      STANDARDSBroad, accessible support for other browsers
      • Simplified CSS
      • 35. Improved standards support
      • 36. XHTML 1.1 Strict
      • 37. Browser support (Safari, Firefox)
      • 38. WCAG 2.0 AA Compliant (for people with disabilities)
      MULTILINGUAL UXMultiple language support of SP sites
    • Data FoundationA powerful yet easy to use data foundation for relational scenarios
      RELATIONSHIPSEasy to enforce referential integrity
      • Cascade, transactional deletion
      • 41. Prevents referential inconsistency from invalid deletions
      VALIDATIONData rules that are easy to enforce
      • Formula-based validation
      • 42. Enforces relational uniqueness
      • 43. Enforces required fields
    • Programmability EnhancementsImproving developer productivity through standards and familiar APIs
      SPLinqRelational, entity-based programming
      • List Joins based on lookup field
      • 44. Field Projections (molding data without retrieving every field)
      RESTSimple, web-based integration
      • Work with SP or XLS data via REST
      • 45. Integration across other technologies
      • 46. .Net Data Svcs Framework (“Astoria”)
      • 47. ASP.NET AJAX
      • 48. “Gemini” Integration
      • 49. Rich Excel access to charts, ranges
      from o in data.Orderswhere o.Customer.City.Name == "London“select o;
      http://.../REST/WL/.../model/charts(‘Chart1’)
      Client APIsPerformance conscious, unified OM
      • Unified OM:
      • 50. JavaScript, .NET, Silverlight
      • 51. Subset of Server OM
      • 52. Asynchronous batched commands
      • 53. Linq-based data retrieval
      WorkflowEnabling process-centric solutions on a powerful WF foundation
      • Focus on doc approval, review
      • 54. Rich client designer
      • 55. Site-scoped (from List scoped)
      • 56. Browser based visualization
      EventsImproved UX control through richer events set
      • After synch events
      • 57. Site scoped events
      • 58. Web and List creation
      • 59. Custom error pages
    • Microsoft SharePoint 2010 The business collaboration platform for the enterprise and the internet
      Connect and Empower People
      Browser
      Office Offline
      Mobile
      Your SharePoint solution across a variety of scenarios
      Cut costswith a unifiedinfrastructure
      Rapidly respond to business needs
      Application experiences
      Human
      workflow
      LOBintegration
      Documentprocessing
      ReportingandAnalysis
      Websites
      Browser
      Online or On Premise
      Shared Services
      Office
      SharePoint Out-of-the-Box Capabilities
      Sites
      Communities
      Content
      Search
      Insights
      Composites
      Sandbox Solutions
      SharePointDesigner
      Administration
      VisualStudio
      Key SharePoint Platform Services
      Application Model
      Programmability
      Security
      Packaging
      Manageability
      Interoperability
      Deployment
      The Microsoft Application Platform (SQL Server, Windows, .NET)
      Your enterprise LOB, external systems and cloud services
      Cloudservices
      ERP, CRM,BUIT applications
    • 60. Microsoft SharePoint 2010 The business collaboration platform for the enterprise and the internet
      Connect and Empower People
      Browser
      Office Offline
      Mobile
      Your SharePoint solution across a variety of scenarios
      Cut costswith a unifiedinfrastructure
      Rapidly respond to business needs
      Application experiences
      Human
      workflow
      LOBintegration
      Documentprocessing
      ReportingandAnalysis
      Websites
      Browser
      Online or On Premise
      SharePoint Out-of-the-Box Capabilities
      Shared Services
      Office
      Sites
      Portal Personalization Customization Web Parts
      Communities
      Wikis - Blogs - Tags My Sites - Ratings
      Content
      Doc Sets CompliancePolicies IRM
      Search
      People search Enterprise searchBI Search
      Insights
      KPIs
      Reporting Scorecards Dashboards
      Composites
      Business ConnectivityOffice UX - SilverlightForms - WorkflowVisio and Access Svcs
      Sandbox Solutions
      SharePointDesigner
      Key SharePoint Platform Services
      Administration
      Programmability
      Application Model
      Security
      Packaging
      VisualStudio
      Web UI Framework
      Content Types
      Lists and Libraries
      Server Object Model
      Client Object Models
      Claims
      Federation
      Unified Packaging
      Manageability
      Site / PageModel
      Forms and Workflow
      Searchframework
      Deployment
      Data APIs
      Events
      PowerShell
      Monitoring
      Templates
      Interoperability
      Backup and Recovery
      Features
      REST
      SOAP
      External data
      WSRP
      CMIS
      Configuration
      Upgrade
      Solutions
      The Microsoft Application Platform (SQL Server, Windows, .NET)
      Your enterprise LOB, external systems and cloud services
      Cloudservices
      ERP, CRM,BUIT applications
    • 61. Integrating services
    • 62. Integrating with WCF-based Services
      • Defining “complex” WCF service (s=a + b)
      • 63. Creating SP web part to use that service
      • 64. IW-based experience for site customization
    • This is our “complex” calculator service
    • 65. The rich set of SharePoint templates available in Visual Studio 2010
    • 66. This is our new SharePoint web part
    • 67. Our web part calling our service
    • 68. Inserting a Breakpoint for testing
    • 69. Easily deploying the web part to the SharePoint site
    • 70. An information worker just uses our web part
    • 71. Notice the ribbon in SharePoint 2010
    • 72. Inserting the web part
    • 73. Web Part Added to the site
    • 74. Using our web part
    • 75. ControlDeployment flexibility
      ControlandDeployment flexibility
    • 76. Sandboxed SolutionsFacilitating safe , easy deployment of code solutions, freeing IT admins from policing them
      User Empowerment
      Site control
      Self-managed
      solutions
      Full Trust SharePoint Solutions
      Enables users to upload code solutions to their sites
      Hosting
      scenarios
      SandboxedSolution
      Web Parts
      Event Receivers
      Feature Activation Callouts
      Workflow Actions
      InfoPath Forms
      Site and List Templates
      Implemented as a subset of the SharePoint Object Model
      Site collection administrators retain control
      Farm admin does not have to be involved once policies are defined
      Automatic monitoring and control of resource utilization
      Corporate Intranet
      SharePoint Online
      Office Live
    • 77. Enables roundtrip
      Simplifiedupgrades
      Discovery
      Unified Packaging FormatSimplified deployment and upgrades regardless of development model
      Unified Packaging Format
      Uniform packaging format across Visual Studio, SharePoint Designer, and browser
      Templates
      Declarative and visual upgrades
      Upgrade callouts for features
      Features
      Solutions
      Richer solution and feature discovery
    • 78. SharePoint ISV Partner Ecosystem
      Business Solutions
      Technology Solutions
      ECM
      Search
    • 79. Call to Action
      Involve your technical experts and IT managers to learn about the value of SharePoint for .NET developers and identify a new or existing application that can benefit from SharePoint collaborative and composite capabilities
    • 80. Questions?
    • 81. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
      The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESSED, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

    ×