| |||| | |
| |||| | |
 | |
| |||| | |
| Jennifer Hurler Semester 2 - Spring 2010 2/23/10: At our meeting we determined that using the dropbox site Chris had found would
not be a safe way to archive old files. So we must think of something else! Chris, Mike, and
I are going to work together to archive the site, manage all of the hardcopies of everything,
gather new data, and present it in a much better way. 2/16/10: Instead of going to our usual meeting location--Professor Pulimood's lab--I
went to Dr. Wolz's. She has meetings with students that are doing independent research at the same
time that we meet on Tuesdays. Chris is one of them. Since I haven't been able to do much lately (I'm
still waiting for Siobhan and Matt to fix the database's login issue & proofreader issue), Dr. Wolz
asked if I could help her with her end of the project. 2/9/10:This week, I got a little crazy with trying to improve the interface. I actually
printed out screenshots of each and every part of the site. I marked each up with comments and
suggestions, as well as posed questions about fuctions. Now I have to take all of that and prioritize
it and make the tasks into tickets.
Right now, the biggest issue is the Proofreader, which simply
does not work. Another big issue is our inability to even log into Cafe. Before that even, I have to translate the pages. I tend to write
in a very colloquial way when dealing with notes I take for myself. But if others read them, they
probably wouldn't know what I was talking about, as I also tend to mix languages, abbreviations,
texting and internet jargon, and such. It's just faster if I have to hand write things! But I am a
capable writer! 1/29/10:We have two weeks to get the database going before we begin testing. I have to
focus on the interface--not the look! Although I know these are two different things, I tend
to not serperate the two. For me, the interface is largely controlled by the look, as is the look
largely affected by the interface. I feel as though the two should be looked upon simultaneously.
For example, there's a function on the journalism site that allows for users to create new articles. In
fact, there are three instances where the same function is present. However, each one looks different.
Three different interfaces for the same function? Graphically, that needs to change. They all need to
look the same.
But I know that for this project we really must get the interface working properly with the database
before worrying about it looking different. We also have to make sure it works well in IE. For testing, we may have to get consent from the IRB, which is a group that makes sure people who
conduct tests on people don't harm them. And I'd have to make a consent form for out testers. 1/22/10: Professor Wolz stopped in today! She seems to focus more on the PR aspects of this
project, which really interests me. She deals with other organizations and conferences, and seems
to handle a lot of how the project looks visually as a whole. Going along with that, she asked me
if I could redesign the logos for the middle school we work with and for IJIMS, as well as the red
squirrel logo, and a new TCNJ logo. I'll have to redo them all in illustrator. Another interesting, and slightly off topic/ slightly relevant topic we discussed was... Barbie!
Frankly, growing up, I hated Barbie, but the topic at hand was interesting. There'd been a poll going
on regarding Barbie's newest career choice. One of them was Computer Engineer Barbie, which scared
everyone at the research meeting (6 women!). We pondered what she'd look like--how they would dress
her. More importantly, we wondered what her impact would be, and the overall view of women working
in technical careers. 1/19/10: While researching, I came across a number of different methods for user testing.
I looked at major corporations such as Google, smaller sites, and the work of user testing gurus such as
Jakob Neilson. The kind of testing I feel is more efficient are the more observational kind. It's not as
though there's going to be someone walking users through a website, so why should they during the
testing? Just observing, and hopefully having them speak their thought process aloud, will help.
Just seeing how long they linger on a page, why they clicked where they clicked... At our meeting, we also even talking about the history of Google, which was facinating. Apparently,
the logo for Google was what it is because of the creator's limited art skills. He just had to
throw something up there! Google is definitely one of those examples of the greatness of simplicity. For IJIMS, I really want to change some of the more design-based areas, but I know that's not
a priority. Right now, I have to standardize a test and test people. Testing either Prof. Pulimood
or Prof. Pearson's classes would have worked, but I have class at the same time. Semester 1 - Fall 2009 12/4/09: Yesterday we had our final meeting before Winter Break. It was
an interesting meeting because, we focussed more on the future than on the present.
We looked at what was done thus far, and what needs to be done. We realized we need
to open communication a whole lot more-- I know I'm guilty of this. We also need to
set deadlines and have longer blocks of time to work together. Or rather just time
dedicated to CREU. We don't need to be working together, per se, but just working.
It's that much more motivating when you're surrounded by other industrious people. Next semester, my user testing has to be broader and more frequent. I've been working on
a couple of different methods, that is, a number of different procedures and steps, as well
as questions to ask before and after a test. Over the Thankgiving break, I bought two
books on user testing.
Over this break, I've been able to actually go through them thoroughly and take notes. It'll be easier to focus on CREU next semester. In addition to the weekly meetings we've
been having, we all
decided to set a few hours each Friday aside so that we can all sit and work. Both days of CREU
are already looking better, as I don't
have to get up really early, nor do I have to leave early and run to class! I need to find out what exactly Chris and I are allowed to change and do to the site.
I've got sketches and layouts on paper,
as well make sure we fix all of the pre-existing bugs. Right now, the ones that irk me the
more are the three
different interfaces for the same function (of course at the moment I can't remember what it
was for. Adding an article perhaps?), as well as
the top menu bar and logo. I'd like the menu on top to remain on top, floating, even when one
scrolls down to the bottom. Little things first. 11/19/09: Today we have our last meeting before Thanksgiving
break. I've been feeling a lot better now, and made a lot of progress.
We've moved into beta testing, and have been for the past two weeks. So I
now know that if something technical isn't working properly, I should
point it out. I mean, I pointed out things before, but was always unsure.
I didn't want to point out flaws about a piece of the project that
someone was working on. If they're working on it, of course it's not going
to run smoothly while being looked at. But now I will. =) I've been able to test the site on two very different people, which was
interesting in terms of the testing and interface itself, but also the
mentality of a user tester. The first person I had test things was an
English major, and someone not technologically savvy. She began worrying
before she even sat down in front of the screen. I couldn't help but find
that intriguing. It was as if she felt that by my conducting user testing,
I was testing her ability. I had to remind her that it was the site
being tested--not her and her ability to navigate a site. It's the process
that's o be looked at. Also, she was reluctant to voice her thoughts,
which is important. I told her it was, and that I wouldn't be offended. I
asked her to literally speak her thoughts, her reactions to things. People
seem reluctant to be vocal and blunt. She tried to test it really fast
too. On the other hand, I myself had to learn self-control. I can't guide
the user--that defeats the purpose! I had to simply sit back and observe. On the other side fo the spectrum, we had my other friend and
well-respected colleague, a senior Computer Science major. He was, again,
completely opposite of my sophomore friend. There were no problems as far
as fear--neither fear of navigating nor voicing their thoughts. Whereas
with the first person I got comments about the design and layout, I got
that plus more on the technical aspects, the actual coding from the
second. 10/30/09: I met with Chris! What I thought would be, perhaps an
hour, hour and a half long meeting turned into a two and a half hour one.
It was great! We messed around with the CSS and have plans to change a
lot a lot a lot. 10/21/09: Rediscovered an email from September. It had been from
one of Dr. Pulimood's past students regarding navigating the web and color
blindness. A guest lecturer in my IMM class today really got me thinking
about it. I explained CREU to her upon Professor Pearson's suggestion, as
she is one of the faculty involved. Have to talk to Chris. 10/15/09: Have to update the Wiki. And talk to Chris now that
we're back from fall break. Need to do a screen reading test soon. We're
moving into beta testing, so I should just prepare to redo everything. 10/12/09: Fall break! Got to meet with my aunt, a program
manager at Johnson & Johnson. Talked to her about the project and about
coding. Found old PHP notes from a pre-TCNJ class. Saw how issues have
been fixed so far and see what still needs work. 10/1/09: Emailed Chris. I want to get more hands on experience
fixing up the site. I don't want to just tell him things to fix, but do
them as well. We're discussing times to meet. I have to try out Smarty
more. 9/26/09: Compiled the list of bugs, accessibility issues, and
general design and interface issues and improvements/suggestions. Talked
them over with Chris. Also discussed template making in Smarty.
9/24/09: Testing! What's working/Not working; didn't focus as
much on what should be added/fixed for design, but rather on what HAS to
be fixed. But I made note of the smaller details. 9/17/09: Had another Thursday morning meeting. At 3 I went with
Dr. Pulimood to Fisher Middle School and got to see the immediate effects
and benefits of our work. Got to talk to most of the children and worked
with them on their magazine, helping them form categories and ideas for
their articles. It also gave me a great opportunity to see how they
interacted with the site, where they seemed confused, and what they
thought of it. 9/11/09: Met Chris! We talked about CSS, PHP, and our major
(Interactive Multimedia) in general. We also went over the large list of
issues I took note of. Should dust off that PHP book! 9/10/09: Testing bugs. It works out that I'm new to the site
and can
unbiasedly test usability and the interface--the site in general. 9/9/09: Siobhan and I met with Julius for the first time. He
gave me a really good idea of what was expected of me and what I should
fpcus on. Found out I'd be working with Chris H. 9/8/09: We've met twice--Thursday mornings! I've begun
exploring the different versions of the site. Tabbed different parts of
the textbook. 9/01/09: Went over old notes from a previous class. The
textbook will also prove useful. They cover various aspects of
accessibility. 8/27/09: Orientation, discuss timeline, project goals
|