Reading Seminar 1- Mehrdad Bahador

The Question:

Why is there no clear consensus definition when it comes to User centered system designs? and how would we benefit from having one/ or not having one ?

Chapter 7,8 and 10

In this way we know what the user needs and expects from our design. The second being production, by building stable ground requirements which we can utilize in our work. The question being whether the process of identifying a user is iterative is important as well. Because we must adapt to our user in a way that they evolve and our design must do so as well.  I also saw the importance between high fidelity and low fidelity prototyping, it is also important to note that high fidelity prototypes can be vertical and horizontal. Thus in the early stages of a designing process the low fidelity prototype technique is preferred. Conceptual and physical design are two keyword that one must discuss when thinking off designing software. Conceptual is more focused on the behavior of the software while the physical is more centered around details of the software, for example screen layout.

In a user centered design which is the preferred method the process of evaluation and the design itself are closely related and almost intertwined. In evaluation some of the main goals are consistent with the designing goals. However, the method used to obtain the data is different. For example the use of interviews or questioners in an evaluation is warranted.

To get different perspectives on examination of data the method of triangulation can be used.

Key principles for User-centered systems design

The article argued that User centered system designs has no clear definition. Thus there is no clear consensus on how and when it shall be applied. Leading to low quality UCSD that we can find in the industry. The project was also about the authors own experiences with UCSD and how they have used it.