Jana Herwig

Java’s Inner Sanctum: A Visit to Sun Microsystems’ Usability Lab in Prague

The walls in room 3328, the observation room at Sun Microsystem’s usability lab in Prague, are painted a subdued blue. It swallows all the light, ensuring the testing scenario is not interrupted by curious guests like us, the Kiwi-project team members who were granted the privilege of a tour of the inner sanctum of Sun’s developer den. Through the one-way mirror, we can see a rosy-cheeked developer, talking to himself in Czech, interrupted by little sips from a coke bottle. He does not see us. The fact that very few of us understand Czech gives the situation an even more experimental appeal.

Sun Usabilty Lab, Prague
The new usability lab at Sun Microsystems, Prague

Jakub Franc, the cognitive psychologists in charge of the design of the study, explains to us that Sun rely on the Think Aloud method and observation in most of their test cases, rather than analyzing data from biofeedback sensors or eye-tracking devices. “Eye-tracking is good for testing the usability of web sites,” he says, “but for our purposes, the think aloud method, where the test person describes what he does and thinks, has greater benefits to offer.” The authenticity of the tasks to be performed in the study is a key: The developer behind the sound-proof glass wall is currently busy importing his own PHP application into NetBeans, Sun’s open source development environment, while the interaction designers and developers who created the tested module observe. A typical testing scenario lasts about 90 minutes, with the final 20 minutes consisting of an interview. “I always tell the testers that it’s not their fault if they fail to perform a task,” says Jakub. “If they fail, it’s the product’s fault. After all, that’s why we’re testing it.”

Before a software product is tested in its design or redesign phase, the ideal candidates are identified based on the results of questionnaires that are sent out to people in the tester database. The database includes both users of open source software as well as of competitive products, with the ideal test sample consisting of people who represent the whole spectrum of the target group, ranging from expert to newbie – and they must not necessarily be open source enthusiasts: “We offer a relatively high reward of 1000 CZK* as we want testers from all levels and backgrounds and not just the volunteering enthusiasts.”

Until Sun Microsystems moved into their new building in 2006, they collaborated with the Department of Computer Science at Czech Technical University (CTU), where they set up the very first usability lab in the Czech Republic in 2004. The deal was that Sun would supply the equipment and know-how, and CTU would supply the space and construction. Both institutions shared the facility until, after three years, all usage rights and equipment were transferred to CTU. One of the features of the new lab is the one-way mirror – the previous one relied on video observation: “From our experience, despite the fact that some participants feel less comfortable in this set-up, it makes a difference to observers”, writes Jiri Mzourek on his, i.e. one of the many Sun blogs, “they feel more connected to the participants”.

Jakub Franc
Jakub Franc, cognitive psychologist and usability researcher

Even though there is now an in-house usability lab at Sun, the collaboration between Sun and CTU continues, in particular in research and design projects. Students participate in projects led by Sun that focus on Sun products, learning about research methodology as well as gaining experience in project management in a real business environment. Jakub Franc also gives seminars in cognitive psychology and research methodology to CTU students, and is himself pursuing a PhD in environmental psychology – a relatively new discipline which, according to Jakub, deals with questions such as: “How should buildings be designed so that people are not getting lost in them? What recreational areas help people to recover from daily stress? What kinds of front gardens discourage burglars from invading the place?” In other words: Jakub studies the cognitive parameters of the usability of real objects.

Once the KiWi/Sun usecase enters the evaluation stage, the KiWi team will again be given access to the lab – but this time not as visitors, but as observers, witnessing how usable the KiWi-Wiki system really is to the inclined user. We are looking forward to the experience – and thank the designers of the lab for implementing a sound-proof wall, just in case the KiWis get emotional!

*) worth about 2 monthly passes for the metro in Prague, or 40 beers in a good pub

Zemanta Pixie
Jana Herwig

Not a pipeline, but a graph: software development in the KiWi/Sun usecase

Josef Holy‘s report this morning about the status quo in the KiWi usecase conducted in collaboration with Sun microsystem presented us with an interesting contrast. While the point of departure in the Logica usecase was a conceptual model of knowledge that is shaped by CMMI, Josef made the point that software development in an open source project follows quite different rules: “The lack of formal processes IS the process”, said Josef, characterizing the collaboration in the NetBeans development environment which (as reported earlier) has about 200 Sun developers working on it, in addition to thousands of external contributors and hundreds of thousands of active users. Correcting his own presentation regarding the development process from May ’08 he said: “We shouldn’t think of a production pipeline here, but of a graph.”

