God of War 2

Hello today I am going to review God of war 2 . I have been playing I have been playing God of War 2 for last 1 year. This is perhaps the best game that i have ever played.

Storyline: 8/10
Graphics: 7/10
Control: 8/10
Ingame Visuals: 10/10
fight Sequence: 10/10
Weapons: 10/10
Usability: 9/10

The game storyline runs great. The player is thoroughly engaged in the Game. Cutscenes are excellent and its great to watch them. However there are lot of places where you can get stuck while playing the game. But do not worry and do not give up. It took me 4 month to finish the game first time I was playing. After that, I have finished this game as many many as 8 time. All these 8 times i started in friday and was done by sunday afternoon. Youtube have videos of all the stages so there would never be situation, wherin you would be stuck forever. And the best part is once you get going with the joystick on PS2, fun gets unlimited and its thrill to play it then.

For the first time the cutscenes are a feast to watch. However from the second time, you might find them 'too long a wait'. I believe there should have been an option to skip the cutscene from the second time. However, that in no way a drawback for the game. God of war is simply out of the world. So get your copy today.

Usability: Why You Only Need to Test with 5 Users

Author: Jakob Neilson & Tom Landauer

Problems found(i)= N(1-(1-L)ⁱ)

where

ProblemsFound(i) indicates the number of different usability problems found by aggregating reports from i independent evaluators,

N indicates the total number of usability problems in the interface

L indicates the proportion of all usability problems found by a single evaluator.

In six case studies (Nielsen and Landauer 1993),

The values of L ranged from 19 percent to 51 percent with a mean of 34 percent.

The values of N ranged from 16 to 50 with a mean of 33.

Using this formula results in curves very much like that shown in Figure above, though the exact shape of the curve will vary with the values of the parameters N and L, which again will vary with the characteristics of the projet

Contextual Inquiry: The Art of User Centered Designs

The Art of User Centered Designs :Contextual Inquiry

Contextual Inquiry is the most important aspect of the Web application development. When we are talking in terms of developing Web Application with a fixed set of users in mind ie. User Centered Design(UCD), contextual inquiry would go a long long way in developing the application. I have worked extensively in Developing Web Application for the Clinical Trial Industry, specifically dealing with the Phase 1 drug testing. I always had this in my mind that my users are Doctors, Nurses, Phlebotomists, Medical Practitioners and others related to the Pharmaceutical Industry, do not look at Web Applications like I do. They treat it like any other web site.



Introduction

Getting Introduced to the user is the first step to contextual inquiry. For a user a UI Engineer is no different from the Programmer or a DBA. Moreover, the user need not understand what actually you are trying to achieve. That would dilute the essence of the Contextual Inquiry. The effort of the UI Engineer should be to build a good rapport with the user. This would assure that he would speak his mind out when you inquire him. He complains to his best. The notion of the contextual Inquiry is not hear good things about the Application. It tries to find the issues and concerns the user is facing and attempts to address and resolved them.



Data Collection and Compaction

Data collection and compaction is the most important thing to do before you start speaking to the actual user. Data collected gives you the understanding of needs and the want of the users. However it could also lead to a mind block. Data at time could be misleading. So study the data carefully but do not jump to conclusions. 90% of the application users prefer mouse over keyboard does not mean that your contextual inquiry should eliminate the query related to Keyboard/mouse. Keyboard/mouse usage is much broader than that. Data collection should be done for reference and better understanding of the process and the product. They contributes extensively to the understanding of the functionality as well.



Query and Inquiry

More then often Contextual Inquiry starts as an inquiry and end up being an Interview session. The UI Engineer sits with a pen and paper taking notes aggressively, asking probing questions. User out of words and being interrupted time and again, tends to get afraid assuming he is giving some legal commitment that he need to sign at the end.



Keep your paper and pen aside. Talk to your user without any obstruction. Let him speak his mind. Let him complain. Let him come up with his wants and desire. Remember that we are building a User Centered Web Application. The user is in the center of this entire process. Ask him simple and straightforward questions.



General Questions

1. So Mike, how is the software working.

2. Is it better then pen and paper (be careful when you are being sarcastic).

3. You are able to enter data easily using keyboard and mouse(be prepared to listen all kind of answers)

4. What kind of issues you face.

5. Are you okay with the color of the Software

6. Some select boxes are too small/big. Don't you think so?

Process Specific queries.


Process specific query should be absolutely open ended. The user has been the part of process on a day to day basis. He has been doing that again and again every day and knows it in and out. Let him speak as if there is no tomorrow. Let him try to explain things to you. This not only would be fruitful for the contextual inquiry, it would also help you in better understanding of the process for which you are trying to develop/enhance the Web Application.



Workplace

Better understanding of the user workplace is important to realize the way the Web Application should be designed.