hci project

Problem

We found that a common issues that every human have unexpected desire. Desire will make us to want something there is out of our ability. We are always hunted by the beauty of the goods and the fun. We don’t thinking the impact of doing something. Sometimes will regret on certain action we do. In another words, we cannot differentiate between the most importance and less importance. Some people like to waste their money to buy unnecessary thing. For example, some student always study and ignore the exercises or some women like shopping and spend money over their income. So, we want to design an application that addressed those various problems by record down the activity of user carry out and the financial status of the users.At the end it can classified as 3 main problem there is

people like to waste their money to buy unnecessary
people like carry out unnecessary activity
people have imbalance daily activities

Target user

The target user is Teenagers, workers, student, and married people. Our target audience for this application was anyone who can carry out activity and anyone who wants to better manage to their money and time. Our primary focus was targeting this application towards university students who are on a budget since they still a student, they don’t have financial income and busy with their activity. Our secondary target users is teenagers. Their age is among 13 years old to 19 years old. As we know that, current teenagers no matter boys or girls are prefer shopping and spend money. So that, they need this apps to restrict them or as a reminder them on financial side. Next target was the employee with still single. Nowadays, the employee are working hard to make their life easy. So that, they need something to make their financial clear and if wish to find a partner they need to make sure their social circle is works.

Task

Task 1 – Sign up

Task 2 – Log in

Task 3 – Add activity

Task 4 – View report

Task 5 – Log out

There are many tasks that we thought would be useful for this application, but there was a handful of essential tasks that were absolutely necessary. First tasks is login, we need to login because we need to make sure the people using the profile of apps is the same person, second purpose is to make sure all the information is private inside the application. For those who are new the first task is sigup. If the user dint singup they cannot perform login task. This can reduce the illegal enter or stole the phone information occurs. Another task on this application is add activity, this feature user need to enter the activity he carry out. In this session, user can choose either want to upload the pictured which related to the activity or not. There have a button choose which source you want take the photo such as media library or directly take from camera. Description is required to enter to make sure the user can check back the details after ward. User can choose either want to tag friends or other user together. Users can also need to enter the total money spend and the type of activity filed into the application. Another important activity is view the activity as a report in a calendar. The monthly calendar will show the yellow point as a notification to let the user know that it have activity carry out in that days. If the user select a days from the calendar that have yellow point, it will enter the days and view the summary of the activity on that days. Apart from that, user can also view the activity and financial status separately. The last activity is log-out. The data will be saved after the user press log-out.

Design

Final prototype design –high fidelity

The application consist Home , Activity and Expenses report and Edit Profile.

The home screen features recent activity of the current user activities where they can update their ongoing activities such as shopping, eating, studying or exercising and they can share with their circle and their activities will appear on their circles timeline. This features are the same as Facebook where people can see their friends’ statuses, pictures or any kind of activities. As a conclusion of their daily activities, this application will calculate their percentage of living to see whether they are living a healthy life or otherwise.

In the Activity section, they can add their activities, by uploading a picture, include their expenses (optional) and choose their activity and tag people (optional) and by that user input this application will calculate and show their activities percentage and display which activities they involved the most in that particular month. They can also pick a date to see their activities per day from the History.

In the Expenses section , it will display the user report of finances. They can input their monthly income and expenses and this application will automatically calculate their total expenses and total saving/balance. They can view how much have they spend for a month or they can view how much they spend for a day in the history section.

In the Edit profile section we have basic editing profile features which is name, phone number, email and confirm email.

Design Revision

Low fidelity design

Our first design was in the low fidelity where we lack of buttons and many functions. Our design makes many of our user confused on where to navigate as we lack of using words for an icon because we thought that user would understand but we thought wrong.

Our first design was a simple design where we don’t place much attractive background. Our background at first was white but then we changed it later at the high fidelity stage.

But overall we have many positive feedbacks.

Implementation

Functionality

This application can calculate users life percentage regards of their life activities.

This application can also calculate their daily expenses.

Technology

In order to test if the functional requirements and the look and feel was acceptable, we decided to make some prototypes. This way we could check the usefulness of the application, validate requirements.