Roles in a Software ProjectWithin Sun (or any software development project), one can draw a distinction between three groups of people working on a software project, depending upon the intensity of interaction and impact they have on the project: First of all, you have the planners, designers, developers and testers who interact intensely and whose work strongly affects the actual product. Secondly, you have people like the documentation writers who describe a software, but who do not shape it. And thirdly, there are people who translate the work of the second level to different markets or target groups, e.g. people working in localization.

A first important decision to be made was: Who to involve in the KiWi usecase? As the KiWi approach is decisively informed by the wiki philosophy, it only made sense that the designers, rather than the developers, should participate. Designers need to have access to various repositories of information, for instance user interface specifications, requirements descriptions, usability reports, marketing intelligence data, etc. And, to a much greater extent than is the case with developers, their work relies primarily on the written word, in the form of definition and documentation. And that makes them ideal candidates in the KiWi-Wiki usecase.

P.S: Yes, we all know that documentation is also a crucial part of the work of developers – yet we also know that the world has seen a lot of software developments that went undocumented;-)

Zemanta Pixie
Jana Herwig

KiWi Joint Work Package Meeting in Prague

So here we go again, the KiWi and me: Today, tomorrow and Friday I am in Prague with my colleagues Andreas Blumauer and Matthias Samwald, attending the first Joint Workpackage Meeting in the EU-funded project KiWi – Knowledge in a Wiki. The present meeting is hosted by Sun Microsystems - Josef Holy and Inka Havlova gave us a very warm welcome, but thankfully the Sun offices are the direct opposite, namely perfectly chilled on this hot June day:-)

The day started with Sebastian Schaffert, project coordinator from Salzburg Research, giving us an overview of the actitivies of the first quarter in the project and a primer on the objectives of the meeting. The overall concern of this full meeting, in order to align core developments of the project early on, is to develop a common understanding of the functionalities and behaviour of the KiWi system, to define a core data model and to develop an outline for the upcoming dissemination plan.

An IT project is like herding cats, they say – in our case, we’ll be herding kiwis, and if we can enjoy it only half as much as these guys, I’ll be fine:-)

The first session is coming up: Peter Axel Nielsen’s report from Work Package 5, i.e. the usecase developed by Logica and Aalborg University. More updates coming up soon!

Zemanta Pixie
Jana Herwig

KIWI Project Partners, Pt.4: Sun

Josef HolyAs soon as KIWI enters the use cases stage, collaboration with business partners is going to gain particular importance. One of these partners is Sun Microsystems – who hardly need an introduction. Yet an interesting new fact that I learned about Sun on Thursday was that they are not only a main contributor to open source software development, but that they are also opensourcing hardware: OpenSPARC is the world’s first free 64-bit micro-processor – the source code for the OpenSPARC T2 chip was released unter GNU GPL and can be downloaded here. Sun is also known for making an authentic web2.0 commitment, building communities within and beyond corporate boundaries: According to Josef Holy (pic on the right), Sun interaction and social network designer, they have literally hundreds of internal wikis, plus a universe of public wikis, public forums and blogs – Jonathan Schwartz is blogging, too.
So Sun has extensive experience with developing community infrastructures, for instance also in association with NetBeans, their integrated development environment, which is used by about 200 Sun developers, thousands of external contributors and hundreds of thousands of active users. The development of NetBeans might also serve as a testbed for KIWI, as the usecase conducted in collaboration with Sun is going to focus on software knowledge management; Josef suggested that KIWI should serve as a structured hub in an unstructured environment. When talking about the ideal user-centred design, he presented an empty slide, pointing out that no preconceived ideas must stand in the way, but that it must reflect real world problems.
Another interesting proposal that might influce KIWI is Sun’s Community Equity Specification – Peter Reiser, Principal Engineer, CTO Office, and Chief Architect for CE2.0 blogged about this recently after the patents were finally filed:

The objective is to build a dynamic Social Value system by calculating the Contribution, Participation, Skills, and Reputation equity a person can gain by actively engaging in online communities. The Equity values are captured through activities that the Community members are participating in.

Also involved in the Sun usecase is the Semantic Web Company (i.e. my employer), and from SWC in particular Andreas Blumauer, Matthias Samwald and Tassilo Pellegrini. Together and with the input of the entire KIWI team they are going to do their best to explore the opportunities of combining bottom-up maintenance (i.e. tagging and folksonomy) with top-down maintenance (i.e. reasoning and ontologies). The Sun team includes Peter Reiser, Josef Holy, Henry Story (semantic web evangelist – I already blogged about him and Josef yesterday) and Inka Havlova who is backing the team with administrative power.