The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #10 BOO! BOO!

Slides:



Advertisements
Similar presentations
Structured Design The Structured Design Approach (also called Layered Approach) focuses on the conceptual and physical level. As discussed earlier: Conceptual.
Advertisements

Chapter 11 Designing the User Interface
Chapter 19 Design Model for WebApps
Practical Business Modeling in the Unified Process Tom Morgan Software Architect, Fidelity National Information Services
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 7: teams present research plan + a sequence diagram from phase 2 homework; Affinity.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #21.
Technical Writing II Acknowledgement: –This lecture notes are based on many on-line documents. –I would like to thank these authors who make the documents.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #18.
Midterm Exam Review IS 485, Professor Matt Thatcher.
Term Project User Interface Specifications in a Usability Engineering Course: Challenges and Suggestions Laura Leventhal Julie Barnes Joe Chao Bowling.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #3.
Mid-Term Exam Review IS 485, Professor Matt Thatcher.
Web Design cs414 spring Announcements Project status due Friday (submit pdf)
Chapter 13: Designing the User Interface
Remedy, a BMC Software company Storyboarding the User Interface: Blueprint for an Application Shanaz Kanga | Michele Sarko Sr. UI Design Engineer | Manager,
Why planning? In order to make a successful project good communication is key! The process of planning and designing a project involves many people from.
DESIGN PROCESS. DESIGN Every design starts from research and early concept.
Systems Analysis and Design in a Changing World, 6th Edition
Chapter 7 Requirement Modeling : Flow, Behaviour, Patterns And WebApps.
INFORMATION X INFO415: Systems Analysis Systems Analysis Project Deliverable 3 Requirements Models.
Model the User Experience Today:  Detail some Use Cases  Develop a storyboard of the use cases  Sketch mock-ups of the use case's information requirements.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Information Architecture The science of figuring out what you want your Web site to do and then constructing a blueprint before you dive in and put the.
Chapter 8: Actor-System Interaction Modeling
Interaction Modeling Interaction model describes how objects interact to produce useful results. Interactions can be modeled at different levels of abstraction:
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
Software Architecture and Design Dr. Aldo Dagnino ABB, Inc. US Corporate Research Center October 23 rd, 2003.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Object-Oriented Analysis and Design Fall 2009.
User Interface Design & Usability for the Web Card Sorting You should now have a basic idea as to content requirements, functional requirements and user.
User Interfaces 4 BTECH: IT WIKI PAGE:
1 Version /05/2004 © 2004 Robert Oshana Requirements Engineering Use cases.
University of Washington HCDE 518 & INDE 545 Sketching HCDE 518 & INDE 545 Winter 2012 With credit to Jake Wobbrock, Dave Hendry, Andy Ko, Jennifer Turns,
Information Architecture & Design Week 3 Schedule -Syllabus Updates -Group Project Deliverables -IA Methodologies -Research Topic Presentations.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #16.
Digital Libraries Lillian N. Cassel Spring A digital library An informal definition of a digital library is a managed collection of information,
SBD: Information Design
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #14.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #15.
Information Architecture
School of Information, Fall 2007 University of Texas A. Fleming Seay Information Architecture Class Four.
CS223: Software Engineering
Information Design Goal: identify methods for representing and arranging the objects and actions possible in a system in a way that facilitates perception.
Chapter 7 Part II Structuring System Process Requirements MIS 215 System Analysis and Design.
Learning Aim B.  It is a good idea to think carefully about the design of a website before you try to implement it.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #13.
Designing User Experience (UX) This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.Creative Commons.
Day 4 – Process Modeling cont’d Today’s Goals  More on Process Models  Leveling DFDs  Exercise 5 – in class  Group Project / Client Project reminders.
University of Washington HCDE 418 Storyboarding HCDE 418 Winter 2014.
Activity Design Goal: work from problems and opportunities of problem domain to envision new activities.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #20.
© 2011 DigitalDay | MOBILE WEB INFORMATION ARCHITECTURE Best Practices Workshop 1.
Module: Software Engineering of Web Applications Dr. Samer Odeh Hanna 1.
The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #11.
Information Architecture & Design Week 3 Schedule -Syllabus Updates -Group Project Finalized -Research Presentations Finalized -IA Methodologies -Class.
User-Centered Design Services for MSU Web Teams Sarah J. Swierenga, Director Usability & Accessibility Center MSU Webmasters 402 Computer Center February.
Elaboration popo.
Object-Oriented Analysis and Design
Information System Design Info-440
Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN
Week 10: Object Modeling (1)Use Case Model
Information System Design Info-440
Informatics 121 Software Design I
Information System Design Info-440
Information System Design Info-440
Website Planning EIT, Author Gay Robertson, 2018.
Phases of Designing a Website
Information System Design Info-440
Presentation transcript:

