Reading Seminar Group Discussion

Reading Seminar Group Discussion

The questions we discussed were as follows:

• How does one obtain qualitative results that are as reliable as possible?
• 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 ?
• How do we ensure that the data we get correlates with what they do in reality?
• How can we articulate and establish the requirements so that we can set clear and precise objectives to work towards?

We discussed our project and the limitations thereof, as our project is of a qualitative nature we deemed it hard to actually pinpoint a specific method that would be a best fit. Thus we deduced general guidelines for how to obtain reliable results. First of, extract the data needed through a general framework of questions/data-obtaining method and as much as one can one should try to stick to the same questions and/or framework. In summary, we concluded that we must try to systematize as much as possible in order for any results to be as reliable as possible.

The concept of UCSD (User Centered System Designs) was a term coined in the late 80s and pretty much explains itself. The term has overtime, however, both according to us, and the authors of the article for the reading seminar been described as a term that carries absolutely no meaning. It simply means that one should think about the user while designing the product, but one does not have to ask or question the user, thus reducing it to a basically meaningless phrase.  We discussed the possibility of implementing a framework for UCSD is non existent since as stated above we and other professionals deemed the phrase meaningless, although that is not to say that the concept as a whole is meaningless, and maybe we will use the concept behind UCSD.  

Since people could give answers that they perceive is the right answer or what they think we want to hear, which is a legitimate worry since these biases exist. So what we propose is that the questions regarding how they use the available infrastructure at the stations should be completed with observations. For example if they say that they never spend time looking at the time tables but we can clearly see in our observations that they do, then we can disregard the data gathered for these questions and fill it in with the observations instead. This will make it so that our data will overall have higher quality and allow us to make more accurate conclusions which in turn allows for better analysis of the data gathered.    

Regarding the clarification of objectives we came to the conclusion that we should form some kind of hypothesis regarding the current technologies and infrastructure available so that we have some grounding in the theory. With this grounding we will then gather the data that we see fit and based on the data that is gathered we will then sit down and reevaluate our hypothesis to see how well our perception of the situation correlated with reality.

Overall, our group had taken away a couple of key points for the study which were:

• To set a clear framework for our project before we conduct anything
• To be user-centered and to focus on our specific target group.
• Try to set up our framework so that it removes as many biases that we can, thus removing as much uncertainty as possible.

Reading Seminar 1- Dawood Rehman

Chapter 7 manages the notion data gathering. The text emphasizes five key concept that requires attention for a successful data gathering session: goal setting, pilot studies, triangulation, identifying participants and the relationship between the individuals that collects and provides the data. Furthermore the chapter introduces some main techniques for collecting information: observation, interviews and questionnaires. Since we will be traveling between Slussen and Allmänna Gränd with a ferry, we will probably mostly be using direct observations and a semi-structured interviews to get the most reliable data. I also think that it is important to give the five key concepts that were earlier mentioned our attention because these concepts are necessary for successful data gathering sessions.

Once the data have been gathered one need to analyse the data. The difference between qualitative and quantitative data and analysis is discussed throughout the chapter. The separation between these concepts is how the data is expressed and the methods that are used to ascertain various attributes during the analysis. Quantitative data is expressed in numerical terms and Quantitative analyses uses numerical methods. Since the majority of the data that we need to gather cannot be attained using numerical methods we will mostly be focusing on qualitative analysis. But we will undoubtedly utilize quantitative analysis as well to represent data that can be represented numerically, such as age and gender. We might even utilize some of the frameworks presented for qualitative analysis.

Chapter 10 emphasizes the importance of articulated requirements and explains some useful techniques that can be used for establishing requirements. The reason why this is so important is because it clarifies the expected behaviour of the product. Not having a clear picture of the final product may result in setting up false objectives which may end up in collecting the wrong data. This will undoubtedly lead to the fact that the product that we expected is not product that we produced. There are various requirements and in chapter 10 some useful techniques are presented for establishing the different requirements.

These chapters present some very useful ideas and techniques that I had not thought of. I think that bearing these ideas and techniques in mind can help us greatly along the way. In my opinion our group should focus on having clear requirements and establishing the requirements. This will save us from having to redo our work which otherwise we might have to do because our objectives were not set properly.

Question: How can we articulate and establish the requirements so that we can set clear and precise objectives to work towards?

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.

Reading Seminar 1- Ramtin Javanmardi

In chapter 7 we are introduced to the concept of data gathering and all the standardized structures around data gathering such as interviews, observation and questionnaires. The text goes on to describe sub-structures to each of the above mentioned data gathering methods, for example interviews can be structured, semi-structured or unstructured.

This chapter presented these concepts, that I believe are familiar to most in a way that made me realize that there is actually a fairly rigid structure around something as simple as an interview for example. The two key concepts that stood out to me from this chapter was:

     1)    Its is extremely important that the data gathering is done with focus on a target group.

     2)    Triangulation, which is when the thing we want to study is viewed from many different angles.

Chapter 8 teaches us how to analyze the data that we have gathered. The difference between quantitative and qualitative analysis is explained to great detail and a few frameworks such as grounded theory, distributed cognition and activity theory is presented.

I find the parts about the theoretical frameworks to be really interesting, in particular activity theory. Reason being that we could use this theoretical framework to identify how people use the current technologies at the end points of the route we have chosen for this project i.e. we could use this find reoccurring patterns.  

Chapter 10 describes the importance of setting up clear requirements for each part of the project, and indeed the interactive product itself. Not surprisingly we are presented with different standard methods for finding the right requirements such as Task analysis which helps us get a better understanding of existing systems and practises.

I think that our group should really look into the Essential Use Cases method since it allows for abstraction of what the user is supposed to do and what the system that is to be designed should do. I believe that this would give a great deal of clarity regarding what the system we are to design should have as it’s main focus. 

Question : how do we ensure that the data we get correlates with what they do in reality?

Reading Seminar 1- Denny Lekic

Reading Seminar One

Chapter 7 encompasses a few general methods of gathering information or data. It reflects upon what methods to use, how they should be standardized and what target groups one should have. The methods presented include interviews, observation, and questionnaires.  For interviews, the authors mention different concepts such as structured interviews and semi-structured interviews where the main differences between the interviews is the rigidity of how one follows a strict question-list versus a general theme with semi-structured interview (you may follow a question-list with a semi-structured interview as well but the importance of following it strictly is not present). A key concept from this chapter is triangulation which encompasses the idea of using different methods to record and analyze data, in order to provide depth to the research.

Moreover in chapter 8 one is taught on how to analyze data. This part is dependent upon what data and information you have gathered. The chapter more or less presents data as quantitative and qualitative where the main differences are whether or not one can standardize the data collected with numbers. Which one can do to a certain extent with all data, but it is for instance hard to enumerate feelings, this is where qualitative research comes in.

Lastly, in chapter 10, the book is very keen on expressing the importance of coming into a project with clear goals and establishing requirements.  This is of course since one has to be very sure of what they are actually testing, or observing before going out in the field. This is because unclear goals might produce unclear results and non-coherent data. Thus, one must make sure that all bases of the project are covered and that everything is done before actually doing anything, as a mistake can easily multiply over the course of the study, starting from observation, to interviews and so on and so forth.

Our group should focus on defining our goals beforehand, obtaining as much information as possible to get reliable results. We will use qualitative analyzing tools, and so the importance of being rigid are less present, although we must stick to what we have chosen as to not be led astray.

Question: How does one obtain qualitative results that are as reliable as possible?