When to Develop on a Platform (IndyTechFest 2008)
1 like690 views
The document discusses when to develop on the SharePoint platform, highlighting its evolution, capabilities, and advantages in various scenarios such as composite applications, business process management, and user personalization. It emphasizes the importance of planning, extending out-of-the-box features, and integrating with other systems while considering organizational needs and developer resources. Additionally, it notes the increasing prevalence and job opportunities related to SharePoint in the market.
![When you want to offset the cost of developmentMore time spent in the planning and design stages should surface more out-of-the-box features [that should save time later]Out-of-the-box features should reduce the cost of custom software developmentDeveloper focus should shift immediately to the business needs and extending the out-of-the-box features](https://image.slidesharecdn.com/itf2008sharepointplatform-100727113300-phpapp01/85/When-to-Develop-on-a-Platform-IndyTechFest-2008-15-320.jpg)
When to Develop on a Platform (IndyTechFest 2008)
- 1. SharePoint: When to Develop on a PlatformRob Wilson, MCTS SharePoint & Project 2007rwilson@kellerschroeder.comhttp://sharepointblog.kellerschroeder.comtwitter.com/theRobManDotNet
- 2. AgendaEvolution of a platformThe SharePoint PropositionWhen to develop on SharePoint
- 3. Ode to Young CoderThere once was an eager lad coderA small planet perched on his shouldersNo build versus buyIt was build every timeA practice that left a foul odor<-Young developer<-Big Head<-Only his code would do<-That really stunk!
- 4. Those Were the DaysWatch me code!
- 5. How They Stack UpPlatformBusiness AppsMuch Other StuffRADCustom CodeMVC FrameworkSEO FriendlyBusiness AppsBusiness AppsStandards-BasedSearchRADSeparation of RolesError HandlingSEO FriendlyUniformityStandards-BasedSearchContent ManagementSeparation of RolesAdministration AreaContent ManagementAdministration AreaUniformity Error HandlingError HandlingMenusMenusMenus (Menu Control)AuthorizationAuthorizationAuthorizationAuthenticationAuthenticationAuthentication
- 6. Toughest JobsDefining SharePoint in a single sentenceComparing SharePoint tocompetitive platforms
- 7. When the requirements call for itNot a brochure siteAuthentication and search requiredDoes not have to be a large-scale project
- 8. When you need self-serviceWeb Parts (re-usability)AlertsRSSRecycle BinMy SiteConnecting with peersPublishing
- 9. When you need personalizationFrom a webmaster’s perspectiveTargeted contentFrom a visitor’s perspectiveAbility to customize look and feel
- 10. When you need workflowBased on Workflow FoundationAdditional featuresSharePoint front-endDocument libraries and task listsWorkflow history lists
- 11. When you want flexible development optionsWeb PartsObject modelWeb servicesSeparation of development rolesGUI expert, workflow developer, reports and queries, event handlersVarying levels of experience on a project team
- 12. When you want to focus on the business requirements instead of the frameworkDo not worry about how someone will find your application or how it integrates with the security modelEliminate the headache of external content repositories
- 13. When you want consistency in your organization or client-baseCommon user interfaceVocabularyStandardized code base
- 14. When you want to take advantage of the inherent features of that platformCollaborationPortalContent ManagementSearchBusiness IntelligenceForms and Business Processes
- 15. When you want to offset the cost of developmentMore time spent in the planning and design stages should surface more out-of-the-box features [that should save time later]Out-of-the-box features should reduce the cost of custom software developmentDeveloper focus should shift immediately to the business needs and extending the out-of-the-box features
- 16. When you need SOAWeb services expose SharePoint contentSharePoint as a SOA consumer provides the user interface via XML and page viewer web parts – IntranetJournal.com, March 2006, Rob Bogue
- 17. When you need composite applicationsDashboards, Mash-upsBusiness Data CatalogAll levels of your organization
- 18. When you need composite applicationsERPBefore SharePointCRMLegacy SystemsMiddleware
- 19. When you need composite applicationsERPSharePointCRMLegacy Systems
- 20. When you need Single Sign OnMultiple built-in authentication optionsSupport for third-party authentication providersBuilt-in SSO providerManages credentials for other apps on your intranet
- 21. When you need off-line support of your dataOffice IntegrationImporting/exporting lists from/to excelLinked tables with AccessCalendar/Task List integration with OutlookGroove/SharePoint Workspace
- 22. When you need auditing and retention policiesLog just the events you need for what lists are of interest to youDevelop auditing reports using SSRSDevelop/customize workflows for content retention and disposal
- 23. When you need to equip your power usersSharePoint DesignerCustom queries with Data View Web PartSimple workflowsInfoPathSimple forms – really!
- 24. When your culture allows for itUser acceptance is keyLarge implementations are going to take a team of both IT and line of business usersMay require a paradigm shiftSmall, quick wins where possible
- 25. When a development community is important to youBlogs and forumsCommunity video tutorialsUser GroupsCodePlexCommercial/Open Source Features and Web Parts
- 26. When you are ready to stop dating around and marry the right platformUp to 92% satisfaction rating in the categories of functionality, end user experience, total cost of ownership and end user acceptanceUp to 59% of all companies are projected to have SharePoint or an equivalent platform by the end of this year and that number is projected to increase 19% between 2009 and 2011
- 27. When you want to build your resumeDice.com: 2,800 jobs (JUL 2010)Monster.com: 1,000+ jobs (JUL 2010)HotJobs.com: ~500 jobs (JUL 2010)
- 28. AlternativesFree BulletinBoardFree Blog HostJavaScript Menu BuilderEmbedded Google CalendarSpam-friendly form submission scriptsCoffee Cup Editor for CMS
- 29. Ode to Wise CoderThere once was an eager lad coderWho grew wiser as he grew olderThe greyer his hairThe more he did ShareAnd now this presentation is over
Editor's Notes
- #5: It’s a trapMost people write code because it is easier to write your own than it is to follow someone else’sYou will price yourself out of a jobTrust others
- #6: In the beginning there was custom code. Every new project started out the same way.I am a firm believer in frameworksPlatform is a framework on steroids….we’ll talk about the Much Other Stuff
- #7: This is the guy at Microsoft they told to come up with a one sentence summary of SharePoint for the product page.Trying to define SharePoint in a simple sentence is all but impossible….completely impossible if you want to do it justice.An integrated, information management platform.So if you talk to other people about how they’re using it, you get even more confused. Some are using it to replace Lotus Notes or IBM Workplace. Others are replacing Documentum or ECM LiveLink or Interwoven. Some are using it in place of Google’s enterprise search. I would personally describe is a platform with some built-in collaboration features. If you don’t include the word platform in the definition, then you’re missing a big part of the picture.CMSWatch.com’s SharePoint Report said “SharePoint is truly a collection of individual components that interact together to varying degrees, but require extra work to weld into a cohesive package.”
- #8: If it is just a 5-page brochure site with static text, SharePoint may not be for you.If it is simply a CMS solution for a public-facing web site, DNN may be a better toolSharepoint scalesSome people adopt it just because of the authentication integration with AD and security trimmingSome got it in the door through a requirement for a blogOthers just needed a simple workflow application over documents in a library
- #9: Compare to facebook apps, iGoogle gadgets, Vista gadgets
- #10: Key factor in user adoption and acceptance!
- #14: One partner said if his client won’t use SharePoint for a web project, he walks away…..that’s hard coreSame vocabulary
- #15: Collaboration – Blogs, wikis, discussions, check-in/check-out
- #18: Centralized knowledge managementTargetable to all levels of your organization
- #19: EAI - Popular at the turn of the millennium, but on the decline with the advent of SOAData is shared between the disparate systems…sometimes creating redundancy and latency….multiple versions of the truth…Which system is the system of record?
- #20: With SharePoint you get a service-oriented architecture and connectors via the Business Data CatalogYou end up with a single version of the truth and one portal to go to for all of your data mining
- #24: DV web part – put a plug for Vanessa’s sessionInfopath – story of SSG
- #26: Compare to BlackBerry, Windows Mobile or iPhoneCompare to facebook or twitter
- #27: Stats above from Info-Tech.com survey of 258 companies who are already using sharepointFrom CMSWatch.com 2008 SharePoint ReportAt the Microsoft-sponsored SharePoint Conference 2008, Bill Gates shared that Microsoft hadlicensed more than 100 Million seats to the platform and generated more than $US 1 Billionfrom that. To be sure, many of those seats fall under enterprise license agreements and may notreflect actual usage, but even if a fraction of those users actually logs into SharePoint each day,clearly it makes for the most significant – and fastest growing – information platform on themarket today.
- #29: Before frameworks and platforms, there was custom code. Every new project started out the same way.