Contextual Considerations: Logical Architecture And Taxonomy


Published on

SharePoint adoption tends to be viral in most organizations, growing faster than IT groups are able to able handle. Most organizations work toward quick user adoption. Only a handful properly assess what their true vision for SharePoint is within their organization, building their physical architecture without having a logical architecture or core taxonomy in place.
In this session we will cover the basics of core design requirements, how they affect logical architecture design and taxonomies, and in turn how best to utilize the equipment available to the IT organization.

Published in: Technology, Education
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Contextual Considerations: Logical Architecture And Taxonomy

  1. 1. Contextual Considerations: Logical Architecture and Taxonomy SharePoint Saturday – Boston 14 March 2009 Dan Usher
  2. 2. Agenda <ul><li>Introduction </li></ul><ul><li>Logical Architecture </li></ul><ul><li>Taxonomy </li></ul><ul><li>Project Planning </li></ul><ul><li>Technical Requirements </li></ul><ul><li>Scenarios </li></ul><ul><li>Conclusion </li></ul>
  3. 3. Introduction <ul><li>Who am I? </li></ul><ul><li>What environments have I worked in? </li></ul><ul><li>What have I seen? </li></ul><ul><li>What is this talk about? </li></ul>
  4. 4. How about you all? <ul><li>How many Solutions Designers do we have in the room? </li></ul><ul><li>How many Developers? </li></ul><ul><li>How many SharePoint Infrastructure Engineers and Architects? </li></ul><ul><li>How many Project Managers that are looking to get a better idea of taxonomy and architecture? </li></ul>
  5. 5. What's your system's vision?
  6. 6. Stepping into Contextual Design… <ul><li>Considerations, Tradeoffs and Compromises to meet the Context </li></ul><ul><li>Assessing the context… </li></ul><ul><ul><li>Are you building into the cloud? </li></ul></ul><ul><li>Always consider the context… </li></ul>
  7. 7. What’s a vision in look like? <ul><li>What’s the context of your use for SharePoint? </li></ul><ul><li>Do you need to be able to roll up data? </li></ul><ul><li>Re-utilize SharePoint groups </li></ul><ul><li>Workflow tools? </li></ul><ul><li>Consider the context of your environment and requirements </li></ul>
  8. 8. Do you feel like it’s like this?
  9. 9. Agenda <ul><li>Introduction </li></ul><ul><li>Logical Architecture </li></ul><ul><li>Taxonomy </li></ul><ul><li>Project Planning </li></ul><ul><li>Technical Requirements </li></ul><ul><li>Scenarios </li></ul><ul><li>Conclusion </li></ul>
  10. 10. Logical Architecture <ul><li>What defines a logical architecture? </li></ul><ul><li>Why is a logical architecture important? </li></ul><ul><li>How can you really make use of a logical architecture? </li></ul><ul><li>What does a logical architecture consist of and look like? </li></ul>
  11. 11. What makes up a logical architecture?
  12. 12. Reference: Windows SharePoint Services Example
  13. 13. Reference: Microsoft Office SharePoint Server 2007 Logical Architecture Example
  14. 14. How is your logical architecture affected by your requirements? <ul><li>Extranet </li></ul><ul><li>Public Facing Website </li></ul><ul><li>Permissions models </li></ul><ul><li>Authentication Schemes </li></ul><ul><li>Interoperability with other applications </li></ul>
  15. 15. Agenda <ul><li>Introduction </li></ul><ul><li>Logical Architectures </li></ul><ul><li>Taxonomy </li></ul><ul><li>Project Planning </li></ul><ul><li>Technical Requirements </li></ul><ul><li>Scenarios </li></ul><ul><li>Conclusion </li></ul>
  16. 16. What is a taxonomy? <ul><li>Taxonomy is the science (and art) of classifying a broad range of things. Originally used to classify plants and animals – phylum, genus, species, etc. – taxonomy is now applied to everything from product inventory to web sites. </li></ul>Reference:
  17. 17. What is a site taxonomy? <ul><li>SharePoint Farms </li></ul><ul><ul><li>Web Applications </li></ul></ul><ul><ul><ul><li>Collections of Site Collections </li></ul></ul></ul><ul><ul><ul><ul><li>Collections of Sites </li></ul></ul></ul></ul><ul><ul><li>Managed Paths </li></ul></ul><ul><ul><li>Nesting Paths </li></ul></ul><ul><ul><li>Reflection of the Organization </li></ul></ul><ul><ul><li>Requires out of the box thinking </li></ul></ul>
  18. 18. What are the components of Taxonomy?
  19. 19. But do I really need a taxonomy? <ul><li>Why not just deposit everything in a single document library? </li></ul><ul><li>Why not just use search for everything? </li></ul>
  20. 20. What about permissions? <ul><li>Inheritance and Breaking it… </li></ul><ul><ul><li>… and re-inheriting it </li></ul></ul><ul><li>SharePoint Groups </li></ul><ul><li>AD / LDAP Groups </li></ul><ul><li>Single Users </li></ul>
  21. 21. Taxonomy & Logical Architecture – What’s the Bridge? <ul><li>Site collections bridge logical architecture and information architecture. The design goals for site collections in the model are to satisfy requirements for URL design and to create logical divisions of content.* </li></ul>Reference:
  22. 22. Agenda <ul><li>Introduction </li></ul><ul><li>Logical Architectures </li></ul><ul><li>Taxonomy </li></ul><ul><li>Project Planning </li></ul><ul><li>Technical Requirements </li></ul><ul><li>Scenarios </li></ul><ul><li>Conclusion </li></ul>
  23. 23. Project Plans <ul><li>How does a project plan fit into logical architectures and taxonomies? </li></ul><ul><li>Or rather… </li></ul><ul><li>How does a logical architecture and taxonomy fit into a project plan…  </li></ul>
  24. 24. Project Plans <ul><li>Microsoft has a project plan for planning… </li></ul>
  25. 25. Agenda <ul><li>Introduction </li></ul><ul><li>Logical Architectures </li></ul><ul><li>Taxonomy </li></ul><ul><li>Project Planning </li></ul><ul><li>Technical Requirements </li></ul><ul><li>Scenarios </li></ul><ul><li>Conclusion </li></ul>
  26. 26. Technical Requirement Considerations <ul><li>What will the system do? </li></ul><ul><ul><li>Collaboration? </li></ul></ul><ul><ul><li>Publishing? </li></ul></ul><ul><ul><li>Development Platform? </li></ul></ul><ul><li>How big will the system be? </li></ul><ul><li>How will it be accessed? </li></ul><ul><li>What will be the level of usage? </li></ul><ul><li>Are we dealing with a cross domain solution? </li></ul><ul><li>SQL Mirroring or Clustering? </li></ul>
  27. 27. What are your limitations technically? <ul><li>Surrounding Infrastructure </li></ul><ul><li>System Memory </li></ul><ul><li>IIS - Number of Web Applications </li></ul><ul><li>Number of sites / site collections </li></ul><ul><li>DNS </li></ul><ul><li>Authentication Methods </li></ul><ul><li>PKI / SSL / Wildcard Certificates </li></ul><ul><li>Network Interfaces / IP Addresses </li></ul><ul><li>Storage </li></ul>
  28. 28. Agenda <ul><li>Introduction </li></ul><ul><li>Logical Architectures </li></ul><ul><li>Taxonomy </li></ul><ul><li>Project Planning </li></ul><ul><li>Technical Requirements </li></ul><ul><li>Scenarios </li></ul><ul><li>Conclusion </li></ul>
  29. 29. Scenario 1 - Requirements <ul><ul><li>Small Organization (250-300) </li></ul></ul><ul><ul><li>Document Management </li></ul></ul><ul><ul><li>Collaboration </li></ul></ul><ul><ul><li>Federation </li></ul></ul><ul><ul><li>Low Budget </li></ul></ul><ul><ul><li>Information Rollups </li></ul></ul>
  30. 30. Scenario 1 – Considerations <ul><li>May reflect an organization’s natural divisions </li></ul><ul><li>Rolls up information easily </li></ul><ul><li>Works well with small numbers of users </li></ul><ul><li>Out of the box method… </li></ul><ul><li>Pushes down Site Columns </li></ul><ul><li>Reutilizes Content Types </li></ul>
  31. 31. Scenario 1 – Potential Solution
  32. 32. Pirate Nosh Taxonomy Example
  33. 33. Pirate Nosh Logical Architecture Example
  34. 34. Pirate Nosh – Example Physical Architecture
  35. 35. Scenario 2 Requirements <ul><ul><li>Collaboration </li></ul></ul><ul><ul><li>Document Management </li></ul></ul><ul><ul><li>Workflow </li></ul></ul><ul><ul><li>Records Management </li></ul></ul><ul><ul><li>Large User base - 100k users </li></ul></ul>
  36. 36. Scenario 2 Requirements – But wait there’s more… <ul><ul><li>Complex Permissions </li></ul></ul><ul><ul><li>Extranet Access </li></ul></ul><ul><ul><li>Smartcard Authentication </li></ul></ul><ul><ul><li>High Availability </li></ul></ul><ul><ul><li>Integrity of Data </li></ul></ul><ul><ul><li>AD Infrastructure - Security Groups </li></ul></ul>
  37. 37. Scenario 2 – Potential Solutions
  38. 38. Scenario 2 - Potential Solutions
  39. 39. Scenario 2 - Considerations <ul><li>Typically doesn’t get planned overnight </li></ul><ul><li>May or may not reflect what an organization actually looks like </li></ul><ul><li>Best to plan it out with time </li></ul><ul><li>Discover what is out there… </li></ul>
  40. 40. Binary Brewery Logical Architecture Example
  41. 41. Binary Brewery Taxonomy Example
  42. 42. Binary Brewery Physical Architecture Example
  43. 43. Agenda <ul><li>Introduction </li></ul><ul><li>Logical Architectures </li></ul><ul><li>Taxonomy </li></ul><ul><li>Project Planning </li></ul><ul><li>Technical Requirements </li></ul><ul><li>Scenarios </li></ul><ul><li>Conclusion </li></ul>
  44. 44. Conclusion I <ul><li>Each project requires that you examine the contextual considerations of the environment and vision that you are working toward to accomplish with successful effectiveness. </li></ul>
  45. 45. Conclusion II <ul><li>Your requirements drive your taxonomy and logical architecture... </li></ul><ul><li>Which in turn drive your hardware requirements... </li></ul><ul><li>If you don't know what you're going to use SharePoint for, start off small and scale your farm up as you go... </li></ul><ul><li>Crawl… Walk… Run… </li></ul>
  46. 46. Conclusion III <ul><li>What you start with on Day One isn’t what you’re going to end up with in… </li></ul><ul><ul><li>Six months… </li></ul></ul><ul><ul><li>A year… </li></ul></ul><ul><ul><li>Day 472… </li></ul></ul>Remain Flexible !!!
  47. 47. Conclusion IV <ul><li>User adoption in and of itself will cause your environment to change… </li></ul><ul><li>… adapt to the context as it changes. </li></ul>
  48. 48. And that’s a wrap… <ul><li>Follow me on Twitter – </li></ul><ul><li>Follow my blog – </li></ul><ul><li>IM? </li></ul><ul><ul><li>gTalk danusher79 </li></ul></ul><ul><ul><li>Live [email_address] </li></ul></ul><ul><li>E-mail: [email_address] </li></ul>