Developing an Information Architecture IA 201
Mark Ferraz <ul><ul><li>SolutionsMark </li></ul></ul><ul><ul><li>Houston, TX </li></ul></ul><ul><ul><li>www.solutionsmark....
Session Discussion <ul><li>Why Information Architecture </li></ul><ul><li>Importance of Architecture Forethought </li></ul...
Why Information Architecture  <ul><li>GOALS </li></ul><ul><li>A centralized place for storing and locating data quickly in...
Work Towards a Shared Goal and Vision <ul><li>Alice: “Would you tell me please, which way I ought to go from here?”  </li>...
Best Practice <ul><li>Architecture Forethought: Do the necessary discovery and planning work needed to answer these questi...
“ Who” - Defining our Audience <ul><li>Not the “Audience” feature in Office SharePoint Server 2007  </li></ul><ul><li>An I...
“ What” – Activities & Capabilities Capability Information Objective Audience Publishing Others Need to See Wide Collabora...
“ Security” – Access & Permissions Web Application Http://<web-application.fabrikam.com/ Web Application Security Policy S...
Information Context
 
Key Stakeholders Type of Stakeholder Entity Roles/ Involvement <ul><ul><li>Project Sponsor(s) </li></ul></ul>Initiates, fu...
Gaining Quality Feedback Communication Team Facilitator Architecture/Design Team
Best Practice <ul><li>Involve stakeholders early and leverage good communication practices and tools in order to: </li></u...
Stakeholder Analysis Influence Impact Low High Low High Managed Relationship Informed Relationship Coordinated Relationshi...
Stakeholder Analysis Influence Impact Low High Low High Informed Relationship Very influential but low to moderate impact ...
Stakeholder Analysis Influence Impact Low High Low High Informed Relationship Coordinated Relationship Managed Relationshi...
Stakeholder Analysis Influence Impact Low High Low High Managed Relationship Coordinated Relationship Low to moderate infl...
Satisifiers : generates proportional satisfaction with the quality and quantity of what is delivered Requirements Classifi...
Managing Iterations using Kano Analysis Diagram Dissatisfiers Delighters Customer Satisfaction Customer Dissatisfaction Me...
Piloting Your Architecture  <ul><li>Test driving your design with focused group of stakeholders to validate your assumptio...
Best Practice <ul><li>Deliver meaningful, sustainable, and reusable business value by offering SharePoint as a Service: </...
 