The Information School of the University of Washington Information System Design Info-440 Autumn 2002 Session #10 BOO! BOO!

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 2 Agenda Admin/review Conceptual modeling –Discussion of exercises Site maps –Describing information architecture & flow Break Assignment #2 –Return and discussion

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 3 Admin Announcements –Anyone? Interactive design project –See Acer Tablet computer at: –Questions? Upcoming –Quiz #2: Nov 6 th [covers weeks: 3-5] –Design Exercise #3: Nov 13 th

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 4 Last time Conceptual modeling Metaphors

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 5 Metaphors Metaphors are persuasive in technology Consider online shopping –Product catalog –Shopping cart (some cards are abandoned) –Checkout process Metaphors give users a base conceptual model to extend BUT metaphors can be limiting –You can leave notes behind at Amazon but not at Barnes & Noble

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 6 Metaphors in design Use metaphors to brainstorm about design For example, in Jill’s picture scenario –Matching is like ….. –History is like … –Environment is like … –Change is like … In your systems, use metaphors to explain abstract concepts

The Information School of the University of Washington Conceptual modeling: Discussion of examples

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 8 Examine problem Scenario Tasks analysis Initial ideas

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 9 Begin with a very simple idea

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 10 … and then start refining it Place Photograph

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 11 Brainstorm: UI elements, entities, goals Map Timeline User goals

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 12 Invent new scenario but avoid details New scenario New Entities

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 13 Start simple Feels like a task analysis High-level entities

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 14 Elaborated… Focuses on entities Internal vs. external

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 15 Sketch first, model second Root of tree Sub-topics Sketch schematic

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 16 Observations The problem statements are vague –Therefore: Refine the problem on your terms The objective is ill-defined –Therefore: Decide on an target end-state You lack information –Therefore: Make assumptions

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 17 Problem-solving guidelines Move from the users’ perspective –First: Task analysis or metaphors –Then: conceptual model Move from the system’s perspective (be *very* careful) –First: What’s the database look like –Then: conceptual model Sketch the user interface then –Identify entities, relationships, attributes

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 18 Problem-solving guidelines Explore by trial and error –Its okay if it feels wrong at first Iterate –Try again Brainstorm –Free associate synonymous words –Use metaphors –Examine similar systems

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 19 Problem-solving guidelines Get feedback from others –Talk it through with a colleague Look for simple problems –Reuse elements from existing conceptual models Avoid premature details –Event higher-level abstractions

The Information School of the University of Washington Site Architecture Blueprints

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 21 Objective of site architecture blueprints Specify the structure of the system Developed –In cross-functional team; or –Interaction designers/information architects In theory, engineering team implements system to blueprints

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 22 Blueprint notations Many different kinds of notations Consultancies invent their own versions Example (from reading) –Visual Vocabulary from Jesse James Garrett The goal is to represent –Paths –Goals –Results

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 23 Basic elements

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 24 Labeling Relationships

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 25 Concurrent Actions

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 26 Decision points

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 27 Summary Site blueprints specify the structure of the system Enough detail to implement the website A physical representation

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 28 Recap of system representations User flowSystem (logical) System (Physical) Task analysis * Conceptual modeling * Site architecture *

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 29 Exercise Think of your website for assignment #2 Draw a quick sketch of this information architecture using this vocabulary Reminder: –Read

The Information School of the University of Washington Assignment #2

The Information School of the University of Washington Wonderful websites and wonderful thinking It was a joy to explore your ideas

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 32 Discussion Telling a story is very important –Introduction on 1 st page –Ordering of navigation links –Internal navigation links Engaging readers –Use of images –Whitespace & information hierarchy –Personality (photographs of designers) –Interesting layouts

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 33 Discussion (cont.) Be careful of –Linking styles Underlined headings Links that don’t look like links –Consuming too much vertical space at the top –Emphasizing the ‘brand’ instead of the ‘topic’ –Using secondary windows, which do not come to the front –Aim to make the site feel whole –Make writing/look-and-feel correspond with purpose of content, etc.

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 34 Discussion (cont.) Challenges with taxonomy –Why two representations? –How to show original materials? Challenges with methodology –Will people really understand process? Social issues –Did the affinity diagram really help?

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 35 Grade Distribution

The Information School of the University of Washington Copyright David Hendry (INFO-440 session /30/2002) 36 Next Week Topics –Participatory prototyping –More on Information Architecture Monday –Introduction to assignment #3 Wednesday –Quiz 2 –Feedback on proposals Readings