Two kinds of prototypes were implemented: low fidelity and high fidelity. For the user testing, the first implementation was a paper prototype screen captured and make it as it looks like an application.

The feedbacks are mixed with positivity and negativity.

We do not require any technology because we only have the high fidelity prototype which we didn’t implement in phones instead we implemented it through third party software which was pidoco.

Takeaways

The big lesson we learned from this project is the importance of fully realizing your design before beginning the implementation. We truly believed that if we started to implement as soon as possible, the design would follow, no matter how broken it was. Our reasoning was that if we started to develop quickly, we could start testing sooner and iterate on those changes rapidly. Yet, instead, we became bogged down by the technicalities and execution of our implementation. Practically every time estimate we made that involved implementation details should have, in reality, been doubled. At the end of the day, no matter how well something is implemented, a feature is completely useless if it is poorly designed. By skimping on the details during our initial round of designs, we missed key elements that should’ve been present in our functional prototype from the start. Not just speciﬁc features, but even obvious components.

Evaluation

Method

Our target user is not only from the staff or student in UTM. The user can be at any different level of age in range from 13 to 40 and above. Their level of education does not make any difference while using this system. They also do not have to be a computer expertise to use this system. However, this system is not intended to be used by deaf or blind people.

For low-fidelity prototyping, there are only three users who evaluate our usability system. All of them are UTM’s student and in the same range of age which is 20 years old. For high-fidelity, there are 6 user testing. All of them are not in the same age and certain user testing not from UTM. One person from our group welcomed and explained to the user about the system that we will develop while the rest of the group member took important note. We took time for every task performed by the user. So that, we will analyze about the difference time taken by each user.

Low fidelity evaluation

There are lots of comments from user testing about our paper-prototype interface. For this paper-prototype, there are only three tasks for the user to perform which is login, add activity and view report. This is some feedback from our user testing regarding to our paper-prototyping.

Task Number 1:

Task Name: Login

User 3:

User’s Name : Shahirah

Group name : 9

1. What was easy?

Easy to use, the clear instruction.

2. What was difficult?

Not.

3. What would you suggest to improve the interaction flow?

For login, nothing.

4. Would you use/not use the system in real life? Please give brief reason.

Yes, easier for daily report.

Task Number 2:

Task Name : Add activity

User number : 3

User’s Name :Shahirah

Group name : 9

1. What was easy?

Yes.

2. What was difficult?

Not that difficult.

3. What would you suggest to improve the interaction flow?

The upload icon, too small. Add skip icon. No instruction on added expenses. No button added other on activity. Make the activities option limited.

4. Would you use/not use the system in real life? Please give brief reason.

Yes.

Task Number 3:

Task Name: View report

User number : 3

User’s Name :Shahirah

Group name : 9

1. What was easy?

The icon is easy.

2. What was difficult?

No difficult. Because it just viewing.

3. What would you suggest to improve the interaction flow?

Starter report, like weight.

4. Would you use/not use the system in real life? Please give brief reason.

Yes

High fidelity evaluation

Task 1: Sign up

Performance table for Sign Up

For this task, all of the user could complete the task. Some of the user can perform really well on this task. However, there are also some users who take longer time than we expected. In conclusion for this task, user thinks it is easy but a bit confusing.

Task 2: Log In

Performance table for Log In

For this task, each user managed to complete it. Some of the user could log in quite fast where as some are averages. In conclusion for this task, it is not really hard to carry out.

Task 3: add activity

Performance table for add activity

For this task, all of the user can perform this task completely. However, the performance for this task is not really good. Majority of the user take longer time than we expected. In conclusion for this task, it is quite hard for user to perform because of the symbols that make the user confuse.

Task 4: view report

Performance table for view report

For this task, each user completed this task. Some of the user can perform well. In conclusion for this task, users think this task is easy and the symbols help them a lot in making decision to perform this task.

Task 5: Log Out

Performance table for log out

For this task, every user completed this task successfully. Even, there are some users managed to complete this task, less than time taken we expected. In conclusion for this task, it is very easy to carry out.

Subjective measurement