Horizontal Capabilities & Vertical Segments Publishing Portal for Viewer Audience Collaboration  Records Management R & D ...
Going Vertical Publishing Capability Information Others Need To See Wide Audience Collaboration Capability Information Sha...
Best Practice <ul><li>Allow for the creation of a meaningful information context within your information architecture by u...
Architecture Building Blocks  <ul><li>Web Application </li></ul><ul><li>Defined within a Farm </li></ul><ul><li>Topmost ob...
Building Blocks Applied  Farm “ /” <Root> (Managed Path) “ /” <Root> (Managed Path) “ /depts/” (Managed Path) “ /sites/” (...
Example 1 Site l  Production Team:  Print Media List l  Document Library List: Proof Documents Item l  Document Content Ty...
Example 2 Site l  Department :  Wingtip Toys Marketing Site l  Project:  Summer Sales Boost List l  Document Library List:...
Example 3 Site l  Asset:  Press 201 List l  Document Library List:  Proof Documents Field l  Department:  Wingtip Toys Mar...
 
Thank you for attending! Please be sure to fill out your session evaluation!
Thank you for attending! Please be sure to fill out your session evaluation! <ul><li>Post conference DVD with all slide de...
Upcoming SlideShare
Loading in …5
×

Ferraz Ia252 Developing An Information Architecture

913 views
836 views

Published on

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
913
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
43
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • One of the most  fundamental design elements in a successful Office SharePoint Server 2007 implementation is the underlying Information Architecture. Information Architecture provides a common, well-understood framework for the arrangement of data. A well considered Information Architecture includes how data will be structured and divided, as well as presented to and navigated by users.
  • Ferraz Ia252 Developing An Information Architecture

    1. 1. Developing an Information Architecture IA 201
    2. 2. Mark Ferraz <ul><ul><li>SolutionsMark </li></ul></ul><ul><ul><li>Houston, TX </li></ul></ul><ul><ul><li>www.solutionsmark.com mark@solutionsmark.com </li></ul></ul><ul><ul><li>President, SolutionsMark. Mark is an Senior Information Architect and Developer specializing in Information Management, Collaboration Tools, and Knowledge Management systems for medium to large enterprises. Mark has over ten years of experience designing, managing, and implementing complex technology projects involving application implementation, supporting infrastructure, custom development, and integration. Most recently Mark has been working with the team at Chevron as the Technical Development Lead for one of the largest SharePoint deployments to date. </li></ul></ul>
    3. 3. Session Discussion <ul><li>Why Information Architecture </li></ul><ul><li>Importance of Architecture Forethought </li></ul><ul><li>Office SharePoint Server 2007 Capabilities </li></ul><ul><li>Identifying Opportunity </li></ul><ul><li>Going Vertical </li></ul><ul><li>SharePoint as a Service </li></ul><ul><li>Information Arrangement/Context </li></ul><ul><li>How to best combine the capabilities of SharePoint with the identified opportunities to create value and emergent capability within an organization </li></ul>
    4. 4. Why Information Architecture <ul><li>GOALS </li></ul><ul><li>A centralized place for storing and locating data quickly in a consistent, yet flexible user experience that is in alignment with the organizational goals. </li></ul><ul><li>To provide rich capabilities for working with and providing additional metadata for both internal as well as external content. </li></ul>A well considered Information Architecture is both essential for implementation success, as well as for the overall supportability and longevity of the system over time.
    5. 5. Work Towards a Shared Goal and Vision <ul><li>Alice: “Would you tell me please, which way I ought to go from here?” </li></ul><ul><li>Cat: “That depends a good deal on where you want to get to.” </li></ul><ul><li>Alice: “I don’t much care where …” </li></ul><ul><li>Cat: “Then it doesn’t matter which way you go.” </li></ul><ul><li>Alice in Wonderland by Lewis Carroll </li></ul>
    6. 6. Best Practice <ul><li>Architecture Forethought: Do the necessary discovery and planning work needed to answer these questions: </li></ul><ul><li>Who will be visiting a given site? </li></ul><ul><li>What will they be doing within the site? </li></ul><ul><li>What level of information security is necessary within the site? </li></ul>
    7. 7. “ Who” - Defining our Audience <ul><li>Not the “Audience” feature in Office SharePoint Server 2007 </li></ul><ul><li>An Identified Group of Users who visit the site </li></ul><ul><ul><li>Access to the site and it’s associated content </li></ul></ul>
    8. 8. “ What” – Activities & Capabilities Capability Information Objective Audience Publishing Others Need to See Wide Collaboration Shared Among The Team Member Records We Need To Keep Managed
    9. 9. “ Security” – Access & Permissions Web Application Http://<web-application.fabrikam.com/ Web Application Security Policy Site Collection / -or- /<Site Collection>/ Top Site Security Permissions Sub-Site /<Sub Site> Sub Site Security Permissions
    10. 10. Information Context
    11. 12. Key Stakeholders Type of Stakeholder Entity Roles/ Involvement <ul><ul><li>Project Sponsor(s) </li></ul></ul>Initiates, funds and approves the effort <ul><ul><li>Customer(s) (also known as business sponsors) </li></ul></ul>Takes receipt of the solution and expects to gain business value from the solution <ul><ul><li>User(s) </li></ul></ul>Interacts with the solution <ul><ul><li>Operations </li></ul></ul><ul><ul><li>Hosts the solution </li></ul></ul>
    12. 13. Gaining Quality Feedback Communication Team Facilitator Architecture/Design Team
    13. 14. Best Practice <ul><li>Involve stakeholders early and leverage good communication practices and tools in order to: </li></ul><ul><li>Collect good accurate, quality feedback from stakeholders through the creation and distribution of clear, concise and effective communication. </li></ul><ul><li>Collect feedback through: </li></ul><ul><ul><li>Survey </li></ul></ul><ul><ul><li>Interview </li></ul></ul><ul><ul><li>Joint Sessions </li></ul></ul>
    14. 15. Stakeholder Analysis Influence Impact Low High Low High Managed Relationship Informed Relationship Coordinated Relationship Source: Microsoft
    15. 16. Stakeholder Analysis Influence Impact Low High Low High Informed Relationship Very influential but low to moderate impact – keep apprised of project status but do not need to be closely managed Managed Relationship Coordinated Relationship Source: Microsoft
    16. 17. Stakeholder Analysis Influence Impact Low High Low High Informed Relationship Coordinated Relationship Managed Relationship Very influential with significant impact – relationship needs to be well managed Source: Microsoft
    17. 18. Stakeholder Analysis Influence Impact Low High Low High Managed Relationship Coordinated Relationship Low to moderate influence but significant impact – continually engage through out the lifecycle Informed Relationship Source: Microsoft
    18. 19. Satisifiers : generates proportional satisfaction with the quality and quantity of what is delivered Requirements Classification & Prioritization (Kano Analysis Diagram) Satisfiers Dissatisfiers Delighters Customer Satisfaction Customer Dissatisfaction Meets Expectations Misses Expectations Delighters: unanticipated requirements; presence generates significant satisfaction; absence is acceptable and therefore do not generate dissatisfaction Dissatisifiers : expected requirements; absence generates significant dissatisfaction; presence generates a diminishing dissatisfaction towards a neutral feeling Source: Microsoft
    19. 20. Managing Iterations using Kano Analysis Diagram Dissatisfiers Delighters Customer Satisfaction Customer Dissatisfaction Meets Expectations Misses Expectations Satisfiers Source: Microsoft Minimum Acceptance Level Iteration #3 Iteration #2 Iteration #1
    20. 21. Piloting Your Architecture <ul><li>Test driving your design with focused group of stakeholders to validate your assumptions </li></ul><ul><li>Expand activity if need to ensure acceptance </li></ul><ul><li>Re-evaluate and make changes/ enhancements to your design prior to going live </li></ul>
    21. 22. Best Practice <ul><li>Deliver meaningful, sustainable, and reusable business value by offering SharePoint as a Service: </li></ul><ul><li>Create a service offering platform on which usage specific solutions can be built. </li></ul><ul><li>Create service offerings that align vertically with activities of the business and encourage organizational capability. </li></ul><ul><li>Provide for the automated movement of content throughout it’s lifecycle. </li></ul>
    22. 24. Horizontal Capabilities & Vertical Segments Publishing Portal for Viewer Audience Collaboration Records Management R & D Engineering Design QA/QC
    23. 25. Going Vertical Publishing Capability Information Others Need To See Wide Audience Collaboration Capability Information Shared Among The Team Member Audience Publish Approved Content Retain Important Content Project Sites Department Sites Asset Sites Workflow Sites
    24. 26. Best Practice <ul><li>Allow for the creation of a meaningful information context within your information architecture by using a pluggable, building-blocks-based design approach that: </li></ul><ul><li>Allows for the significant diversity that can exist in highly distributed organizations or across business functions. </li></ul><ul><li>Provides any single group the ability to get started quickly and with minimal training. </li></ul><ul><li>Provides overall design consistency, while promoting the unique capabilities and work styles of any given workgroup. </li></ul><ul><li>Provides a contextually clear user experience, making it easy for users to understand the significance of a piece of information, as well as the context necessary to find or store information quickly, clearly, and easily. </li></ul>
    25. 27. Architecture Building Blocks <ul><li>Web Application </li></ul><ul><li>Defined within a Farm </li></ul><ul><li>Topmost object within the hierarchy and the native container of the topmost site collection </li></ul><ul><li>Representative of a specific Microsoft Internet Information Services (IIS) Web site, and defines a specific IIS application scope </li></ul><ul><li>Has no visual presentation within the user interface and it is in no way visually apparent to the end user </li></ul><ul><li>Can be extended into multiple zones </li></ul><ul><li>Zone </li></ul><ul><li>Defined within a Web Application </li></ul><ul><li>Allows users to access the same Web site through separate and independent URLs </li></ul><ul><li>Has its own load-balanced URL (protocol, host reader, and port) </li></ul><ul><li>Allows for many configurations (multiple authentication stores, caching scenarios, content databases, or custom HTTP modules) </li></ul><ul><li>Managed Path </li></ul><ul><li>Defined within a Web Application </li></ul><ul><li>Used to incorporate a second tier of top-level site collections </li></ul><ul><li>Implement either an explicit inclusion (allows you to assign an explicit URL that is appended to the path e.g. http://fabrikam.com/dept) </li></ul><ul><li>or a wildcard inclusion (automatically assigns a path name e.g. http://fabrikam.com/depts/) </li></ul><ul><li>Site Collections </li></ul><ul><li>Defined within a Managed Path </li></ul><ul><li>Are the native containers of Office SharePoint Server 2007 sites </li></ul><ul><li>Contain a single top-level site that in turn may contain any number of child sites </li></ul><ul><li>Enforce specific feature and security boundaries that cannot be inherited or discovered by a parent or child site collection </li></ul><ul><li>The top-level site collection in a Web application may contain site collections through the use of managed paths </li></ul><ul><li>Features that are bound within a site collection and cannot be shared include global navigation, branding, security groups, </li></ul><ul><li>content types, content sharing Web Parts, site aggregation Web Parts, usage reports, alert management and workflows </li></ul><ul><li>Sub-sites </li></ul><ul><li>Defined within a Site Collection </li></ul><ul><li>May share navigation between sites </li></ul><ul><li>May inherit permissions from parent sites </li></ul><ul><li>Allow for the sharing of lists between sites </li></ul><ul><li>Allow for the sharing of design elements (such as themes or styles) between sites </li></ul>
    26. 28. Building Blocks Applied Farm “ /” <Root> (Managed Path) “ /” <Root> (Managed Path) “ /depts/” (Managed Path) “ /sites/” (Managed Path) Corporate Portal (Site Collection) http://portal.fabrikam.com/ Sites, Settings, and Content Projects Portal (Site Collection) http://projects.fabrikam.com/ Sites, Settings, and Content Marketing Project 1(Site Collection) http://projects.fabrikam.com/sites/mrkt1 Sites, Settings, and Content IT Project 1(Site Collection) http://projects.fabrikam.com/sites/it1 Sites, Settings, and Content Finance Dept. (Site Collection) http://projects.fabrikam.com/depts/finance Sites, Settings, and Content Marketing Dept. (Site Collection) http://projects.fabrikam.com/depts/marketing Sites, Settings, and Content Sales Dept. (Site Collection) http://projects.fabrikam.com/depts/sales Sites, Settings, and Content Portals (Web Application) http://portal.fabrikam.com Project Sites (Web Application) http://projects.fabrikam.com
    27. 29. Example 1 Site l Production Team: Print Media List l Document Library List: Proof Documents Item l Document Content Type: Wiget 101 Print Ad.doc Field l Project: Summer Sales Boost Field l Status : Pending Review Field I Creative Team : Graphic Design Field l Asset: Press 201 Site l Department : Wingtip Toys Marketing
    28. 30. Example 2 Site l Department : Wingtip Toys Marketing Site l Project: Summer Sales Boost List l Document Library List: Proof Documents Field l Stats: Summer Sales Boost Field l Production Team: Pending Review Field I Creative Team: Graphic Design Field l Asset: Press 201 Item l Document Content Type: Wiget 101 Print Ad.doc
    29. 31. Example 3 Site l Asset: Press 201 List l Document Library List: Proof Documents Field l Department: Wingtip Toys Marketing Field l Project: Summer Sales Boost Field I Creative Team: Graphic Design Field l Status: Pending Review Site l Production Team : PrintMedia Item l Document Content Type: Wiget 101 Print Ad.doc
    30. 33. Thank you for attending! Please be sure to fill out your session evaluation!
    31. 34. Thank you for attending! Please be sure to fill out your session evaluation! <ul><li>Post conference DVD with all slide decks </li></ul>Sponsored by

    ×