Feb 9th Presentation

613 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
613
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Feb 9th Presentation

    1. 1. Requirements Definition of the Geospatial Web - Continued ENVS 4522
    2. 2. House Keeping
    3. 3. Papers Are marked and available at the break. Second Assignment: Is due February 17th you can email it to me or provide me with a hard copy.
    4. 4. Course Outline Topics to complete:   Experience Design for the Geospatial web Changing role of Geospatial Information for Citizen Engagement Future of Geospatial Information Use   We need to have three more classes to cover these topics.
    5. 5. Course Dates: Feb 9th Feb 16th (Family Day)   Classes Finish Feb 20   Proposed Lecture Revisions:   Wednesday Feb 11th,  Friday Feb 13, Tuesday Feb 17th,  Wednesday Feb 18th
    6. 6. We can still do a group assignment.   Final Submission                      - March 3rd   Still worth 30%? For your assignment each member of your group will be tasked with a deliverable.  One person will develop documentation for the different Stages of the assignment which we will discuss today. Final Assignment
    7. 7. Final Assignment <ul><li>Will contain: </li></ul><ul><li>Table of Contents </li></ul><ul><li>Introduction: Summarizing which option you choose and a brief summary about your design appraoch </li></ul><ul><li>Methodology: Description of the documents you created to guide your design exercise. ie. personas, user flows, competitive review, heuristic evaluation etc. Each student is responsible for one deliverable.  </li></ul>
    8. 8. Final Assignment <ul><li>Will contain: </li></ul><ul><li>Phase 1 deliverables: Final documents used in the design exercise. This will include those things you described in the methodology. </li></ul><ul><li>Phase 2 deliverables: Illustrations of your final Wireframes with annotation describing your design approach based on your phase 1 work.  </li></ul><ul><li>Conclusion: Summary of benefits of your approach, challenges in the design process, and projected impact of your design implementation. </li></ul>
    9. 9. Recap Tools of the Geospatial Web
    10. 10. OpenLayers Google Maps API Mapserver Geoserver ESRI ArcIMS     Google Earth
    11. 11. 2 Kinds of maps Static maps Dynamic Maps
    12. 12. Recap Requirements definition of the geospatial web
    13. 14. Duality of Web Design Application Design Information Distribution and Retrieval Human Computer Interaction Information Architecture Interaction Design ? Knowledge Management
    14. 16. Exists in the Strategy and Scope Planes Stage 1: Requirements Definition
    15. 17. User Requirements Site Objective Content Requirements Functional Specifications Stage 1: Requirements Definition
    16. 18. Stage 1: Requirements Definition <ul><li>User needs are defined through: </li></ul><ul><li>  </li></ul><ul><ul><ul><li>Interviews </li></ul></ul></ul><ul><ul><ul><li>Surveys </li></ul></ul></ul><ul><ul><ul><li>Want & Needs Analysis </li></ul></ul></ul><ul><ul><ul><li>Goal/Task Analysis, propritization </li></ul></ul></ul><ul><ul><ul><li>Focus Groups </li></ul></ul></ul><ul><ul><ul><li>Field Studies </li></ul></ul></ul><ul><ul><ul><li>Persona & Scenario development </li></ul></ul></ul>
    17. 19. Stage 1: Requirements Definition <ul><li>User needs encompass: </li></ul><ul><li>  </li></ul><ul><ul><ul><li>Accessibility Issues </li></ul></ul></ul><ul><ul><ul><ul><li>Do your users have any disabilities? </li></ul></ul></ul></ul><ul><ul><ul><li>  Technology issues </li></ul></ul></ul><ul><ul><ul><ul><li>What browsers do they use? </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Do they use Javascript or Flash etc? </li></ul></ul></ul></ul><ul><ul><ul><ul><li>How savvy are they? </li></ul></ul></ul></ul><ul><ul><ul><li>Demographic </li></ul></ul></ul><ul><ul><ul><li>Defines User Groups </li></ul></ul></ul><ul><ul><ul><ul><li>Occasional users vs regular users </li></ul></ul></ul></ul><ul><ul><ul><ul><li>What are they going to use it for? </li></ul></ul></ul></ul>
    18. 20. Stage 1: Requirements Definition <ul><li>User Needs are Defined in Personas that can be used to inform the design </li></ul><ul><ul><li>User Personas are based directly on the quantitative and qualitative research to arrive at composites based on real customer attributes </li></ul></ul><ul><ul><li>Provide simple, clear aggregate profiles of target customer types </li></ul></ul><ul><ul><li>Focus around the goals and needs of the people who will interact with the end solution </li></ul></ul><ul><ul><li>Describes key goals, behaviours, motivators, and pain points </li></ul></ul>
    19. 24. Stage 1: Requirements Definition <ul><li>Personas can then be used to prioritize user tasks; </li></ul><ul><li>Example: Bill </li></ul><ul><li>  </li></ul><ul><li>Support </li></ul><ul><li>With limited experience with the markets, he decides to jump right in and make an options purchase. During the process, he comes across several terms that he is unfamiliar with. He needs to do more research and has noticed the contextual help for options trading. </li></ul>
    20. 25. Stage 1: Requirements Definition <ul><li>Site Objective: </li></ul><ul><li>Defines what you want the site to do and is defined through: </li></ul><ul><li>  </li></ul><ul><ul><li>Interviews </li></ul></ul><ul><ul><li>Site History </li></ul></ul><ul><ul><li>Business goals </li></ul></ul>
    21. 26. Stage 1: Requirements Definition <ul><li>Helps define the scope of the project. </li></ul><ul><li>What the project will develop the extent and level of detail. </li></ul><ul><li>Example: E-commerce site </li></ul><ul><li>The site allows users to purchase a product </li></ul><ul><li>  </li></ul><ul><li>Does it let the user save their account information, create a wish list, or post reviews? </li></ul>
    22. 27. Stage 1: Requirements Definition <ul><li>This is generally a written summary highlighting the requirement and goals of the project. </li></ul><ul><li>Site Requirements: </li></ul><ul><ul><li>The purpose of this project is to design an e-commerce site for the sale of sports equiptments </li></ul></ul><ul><ul><li>Customers can purchase several products at once using any major credit card </li></ul></ul><ul><ul><li>Users can create wish lists and save products for later use. </li></ul></ul><ul><ul><li>They can send these wish lists to other people via email. </li></ul></ul>
    23. 28. Stage 1: Requirements Definition <ul><li>Content Requirements: </li></ul><ul><li>Is a description of the various content elements needed for the site.  </li></ul><ul><li>This can include written content, illustrations, animations, geospatial data etc. </li></ul><ul><li>This information can be defined by the site objective and the user needs </li></ul>
    24. 29. Stage 1: Requirements Definition <ul><li>This is generally a written summary or matrix defining the content required for each page. </li></ul><ul><li>  </li></ul><ul><li>  </li></ul>
    25. 30. Stage 1: Requirements Definition <ul><li>Functional Requirements </li></ul><ul><li>Define what the does and how it does it.  </li></ul><ul><ul><li>This includes the technical requirements </li></ul></ul><ul><ul><ul><li>Does the site use AJAX? </li></ul></ul></ul><ul><ul><ul><li>What type of mapping system does it use and why? </li></ul></ul></ul><ul><ul><ul><li>Defines the user interactions. </li></ul></ul></ul><ul><li>  </li></ul><ul><li>Example: E-commerce </li></ul><ul><ul><li>If the site uses a wish list where does it live. How does the interaction work? </li></ul></ul>
    26. 31. Use cases <ul><ul><li>Describe how a particular user will perform a given task on your website </li></ul></ul><ul><ul><li>These are usually narrative in format and define through the story the steps a user must take to perform the task </li></ul></ul><ul><ul><li>Each use case captures </li></ul></ul><ul><ul><ul><li>The Actor (who is using the Website) </li></ul></ul></ul><ul><ul><ul><li>The Interaction (what the user does) </li></ul></ul></ul><ul><ul><ul><li>The Goal (the user’s purpose) </li></ul></ul></ul>
    27. 33. Stage 1: Requirements Definition <ul><li>These documents will then feed into the next stage of the design process and inform the structure and skeleton planes. </li></ul><ul><li>  </li></ul><ul><li>  </li></ul><ul><li>Next Class Stage 2: Experience Desgn for the geospatial web </li></ul><ul><li>  </li></ul><ul><ul><li>Structure Plane  </li></ul></ul><ul><ul><li>Skeleton Plane </li></ul></ul><ul><li>  </li></ul>
    28. 34. Stage 1: Requirements Definition <ul><li>For your assignment each member of your group will be tasked with a deliverable.  </li></ul><ul><li>One person will develop documentation for the different Stages of the assignment.  </li></ul><ul><li>Next Class Stage 2: Experience Desgn for the geospatial web </li></ul><ul><li>  </li></ul><ul><ul><li>Structure Plane  </li></ul></ul><ul><ul><li>Skeleton Plane </li></ul></ul>

    ×