Microsoft Portal Presentation 2009v1

269 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
269
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Microsoft Portal Presentation 2009v1

  1. 1. PORTAL DESIGN & CASE STUDY<br />1999 - 2009<br />
  2. 2. INFRASTRUCTURE DESIGN<br />Infrastructure is designed on the following criteria:<br /><ul><li> Project Scope (Internet facing? excel services?)
  3. 3. Budget
  4. 4. High Availability
  5. 5. Capacity Planning
  6. 6. Use of existing infrastructure
  7. 7. Information Architecture
  8. 8. Governance
  9. 9. Run the SharePoint Capacity Planning Tool</li></li></ul><li>INFRASTRUCTURE DESIGN <br />
  10. 10. CUSTOM DEVELOPMENT<br /><ul><li> Strong Microsoft Web Development team since 1999
  11. 11. ASP;
  12. 12. ASP.NET 1.0 – 3.5;
  13. 13. SQL Server 7.0 – 2008
  14. 14. Experienced in building custom web parts populated by Web Services, </li></ul> SharePoint lists and the SSP database<br /><ul><li> Custom Development is based on the following industry standards
  15. 15. Microsoft ASP.NET AJAX Controls
  16. 16. jQuery
  17. 17. W3C compliance
  18. 18. Developing with Telerik controls for over 2 years</li></li></ul><li>CUSTOM DEVELOPMENT:WEATHER<br />Current Weather web part<br /><ul><li> Weather details are retrieved via a web service
  19. 19. Details are in XML and is styled in XSLT
  20. 20. Configuration settings allow administrator to select different location </li></ul> and temperature unit (Fahrenheit or Celsius)<br /><ul><li> Web part is easily styled by designer by editing XSLT file (no need to </li></ul> edit code)<br />
  21. 21. CUSTOM DEVELOPMENT:MOST VIEWED<br />Most Viewed Pages Web Part<br /><ul><li>Data retrieved via SharePoint Usage Reports Data
  22. 22. Data is automatically managed via SP
  23. 23. No need for an additional database
  24. 24. Can display the number of times page was hit in the last predefined period (7 days, 1 month, 6 months, 1 year)
  25. 25. Web part is easily styled by designer via style sheets
  26. 26. Title of parent page is displayed for easier navigation
  27. 27. Data is updated once a day and stored in a SharePoint list</li></li></ul><li>CUSTOM DEVELOPMENT:TOP SEARCHES<br />Top Searches Web Part <br /><ul><li>Data retrieved via SharePoint Usage Reports Data
  28. 28. Data is automatically managed via SP
  29. 29. No need for an additional database
  30. 30. Web part displays the most frequently used key words when searching the website
  31. 31. Web part is easily styled by designer via style sheets
  32. 32. Web part takes you directly to search results page
  33. 33. Data is updated once a day and stored in a SharePoint list </li></li></ul><li>CUSTOM DEVELOPMENT:CHAT<br />Persistent Chat Web Part<br /><ul><li> Easier and quicker than using the discussion board
  34. 34. Chat is stored in a SharePoint list
  35. 35. Administrators can block users from contributing to the chat
  36. 36. Web part is easily styled via style sheets (no need to edit code)</li></li></ul><li>CUSTOM DEVELOPMENT:STOCK QUOTE<br />Stock Quote Web Part <br /><ul><li> Displays a graphical representation of Stock for predefined company
  37. 37. Data/images retrieved via MSN Money and stored in SharePoint list
  38. 38. Configuration settings allows SharePoint administrator to configure the Stock Quote code</li></li></ul><li>CUSTOM DEVELOPMENT:POLL<br />Poll Web Part<br /><ul><li> Provides an easier interface for a one question poll than surveys
  39. 39. Poll results are stored and managed in a SharePoint list
  40. 40. Response of old poll’s is archived for record purposes
  41. 41. Poll settings are configured directly from the web past display or SharePoint list</li></li></ul><li>STANDARD WEB PARTS<br />Strong design and configuration skills on standard SharePoint web parts<br />
  42. 42. PRODUCT ENHANCEMENTS<br />Product development and enhancements considerations<br /><ul><li> Easy to configure
  43. 43. Easy to style
  44. 44. Dependant on SharePoint lists and database
  45. 45. Based on Microsoft Standards and recommendations
  46. 46. Fantastic 40 templates
  47. 47. Open Source solutions from CodePlex
  48. 48. Enhanced by our development and design experience
  49. 49. Produce “SharePoint on Steroids” products </li></li></ul><li>PRODUCT ENHANCEMENTS<br />NEW<br />NEW<br />NEW<br />
  50. 50. THE END RESULT<br />SharePoint <br />On Steroids<br />
  51. 51. WORKFLOW<br />Built workflows to achieve the following goals<br /><ul><li>Automation
  52. 52. Automatically update leave calendar when leave is </li></ul> approved<br /><ul><li> Automatically create a discussion forum thread for a new document added to the document library
  53. 53. Approval
  54. 54. Approval required to publish content added or updated by content contributor
  55. 55. Notification
  56. 56. Administrators are notified of “Feedback” form submission
  57. 57. Group of users are notified via email when a new discussion thread or poll is created
  58. 58. Task delegation
  59. 59. Tasks assigned to predefined workers when a request form is submitted</li></li></ul><li>WORKFLOWCASE STUDY<br />Recruitment Workflow Process<br />
  60. 60. POST DEPLOYMENT<br />Post deployment include the following:<br /><ul><li> Skills Transfer
  61. 61. Custom built end user manuals
  62. 62. Custom built administrator manuals
  63. 63. Project specific training videos
  64. 64. Onsite training sessions to end users and administrators
  65. 65. Support
  66. 66. Source code and manuals available on CD
  67. 67. Quality checks performed by trained copy writer
  68. 68. General task assistance and troubleshooting
  69. 69. Change Management
  70. 70. Support include new development request
  71. 71. Change management is based on ...
  72. 72. feedback from end user and administrators
  73. 73. information received from usage reports
  74. 74. Streamlining analysis</li>

×