We calculate the subjective measurement based on 3 positive and 3 negative experiences that users feel about this system. After analyze the data collected, the results are not as what we expected and we also get inconsistence result. For mean, we expect to have positive experience more than 4 and all negative experience less than 2. For standard division, we expect all categories get below than 0.5. We believe that the biggest factors that contribute to this result due to the difference group of age of user testing. By far, the hardest task would be task 3 which is to add activity meanwhile the easiest task is task 5 which is log out. It is because the average time taken for user to perform this task is higher at task 3 and lowest at task 5.

Reflection

During the making of this prototype that were assigned to us we have experience a new experience where we create our own application instead of using others.

Every week we have a group discussion where we discuss what we want to have in our project. We learn new skill while building the project.

We spent much time focusing on the designing the interface rather than the testing and implementation of the LiveEnergy. Our design was praised for the attractiveness. Issues are lack of functionality and have a non-understandable icons and no guide words.

At the very last of our presentation we learned so much what we lack and what we have.We took it as our guide to improve our project in the future.

Presentation Slide

http://www.slideshare.net/weeequan/hcipresentation-43102151

User number	User’s name	Duration(t)(s)	P(%)	Performance score s=pc/t
1	Nurul Wahyuni bt wahid rahayu	65	100	103.07%
2	Ummi syafiqah	72	100	93.05%
3	Nur Atikah Shamat	64	100	104.69%
4	Siti Noor suhaila binti Jamil	83	100	80.72%
5	Siti noorraishah binti ahmad	105	100	63.80%
6	Siti hawa binti abd rahim	155	100	43.22%

User number	User’s name	Duration(t)	P(%)	Performance score s=pc/t
1	Nurul Wahyuni bt wahid rahayu	32	100	90.62%
2	Ummi syafiqah	20	100	145%
3	Nur Atikah Shamat	20	100	145%
4	Siti Noor Suhaila binti Jamil	38	100	76.31%
5	Siti noorraishah binti ahmad	44	100	65.90%
6	Siti hawa binti abd rahim	86	100	33.72%

User number	User’s name	Duration(t)	P(%)	Performance score s=pc/t
1	Nurul Wahyuni bt wahid rahayu	51	100	58.82%
2	Ummi syafiqah	25	100	120%
3	Nur Atikah Shamat	36	100	83.33%
4	Siti Noor Suhaila binti Jamil	46	100	65.21%
5	Siti noorraishah binti ahmad	41	100	73.1%
6	Siti hawa binti abd rahim	70	100	42.85%

User number	User’s name	Duration(t)	P(%)	Performance score s=pc/t
1	Nurul Wahyuni bt wahid rahayu	14	100	85.71%
2	Ummi syafiqah	38	100	31.57%
3	Nur Atikah Shamat	15	100	80%
4	Siti Noor Suhaila binti Jamil	15	100	80%
5	Siti noorraishah binti ahmad	25	100	48%
6	Siti hawa binti abd rahim	35	100	34.28%

User number	User’s name	Duration(t)	P(%)	Performance score s=pc/t
1	Nurul Wahyuni bt wahid rahayu	7	100	85.71%
2	Ummi syafiqah	11	100	54.54%
3	Nur Atikah Shamat	7	100	85.71%
4	Siti Noor Suhaila binti Jamil	9	100	66.66%
5	Siti noorraishah binti ahmad	12	100	50%
6	Siti hawa binti abd rahim	13	100	46.15%

hci project

Sunday, 11 January 2015

Link For Project Report Softcopy

Wednesday, 31 December 2014

Video UserTesting

All remaining video can get from dropbox https://www.dropbox.com/sh/khh3cg3pcbp9ado/AACi2UtyW5V6BKcelCx5av2Ja?dl=0

Tuesday, 30 December 2014

Submission 8

Problem

Design

Final prototype design –high fidelity

Design Revision

Low fidelity design

Implementation

Functionality

Technology

Takeaways

Evaluation

Method

Low fidelity evaluation

High fidelity evaluation

Task 1: Sign up

Subjective measurement

Reflection

Presentation Slide

Briefing To The Users

BRIEFING

Changed From Low Fidelity To High Fidelity

Link To High Fidelity Prototype

User Testing Result

User Testing

Subjective Measurements

Blog Archive