1. Czym jest IxD?
Mariusz Dziechciaronek
IxDA Poznań Co-Founder

2. O czym będę mówił dziechciaronek@ucd.com.pl
1. Koncepcja IxD
2. Human-Computer Interaction 1940 – 2010
3. Miejsce i rola designera w procesie rozwoju
oprogramowania
4. Human-Computer Interaction w przyszłości
2

3. http://faculty.washington.edu/roesler/IxD/visualMCP.pdf
Mauris sed augue
I
„ NPUT DEVICES: Originally, our concept focused on developing
a new, more intuitive system for input into a redesigned Mode
Control Panel. This included exploration of a variety of possible
knobs, buttons, and touch-screen combinations and configurations.
As our design progressed, we decided it would be best to take
hat we learned from our work in this area and concentrate on the
design for a display.”

4. http://faculty.washington.edu/roesler/IxD/visualMCP.pdf
Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
„D ISPLAY: The display became the main focus for our design
as we focused on creating a device for the cockpit that would
provide the pilot with both current and future feedback regarding
the impact of the autopilot system on the plane’s movement.
The actual display consists of three parts. A dashboard display
4 the top depicts altitude, speed, pitch, roll, and heading.”
at

5. http://faculty.washington.edu/roesler/IxD/visualMCP.pdf
„ Our project visualizes autopilot modes for the MCP.
The screen is broken:down into four areas: The Dashboard, 3D Display,
Mode Indication Panel, and Interactive Timeline. These areas display
information about the flight.”
5

6. http://www.designingforinteraction.com/
Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
Strategia
w jakim stopniu produkt spełnia swoje cele
biznesowe?
Experience
powtarzalna interakcja w określonym
kontekście użycia (szkoła, praca, zabawa,
etc.)
Interaction
używanie interfejsu w czasie przez różne
osoby
Informacja i funkcjonalność
kategorie, typy, powiązania architektura
informacji

7. Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
I
„ nteraction Design (IxD) defines the structure and behavior of
interactive systems. Interaction Designers strive to create
meaningful relationships between people and the products and
services that they use, from computers to mobile devices to
appliances and beyond.”
7

8. http://www.boxesandarrows.com
Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
Human/machine communication – translate the
conversation that goes on between the technology and the
user; understand both parties.
Action/Reaction – understand and anticipate how interactions
unfold over time, designing for the wide range of permutations
that can occur
State – ensuring the user understands the current state of the
application, what type of operations are possible or appropriate
at any given time.
Workflow – concerned with the completion of multi-task goals
such as browsing, selecting, and purchasing an item.
Malfunction –anticipate and mitigate those problems, ensuring
that both the user and the system can easily recover.
8

9. Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
9
http://www.slideshare.net/KMcGrane/foundations-of-interaction-design-presentation

10. Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
10
http://www.slideshare.net/KMcGrane/foundations-of-interaction-design-presentation

11. Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
11
http://www.slideshare.net/KMcGrane/foundations-of-interaction-design-presentation

12. Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
12
http://www.slideshare.net/KMcGrane/foundations-of-interaction-design-presentation

13. Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
13
http://www.slideshare.net/KMcGrane/foundations-of-interaction-design-presentation

14. Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
14
http://www.slideshare.net/KMcGrane/foundations-of-interaction-design-presentation

15. http://www.boxesandarrows.com/view/bringing-user
http://www.boxesandarrows.com/view/bringing
Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
1. poznanie użytkownika przed sformułowaniem wymagań,
2. priorytetyzacja realizacji funkcjonalności: biznes, designer (user),
development,
3. uwzględnienie designera w każdej fazie powstawania oprogramowania,
4. testy z użytkownikami w fazie „customer review”,
5. wizualizacje przypadków użycia w postaci interfejsów,
6. badania użytkowników po „launchu”.

16. Etiam a velit at enim
pretium fermentum
Allegro – proces rozwoju produktu lorem@ipsum.com
16
http://tebe.blox.pl/resource/alegroproces.jpg

17. Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
RUP i UCD
ORACLE product lifecycle
17

18. agile
18

19. Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
19

20. Etiam a velit at enim
pretium fermentum
lorem@ipsum.com
http://asset.soup.io/asset/1009/6079_5d56.jpeg
http://asset.soup.io/asset/1009/6079_5d56.jpeg
20

21. Gdzie warto zajrzeć? dziechciaronek@ucd.com.pl
Koncepcja IxD http://www.uxmatters.com/mt/archives/2006/12/clash-
of-the-titans-agile-and-ucd.php
http://faculty.washington.edu/roesler/IxD/visualMCP.pdf
http://www.billbuxton.com/SoftwareDesign.pdf
http://en.wikipedia.org/wiki/Interaction_Design
http://www.ibm.com/developerworks/rational/library/27
http://ixda.org 74.html
http://pschmid.net/blog/2006/10/09/58
Human-Computer Interaction 1940 – 2010 http://blogs.technet.com/b/office2010/archive/2009/10/
http://www.slideshare.net/mrettig/interaction-design- 29/ux-research-tools-and-techniques.aspx
history
http://en.wikipedia.org/wiki/History_of_the_graphical_us Human-Computer Interaction w przyszłości
er_interface
http://www.gartner.com/it/page.jsp?id=1447613
http://designinginterfaces.com
http://liftlab.com/think/nova/2010/10/03/deconstructing
http://www.sapdesignguild.org/resources/ui_history.asp
-gartners-hype-cycle-myth
http://ignorethecode.net/blog/2010/01/21/realism_in_ui
_design
http://home.vrweb.de/~martin.theus/Design.pdf
Klasyka:
http://www.kickerstudio.com/blog/2010/09/essential-
Miejsce i rola designera w procesie interaction-design-essays-and-articles
rozwoju oprogramowania
http://uxdesign.pl/jak-to-sie-robi-w-apple
http://www.boxesandarrows.com/view/bringing-user
http://www.boxesandarrows.com/view/case-study-of-
agile

22. dzięki za uwagę ;)
zapraszam na mojego bloga: http://www.ucd.com.pl